qbittorrent/qBittorrent

qBittorrent is a mature desktop BitTorrent client with a separate headless variant for servers. If you already know what a .torrent or magnet link is and want a free client you control, it is a reasonable place to start; much of the real work is in how you configure it.

The problem

Someone wants a torrent to keep downloading after they close the laptop lid, or to seed from a small always-on box rather than their desktop. The usual desktop-client workflow ties the job to a window on one machine, so the transfer stops when that machine sleeps and progress is awkward to check from elsewhere. qBittorrent changes that by offering both a graphical client and a headless server variant, so the same job can live on a machine that stays up. The result is a download queue you can revisit from another device instead of a transfer that dies with your session.

What's different

The core is ordinary BitTorrent, built on libtorrent, the library used by a number of clients (project README, libtorrent). Where qBittorrent stands out is packaging: a Qt-based GUI for desktop use and a headless mode that exposes a web interface. That headless path is why people put it on home servers and NAS boxes; commenters on Hacker News describe using the qbittorrent-nox variant on a server and connecting through the web UI (2024-10-02 comment).

The trade-off is that the client does not manage your anonymity for you. A 2024-10-02 thread included a commenter reporting that their IP still appeared when testing with an IP-leak site after torrenting over a VPN (comment). In the reply chain, one commenter argued the report probably concerned a proxy rather than a VPN, and that UDP traffic is hard to tunnel through proxies (reply); another said their own setup, a headless instance in a container, showed no leak (reply). Treat that as an unresolved configuration dispute rather than a verdict on the software. The lesson is that binding the client to a tunnel or using a container that routes all its traffic is something you must set up and verify yourself.

Who should try it

Good fit: a home-server user who wants a web-accessible client and is willing to configure the network path deliberately. Good fit too: a desktop user who wants a free, Qt-based torrent client and does not need remote access. Poor fit: someone who expects the client to protect their address by itself, or who wants a fully turnkey privacy setup with no verification. A second group that should look elsewhere for now: anyone unwilling to run a browser-based remote interface, since the headless path is the main reason to pick this over an ordinary GUI client.

Requirements and limitations

Desktop use needs a Qt-capable GUI environment, and the headless variant needs a machine that stays on plus a browser to reach it. Running as a server means firewall rules, credentials for the web interface and, if you want to tunnel traffic, a proxy or container arrangement. That last part is ongoing upkeep, not a one-time checkbox: the 2024 discussion shows that whether traffic actually leaves through the tunnel depends on protocol choices (UDP in particular) and on how the app is launched, so you have to retest after changes.

On Windows, the client has a separate history: in 2021 it was flagged as a potentially unwanted application, and a commenter listed several other torrent clients also added to Microsoft's list at the time (2021-07-26 comment, HN thread). That does not say anything about the current build, but it is why installer warnings may appear and why downloading from the official site rather than a repack matters (official site). Source installs are covered in the project's INSTALL instructions (project README); signed tarballs and binaries are also published.

HotRepo's take

The only dated signal available is a monthly C++ board placement, #14 with +928 stars on 2026-10-26. HotRepo has no daily-board history for this repository, so whether interest is rising or fading cannot be judged; the age and star totals come from repository metadata, not from that sample. If you are evaluating it, check how the headless web interface handles authentication and interface binding in your deployment before relying on it as a server.