qBit Manage

Open-source torrent housekeeping, honestly reviewed. What you actually get when you run this alongside qBittorrent.

TL;DR

• What it is: A Python-based automation daemon that handles the housekeeping qBittorrent won’t do for you — tagging, categorizing, removing dead torrents, enforcing share limits, and cleaning up orphaned files [README].
• Who it’s for: Self-hosters running qBittorrent at any serious volume who are tired of doing manual cleanup, or whose arr-stack (Sonarr, Radarr, etc.) leaves tag and category chaos behind [README].
• Cost: $0. MIT licensed. Runs as a Docker container or a Python process. Your only cost is the VPS or home server you’re already running qBittorrent on [README][GitHub].
• Key strength: It handles the entire lifecycle of a torrent — from auto-tagging on arrival, to enforcing ratio rules, to safely deleting completed and unregistered torrents — automatically, on a schedule you define [README].
• Key weakness: No third-party benchmarks or user reviews were available in the scraped sources for this article. The GitHub issue tracker and Notifiarr Discord are the closest thing to a community feedback record. Configuration requires working through a YAML file and understanding your own qBittorrent setup — there’s no wizard [README].

---

What is qBit Manage

qBit Manage is a Python script — packaged as a Docker image and available on PyPI — that connects to your qBittorrent instance via its Web API and performs a set of automated management tasks on a schedule [README]. The project describes itself plainly: “This tool will help manage tedious tasks in qBittorrent and automate them.” [GitHub].

If you’ve ever managed a qBittorrent instance at any volume — hundreds of torrents, multiple trackers, shared with an arr-stack — you know the pile of problems it creates: torrents tagged wrong or not at all, completed files sitting in the wrong category folder, dead torrents from defunct trackers eating disk space, orphaned files accumulating in your download directory with no corresponding torrent. qBit Manage exists to solve exactly that class of problem [README].

The project sits at 1,451 GitHub stars with 76 forks and 47 contributors [GitHub]. That’s a modest number for a self-hosted tool, which makes sense — qBit Manage is genuinely niche. It solves a specific problem for a specific audience, and it doesn’t try to be more than that. The repository has seen 1,000+ commits and 80 releases, which suggests consistent maintenance rather than an abandoned side project [GitHub].

The tool is built and maintained by the StuffAnThings GitHub organization, with primary development from bobokun who also maintains the Docker image on Docker Hub [README][GitHub]. Support runs through the Notifiarr Discord under a #qbit-manage channel — not a standalone forum or GitHub Discussions, which means you need to be comfortable asking questions in someone else’s community [README].

---

Why People Choose It

No independent reviews of qBit Manage were available in the sources scraped for this article. What follows is drawn from the README, the GitHub repository, and the tool’s design decisions — which together tell a clear story about the problem it’s solving.

The core appeal is automation of work that never ends. Every active qBittorrent instance needs recurring maintenance: expired tracker registrations leave dead torrents, completed seeding torrents hit ratio limits and need cleanup, files get downloaded and never added to qBittorrent leaving orphans on disk, and cross-seeded torrents need careful handling to avoid losing data. Doing this manually once a week is a 30-minute chore. Having it run every hour automatically is a different category of experience [README].

The second appeal is safety features that raw qBittorrent automation lacks. The RecycleBin function — which moves data to a recycle folder instead of deleting it — is the kind of thing you don’t appreciate until you’ve fat-fingered a cleanup and lost 200GB you wanted [README]. The cross-seed awareness in the “remove unregistered torrents” function is similarly careful: it only deletes data if the torrent isn’t being cross-seeded; otherwise it removes the torrent entry but leaves the files intact [README].

The third appeal is share limit enforcement at a granularity qBittorrent itself doesn’t support. You can define groups based on tag and category combinations and apply different ratio targets, minimum seed times, and minimum seeder counts to each group — matching tracker rules without remembering to check them manually [README].

---

Features

Based on the README, here’s what qBit Manage actually does:

Tagging:

• Auto-tag torrents based on tracker URLs [README]
• Tag torrents with no hard links outside the root folder (useful for identifying data you can safely delete when seeding is done) [README]

Categorization:

• Apply the correct category to uncategorized torrents based on their save_path [README]
• Change categories based on the current category via cat_change rules [README]

Cleanup:

• Remove unregistered torrents — deletes data + torrent if not cross-seeded; removes only the torrent entry if cross-seeded [README]
• Remove orphaned files from your root download directory that have no corresponding qBittorrent entry [README]
• RecycleBin mode: moves files to a RecycleBin folder instead of deleting directly [README]

