Where Does Tdarr Store Config and Its Database?
Tdarr keeps server data, configs and the MongoDB database under its data directory, separate from your media libraries.
Last updated
Tdarr splits state from media by design. Libraries stay where they always were, while everything Tdarr knows lands in its own data tree: configs, caches, transcode working space and the database.
Docker installs map that tree to a volume you chose, so your paths follow your compose file rather than any default. The database plus configs form the backup set. Media needs no backup from Tdarr's side since it never modifies originals in place.
Where Tdarr stores this, by platform
/app/server
Server data inside the container, mapped to your chosen host volume. Configs sit in /app/configs beside it. Back up both plus the MongoDB data volume together, since libraries reference database records.
%APPDATA%\Tdarr
Native Windows installs keep server data and configs here instead of container paths. Transcode cache inside can grow large; clear it from the UI rather than deleting folders mid job.
Frequently asked questions
how do i back up tdarr
Copy the server data and configs directories plus the MongoDB volume with the stack stopped. Media libraries need no copying since Tdarr tracks them by path in the database.
why is tdarr using so much disk space
The transcode cache holds working copies of in progress files. Let queues finish, then clear cache from settings. Stale worker data from crashed jobs is the usual culprit.
Notice an outdated path? Let us know.