Where Does Siril Store Config and Scripts?
Siril versions its config filename per release across Linux, Windows and Mac, with scripts and working folders configured inside.
Last updated
Siril versions its config filename with each release, so quote with the running version in mind. Linux, Windows and Mac each anchor their own root with override flags available. Scripts split into read-only defaults plus user-defined storage dirs.
Working folders decide success more than any setting. Point Home deliberately since script failures trace to wrong directories. Calibration branches follow convention beneath with process folders for intermediates.
Where Siril stores this, by platform
~/.config/siril/configX.Y.ini
Versioned config ini with scripts and working-dir pointers inside. Override through flags. Legacy single-name configs belong to retired builds.
%LOCALAPPDATA%\siril\configX.Y.ini
Windows twin of the versioned config under LocalAppData. Installed scripts ship read-only per platform with custom dirs configured inside the ini.
~/Library/Application Support/org.free-astro.Siril/siril/configX.Y.ini
Mac twin under the app support tree with signed-bundle scripts read-only. Working folder defaults to Pictures with calibration branches beneath.
Frequently asked questions
How do I back up Siril?
Copy the versioned config ini for the running release plus custom script dirs. Installed default scripts ship read-only per platform, especially inside signed Mac bundles. Working folders hold sequences beneath dated biases and calibration sets.
Where should my Siril working folder be?
Point the Home control at a chosen folder, defaulting to Pictures. Saves and sequences default there while wrong choices break most scripts. Calibration sets branch beneath with intermediates in process folders.
Can I use a custom Siril config?
Pass the override flag with an alternate ini path. Legacy single-name configs belong to retired builds. Versioned filenames are the current contract across all three operating systems.
Notice an outdated path? Let us know.