TorrentNG WebUI

TorrentNG WebUI is a torrent manager that runs as a desktop app, a headless self-hosted server, or a bridge in front of rTorrent, qBittorrent, Transmission,…

  • Downloaders
  • Tools & Utilities
TorrentNG WebUI is a torrent manager that runs as a desktop app, a headless self-hosted server, or a bridge in front of rTorrent, qBittorrent, Transmission, Deluge, or its built-in BitTorrent engine, giving self-hosters and heavy seeders a consistent web interface and a qBittorrent-compatible application programming interface for Prowlarr, Sonarr, Radarr, autobrr, and cross-seed.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac
  • 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.

65/100 Good

Maintained
100last commit 6 days ago
Popular
2415 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 17 days ago

GitHub stars
15
Open issues
9
Last commit
2026-11-14
Latest release
main-20261114-3
License
AGPL-3.0
Activity
declining

Checked 6 days ago - source: GitHub (snapetech/TorrentNG)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Unraid backend selection Choose the Backend Type that matches your existing rTorrent, qBittorrent, Transmission, or Deluge instance, then fill only that section. All backend sections appear because Unraid templates cannot hide fields conditionally, so the other fields can be left empty. source
  • Client or engine You can connect to an existing supported torrent client or use TorrentNG's built-in BitTorrent engine. source
  • No hosted account There is no hosted TorrentNG account; it runs on your own server and files stay on the storage you configure. source
  • Desktop and self-hosted setup For Mac, download the desktop app from GitHub Releases; for self-hosting, run TorrentNG as a headless server or as a bridge in front of an existing torrent client. source

Fetched 29 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How should I fill the backend sections in the Unraid template for TorrentNG WebUI?

Choose the Backend Type that matches your existing rTorrent, qBittorrent, Transmission, or Deluge instance and fill only that section. The other backend sections can be left empty because Unraid templates cannot hide fields conditionally.

Where is TorrentNG's capability manifest reported?

The torrentngd process reports its capability manifest through the health endpoint.

Does torrentngd also serve the WebUI and automation routes?

Yes, the torrentngd process owns startup and shutdown and serves the WebUI and automation routes.

Answers sourced from ca.unraid.net, github.com

Community

Collected 49 days ago - public community threads