TorrServer
github.com
- Free plan
- Windows
- macOS
- Linux
- Web
- iPhone and iPad
- Android
- API
- Self-hosted
What TorrServer is
TorrServer is a free, self-hosted server that streams torrent content over HTTP without first downloading the entire file. It caches torrent data, and its cache size can be adjusted to system parameters and internet connection speed. The project provides a cross-browser web interface, a REST API, and a native MCP endpoint for compatible clients to manage torrents and obtain playback URLs. URLs can be used with VLC, mpv, or a browser; Smart TV use through Media Station X is also documented.
Torznab search works with Jackett, Prowlarr, and similar indexer managers. Optional features include a DLNA server and GStreamer HLS remuxing and transcoding in designated builds. Deployment options include standalone installs, Docker, and Docker Compose. Security controls include HTTP Basic authentication, HTTPS with user-supplied or generated certificates, and read-only database mode. TorrServer supports Windows, macOS, Linux, Android, and iOS and is licensed under GPL-3.0. The project warns that HTTP media sends stream URLs and Basic authentication credentials unencrypted, so it should be used only on a trusted network.
Who it suits
TorrServer suits people who want to stream torrent content from a self-hosted server and use compatible players or clients. Its documented deployment options include standalone, Docker, and Docker Compose installs.
Good to know, and what to watch
- Streams without downloading the full file first
- Offers a web interface, REST API, and MCP endpoint
- Supports playback through VLC, mpv, or a browser
- Can be deployed with Docker or Docker Compose
- HTTP media sends URLs and Basic credentials unencrypted
- iOS requires version 18.0 or later
- FUSE and GStreamer are unavailable on iOS
- iOS background playback depends on the host app
Plans
Every plan and priceTorrServer
Free plan
Getting started
- Open the TorrServer GitHub repository
- Choose a standalone, Docker, or Docker Compose deployment
- Start the server and open http://127.0.0.1:8090
- Configure cache sizing for the system and connection
- Set authentication or HTTPS certificates as needed
- Connect a player, browser, Smart TV, or compatible API client
Limits to check
On iOS, the XCFramework requires iOS 18.0 or later, while FUSE and GStreamer are unavailable and background playback depends on the host app. When HTTP media is enabled, stream URLs and Basic authentication credentials are unencrypted and should be used only on a trusted network.
The Club's review
TorrServer is a self-hosted service that turns torrent content into HTTP streams instead of waiting for complete downloads. It is aimed at technically confident users building a personal media setup, API workflow, or home server. The free GPL-3.0 release is unusually flexible, provided you can manage deployment and network security yourself.
Overview
TorrServer’s central value is immediacy: torrent content can be sent to a compatible player while data is still arriving. Because it is self-hosted, you retain control over storage, networking, and client access rather than handing playback to a hosted service. That makes it a strong fit for home labs, media servers, and developers integrating torrent playback into another application, but it is a less natural choice for anyone seeking a polished, managed consumer app.
Key features
The server caches torrent data and lets you adjust cache size to available system resources and connection speed. In practice, that gives an administrator control over the trade-off between disk usage and smoother streaming; it also means sensible tuning is part of deployment rather than an automatic guarantee.
A cross-browser web interface is available at the default local address http://127.0.0.1:8090. Torznab search support connects with Jackett, Prowlarr, and comparable indexer managers, which is useful when search and playback need to live in one workflow.
The REST API and native MCP endpoint let compatible clients manage torrents and retrieve playback URLs. Those URLs can be opened in VLC, mpv, or a browser, and Smart TV playback is documented through Media Station X. Optional DLNA support and GStreamer HLS remuxing or transcoding can broaden device compatibility, but those media functions are tied to designated builds and should not be assumed in every installation.
Deployment can be standalone, through Docker, or with Docker Compose. HTTP Basic authentication, HTTPS with supplied or generated certificates, and read-only database mode provide useful controls for a self-hosted service. The important limitation is explicit: when HTTP media is enabled, stream URLs and Basic authentication credentials travel unencrypted. Use that mode only on a trusted network; HTTPS is the safer choice when traffic could be observed.
Pricing
TorrServer: free includes a self-hosted torrent streaming server under the GPL-3.0 license. There are no paid tiers, seat charges, quotas, or renewal terms. The trade-off is operational rather than financial: you supply the host, networking, storage, and administration.
Platforms
Supported platforms are Windows, macOS, Linux, Android, iOS, web, API deployments, and self-hosted environments. Magnet links, remote control, and DHT support are included in the product specification. The iOS option has material constraints: its XCFramework requires iOS 18.0 or later, FUSE and GStreamer are unavailable, and background playback must be handled by the host application. That makes iOS a specialised integration target rather than an equivalent to the server builds.
Who it's for
Choose TorrServer if you are comfortable running a local or rented host and want torrent streaming exposed to browsers, media players, smart TVs, or your own software. It is particularly suitable for developers who need REST or MCP control and for home-server operators who value configurable caching and container deployment. Look elsewhere if you need turnkey setup, broad iOS parity, or secure streaming on networks you do not fully trust without additional configuration.
Pros and cons
Pros
- Streaming before completion: HTTP playback avoids waiting for an entire torrent to download.
- Flexible integration: REST, MCP, playback URLs, VLC, mpv, browser, and Media Station X cover varied client setups.
- Deployment choice: Standalone, Docker, and Docker Compose options suit both simple servers and repeatable infrastructure.
- Configurable storage: Adjustable caching lets operators match disk capacity and connection conditions.
- Free and open source: The GPL-3.0 plan has no subscription or usage fee.
Cons
- Unsafe HTTP media on untrusted networks: URLs and Basic credentials are unencrypted when that mode is enabled.
- Uneven iOS capability: iOS 18 or later is required, with no FUSE or GStreamer and host-managed background playback.
- Operational burden: Self-hosting leaves installation, updates, storage, and network exposure to the operator.
- Build-dependent media extras: DLNA and GStreamer functions are not universal across installations.
Alternatives
If you want a conventional desktop torrent application with free and paid ad-free options on macOS and Windows, consider BitTorrent Classic. µTorrent Classic is a better fit for bulk downloading on Android or Windows, with free, ad-free, and Pro annual plans. For direct transfers across a broad device mix rather than torrent streaming, Feem offers unlimited transfers on its free plan and an iOS Pro option.
BitComet suits users wanting a free client across desktop, Android, web, and self-hosted environments, while Transmission keeps all features free with no ads or tracking across Linux, macOS, Windows, web, and self-hosted setups. WebTorrent is the alternative for a free, non-profit, MIT-licensed approach with API and browser-oriented platforms. Deluge is another free, open-source BitTorrent client with API, web, and self-hosted support. JSTorrent is a free, open-source, multi-platform project for readers who prefer that model.
Browse more options in Peer-to-Peer File Sharing Software.
Verdict
TorrServer is the right choice for a self-hosting-minded user who wants torrent streams, programmable control, and flexible media-player output without paying for a plan. Its strongest reason to choose it is the combination of HTTP streaming, API/MCP access, and deployment control. Look elsewhere if you need a managed interface, full iOS media capabilities, or safe HTTP playback across untrusted networks.
The verdict
TorrServer provides several ways to manage torrent streams and send playback URLs to compatible players. Its HTTP-media security warning and iOS limitations are important considerations before deployment.
Questions people ask
Is TorrServer free?
Yes. The TorrServer plan costs nothing and is GPL-3.0 licensed.
Which platforms are supported?
Supported platforms include Windows, macOS, Linux, Android, iOS, web, API, and self-hosted environments.
How can I deploy TorrServer?
The project documents standalone installation, Docker, and Docker Compose deployment.
Which players can use TorrServer playback URLs?
Playback URLs can be used with VLC, mpv, or a browser. Smart TV use through Media Station X is also documented.
Does it provide API access?
Yes. TorrServer provides a REST API and a native MCP endpoint for compatible clients to manage torrents and obtain playback URLs.
What security options are available?
Documented controls include HTTP Basic authentication, HTTPS with user-supplied or generated certificates, and read-only database mode.
What the maker publishes
- API and MCP
- TorrServer provides a REST API and a native MCP endpoint that compatible clients can use to manage torrents and obtain playback URLs. source
- Caching
- It caches torrent data and allows the cache size to be adjusted to system parameters and internet connection speed. source
- Deployment
- The project documents standalone installs, Docker, and Docker Compose deployment. source
- iOS limits
- The iOS XCFramework requires iOS 18.0 or later; FUSE and GStreamer are unavailable on iOS, and background playback is the host app’s responsibility. source
- License
- The repository identifies its license as GPL-3.0. source
- Media features
- Optional features include a DLNA server and GStreamer HLS remuxing and transcoding in designated builds. source
- Player integrations
- The project says playback URLs can be used with VLC, mpv, or a browser, and documents Smart TV use through Media Station X. source
- Purpose
- TorrServer streams torrent content over HTTP without requiring users to download the full file first. source
- Search integrations
- Torznab search supports Jackett, Prowlarr, and similar indexer managers. source
- Security caveat
- The README warns that when HTTP media is enabled, stream URLs and Basic authentication credentials travel unencrypted, and says to use it only on a trusted network. source
- Security controls
- Documented options include HTTP Basic authentication, HTTPS with user-supplied or generated certificates, and read-only database mode. source
- Web interface
- The project lists a cross-browser web interface and says the default local address is http://127.0.0.1:8090. source
Checked against the maker's pages on 7 Oct 2026.