qBit Manage
This is a program used to manage your qBittorrent instance such as:
- Tag torrents based on tracker URLs
- Apply category based on
save_pathto uncategorized torrents in category'ssave_path - Change categories based on current category (
cat_change) - Remove unregistered torrents (delete data & torrent if it is not being cross-seeded, otherwise it will just remove the torrent)
- Recheck paused torrents sorted by lowest size and resume if completed
- Remove orphaned files from your root directory that are not referenced by qBittorrent
- Tag any torrents that have no hard links outside the root folder (for multi-file torrents the largest file is used)
- Apply share limits based on groups filtered by tags/categories and allows optional cleanup to delete these torrents and contents based on maximum ratio and/or time seeded. Additionally allows for a minimum seed time to ensure tracker rules are respected and minimum number of seeders to keep torrents alive.
- RecycleBin function to move files into a RecycleBin folder instead of deleting the data directly when deleting a torrent
- Built-in scheduler to run the script every x minutes. (Can use
--runcommand to run without the scheduler) - Webhook notifications with Notifiarr and Apprise API integration
Supported qBittorrent Versions
We rely on qbittorrent-api to interact with qBittorrent.
Generally expect new releases of qBittorrent to not immediately be supported. Support CANNOT be added until qbittorrent-api adds support for the version. Any material changed and impact must then be assessed prior to Qbit Manage supporting it.
Version bumps are automated — no issue or PR needed. Renovate watches
qbittorrent-api on PyPI and always auto-merges its updates (major, minor, patch — see .github/renovate.json) as
soon as a new release is 3+ days old. Merging that bump changes pyproject.toml, which triggers CI
(update-supported-versions.yml) to refresh SUPPORTED_VERSIONS.json and the badges below — the whole chain runs
without a human touching it. Issues asking us to "add support for qBittorrent vX.Y" will be auto-closed and point
back here; if qbit_manage still doesn't work on a version already shown as supported below, that's a real bug —
please file one.
Master
Develop
Getting Started
Check out the wiki for installation help
- Install qbit_manage either by installing Python 3.10+ on the localhost and following the Local Installation Guide or by installing Docker and following the Docker Installation Guide or the unRAID Installation Guide.
- Once installed, you have to set up your Configuration by create a Configuration File filled with all your values to connect to your qBittorrent instance.
- Please refer to the list of Commands that can be used with this tool.
Usage
To run the script in an interactive terminal with a list of possible commands run:
python qbit_manage.py -h
Support
- If you have any questions or require support please join the Notifiarr Discord and post your question under the
qbit-managechannel. - If you're getting an Error or have an Enhancement post in the Issues.
- If you have a configuration question post in the Discussions.
- Pull Request are welcome but please submit them to the develop branch.
Metadata
Release files for qbit-manage 4.13.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| qbit_manage-4.13.0.tar.gz | 757.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qbit_manage-4.13.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 MB
Release files / qbit_manage-4.13.0.tar.gz
| Download URL | qbit_manage-4.13.0.tar.gz |
|---|---|
| Size | 757.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7821b50e1cc46cd1c8775931bad1f82d9c47a82e6855dd9f244c06017b6181ab
|
|
BLAKE2b-256 checksum How to use checksums |
b89dc71aee09c0c29f6cccf569ff0637a3746378a0bd0def3770fc0b88dd0402
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 4, 2026.
Transparency logRelease files / qbit_manage-4.13.0-py3-none-any.whl
| Download URL | qbit_manage-4.13.0-py3-none-any.whl |
|---|---|
| Size | 800.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6c5ff6a743396d652a117aed89fce8f24d44414f60a72cc5c5999087e0dfe15e
|
|
BLAKE2b-256 checksum How to use checksums |
813231c73f45f7612427e14f337485972a95b46e1f2ed86c075d813be9da1866
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 4, 2026.
Transparency log