Where Does NINA Store Profiles and Plugins?
NINA keeps profiles, versioned plugins and logs under AppData Local NINA on Windows. Imaging output folders are user-chosen.
Last updated
NINA centralizes everything configurable under one Local AppData root. Profiles, plugins with versioned subfolders, and logs branch from there. The design rewards a single backup of the NINA tree minus output.
Imaging destinations break the pattern on purpose. Targets, sequences and atlas directories point wherever the user aimed them, so no default path exists to document. Guesses involving Documents are wrong. Windows-only throughout, with AppData hidden by default.
Where NINA stores this, by platform
%LOCALAPPDATA%\NINA\Profiles
Profile files for equipment and sequences. Copy the folder to migrate rigs. Versioned plugin subfolders and logs branch from the same NINA root.
%LOCALAPPDATA%\NINA\Plugins
Plugin tree with per-version subfolders since the 3.0 layout plus the logs folder beside it. Reach logs through Options General in-app, then up one level. Output folders stay user-chosen elsewhere.
Frequently asked questions
How do I migrate NINA profiles?
Copy %LOCALAPPDATA%\NINA\Profiles with its profile files to the new machine. Plugins reinstall per version under the versioned Plugins tree rather than transferring. Logs stay behind unless an old fault needs review.
Where are NINA log files?
Open Options, General, follow the log level link, then go up one level to the logs folder. That navigation is the documented route users confirm. Sequence targets and Sky Atlas directories configure separately under Imaging options.
Where does NINA save my images?
There is none to copy. Output, sequence and atlas directories are user-configurable with no fixed default anywhere. Documents NINA guesses found online are wrong. Set them deliberately in Options instead of hunting the disk.
Notice an outdated path? Let us know.