← Directory

qBitrr

qBitrr is a companion automation tool that bridges qBittorrent with the *Arr ecosystem (Radarr, Sonarr, Lidarr, Readarr), monitoring torrent health,…

  • Automation
  • Media Applications
  • Media Servers
  • Tools & Utilities
qBitrr is a companion automation tool that bridges qBittorrent with the *Arr ecosystem (Radarr, Sonarr, Lidarr, Readarr), monitoring torrent health, triggering instant imports, automating quality upgrades, and managing disk space for self-hosted media stacks.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

69/100 Good

Maintained
100last commit 9 days ago
Popular
46191 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 8 days ago

GitHub stars
191
Open issues
0
Last commit
2026-10-06
Latest release
v5.14.6-1
License
MIT
Activity
steady

Checked 6 days ago - source: GitHub (Feramance/Qbitrr)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Fill in qBitrr’s config before starting Enter the WebUI port and access token (the password-like code for the browser screen), the qBittorrent address, port, username, and password, and each Arr app’s URL and API key (the secret code that lets qBitrr control it). If these are missing or wrong, qBitrr can’t reach the WebUI or manage torrents. source
  • Open port 6969 for the WebUI You can open the WebUI at http://localhost:6969/ui. If you want to use it from another device, open that same port on your router or firewall so the connection isn’t blocked. source
  • Keep config and logs in a safe folder When using systemd (the background service manager), keep qBitrr’s config and logs in folders like /opt/qbitrr/config and /opt/qbitrr/logs, and make sure the qbitrr user owns them. If those folders are missing or have the wrong permissions, qBitrr may not start or may forget your settings. source

Fetched 8 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How does qBitrr coordinate request tools with qBittorrent and media managers?

It keeps qBittorrent, Radarr, Sonarr, and your request tools communicating so downloads finish, import, and clean up.

Does qBitrr automate searches and quality upgrades?

It monitors torrent health, triggers instant imports, automates searches, and manages quality upgrades.

Where should I look for qBitrr Docker or database issues?

The troubleshooting section covers common problems, debugging techniques, Docker-specific issues, and database corruption prevention.

Why should I keep a finished qBittorrent torrent seeding?

Seeding the file after a full download improves speed for others and uses few resources.

Answers sourced from feramance.github.io, feramance.github.io, github.com, www.reddit.com

Community

Collected 16 days ago - public community threads