qBittorrent

Open-source BitTorrent client, honestly reviewed. No marketing copy, just what you get when you run it.

TL;DR

• What it is: Free, open-source BitTorrent client built in C++/Qt — the most popular open-source µTorrent replacement, with 36,032 GitHub stars [merged profile].
• Who it’s for: Anyone who wants a capable, ad-free torrent client on Windows, Linux, macOS, or BSD — including self-hosters who want a headless server instance they can control from a browser [1][2].
• Cost savings: µTorrent and BitTorrent (the apps) have drifted into ad-ware and paid premium tiers. qBittorrent is $0, with no premium tier, no ads, no tracking [3][merged profile].
• Key strength: Feature-complete out of the box. Built-in search engine, RSS downloader with regex filtering, full WebUI, bandwidth scheduler, IP filtering, and sequential download — no plugins required for the core workflow [website].
• Key weakness: The desktop UI looks dated compared to modern apps. The WebUI got a meaningful overhaul in v5.0 (dark theme, improved responsiveness), but the desktop client hasn’t had a visual refresh in years [2][3].

---

What is qBittorrent

qBittorrent is a BitTorrent client written in C++ using the Qt framework and the libtorrent-rasterbar library. The project was started by Christophe Dumez and describes its goal plainly: “an open-source software alternative to µTorrent” [website]. That’s a less glamorous pitch than most software makes, but it’s accurate and honest.

It runs on Windows, Linux, macOS, FreeBSD, OS/2, and Haiku. The UI is available in roughly 70 languages. Development is volunteer-driven — the project explicitly asks for donations to keep running [website].

There are two deployment modes. The standard desktop client (qBittorrent) gives you a full GUI. The headless variant (qBittorrent-nox) runs as a background service with no display attached and exposes a WebUI on a configurable port — useful for always-on server deployments on a NAS, VPS, or Raspberry Pi [1].

The project sits at 36,032 GitHub stars as of this review, which puts it comfortably in the top tier of self-hosted media tools. It is not backed by a company. There is no commercial edition, no enterprise tier, no paid support contract — it’s entirely community-maintained [merged profile].

---

Why people choose it

The consistent reason across reviews and community discussions is simple: µTorrent became something people didn’t want. The once-clean Windows client added ads, bundled browser toolbars, and launched a cryptocurrency mining component that quietly used your CPU. The paid “ad-free” tier costs money for something that used to be free. BitTorrent (the app, owned by the same company) followed the same path [3].

qBittorrent stepped into that gap. It looks similar to the µTorrent of 2010 — deliberately so, the website describes the UI as “µTorrent-like” — but without anything running in the background that shouldn’t be [website][3].

The comparison reviewers draw most often is:

qBittorrent vs µTorrent: µTorrent still works, and many long-time users haven’t left because the interface is familiar. But the adware bundling, the crypto mining episode, and the gradual feature-gating behind paid tiers have worn down goodwill. qBittorrent covers the same feature set with none of that baggage [3][4].

qBittorrent vs Transmission: Transmission is lighter and has a cleaner, more minimal UI — it’s the better pick if you want the lowest possible resource footprint on an old Mac or a NAS. qBittorrent has significantly more features: built-in search, RSS with regex, granular IP filtering, torrent creation tool. If you need those features, Transmission won’t have them [3].

qBittorrent vs Deluge: Deluge is also open-source, also free, and also has a WebUI. The main practical difference is that qBittorrent ships those features built-in, while Deluge extends via a plugin architecture. Deluge’s plugin ecosystem is less maintained than it once was; several popular plugins haven’t been updated in years. qBittorrent’s approach of bundling the core features avoids that maintenance cliff [3].

qBittorrent-nox (headless) specifically: The linuxfordevices.com tutorial [1] makes the case for the server deployment mode: you get 24/7 torrent management without leaving a desktop machine running. A Raspberry Pi 4 or a $5 VPS handles the actual downloading, and you manage it through the WebUI from any device. That use case — separating the “always-on downloader” from the device you actually use — is exactly what qBittorrent-nox is built for [1].

---

Features

Based on the official website and confirmed in reviews:

Core download management:

• Full BitTorrent protocol support with DHT, PEX (peer exchange), and LSD (local peer discovery) [website]
• Magnet link support [website]
• Sequential downloading — download in order so you can start watching a video before it finishes [website]
• Encrypted connections [website]
• Private torrent support [website]
• Torrent queueing and prioritization [website]
• Per-torrent file selection and file prioritization [website]
• Bandwidth scheduler (set limits by time of day/week) [website]

Search and discovery:

• Built-in, extensible search engine that queries multiple torrent sites simultaneously [website]
• Category-specific search (Books, Music, Software, etc.) [website]
• RSS feed support with advanced download filters including regex [website]

WebUI and remote control:

• Full-featured WebUI written in AJAX — described as “nearly identical to the regular GUI” [website]
• v5.0 added dark theme, tab restoration, new columns, and improved login behavior [2]
• Accessible from any browser once deployed; no VPN required if you configure it on a server with a domain [1]

