QBitWebUI

A modern, lightweight web dashboard for self-hosters to manage one or more qBittorrent instances, with multi-instance controls and a mobile-friendly UI.

  • Downloaders
  • Tools & Utilities
A modern, lightweight web dashboard for self-hosters to manage one or more qBittorrent instances, with multi-instance controls and a mobile-friendly UI.

Platform availability

Available on 1 of 10 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)
  • Any server (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.

64/100 Good

Maintained
78last commit 41 days ago
Popular
56602 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
83no serious findings, 2 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
602
Open issues
1
Last commit
2026-10-11
Latest release
v2.45.0
License
MIT
Activity
stale

Checked 3 days ago - source: GitHub (Maciejonos/qbitwebui)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install Docker and set the key Make sure Docker is installed and running, then replace the ENCRYPTION_KEY value (the secret key the app uses to protect stored data) with a long random key before starting qBitWebUI. Without Docker the container cannot start, and without a good key the app may not work properly or your data may not be protected. source
  • Open port 3000 for the web UI Port 3000 is the address you use to open qBitWebUI in a browser after it starts. If that port is blocked, the app may be running but you cannot reach the interface. source
  • Keep the data folder safe The local ./data folder is mounted into /data and is where the app keeps its settings and data. If you delete it or do not back it up, you can lose your configuration and have to set everything up again. source
  • Use a long random encryption key Replace the ENCRYPTION_KEY value with a long random key before starting qBitWebUI; this key protects stored data. source
  • Docker deployment Use the project's Docker examples in the README to create a working QBitWebUI container configuration. source

Fetched 4 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which Docker environment variables control authentication and registration?

Set ENCRYPTION_KEY to a value generated with openssl rand -hex 32. Use DISABLE_AUTH=true for single-user mode without login, and DISABLE_REGISTRATION=true to create a default admin account.

Which Docker port and persistent volume should I expose?

Map host port 3000 to container port 3000 and mount a persistent directory to /data.

How do I enable the file browser for downloaded files?

Set DOWNLOADS_PATH=/downloads and mount your downloads directory to /downloads. A read-only mount allows browse and download only, while a read-write mount enables delete, move, copy, and rename.

How do I allow self-signed HTTPS certificates?

Set the ALLOW_SELF_SIGNED_CERTS environment variable to true in the Docker configuration.

Is the built-in Cross Seed feature stable?

The README lists Cross Seed as an automatic cross-seeding feature, but it is marked as experimental.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads