TorrentNG

TorrentNG is a self-contained BitTorrent client and management stack built for high-volume headless seeding.

  • Downloaders
  • Tools & Utilities
TorrentNG is a self-contained BitTorrent client and management stack built for high-volume headless seeding. It bundles torrentngd, a Rust-native BitTorrent daemon, with a built-in WebUI, REST/SSE API, and a qBittorrent-compatible API for integration with Prowlarr, Sonarr, Radarr, autobrr, and cross-seed. Use it when you want a single container with no external torrent client; for a UI layer in front of an existing rTorrent, qBittorrent, Transmission, or Deluge, use the TorrentNG WebUI template instead.

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 5 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

  • FIRST RUN torrentngd reads its settings from a config.toml file, not environment variables (this is intentional). source
  • Client setup choice Connect TorrentNG to an existing torrent client or use its built-in BitTorrent engine; files remain on the storage you configure. source

Fetched 46 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does TorrentNG use environment variables for first-run settings?

No. torrentngd reads its settings from a config.toml file, not environment variables, on first run.

Can I use TorrentNG in front of an existing torrent client?

Yes. It can act as a WebUI and client interface for the TorrentNG Engine, qBittorrent, rTorrent, Transmission, Deluge, and other clients.

Will existing automation tools be able to talk to TorrentNG?

It is designed to expose the APIs that automation tools already speak.

Is TorrentNG intended for very large headless seeding collections?

It is described as targeting headless seeding at 10k-100k+ torrents and 200-500+ TB.

How do I install TorrentNG on Unraid?

Install it from Unraid's Community Apps.

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

Community

Collected 49 days ago - public community threads