Magneterie is a browser-based video streamer centered on the magnet link. Its own description states that it streams any magnet link or MP4 URL right in your browser, with no downloads and no installs. The product opens on a single panel labeled 'Load video,' where a user supplies a source — a magnet link, a video URL, or a web page address — or uploads a .torrent file, and then presses Play. The purpose is narrow and practical: take a link or a torrent file and turn it into playing video inside the browser tab, without a separate desktop client and without a download step preceding playback. It is built for people who already handle magnet links, .torrent files, or direct video URLs and want a lighter way to play them.
The friction Magneterie targets is the overhead that normally sits between a link and a playing video. The site frames its value around the two things it removes: downloads and installs. In a conventional workflow, a magnet link or .torrent file implies acquiring software first and then waiting for content to arrive on disk before anything can be watched. Magneterie collapses that sequence into a browser tab — the link goes in, playback starts, and the file does not have to be saved anywhere first. That matters most for casual, one-off viewing, for checking whether a source is the right one, and for anyone who does not want to maintain a dedicated client just to play a single link. The pitch is deliberately minimal: no downloads, no installs, just the browser.
The input surface is intentionally small. A single text field accepts a magnet link, a video URL, or a page address, and a separate upload control accepts a .torrent file. Once a source is supplied, a Play button starts the stream. Because the field accepts a web page as well as a direct video address, the same entry point covers several kinds of sources without a separate mode for each, and the .torrent upload gives users whose source is a file rather than a link a path in as well. Every route converges on the same player, so the experience after pressing Play does not change based on how the source was provided.
Magneterie documents how the player is wired, which is unusual for a consumer-facing streaming tool. The interface explains that the online player runs browser-side peers over WebRTC and uses webseeds. There is also a 'Server mode (TCP/UDP peers)' control, but the site is explicit that server mode is not available online: on the hosted site only the browser player runs, using WebRTC peers and webseeds. To use TCP/UDP peers, the project has to run on your own machine via npm start. This is spelled out directly in the interface rather than buried in documentation, so a user knows before flipping the switch which peer types are actually in play in the hosted version and which require the local build.
While a stream is running, Magneterie surfaces a live status panel. The readouts include Downloaded as a percentage, Speed in B/s, and a Peers count. A second group reports on the media itself: Size, Duration, Resolution, and Type. A third group describes provenance: Page, Origin, and Video source. Together these turn an otherwise opaque playback into something observable — a user can see whether peers have connected at all, whether data is arriving, how fast, and how far the transfer has progressed, while also confirming that the duration and resolution match the expected file and that the video is coming from the source they intended. When nothing is loaded, the panel simply reads zero: 0% downloaded, 0 B/s, 0 peers, with the media fields blank.
Below the player, a 'Torrent files' section lists the files contained in the torrent. For a torrent that holds several items, this is what tells a user what is actually inside the source before or during playback, rather than treating the link as a single anonymous blob. Combined with the provenance fields — page, origin, and video source — the interface gives a compact audit trail of what is being played and where it came from, which is useful when a link has been passed around or when several similar sources are being compared.
The overall approach is to keep the heavy lifting in the browser and be explicit about the boundary. On the hosted site, playback is handled by the browser player using WebRTC peers and webseeds; the server-side peer mode is deliberately not offered online, and the local run via npm start is the documented way to reach TCP/UDP peers. The product does not try to hide this split — it states it in the interface. The result is a tool with a very thin surface: one load panel, one play control, a status readout, and a file list. There are no accounts, libraries, or queue management described in the content; the flow is source in, playback out, with telemetry visible throughout.
The benefits follow directly from what is claimed. Because there are no downloads and no installs, there is nothing to set up and nothing left behind on disk after a viewing session — the video plays in the tab. Because the browser player uses WebRTC peers and webseeds, playback can proceed without the local server component. Because the status panel is always visible, problems are diagnosable in place: a peers count stuck at zero or a speed holding at 0 B/s is immediately visible rather than surfacing as an unexplained buffering spinner. And because duration, resolution, type, page, origin, and video source are all displayed, a user can verify that what is playing is what they meant to play.
Typical scenarios map to the interface. Someone handed a magnet link can paste it into the load field and press Play instead of installing a client. Someone with a direct MP4 or video URL can use the same field as a quick browser player. Someone holding a .torrent file can upload it and play from there. A user who needs TCP/UDP peers can run the project locally with npm start and use server mode, which is the documented route for that configuration. Someone comparing several links can watch the peers, speed, and video source readouts to tell which source is actually serving data. And anyone who wants to know what is inside a torrent can read the files list.
Magneterie is listed publicly under Web App, Video Streaming, and Developer Tools, which matches its shape: a single-page browser tool that also documents its own plumbing. Its stated mechanisms are WebRTC peers and webseeds for the online player, with TCP/UDP peers available only through a local run started with npm start. No pricing, plans, or tiers appear in the content provided, and no account system is described. The intended user is someone comfortable enough with magnet links and .torrent files to have one on hand, who wants playback rather than a download, and who may also be the sort of person who appreciates being told exactly which peer types the hosted player supports.
The takeaway is that Magneterie reduces torrent playback to a browser tab. Paste a magnet link, video URL, or page, or upload a .torrent file, press Play, and watch with live numbers for speed, peers, and progress alongside the file's duration, resolution, and origin. No downloads, no installs, and an honest account of what runs where — WebRTC peers and webseeds online, TCP/UDP peers through the local npm start build.