Where Does SABnzbd Store Config and Queue Data?
Where SABnzbd keeps sabnzbd.ini, the queue database, and logs on Windows, Linux, macOS, and Docker.
Last updated
SABnzbd separates its program from its data. Settings live in sabnzbd.ini, while the queue, history database, and logs sit in a data directory next to it. On Windows that is %LOCALAPPDATA%\sabnzbd, on Linux ~/.sabnzbd.
The reliable way to confirm either path is inside the app itself. Config > Folders prints the directories SABnzbd is actually using, which matters because the -f flag and Docker mounts move them without warning. Container installs keep the same files under /config instead.
Where SABnzbd stores this, by platform
%LOCALAPPDATA%\sabnzbd
sabnzbd.ini plus the admin/ subfolder (queue and history databases) and logs/ live here. Installed as a service it may run as SYSTEM with the same path. Stop the service before copying the admin folder.
~/.sabnzbd
sabnzbd.ini at the root with admin/ and logs/ beside it. Distro packages running a sabnzbd user may use /var/lib/sabnzbd or ~/.config/sabnzbd instead, so confirm under Config > Folders. Docker images relocate everything under /config.
~/Library/Application Support/SABnzbd
Under ~/Library/Application Support/SABnzbd with sabnzbd.ini at its root. The macOS app and a manual Python launch share it, so settings carry over when you switch launch methods.
Frequently asked questions
where is the sabnzbd data folder
In the data directory: %LOCALAPPDATA%\sabnzbd on Windows, ~/.sabnzbd on Linux. It holds the queue database, history, and logs. The sabnzbd.ini beside it holds paths and ports. Back up both together with the service stopped.
can i run two sabnzbd instances
Yes, with the -f flag pointing at a second ini file and a different port in each. Keep the data directories strictly separate or the two instances fight over the same queue database.
how do i find the live sabnzbd paths
Open the running SABnzbd and check Config > Folders and Config > General. Those pages print the live directories, which beat any documented default when the install was customized or runs in Docker.
Notice an outdated path? Let us know.