Tools and privacy:

• Built-in torrent creation tool [website]
• IP filtering in eMule and PeerGuardian formats [website]
• IPv6 support [website]
• UPnP / NAT-PMP port forwarding [website]
• “Mark of the Web” on downloaded files for Windows security (v5.0) [2]

v5.0 additions (desktop):

• Popularity metric for torrents [2]
• Ability to pause/resume the entire BitTorrent session [2]
• Shutdown timeout option [2]
• SSL torrent support [2]
• Larger piece sizes for torrent creation [2]

---

Pricing: the actual math

qBittorrent is free. There is no SaaS version, no paid tier, no premium features behind a paywall [merged profile][website].

The useful cost comparison is against the alternatives people are actually leaving:

µTorrent Pro: $19.95/year for ad-free + premium features. You’re paying annually for what used to be free, from a client that has a track record of bundling things you didn’t ask for [3].

Seedbox services (remote torrent hosting): If you want the 24/7 always-on download use case without running your own server, seedbox providers like Seedhost, RapidSeedbox, or Seedit4.me start around $5–15/month. qBittorrent-nox on a $5–6 Hetzner or Contabo VPS covers the same use case for the cost of the VPS — no per-GB charges, no provider lock-in, full control of the filesystem [1].

Usenet (alt.binaries): Some non-technical users considering this comparison are actually on Usenet indexers + providers ($10–20/month combined) for the faster speeds and better availability on popular content. That’s a different tool for a different use case — not an apples-to-apples replacement.

The honest framing: qBittorrent has no pricing problem. The decision is purely about whether it does what you need, not whether you can afford it.

---

Deployment reality check

Desktop install: Download the installer from qbittorrent.org, run it, done. There’s nothing unusual here [website]. v5.0 requires Windows 10+, 64-bit only, or macOS 11 Big Sur+ [2].

Headless server (qBittorrent-nox): This is where more steps are involved. The linuxfordevices.com guide [1] walks through it thoroughly. The short version:

1. Install with your package manager: sudo apt install qbittorrent-nox on Debian/Ubuntu, sudo dnf install qbittorrent-nox on Fedora, sudo pacman -S qbittorrent-nox on Arch [1].
2. Create a dedicated system user (qbit-nox) so it doesn’t run as root [1].
3. Write a systemd service file pointing at that user, launching on your chosen port (--webui-port=8080) [1].
4. Enable and start the service. WebUI comes up at http://your-server-ip:8080 [1].
5. Change the default credentials immediately. Default login is admin/adminadmin — this is documented, which means it’s known [1].

What can go wrong:

• Forgetting to change the default password and exposing the WebUI to the internet is the most common security mistake [1].
• The WebUI default port (8080) conflicts with a lot of other services. If you’re running multiple self-hosted tools, you’ll need to either change the port or put it behind a reverse proxy (Caddy or nginx) with a subdomain and HTTPS.
• The article [1] mentions VueTorrent as an alternative WebUI theme for users who want a more modern look — the default WebUI is functional but not pretty, even after the v5.0 improvements [2].
• If you’re on a VPS and want to use a VPN for the torrent traffic (common for privacy), configuring qBittorrent to bind only to the VPN interface requires a few extra steps that aren’t in the basic guides.

Realistic time to a working headless instance for a competent Linux user: 20–30 minutes. For someone learning as they go: 1–2 hours including reverse proxy setup.

---

Pros and cons

Pros

• Completely free, no ads, no tracking, no upsell. This sounds baseline but it’s now genuinely rare in the BitTorrent client space [3][4][website].
• Open source — you can audit what it does, fork it, or patch it [merged profile][3].
• Feature-complete out of the box. Built-in search engine, RSS with regex, bandwidth scheduler, IP filtering, torrent creation — no plugin hunting required [website][3].
• Cross-platform parity. Same features on Windows, Linux, and macOS — not a Linux-primary tool with a half-maintained Windows port [website].
• WebUI is good enough for remote management. v5.0 added dark mode and improved the UX meaningfully [2].
• qBittorrent-nox for headless deployment is well-documented and actively maintained — the headless mode is first-class, not an afterthought [1].
• Active development. v5.0 is a real major release with meaningful changes, not a version bump [2].
• 36,032 GitHub stars — this is not an abandoned project [merged profile].

Cons

• Desktop UI looks old. The µTorrent-inspired design made sense in 2010. In 2026, it reads as dated. The WebUI got a refresh; the desktop client didn’t [2][3].
• Initial search plugin setup requires some work. The built-in search engine needs plugins installed per-site, and some popular sites have removed their plugins from the default list [3].
• No mobile client. If you want to add a torrent from your phone, you’re going through the WebUI in a mobile browser — there’s no official iOS/Android app [4].
• No built-in Plex/Jellyfin integration. If you’re running an *arr stack (Sonarr, Radarr, etc.), qBittorrent integrates cleanly via its API. But there’s no first-party media server connection — you set that up yourself.
• Documentation is scattered. The official wiki at wiki.qbittorrent.org covers the basics, but for advanced configuration (VPN binding, reverse proxy hardening, API automation) you’re relying on community guides of varying quality [1][website].
• Volunteer-maintained. No company funding development means releases depend on contributor availability. The gap between major versions can be long [merged profile].

