Download Clients

Torrent and Usenet clients that Luminarr uses to download releases. You can configure multiple clients and assign each one a priority — Luminarr uses the highest-priority enabled client that matches the release type.

Supported Clients

Torrent Clients

Three torrent clients are supported. All three support per-client categories and save paths to keep downloads organized.

qBittorrent

Full-featured BitTorrent client with a JSON-RPC API. Recommended for most setups.

Transmission

Lightweight torrent client with a simple RPC interface. Good for low-resource environments.

Deluge

Plugin-based torrent client accessed via its JSON-RPC daemon interface.

Usenet Clients

Two Usenet clients are supported for NZB-based downloads.

SABnzbd

The most widely-used Usenet downloader. Luminarr uses its JSON API to submit NZBs and monitor queue status.

NZBGet

High-performance Usenet downloader with an XML-RPC API. Efficient alternative to SABnzbd.

Configuration

General Settings

These fields apply to every download client type.

Field Description Notes
Name Display name for this client Used in logs and the queue view
Enabled Whether Luminarr will use this client Disabled clients are ignored during grabs
Priority Selection order when multiple clients match Lower number = higher priority
Torrent

qBittorrent

Field Description Example
URL Base URL of the qBittorrent web UI http://localhost:8080
Username Web UI login username admin
Password Web UI login password
Category Tag applied to added torrents luminarr
Save Path Directory where downloads are saved /downloads/movies
Use SSL Connect via HTTPS Enable if your instance uses TLS
Skip TLS Verify Disable certificate validation Only for self-signed certs

Seed ratio and time enforcement: Luminarr can automatically apply per-indexer seed ratio and seed time limits after a torrent is imported. Configure these limits on the indexer, not the download client.

Torrent

Transmission

Field Description Example
URL Base URL of the Transmission RPC endpoint http://localhost:9091
Username RPC authentication username
Password RPC authentication password
Category Label applied to added torrents luminarr
Save Path Download directory override /downloads/movies
Skip TLS Verify Disable certificate validation Only for self-signed certs
Torrent

Deluge

Field Description Example
URL Base URL of the Deluge web UI or daemon http://localhost:8112
Password Deluge web UI password
Category Label applied to added torrents luminarr
Save Path Download directory override /downloads/movies
Skip TLS Verify Disable certificate validation Only for self-signed certs
Usenet

SABnzbd

Field Description Example
URL Base URL of the SABnzbd web interface http://localhost:8080
API Key SABnzbd API key (found in Config → General)
Category SABnzbd category applied to submitted NZBs movies
Save Path Override the default completed download folder /downloads/complete
Skip TLS Verify Disable certificate validation Only for self-signed certs
Usenet

NZBGet

Field Description Example
URL Base URL of the NZBGet web interface http://localhost:6789
Username NZBGet control username nzbget
Password NZBGet control password
Category Category applied to submitted NZBs movies
Save Path Override the default destination directory /downloads/complete
Skip TLS Verify Disable certificate validation Only for self-signed certs
How It Works

Download Handling

Luminarr manages the full lifecycle from grabbing a release to importing the finished file into your library.

  1. 1

    Release selected

    RSS sync or a manual search identifies a release that matches a monitored movie's quality profile. The release is scored and compared against the current file (if any).

  2. 2

    Grab

    The release is sent to the highest-priority enabled download client that matches the release type (torrent or NZB). Luminarr records the grab with the client-assigned ID for tracking.

  3. 3

    Queue polling

    Every 30 seconds Luminarr polls all active download clients for status. Progress is shown in the Queue page in real time via WebSocket.

  4. 4

    Completion detected

    When the client reports a download as complete, Luminarr publishes a download_done event and the importer picks it up.

  5. 5

    Import

    The importer locates the downloaded file, moves or hardlinks it into the configured library path, updates the database, and triggers a media server refresh.

  6. 6

    Seed enforcement (torrents only)

    After a successful import, Luminarr applies the indexer's seed ratio and seed time limits to the torrent in the download client.

Save path matching: The Save Path configured in Luminarr must be accessible from the Luminarr process, not just from inside the download client container. Use the same mount paths or adjust accordingly when running in Docker.