Where Does Decluttarr Store Its Config?
Decluttarr reads config.yaml mounted at /app/config. That file plus compose env is the whole setup to back up.
Last updated
Decluttarr configures through config.yaml, mounted into the container at /app/config/config.yaml. That file holds every *arr URL and API key plus queue rules, stalled thresholds, and removal options. A compose-only mode exists too, where the same values arrive as environment variables instead of a file.
The app keeps no database of its own. Decisions come from live *arr queues each cycle, and logs go to stdout plus an optional log file. Backups therefore mean one file (or one compose file). Protect the API keys inside it: anyone holding config.yaml can manage your Sonarr, Radarr, and download clients.
Where Decluttarr stores this, by platform
/app/config/config.yaml (Docker mount)
*arr URLs, API keys, queue rules, and removal thresholds. Mount the file at /app/config/config.yaml. Compose env vars work instead, but the file is easier to version and review.
Frequently asked questions
how do i migrate decluttarr to a new server
Copy config.yaml (or your compose file if env-only) to the new host and mount it at the same container path. No database travels with it: queue state lives in the *arr apps, so the config file is the complete backup.
why did decluttarr stop reading my config after updating
V2 moved to config.yaml with breaking changes from V1 in late 2025. Old config.conf style files no longer load. Regenerate from config_example.yaml and re-enter your *arr URLs and keys.
Notice an outdated path? Let us know.