Configuration¶

Use the WebUI Config editor or the TOML configuration file. Client identity, connection credentials, torrent scope, paths, monitors, seeding, trackers and maintenance are configured per client, with maintenance tools in Manage. Arr instances keep connection settings beside API credentials and TLS options. Global Settings, Web Settings and Authentication have separate dialogs. See editor workflows.

Configuration structure¶

[Settings]
ConsoleLevel = 'INFO'
LoopSleepTimer = 5

[WebUI]
Host = '127.0.0.1'
Port = 6969
AuthDisabled = true

[TorrentClient.local]
Type = 'qbittorrent'
Host = 'localhost'
Port = 8080
UserName = 'admin'
Password = 'replace-me'
DownloadPath = '/downloads'
TorrentScanIntervalSeconds = 30

[Radarr-Movies]
Managed = true
URI = 'http://localhost:7878'
APIKey = 'replace-me'
Category = 'movies'

Clients may use canonical TorrentClient. or legacy qBit/qBit-name sections. Do not define duplicate identities. All clients are peers. Arr sections are named single tables such as [Radarr-Movies], [Sonarr-TV], [Lidarr-Music], or [Readarr-Books], rather than unnamed arrays of instances.

Configuration sections¶

Full file reference: lookup order, fields, environment overrides, data-directory behavior, migration and live application.
Manage configuration and complete controls: explicit roots, shared storage mappings, bounded recovery, recycling and retention.
Seeding and tracker protection: ordinary limits, legacy aliases, mandatory time, deadlines, partial/freeleech obligations and evidence uncertainty.
Arr configuration, torrent handling, search, and quality profiles.
WebUI and authentication.

Storage and migration¶

DownloadPath is client-visible; FreeSpace[].Path is local to Torrentarr; path mappings translate between them. Monitors start empty and new rows disabled. Global storage fields are legacy migration inputs. Ambiguous multi-client migration leaves monitors disabled for review. See current storage reference and disk-space behavior.

Save and validation¶

Partial saves preserve unrelated values, unknown saved fields and redacted secrets. Numeric bounds, narrowing filters and explicit storage mappings are validated. Torrent scan intervals are selected per client from 5, 15, 30, 60, 90, or 120 seconds; Settings.LoopSleepTimer controls periodic Arr catalog refreshes into SQLite. Identity/connection sections open by default; validation opens affected sections. Worker cycles adopt saved revisions at safe boundaries. Use Config status to distinguish saved/pending/applied. Connection replacement failures do not reuse an old endpoint.

Manage saves only maintenance settings. Checking and applying a reviewed preview are separate actions. Manual applies once; Automatic enables future scheduled runs without requiring a restart. Existing schedules survive migration; persistent automatic execution is explicit per operation. Private tracker protection runs independently, and unknown or unmet obligations preserve seeding. Recovery preserves unresolved failures unless an explicitly configured recycling outcome passes confirmed-repair, continuous-failure, ownership, and protection checks.

Configuration file location¶

TORRENTARR_CONFIG wins, followed by working-directory .config/config.toml, ~/config/config.toml, ~/.config/qbitrr/config.toml, ~/.config/torrentarr/config.toml, and ./config.toml. The first existing file wins. Data/logs normally sit beside the resolved config; Docker's /config layout uses /config as its data directory.

Backup and troubleshooting¶

Back up config and SQLite together. Keep secrets out of version control and screenshots. Use single-quoted TOML literal strings for regex/backslash patterns. Do not delete a rename recovery journal after interruption. Only one Host may own a data directory. See quick start, path mappings, and common issues.