VDO.Ninja routes video peer-to-peer, not through its own servers

The setup

VDO.Ninja is a browser-based tool for pulling a remote camera, phone, or a second performer's feed directly into OBS without installing dedicated conferencing software. As retrieved on 16 September 2026, the project's own documentation describes it as 'a browser-based live video and audio tool for bringing remote guests, smartphones, webcams, screen shares, and audio feeds directly into OBS Studio or other browser-enabled production software,' offered as a free hosted service and, per its public GitHub repository, released under the AGPL-3.0 open-source license.

What the documents show

The 'How does it work' page states the tool is built on WebRTC: after an initial connection is arranged through VDO.Ninja's own servers, video and audio typically travel directly between browsers rather than through a central relay, which the documentation gives as the reason for the tool's low latency. The mechanism is two link types: a PUSH URL run on the sending device to capture and transmit video, and a VIEW URL opened anywhere to watch the resulting stream, which can itself be added to OBS as a Browser Source. The getting-started guide adds a detail worth separating from the latency claim: on a shared local network, video traffic can stay local rather than round-tripping over the internet, a bandwidth claim distinct from the general low-latency claim made elsewhere.

The craft

For a two-performer collaboration or a remote guest segment, the practical workflow documented here is to open a PUSH link on the guest's device, copy the resulting VIEW link, and add that VIEW link as a Browser Source in the host's OBS, which the documentation states requires no extra software or accounts on the receiving end. Because the connection is peer-to-peer once established, the getting-started guide's tip to prefer a wired Ethernet connection over Wi-Fi is a direct consequence of that architecture: a weak link on either end degrades the direct connection with no server in between to smooth it over.

Keeping the creator in control

VDO.Ninja's status as a self-hostable, AGPL-3.0-licensed project, stated in its own repository, means a production team that does not want to rely on the free hosted service can run the signaling infrastructure themselves, a meaningfully different control posture than a closed-source remote-guest tool. The documentation's own terms-of-service reference states a minimum user age of sixteen, a detail worth surfacing plainly for any production inviting guests through the tool rather than assuming it applies only to the account holder.

• Does the receiving OBS Browser Source actually need the VIEW link's full quality, or would a lower-bandwidth parameter reduce strain on the connection?
• Is the collaboration relying on the free hosted service, or does the production need a self-hosted instance for more control over signaling?
• Have all participants in a session been informed of the tool's stated minimum age and its terms of service?

A tool that moves video directly between browsers, rather than through a company's own media servers, shifts both the latency benefit and the connection-quality responsibility onto the two ends of the link. VDO.Ninja's own documentation states that trade plainly rather than hiding it behind a single low-latency marketing claim.