NerdTorrentPlayer is a torrent media player that runs on your machine, not on a website. Clone it, start it locally, and the full player opens in your browser with the whole BitTorrent network behind it.
NerdTorrentPlayer has no hosted app, by design. Torrents need DHT, UDP trackers, TCP peers, and sometimes FFmpeg, none of which a web page can provide. Run the project locally and everything executes on your own hardware, with nothing in between.
The website is the product guide. Clone the repository and start it locally to open the actual player with its private native bridge.
From first peer to final frame, every part of the interface is built around getting you watching while keeping you informed.
Pieces are prioritized around playback, so compatible media can begin while the swarm is still arriving.
The native bridge reaches DHT, TCP peers, and UDP or HTTP trackers directly, without browser-only limitations.
Play browser-ready files directly and use local FFmpeg remuxing or HLS conversion when containers need help.
Subtitles, timing controls, episode switching, keyboard shortcuts, picture-in-picture, and resume are included.
See peers, trackers, speed, progress, buffer health, and transport state while the stream is running.
Sources and watch history stay on your device. The native helper binds to loopback and uses capability tokens.
One command starts the web interface and the loopback-only native bridge together.
Get the public project source from GitHub.
Install the app and local bridge dependencies.
Open localhost, paste a magnet, and choose a file.
Requires Node.js 22.13 or newer. Add FFmpeg for MKV, HEVC, remuxing, and conversion. After npm run dev, the player opens at localhost:3000 with the private bridge running beside it.
$ git clone https://github.com/GautamVhavle/NerdTorrentPlayer.git
$ cd NerdTorrentPlayer
$ npm install
$ npm run devNo hosted torrent backend, no account, and no application server storing your files. The bridge listens only on loopback, while sources and playback history stay on your device.
Real-world torrents need DHT, UDP trackers, TCP peers, and sometimes FFmpeg conversion. Browsers cannot provide those capabilities, so NerdTorrentPlayer runs locally with a small private bridge on your machine.
No. It prioritizes the selected media file and requests pieces around playback. How quickly playback begins still depends on swarm health, file layout, bitrate, and whether conversion is required.
Node.js 22.13 or newer is required. FFmpeg is recommended for MKV, HEVC, incompatible audio, remuxing, and HLS conversion. The standard npm run dev command starts both the app and its private local bridge.
NerdTorrentPlayer has no application server for storing your media. Torrent traffic goes between your device and peers, while saved sources and resume data remain in local browser storage. As with every torrent client, swarm peers can see your public IP address.
A torrent player that lives on your machine, built for the way you actually watch.