---

Who should use this / who shouldn’t

Use qBittorrent if:

• You want to get off µTorrent or BitTorrent (the app) and want something that works the same way without the adware.
• You’re setting up a home server or NAS and want an always-on downloader you can manage from any browser.
• You want built-in RSS automation for series or content feeds without installing extra tools.
• You’re building an *arr stack (Sonarr, Radarr, Lidarr) — qBittorrent is one of the best-supported download clients in that ecosystem.
• You’re on Linux and want a client that’s available in your distribution’s package manager and works predictably.

Skip it (use Transmission instead) if:

• You want the absolute lightest resource footprint — Transmission uses less RAM and CPU at idle, and its daemon mode is slightly simpler to configure.
• You want a genuinely minimal interface with no visual clutter. Transmission’s design philosophy is subtraction; qBittorrent’s is inclusion.

Skip it (use Deluge instead) if:

• You want a plugin-based architecture where you can add only what you need and prefer that extensibility to a bigger built-in feature set.

Skip it (use a seedbox service instead) if:

• You don’t want to manage a server at all, even a simple one.
• You need high upload ratios on private trackers and your home connection can’t deliver — a seedbox with a dedicated IP and fast datacenter connectivity is genuinely better for that use case.

Not the right tool if:

• You’re looking for a Usenet client. qBittorrent is BitTorrent only.
• You need Android support — use Flud or LibreTorrent on mobile [4].

---

Alternatives worth considering

• Transmission — lighter, cleaner, genuinely minimal. Daemon + WebUI mode works well on low-power devices. Missing: built-in search, RSS regex, IP filtering. Best for: NAS deployments where resource use matters.
• Deluge — open source, plugin-based, good WebUI. The plugin ecosystem is less maintained than it was. Best for: users who specifically want extensibility and don’t need the built-in search.
• Tixati — ad-free, highly detailed statistics and bandwidth controls, portable version available [3]. Not open source. Best for: Windows users who want deep per-connection stats.
• BiglyBT — fork of Vuze/Azureus, open source (GPL), feature-heavy, includes Swarm Merge for streaming across multiple torrents. More complex than qBittorrent. Best for: power users on private trackers who need seeding tools.
• rTorrent + ruTorrent — the traditional Linux headless stack. Powerful, widely used in hosted seedbox environments, but the setup complexity is significantly higher than qBittorrent-nox. Best for: experienced admins who want maximum control.
• µTorrent 2.2.1 — the last version before the adware era. Some users still run this decade-old version because it’s lightweight and clean. Not recommended: it receives no security updates.

For most people replacing µTorrent on a desktop, the choice is qBittorrent. For headless server use alongside an *arr stack, the choice is also usually qBittorrent — it has better API support and more active maintenance than Deluge in that context [1][3].

---

Bottom line

qBittorrent is what µTorrent used to be before the company decided to monetize its way into adware. It does the job completely, it’s free, it’s open source, and it doesn’t ask anything from you. The desktop UI is dated and the documentation is scattered, but neither of those is a dealbreaker — the software works reliably, the WebUI got meaningfully better in v5.0, and 36,032 GitHub stars reflect a real and active user base. If you’re still on µTorrent or BitTorrent (the app) out of habit, there’s no good reason to stay. If you want a headless server torrent client for a home lab or VPS, qBittorrent-nox with a reverse proxy is the most straightforward path to get there.

The only time I’d look elsewhere is if you specifically need mobile-first management, a truly minimal resource footprint (Transmission), or are building on a private tracker seedbox where upload ratios and speed matter more than simplicity.

---

Sources

1. Aadesh, linuxfordevices.com — “qBittorrent-nox: Optimize Your Torrenting Experience” (September 26, 2023). https://www.linuxfordevices.com/tutorials/linux/qbittorrent-nox-self-host
2. Corbin Davenport, How-To Geek — “qBittorrent v5.0 Now Available for Testing” (August 20, 2024). https://www.howtogeek.com/qbittorrent-v5-0-release-candidate/
3. appmus.com — “qBittorrent vs Tixati Comparison (2026)”. https://appmus.com/vs/qbittorrent-vs-tixati
4. appmus.com — “qBittorrent vs Flud Comparison (2026)”. https://appmus.com/vs/qbittorrent-vs-flud
5. appmus.com — “qBittorrent vs Downpour Comparison (2026)”. https://appmus.com/vs/qbittorrent-vs-downpour

Primary sources:

• GitHub repository: https://github.com/qbittorrent/qbittorrent (36,032 stars)
• Official website: https://www.qbittorrent.org
• Official wiki: https://wiki.qbittorrent.org