Where Does Jellyseerr Store Settings and Requests?
Where Jellyseerr keeps settings.json and its database in Docker, mirroring its Overseerr sibling.
Last updated
Jellyseerr mirrors Overseerr file for file: a config tree mounted at /app/config holding settings.json, a db folder with the SQLite database, and logs. Bare installs use a config folder under the app directory instead.
The migration rule is the same too. Move the whole tree with the app stopped and mount it at the same container path. Copying settings.json alone produces a familiar looking fresh install with no requests, users, or history behind it. The Plex versus Jellyfin choice only changes settings contents.
Where Jellyseerr stores this, by platform
/app/config (Docker volume)
settings.json holds Jellyfin or Plex connections plus Sonarr and Radarr keys; db/jellyseerr.db holds requests. Bind the tree to a host folder. Overseerr restores with the same steps under its own path.
Frequently asked questions
how do i migrate jellyseerr to a new server
Stop the container and copy the whole mapped config folder (settings.json, db/, logs/) to the new host, mounting it at /app/config. API keys and user approvals travel inside. Jellyfin users restore identically to Plex ones; only the settings contents differ.
where is the jellyseerr database
In db/jellyseerr.db inside the config tree. It holds requests, users, and issues. Copy it stopped and keep the whole folder together rather than cherry picking files. A lone database without its settings.json confuses the app on boot.
does jellyseerr need a persistent volume
Yes. Map /app/config to a persistent volume or everything evaporates on recreate. Overseerr follows the identical layout, so one backup habit covers both request managers. The image itself carries no state.
Notice an outdated path? Let us know.