Where Does Fragments Save Torrents?
Fragments downloads to home Downloads and leans on Transmission storage. App prefs live in dconf under its schema.
Last updated
Fragments is a thin GNOME shell over Transmission. Finished downloads default to the home Downloads folder. Session state (torrents, resume, blocklists) follows Transmission config conventions under the user profile, with Flatpak builds namespaced instead.
Its own preferences are minimal and live in dconf under the app schema. Remote control mode talks to a Transmission daemon elsewhere, in which case the data folders that matter sit on the remote box, not the local one. Port sharing setup can delay first launch on some networks.
Where Fragments stores this, by platform
/home/<username>/Downloads
Default finished download target. Change it in preferences. Remote sessions write to the daemon host instead.
/home/<username>/.config/transmission/torrents
Transmission layer session files when running the native build. Holds torrents and resume state Fragments displays.
dconf database: /de/haeckerfelix/Fragments
Fragments own preferences in dconf. Inspect with dconf-editor. Session content itself stays with Transmission.
Frequently asked questions
How do I change the Fragments download folder?
Point Fragments at the folder in its preferences. Completed files land there, with resume data held by the Transmission layer underneath.
How do I move Fragments to a new machine?
Copy the config folders plus the dconf settings to the new machine. Re add the same torrents and point at existing data to recheck instead of redownloading.
Notice an outdated path? Let us know.