What Is VDO.Ninja and What Can You Use It For?
Updated
VDO.Ninja is a browser-based tool that sends live video from a phone, computer, or remote guest into a studio setup such as OBS. You use it by opening a URL and pasting that URL into an OBS "Browser Source" — no app install is implied by the site. It is useful when your camera, microphone, or a remote collaborator is not physically attached to the machine running your broadcast, and when you want to manage several guests in one place.
The core idea: a URL instead of a capture device
Normally OBS captures a camera plugged into the same computer. VDO.Ninja breaks that link. A device opens a web page, publishes its camera and/or mic, and produces a link. You load that link as a browser source in OBS, and the remote feed appears as a source you can position and mix like any other.
The site's own entry points map directly onto this:
- Create a Room — group chat plus tools to manage multiple guests.
- Add your Camera to OBS — publish a camera feed for use as a browser source.
- Add your Microphone to OBS — same idea for audio only.
- Remote Screenshare into OBS — send a screen instead of a camera.
- View Only — watch without publishing your own camera or mic.
What you can actually do with it
Bring a phone or second computer in as a camera
Open the camera page on the device, allow camera/microphone access, and copy the resulting URL into an OBS Browser Source. The page warns that a director or authenticated remote controller can remotely change your camera, microphone, URL, and digital video effects while the page is open — so treat the link as something with control attached, not just a video stream.
Add just a microphone
If you already have video handled but need audio from another device or person, the microphone flow does that without a camera feed.
Pull in a remote screenshare
Useful for walkthroughs, demos, or sharing an application window from someone else's machine into your scene.
Run a multi-guest room
A room gives you group chat and guest management. Relevant options visible on the room creation form:
| Setting | What it controls |
|---|---|
| Room Name / Password | Basic room identity and access |
| Preferred Video Codec | Default, VP9, H264, VP8, or AV1 |
| Guest access | Public (no sign-in), Require SSO, or Allowlist only |
| Require director approval | Guests wait for approval before joining |
| Guests can see the director but not other guests | Limits guest-to-guest video |
| Director performs as well | Puts the director into group scenes |
The page notes that disabling video sharing between guests improves performance, and that you should only invite guests you trust. It also flags the "Recording" option as experimental.
Use data-only mode
A "Data-only mode" toggle means no local camera or mic is being published — the connection carries data rather than your own media. The page also shows a "WHEP share active" state, described as advertising a WHEP source to room peers via the data channel.
Practical setup notes from the tool itself
The camera page lists conditions for the best experience: device powered, wired connection instead of Wi-Fi, headphones or earphones, other video/calling apps closed, a quiet room, and facing a light source. It also exposes video source quality presets (4K, Highest, High Resolution, Balanced, Smooth and Cool), mono audio, audio output destination, and a default avatar/placeholder image.
Where it fits and where it doesn't
Choose VDO.Ninja when the video source is remote, on a phone, or on a machine that can't be captured directly, and when you want a browser source in OBS rather than a hardware capture path. It is a poor fit if you need a guaranteed, managed service with formal support terms — the site presents itself as a free web tool, and the room features include trust-dependent controls like guest allowlists and director approval, which put the responsibility for who joins on you.
One caveat worth carrying into any decision: because a director or authenticated remote controller can change a guest's camera, mic, URL, and effects while the page is open, share room links only with people you trust, and prefer allowlist or SSO guest access over public rooms when the content is sensitive.