TorrServer

TorrServer is a self-hosted torrent streaming server for homelab users that caches torrents and serves them over HTTP, so you can watch media online without…

  • Media Applications
  • Media Servers
  • Other
  • Tools & Utilities
TorrServer is a self-hosted torrent streaming server for homelab users that caches torrents and serves them over HTTP, so you can watch media online without downloading full files first.

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 (not listed)
  • Windows (not listed)
  • Linux
  • 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.

82/100 Excellent

Maintained
100last commit 10 days ago
Popular
703,209 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
100256 MB minimum RAM, runs on ARM
Security check
82no serious findings, 3 minor, CI, tests

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

GitHub stars
3,209
Open issues
31
Last commit
2026-11-11
Latest release
MatriX.150
License
GPL-3.0
Activity
declining

Checked 10 days ago - source: GitHub (YouROK/TorrServer)

Resources & Compatibility

Minimum requirements: 256 MB RAM, 512 MB disk. ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Map port 8090 so the web UI works Start the container with a port mapping such as -p 8090:8090 so your browser can reach the web interface. If you skip this, the UI is only inside the container and you won't be able to open it. source
  • Choose a folder for downloads and settings Give TorrServer a real folder to use, for example with Docker's -v option or a --path setting, and keep that folder backed up. It holds your settings and torrent files, so losing it can reset or wipe your library. source
  • Add login before exposing it on your network Before letting anyone beyond your PC reach the service, set up login with a username/password file and enable authentication. Otherwise, whoever can access the port can add, remove, or manage torrents. source

Fetched 54 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I access the TorrServer web UI when running it in Docker?

Map port 8090 to the host, for example with -p 8090:8090. If the port is not mapped, the web interface is only reachable inside the container.

Which folder should I persist for TorrServer data?

Give TorrServer a real folder for downloads and settings, such as with Docker’s -v option or a --path setting, and keep that folder backed up. It holds settings and torrent files, so losing it can reset or wipe your library.

Do I need to add login before making TorrServer reachable on my network?

Yes, set up login with a username/password file and enable authentication before exposing it beyond your own PC. Otherwise, anyone who can reach the port can add, remove, or manage torrents.

Is there an Android client that works with TorrServer?

TorrServe is the Android client used with TorrServer. It is also covered for Android TV and PC-adjacent setups.

Answers sourced from context7.com, github.com, torrserve.com

Community

Collected 53 days ago - public community threads