Where Does Deluge Store Config and Torrent State?
Deluge keeps settings, torrent state and resume data in one config folder. Windows and Linux paths plus the daemon user trap.
Last updated
Deluge follows the daemon pattern: one config folder holding JSON settings, a state subfolder with .torrent files and resume data, and plugins beside them. On a normal desktop that folder sits in the standard per-user config location for the OS. Everything portable about your setup lives there except the downloaded files themselves.
The trap is the daemon user. When deluged runs as a system service it reads the config of its own service account, not yours, so hand edits to your home folder change nothing. Configure through a connected client instead, or edit the files under the daemon account's home. Always stop the daemon before copying state by hand.
Where Deluge stores this, by platform
%APPDATA%\deluge
core.conf and the state subfolder live here. If deluged runs as a service, it uses the service account's folder instead of yours; check which user the service runs as before editing. Stop Deluge before copying state files by hand.
~/.config/deluge
JSON configs at the top level, .torrent files and resume data in state/. Systemd user units often run deluged as a dedicated deluge user rooted at /srv/deluge, whose config is /srv/deluge/.config/deluge. The -c flag sets a custom config directory for either side.
Frequently asked questions
how do i move deluge torrents to a new computer
Copy the state subfolder to the same config location on the new machine while Deluge is stopped on both ends, then recheck paths for downloaded data. The .torrent files and resume data move; the downloaded files themselves must be copied separately and pointed at the same paths.
why did all my deluge torrents disappear after a crash
The state file likely corrupted on the unclean shutdown, a long standing Deluge quirk. Stop the daemon, look in the state folder for the automatic .bak backup, restore it over the live state file, and start again paused. Pausing everything for a few minutes before shutdowns avoids a repeat.
why do deluge config edits do nothing
You are editing the wrong user's files. The daemon running as a service uses its own account (often a dedicated deluge user rooted at /srv/deluge), not your login's ~/.config/deluge. Either configure through a connected client or edit the config under the daemon user's home.
Notice an outdated path? Let us know.