qbtmud is a drop-in replacement for qBittorrent's default WebUI. It keeps qBittorrent's Web API semantics and everyday workflows, while adding a more polished application experience around setup, customisation, browser integration, and diagnostics.
- Modern, touch-friendly UI that works comfortably on desktop, tablet, and phone instead of feeling like a desktop page squeezed onto a smaller screen.
- qBittorrent workflow coverage in a cleaner interface, preserving the core behaviours people expect while making everyday navigation and control less clunky.
- Built-in theme system with bundled themes, editable local themes, previews, and repository support for a more customisable look than the default WebUI.
- Guided first-run setup for language, appearance, notifications, and app behaviour so new and returning users can get configured quickly.
- Installable app experience with PWA-aware prompts, browser-specific install guidance, and magnet-handler registration to make the WebUI behave more like a real app.
- Browser notifications with per-event controls so you can decide exactly which torrent events should interrupt you.
- Persistent UI personalisation including remembered layout and table preferences, so the interface stays the way you set it up.
- Dedicated qbtmud app settings and built-in update checks for qbtmud-specific behaviour that does not belong in qBittorrent's own settings surface.
- Prebuilt Docker image with qBittorrent and the international qbtmud UI already installed and enabled, persistent configuration/downloads, and tested updates to the LinuxServer base.
qbtmud is intended to cover the same day-to-day workflows as the default qBittorrent WebUI, including:
- Torrent management: add, remove, start, stop, queue, force-start, rename, relocate, and inspect torrents.
- Torrent details: general stats, trackers, peers, HTTP sources, and content or file priority management.
- Transfer controls: global and per-torrent limits, sequential download, first and last piece priority, and super seeding.
- Organisation: categories, tags, tracker filtering, search, RSS, logs, blocks, and torrent creation tools.
- Client configuration: qBittorrent preferences, bandwidth scheduling, IP filtering, IPv6 support, and related WebUI options.
For a detailed explanation of qBittorrent's underlying options, refer to the qBittorrent Options Guide.
Use ghcr.io/lantean-code/qbtmud:latest to run qBittorrent with qbtmud already enabled. Images are available for amd64 and arm64, with no release archive or manual alternative WebUI configuration needed.
Follow the Docker installation guide for a ready-to-use Compose file, first login, storage/port settings, updates and migration from a compatible LinuxServer container. Available versions are listed on the GHCR package page.
- Download the latest archive from the qbtmud Releases page.
- Extract the archive and locate the directory that contains the
publicsubdirectory. - In qBittorrent, go to
Tools>Options>Web UI. - Enable Use alternative WebUI.
- Set Root Folder to the extracted directory that contains
public. - Save the settings and open your qBittorrent WebUI address, such as
http://localhost:8080.
For more detail on qBittorrent's alternative WebUI mechanism, refer to the Alternate WebUI Usage Guide.
Choose an installation method or explore advanced hosting setups:
- Docs index
- Installation
- Docker installation
- Advanced setup
- Build from source
- Reverse proxy hosting
- Separate API and UI hosting
Main torrent dashboard.
Torrent details view covering the same core inspection workflows as the default WebUI.
First-run setup flow for language, theme, notifications, and storage preferences.
Built-in theme manager with bundled themes, previews, and editing workflows.
App-specific visual settings for theme mode and theme repository configuration.
If you want to help build qbtmud:
- read CONTRIBUTING.md for the issue, discussion, and pull request model
- read SUPPORT.md for the support and troubleshooting routing model
- use GitHub Issues for actionable bugs, scoped feature proposals, UX improvements, performance regressions, and documentation gaps
- use GitHub Discussions Ideas for early-stage ideas
- use GitHub Discussions Show and tell for themes, screenshots, integrations, and community showcases