How to Back Up and Restore Torrent Client Settings Before an Upgrade or Device Change
backuprestoreqBittorrentTransmissionDelugeuTorrentconfiguration

How to Back Up and Restore Torrent Client Settings Before an Upgrade or Device Change

BBitTorrent.site Editorial Team
2026-11-18
6 min read

Back up qBittorrent, Transmission, Deluge, or uTorrent settings safely, restore torrent state, and verify paths, permissions, and seeding.

Before upgrading a computer, reinstalling an operating system, or moving a torrent library to new storage, create a complete client backup. This guide explains what to save for qBittorrent, Transmission, Deluge, and uTorrent, where those files commonly live, how to restore them safely, and how to verify that categories, paths, queue rules, completed status, and seeding state survived the move.

Overview

A torrent client stores more than global preferences. Its configuration may include download and upload limits, listening-port choices, category rules, RSS tasks, queue settings, labels, tracker information, and the local state of each torrent. That state tells the client which torrents exist, where their data is located, which pieces are complete, and whether a torrent should be downloading or seeding.

A reliable backup therefore has three parts:

  • Configuration: preferences, categories, queue rules, connection settings, and automation rules.
  • Torrent metadata and session state: torrent files, magnet-related state, resume information, and the client’s record of completed pieces.
  • Path documentation: a simple record of the old and new locations for incomplete downloads, completed data, watch folders, and backup storage.

Paths and filenames vary by operating system, installation method, client version, and whether the client runs as a desktop application or a service. Treat the locations below as common starting points, not universal rules. If a folder is not present, check the client’s documentation, service account, or application data directory before assuming that no data exists.

For the safest backup, stop all active torrents, allow disk activity to finish, exit the client completely, and then copy the relevant folders to a separate drive. Do not rely on a screenshot of settings alone; screenshots cannot restore torrent state or path mappings.

Checklist by scenario

Before a routine client upgrade

  1. Record the current client name and version, operating system, download paths, and any custom service account.
  2. Pause torrents and wait for disk activity to settle.
  3. Exit the client. If it runs as a service or container, stop that service rather than only closing a web interface.
  4. Copy the configuration and session-state folders to dated backup storage.
  5. Keep the backup until the upgraded client has opened successfully and several torrents have passed a data check.

Before replacing a device or reinstalling an operating system

  1. Back up the client data and the torrent data separately. A configuration backup does not contain the downloaded files.
  2. Copy any standalone .torrent files, watch-folder contents, RSS settings, scripts, and custom certificates or credentials that the workflow requires.
  3. Export or write down category-to-path mappings, especially when using separate locations for incomplete and completed data.
  4. Preserve the original folder structure where possible. Matching paths reduces the amount of relinking required after restoration.
  5. Make at least one test restore to a spare directory or secondary machine if the library is important.

Common client locations

ClientWindowsLinuxmacOSWhat to preserve
qBittorrent%APPDATA%\qBittorrent~/.config/qBittorrent~/Library/Application Support/qBittorrentPreferences, categories, RSS rules, and the BT_backup session data when present.
Transmission%APPDATA%\TransmissionUsually ~/.config/transmission; daemon locations can differ~/Library/Application Support/TransmissionSettings, resume data, torrent metadata, and blocklists or watch-folder configuration where used.
Deluge%APPDATA%\deluge~/.config/delugeOften under the user application-support directoryCore configuration, plugins, state files, and any separate daemon configuration.
uTorrentCommonly %APPDATA%\uTorrentNot generally the primary supported desktop setupAvailability and paths depend on the edition and installation methodPreferences, resume data, torrent files, and any RSS or queue configuration.

For qBittorrent, copy the entire application-data folder rather than only the visible preferences file. For Transmission and Deluge, pay particular attention to whether the desktop client and daemon use different accounts or directories. For uTorrent, preserve the folder containing resume data and .torrent files; copying only the executable will not restore the library.

Restoring after the move

  1. Install the same client family first. If possible, begin with the same major version before changing versions.
  2. Launch it once, close it, and identify the newly created application-data directory.
  3. Replace or merge the new directory with the backed-up files while the client is stopped. Keep the newly created directory as a temporary fallback.
  4. Restore downloaded data to the documented paths, or prepare to use the client’s relocate, set-location, or move-data function.
  5. Start the client and confirm that torrents appear before initiating new downloads.
  6. Force a recheck on a small sample first. Once paths and permissions are correct, recheck the remaining library in batches.

What to double-check

Use this verification template after every restore:

  • Paths: Do incomplete, completed, category, watch, and temporary directories point to real folders on the new system?
  • Permissions: Can the client’s user account read existing data, create files, rename items, and delete temporary files?
  • Torrent state: Do completed torrents still show as complete, and do partially downloaded torrents resume without starting over?
  • Seeding: Are completed torrents queued or seeding according to the intended ratio, time, and upload rules?
  • Categories and labels: Are category-specific save paths and queue priorities intact?
  • Connectivity: Are the listening port, proxy or VPN binding, and connection limits still appropriate for the new network?
  • Automation: Do RSS rules, watch folders, scripts, and remote web interfaces still use valid paths and credentials?
  • Private tracker data: If applicable, verify that tracker-specific metadata and account-related settings were not accidentally discarded. Follow each tracker’s rules when moving or re-adding torrents.

A recheck that finds the data successfully is stronger evidence than a list that merely appears in the interface. For broader library maintenance, see this torrent library maintenance checklist. If the client shows tracker errors after restoration, use a repeatable announce and connectivity workflow rather than immediately deleting and re-adding torrents.

Common mistakes

  • Copying files while the client is running: session databases may be changing, producing an incomplete or inconsistent backup.
  • Backing up settings but not metadata: preferences alone do not recreate the torrent list, resume state, or completed-piece information.
  • Changing paths without planning: a new drive letter, mount point, or case-sensitive path can make valid data appear missing.
  • Restoring into the wrong user profile: desktop and daemon installations may run under different accounts, each with separate configuration folders.
  • Re-adding every torrent immediately: this can create duplicates and lose the original resume state. Restore the client database first and recheck before importing anything again.
  • Deleting the old device too soon: keep the original data or a verified backup until downloads, seeding, permissions, and automation have all been tested.
  • Ignoring network changes: a restored client may retain an obsolete interface binding, proxy, VPN setting, or port-forwarding assumption. Review connectivity separately; the relevant setup choices are covered in this port-forwarding guide.

When to revisit

Run this checklist before every major client upgrade, operating-system reinstall, device replacement, storage migration, or change from a desktop client to a daemon or seedbox. Revisit it whenever download paths, VPN interfaces, automation rules, or remote access arrangements change. A practical schedule is to create a dated configuration backup at regular maintenance intervals and review the restore process at least twice a year, even if no migration is planned.

Keep a short migration note with the backup: client and version, operating system, application-data location, data paths, service account, last successful recheck, and the location of the backup copy. After any restore, test one completed torrent, one partial torrent, one category rule, and one seeding rule before declaring the migration complete. This small verification set catches the most expensive errors while the old system or backup is still available.

Related Topics

#backup#restore#qBittorrent#Transmission#Deluge#uTorrent#configuration
B

BitTorrent.site Editorial Team

Technology Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.