Browser torrent streaming sounds simple: choose a release and press play. Underneath, two different systems have to cooperate. A torrent engine must discover peers and transfer pieces of a media file, while the browser must decode the container, video and audio formats. RELAY separates those jobs so each part has a clear responsibility.
What happens when you choose a release
RELAY Web presents the catalogue and available releases. When source signals are available, it shows useful details such as resolution, container, codec and peer health. PARALLAX Companion, installed on the same Windows computer, performs the torrent connection and prepares the selected media locally. RELAY then asks the browser to play the prepared stream.
The torrent payload does not pass through PARALLAX servers. Account and catalogue requests still use the PARALLAX ecosystem, but peer connections, transfer and media preparation happen on the user’s machine through Companion.
Why some torrents do not play in a browser
A healthy torrent is not automatically a browser-compatible video. Browsers support a narrower combination of containers and codecs than native media players. MP4 and WebM releases using supported video and audio codecs are generally the safest choices. MKV containers, HEVC video and advanced audio formats can fail even when peers and file data are available.
RELAY uses local verification to rank likely playable sources ahead of unavailable or incompatible choices. When it cannot confirm compatibility, it should describe the limitation rather than imply that buffering alone will fix it.
What Companion changes
Companion gives RELAY access to a focused local engine without turning the browser into a full torrent client. It can inspect a release, connect to peers and expose a secured loopback stream to the RELAY player. The browser may request local-device permission because the RELAY page needs to reach that service on the same computer.
Companion does not remove every browser limitation. It improves source verification and keeps networking local, but the final media still has to be understood by the browser. The planned RELAY for Windows application targets a native playback path for broader container and codec support; those capabilities remain roadmap targets until released and tested.
A practical setup checklist
Download Companion only from the official PARALLAX Companion page. Start it before opening RELAY, accept the browser’s local-device request, and choose sources marked as compatible where possible. If detection or playback fails, use the PARALLAX Help centre to distinguish a stopped local service, a pairing issue, weak peers and an unsupported format.
RELAY’s approach is built around transparency: the web interface handles discovery, Companion handles torrent activity locally, and the player communicates the format limits that still apply.