Share limits:

• Apply ratio targets, minimum seed times, and minimum seeder counts per group (filtered by tag/category combination) [README]
• Optional auto-cleanup: delete torrent and data when limits are met [README]

Recovery:

• Recheck paused torrents sorted by smallest size first, and resume if the recheck passes [README]

Scheduling and notifications:

• Built-in scheduler: run every X minutes without an external cron [README]
• --run flag for one-shot execution [README]
• Webhook notifications via Notifiarr and Apprise API [README]

Deployment options:

• Docker image (bobokun/qbit_manage on Docker Hub, also on ghcr.io) [README]
• PyPI package (pip install qbit-manage) [README]
• Local Python installation (3.9.0+ required) [README]

Interfaces:

• The repository includes a web-ui directory and a desktop/tauri directory, suggesting a GUI is either in development or available — the README doesn’t document this prominently, so treat it as experimental [GitHub].

---

Pricing: SaaS vs Self-Hosted Math

There is no SaaS version of qBit Manage and no commercial tier. The tool is MIT licensed and free in every sense [README].

The relevant cost comparison isn’t “qBit Manage vs a paid alternative” — it doesn’t have one. The comparison is “qBit Manage vs your time.”

If you’re manually auditing your qBittorrent instance once a week — checking for dead trackers, cleaning orphans, enforcing ratios, fixing categories — and that takes 20 minutes, that’s 17 hours per year. At any reasonable value of your time, automating it with a tool that takes 2–4 hours to configure once is an obvious trade [README].

Running cost:

• qBit Manage software: $0 (MIT) [README]
• Docker image: $0 [README]
• Compute: runs on the same machine as qBittorrent — no additional VPS required if you’re already self-hosting

The only cost is configuration time. The wiki covers local installation, Docker installation, and unRAID installation — it’s not a one-liner, but it’s documented [README].

---

Deployment Reality Check

qBit Manage connects to qBittorrent via its Web API, which means the setup assumes you already have a running qBittorrent instance with the Web UI enabled [README].

Installation paths:

• Docker (recommended): pull bobokun/qbit_manage, mount your config file, run. Standard Docker Compose workflow [README].
• PyPI: pip install qbit-manage on Python 3.9.0+ [README].
• unRAID: dedicated installation guide in the wiki [README].

Configuration: The tool is driven by a YAML configuration file. You define your tracker tags, category paths, share limit groups, and cleanup rules there. The wiki covers the structure, but there’s no interactive setup — you’re editing YAML directly [README].

This is the realistic friction point. Someone comfortable with Docker and YAML will be running in an hour. Someone who isn’t will struggle — not because the tool is poorly documented, but because it assumes you know your qBittorrent setup (your save paths, your tracker URLs, your cross-seed situation) before you start configuring it.

What can go wrong:

• qBittorrent version support lags new releases. The README explicitly states: “Generally expect new releases of Qbittorrent to not immediately be supported. Support CANNOT be added until qbittorrent-api adds support for the version.” [README]. If you run bleeding-edge qBittorrent, check SUPPORTED_VERSIONS.json before upgrading.
• The “remove unregistered torrents” feature is the most dangerous one to configure wrong. The cross-seed awareness helps, but misconfiguring what counts as unregistered can delete data you wanted [README]. Test with dry-run mode first.
• The RecycleBin feature is only useful if your disk has headroom. If you’re running tight on space, a RecycleBin that fills up silently is worse than direct deletion.

Support: The Notifiarr Discord #qbit-manage channel is the primary support venue [README]. GitHub Issues for bugs, GitHub Discussions for configuration questions [README]. There’s no paid support tier and no SLA.

---

Pros and Cons

Pros

• MIT licensed, genuinely free. No tier gates, no feature paywall, no “community vs pro” split [README].
• Covers the full torrent lifecycle. Tagging on arrival, category assignment, ratio enforcement, cleanup on completion, orphan removal — it’s one tool for the whole flow [README].
• Cross-seed awareness. The unregistered torrent removal checks for cross-seeding before deleting data. This is the kind of edge case that would ruin your week if it weren’t handled [README].
• RecycleBin safety net. Files go to a recycle folder before permanent deletion. Recoverable if you catch the mistake [README].
• Built-in scheduler. No need to set up a cron job externally — configure the interval in the YAML and the daemon handles it [README].
• Multiple notification channels. Notifiarr and Apprise cover most self-hosters’ existing notification setups [README].
• Active maintenance. 1,000+ commits, 80 releases, consistent update cadence [GitHub].
• Multiple install paths. Docker, PyPI, local Python, unRAID — covers the common self-host environments [README].

