Skip to content

Storage

Storage settings define where AstroManager should expect local image data to live and how files should be organized after import, review, calibration, or processing.

Why Storage Exists

AstroManager can now work with both local capture libraries and cloud-backed capture storage. Storage settings provide the local foundation for import, review, grading, missing-path recovery, local calibration, and storage-structure cleanup.

They are most relevant when you want to:

  • keep image locations organized
  • import existing capture libraries
  • inspect and grade imported images
  • keep local originals, rejected files, calibration files, and processed outputs organized
  • make image review, exports, and later processing easier

When It Matters Most

If your current focus is target planning and N.I.N.A. integration, you can usually keep storage simple at first.

It becomes more important once you want AstroManager to be more involved in the captured-image side of the workflow, especially when you use Image Import, the Image Library, or Cloud Service.

Storage Entries

A storage entry describes one local image root.

The important fields are:

  • Base path: the main folder AstroManager should treat as the storage root
  • Not imported path: where files can be moved when they should stay on disk but not enter the active library
  • Calibration files path: where local calibration frames and masters live
  • Path structure: the folder pattern AstroManager can use when moving files into an organized layout

The storage list includes a Re-sync images action. It opens the Image Library with that storage root selected so missing local paths can be reconnected or moved into the configured structure.