Version 1 (modified by charles, 13 years ago) (diff)



On OS X, Transmission's configuration files are stored in $HOME/Library/Application Support/Transmission/.

On other platforms, they're stored in $HOME/.config/transmission/.

Both of these can be overridden by setting the TRANSMISSION_HOME environmental variable.

transmission-daemon stores its files in a sibling folder to transmission's, named transmission-daemon.


The configuration folder typically has the following files:


This is a json-encoded file that holds all the client's settings and preferences. It's currently only used by the daemon and GTK+ clients. json was chosen because it's mostly human-readable and -writable, but also allows data hierarchies to be stored.


This is a json-encoded file that holds session statistics such as running upload and download byte counts.


This subfolder holds the .torrent files that have been added to Transmission. The files in this folder are named with a combination of the torrent's name (to make it human-readable) and a portion of the torrent's SHA1 hash (to avoid filename collisions from similarly-named torrents).


This subfolder holds .resume files that hold information about a particular torrent, such as which parts have been downloaded, the folder the downloaded data was stored in, and so on. These follow an identical naming scheme to the files in the torrents subfolder.


This subfolder holds bluetack-formatted blocklists. Files ending in ".bin" are generated by Transmission as

it parses a bluetack file and stores it into a binary format for faster lookups. On startup, Transmission will try to parse any non-".bin" file and generate a new blocklist from it, so you can have multiple blocklists just by copying new bluetack files into this location.

Legacy Versions of Transmission

Older, pre-[XDG versions of transmission-gtk and transmission-daemon stored their settings in $HOME/.transmission. Newer releases try to automatically migrate these files to $HOME/.config/transmission/.