Cons

• YAML-first configuration. There’s no guided setup. You need to understand your qBittorrent paths and tracker structure before you can configure the tool correctly [README].
• qBittorrent version lag. You cannot immediately use new qBittorrent releases — you’re gated by qbittorrent-api library support, then by qBit Manage’s own assessment of changes [README].
• No independent reviews available. The scraped sources for this article contained zero reviews of qBit Manage. Community experience beyond the GitHub issue tracker and Discord is not captured here.
• Web UI status unclear. The repository contains web-ui and Tauri desktop directories, but the README doesn’t document a stable UI — it may be experimental or unreleased [GitHub].
• Niche tool, small community. 1,451 stars and 47 contributors is small. If development stops, you’re maintaining your own fork [GitHub].
• Dangerous features require careful config. Orphan removal and unregistered torrent deletion can cause data loss if misconfigured. The cross-seed protection helps, but it’s not foolproof [README].

---

Who Should Use This / Who Shouldn’t

Use qBit Manage if:

• You run qBittorrent at any meaningful volume (50+ active torrents) and spend time on manual housekeeping.
• You use an arr-stack (Sonarr, Radarr, Lidarr) and want categories and tags to stay clean automatically.
• You cross-seed and need deletion logic that respects that.
• You’re comfortable editing YAML and running Docker.
• You want ratio enforcement per tracker type, not one global setting.

Skip it if:

• You manage fewer than a handful of torrents and manual cleanup is occasional.
• You’re not comfortable with YAML configuration and don’t have someone to set it up for you.
• You’re running the latest qBittorrent release and can’t wait for version support to catch up.
• You want a polished GUI with guided configuration — this is a config-file-driven daemon, not a desktop app.

---

Alternatives Worth Considering

For the specific problems qBit Manage solves, the landscape is thin:

• Manual qBittorrent management — the baseline. Works, doesn’t scale, wastes time.
• autobrr — focuses on the arrival side (automated download from RSS/IRC/announce) rather than lifecycle management. Complementary rather than competing.
• cross-seed — handles cross-seeding specifically. Overlaps with qBit Manage’s cross-seed awareness but dedicated to that problem. Often run alongside qBit Manage rather than instead of it.
• Sonarr/Radarr/etc. — manage the category and completion side of media torrents within their own import workflows. They don’t handle orphan cleanup, tagging by tracker, or ratio enforcement.
• Custom scripts — the DIY alternative. Full control, no dependency on an upstream project, but you maintain it yourself. qBit Manage’s main value over a custom script is that the edge cases (cross-seed handling, RecycleBin, version compatibility) are already solved.

There’s no direct commercial alternative. qBit Manage occupies a niche that SaaS tools don’t touch — it’s a utility for people already running self-hosted infrastructure, which by definition isn’t the target market for hosted products.

---

Bottom Line

qBit Manage is a well-scoped utility that does exactly what it says. If you run qBittorrent seriously — multiple trackers, an arr-stack, cross-seeding, any meaningful volume — it replaces a recurring manual chore with a scheduled daemon that handles the whole lifecycle correctly, including the edge cases that would bite you with a naive cleanup script. The configuration asks you to know your own setup before you start, and the qBittorrent version lag is a real consideration if you upgrade aggressively. But for anyone running a mature self-hosted media or seeding setup, the one-time configuration cost pays back quickly.

If the setup is the blocker, that’s the kind of thing upready.dev handles for clients — one-time deployment, running and configured, you own it from there.

---

Sources

Primary sources (all claims):

• GitHub repository and README — https://github.com/StuffAnThings/qbit_manage (1,451 stars, 76 forks, 47 contributors, MIT license, 80 releases)
• GitHub repository file structure and metadata — https://github.com/StuffAnThings/qbit_manage (web-ui, desktop/tauri directories, SUPPORTED_VERSIONS.json, CHANGELOG)
• Docker Hub image — https://hub.docker.com/r/bobokun/qbit_manage
• PyPI package — https://pypi.org/project/qbit-manage
• Notifiarr Discord — referenced in README as primary support channel

Note: The third-party review sources scraped for this article (sources [1]–[5]) were unrelated to qBit Manage and are not cited. Independent user reviews of this tool were not available in the research corpus. Community feedback can be found in the GitHub Issues and Discussions, and in the Notifiarr Discord #qbit-manage channel.