Misc options
Platform Specific Issues
Newly Added Parameters

How does it work

VDO.Ninja relies heavily on webRTC, a secure peer-to-peer streaming technology that exists in most modern web browsers. Most of the VDO.Ninja code runs completely within your browser, although some server-side components are hosted to help facilitate an initial ‘handshake’ between connecting peers. As video data is streamed directly from one peer to the other, extremely low-latency and very high video quality is possible; there are few limits. If both peers are on the same local area network, data transfer will still local to your network, saving your upload bandwidth.

Since applications like OBS have a built-in browser, you can use VDO.Ninja to stream low-latency video directly into the application without any downloads or user accounts. It's possible to start streaming within seconds to OBS and many modern applications -- you can even watch VDO.Ninja streams on a Tesla EV or within the Unity game engine.

Essentially, the basic usage of VDO.Ninja makes use of two URLs; one for input and one as an output.

The input URL is loaded up in the browser on the remote device, which obtains access to the device's camera and microphone.

To view the stream, you load up the corresponding output URL in another browser, from any where in the world really. That's it. The video will begin playing in a full-window, without pesky watermarks or visual distractions, ready for professional-level video capture.

Since collaboration is a big part of live streaming video, VDO.Ninja also offers group chat rooms, allowing for more complex options and controls over multiple streams at a time. What's possible with VDO.NInja can be rather overwhelming, as the feature set does not end there, but the basic defaults are designed to satisfy the needs of most users.

One thing that may not be intuitive at first is the use of URL-parameters to control settings, video quality, and many of the other options. URL parameters are used by VDO.Ninja in the same conceptual way that command-line parameters are used, such as by FFmpeg. Some URL parameters are set on the input side, while others can be set on the output side. The documentation is a great resource for finding out more on all the advanced options and how to use them.