vdo.ninja

VDO.Ninja turns your phone or computer into a remote camera feed that OBS can pick up as a Browser Source. You open the "Add your Camera to OBS" page, allow camera/microphone access, copy the generated URL, and paste it into a new Browser Source in OBS. This works for a single camera or as part of a multi-guest room, and it's the standard way to get a phone camera into a stream without a capture card.

Before you start

• OBS installed on the streaming computer.
• A phone or second computer with a browser and a camera.
• Both devices on a stable connection — VDO.Ninja's own tips recommend a hardwired connection over Wi-Fi where possible.
• Headphones for the device sending video, to avoid audio feedback loops.

Step 1: Open the camera page and allow access

Go to the VDO.Ninja site and choose Add your Camera to OBS. The page will request camera and microphone permission — allow it, then wait for the camera to load.

One thing to know before you continue: while this page is open, a director or an authenticated remote controller can remotely change your camera, microphone, URL, and digital video effects. That's by design for remote production, but it means you should only share the link with people you trust.

Step 2: Set your video and audio sources

On the camera page you can pick:

• Video Source — quality tiers including 4K, Highest, High Resolution, Balanced, and Smooth and Cool. Higher tiers cost more bandwidth and CPU; "Balanced" or "Smooth and Cool" is usually the safer pick on Wi-Fi or older phones.
• Audio Source(s) — your mic, or No Audio if you only want video.
• Audio Output Destination — where the audio plays locally.
• Default Avatar / Placeholder Image — a fallback image if the camera drops.

If you don't need a local camera or mic at all, there's a Data-only mode option, which publishes no local camera or mic.

Step 3: Copy the URL into an OBS Browser Source

1. Copy the URL shown on the camera page.
2. In OBS, add a new Browser Source.
3. Paste the URL into the source's URL field.
4. Set the width and height to match your canvas (for example 1920×1080), then confirm.

OBS will load the page and the camera feed should appear. If you see a blank or black source, right-click the Browser Source and refresh it — the page sometimes needs a reload after OBS first connects.

Step 4: Verify the feed

• Check that the video appears in the OBS preview at the expected resolution.
• Confirm audio is coming through on the right track (or that it's muted if you set No Audio).
• If you're in a room, the page will show your status — for example, "Only the director can hear you currently" or "The director has muted you," which tells you the director controls your feed.

Tips for a clean feed

VDO.Ninja lists these conditions for the best experience:

• Keep the device powered.
• Use a hardwired connection instead of Wi-Fi.
• Use headphones or earphones.
• Close other video/calling apps.
• Use a quiet room.
• Face a light source.

Common snags

When to use a room instead

If you only need one camera, the single camera page is enough. If you're bringing in multiple guests, create a Room instead — rooms add group chat and tools to manage multiple guests, plus options like requiring director approval before guests join, disabling video sharing between guests for better performance, and choosing a preferred video codec (Default, VP9, H264, VP8, AV1). Room access can be public, SSO-required, or allowlist-only, and you can change these later in Room Settings.

For a solo phone-to-OBS setup, skip the room and go straight to the camera page — it's fewer steps and less to configure.

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:

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.

A VDO.Ninja room gives the director three guest-access modes (public, SSO required, or allowlist only), an optional "require director approval before guests can join" gate, and a set of in-room controls that let the director mute guests, disable their cameras, or stop their sharing. The trade-off to understand up front: once someone is in your room and you are acting as director or authenticated remote controller, that role can remotely change their camera, microphone, URL, and digital video effects while their page is open. So access control is really about who you let in, not about limiting what a director can do afterward.

Guest access modes

When you create a room, the setup screen offers these guest access options:

For the allowlist, you enter a comma-separated list using @handle or email patterns such as *@domain.com. The page notes you can change these settings later in Room Settings, so you are not locked into your first choice.

One related detail from the room setup: SSO rooms use a managed room secret, and the manual room password field is disabled in that case. If you want a simple shared password instead, that path is tied to non-SSO rooms.

Approval and in-room controls

Beyond the entry gate, the room creator can enable "Require director approval before guests can join." With this on, a guest sits in a pending state — the interface shows a "Pending Join Requests" area — until the director admits them. This is the closest thing to a manual door: even someone with the link cannot enter until you approve.

Once guests are in, the director has live controls. The page evidence shows states such as:

• "Only the director can hear you currently."
• "The director has muted you."
• "The director has disabled your camera temporarily."

There is also a Data-only mode ("no local camera or mic is being published") and a Stop Sharing control, so a participant can be limited to data rather than live A/V.

The remote-control caveat

This is the part worth reading twice. The camera-to-OBS page carries an explicit privacy warning: "A director or authenticated remote controller will be able to remotely change your camera, microphone, URL, and digital video effects while this page is open, if you continue."

That means joining a room as a guest is not a passive act. If you are not comfortable with someone else being able to switch your camera or mic while your page stays open, close the page when you are done, or don't join rooms run by people you don't trust. VDO.Ninja's own tip list says it plainly: "Invite only guests to the room that you trust."

Practical setup for a private room

1. Create a Room and give it a name.
2. Under guest access, pick Allowlist only (or Require SSO if your guests have accounts) instead of Public.
3. Enter the allowed handles or email patterns, comma-separated.
4. Turn on Require director approval before guests can join if you want a second check at the door.
5. Optionally disable video sharing between guests — the page notes this improves performance and also reduces what guests can see of each other.
6. Share the room link only with the people on your list.

A note on what is not specified

The page evidence describes these controls but does not state retention periods, encryption details, or what happens to recordings. The Recording option is labeled experimental, so treat any recording feature as unverified for sensitive sessions. If your use case depends on those guarantees, confirm them before relying on the room for confidential material.

The short version: use allowlist or SSO plus director approval for anything private, and remember that the director role itself is powerful by design — the strongest privacy control is choosing your guests carefully in the first place.

Create a room on VDO.Ninja by opening the site and using the Create a Room panel, where you set a room name, an optional password, guest access rules, and director options. Once inside, you join as the director, and the room's Control Center lets you mute guests, disable their cameras, approve join requests, and control what guests see. This works for group calls and multi-guest productions where you want one person managing the feed rather than everyone controlling their own.

Create the room

1. Go to the VDO.Ninja site and open the Create a Room section.
2. Enter a Room Name. This is the identifier guests use to find the room.
3. Optionally set a Password. Note that if you use SSO for the room, the manual room password is disabled — SSO rooms use a managed room secret instead.
4. Choose guest access:
   • Public — no sign-in required for guests.
   • Require SSO — guests must sign in.
   • Allowlist only — restrict to specific users or emails. The allowed list is comma-separated and accepts entries like @handle or email:*@domain.com.
5. Set director options as needed:
   • Require director approval before guests can join — you approve each guest manually.
   • The guests can see the director, but not other guests' videos — hides guest feeds from each other.
   • The director will be performing as well, appearing in group scenes — include yourself in the output.
   • Preferred Video Codec — Default, VP9, H264, VP8, or AV1.
6. Enter the room in the director's role when prompted. You can change these settings later in Room Settings.

Manage guests from the Control Center

The Control Center is where the director runs the room. From there you can:

• Mute a guest — the room shows "The director has muted you" on the guest's side.
• Disable a guest's camera temporarily — the guest sees a notice that their camera was disabled.
• Approve or reject join requests — pending requests appear for the director to close or accept.
• Invite others using the room's Control Center invite tools.

A few practical notes from the room setup:

• Disabling video sharing between guests improves performance. If guests don't need to see each other, turn this on.
• Only invite guests you trust. The room warns that a director or authenticated remote controller can remotely change a guest's camera, microphone, URL, and digital video effects while the page is open.
• Recording is considered experimental — treat it as a test feature, not a guaranteed capture.

What guests experience

When a guest joins, they grant camera/microphone access and wait for the camera to load. Their page shows the room name and status messages such as "Only the director can hear you currently" or "The director has muted you." Guests can also use Data-only mode, where no local camera or mic is published.

For the best experience, the setup page recommends: keep the device powered, use a wired connection instead of Wi-Fi, use headphones/earphones, close other video or calling apps, use a quiet room, and face a light source.

Common questions

Can I just chat instead of directing? Yes — join the room as a Participant rather than a director if you only want to chat and not manage the room.

Can I customize the room further? Yes — advanced URL parameters are available to customize rooms.

What if I lose the room? If a previous session is found, you can load it from the prompt.

What about the "WHEP share active" status? This means the room is advertising a WHEP source to room peers via the data channel — relevant if you're routing the stream into another player or studio rather than just the browser view.

VDO.Ninja is described on its own site as "100% free," and it works by bringing live video from a phone, computer, or other people directly into a studio setup such as OBS. Before you rely on it, know three practical things: recording is labeled experimental, guest-to-guest video sharing is best disabled for performance, and a director or authenticated remote controller can remotely change your camera, microphone, URL, and digital video effects while your page is open.

What "free" means here

The site presents the service as free and built around browser-based video contribution rather than paid tiers. The page evidence shows no pricing links, payment platforms, or paid-plan keywords, so there is no documented paid tier to compare against. Treat "free" as the stated model, not as a guarantee about every future feature.

What you should know before using it

Recording is experimental

The room setup explicitly notes that the "Recording" option is considered experimental. If a recording matters to you, don't treat it as your only copy — plan a separate capture method and verify the result.

Remote control is real

A privacy warning on the camera page states that a director or authenticated remote controller can remotely change your camera, microphone, URL, and digital video effects while the page is open. This is a feature, not a bug, but it means you should only join rooms run by people you trust.

Performance depends on how you configure the room

The tips shown during room creation include:

• Disabling video sharing between guests to improve performance
• Inviting only guests you trust
• Using a wired connection instead of Wi-Fi
• Using headphones or earphones
• Closing other video or calling apps
• Keeping the device powered
• Using a quiet room and facing a light source

Rooms can be customized

Advanced URL parameters are available to customize rooms, and room settings can be changed later. Guest access can be public (no sign-in required), require SSO, or be limited to an allowlist of specific users or emails. You can also require director approval before guests join.

Quick reference

A practical example

Suppose you're bringing a remote guest into OBS. You create a room, send the guest link, and the guest opens it in a browser. While that page is open, you (as director) can adjust their camera, microphone, and effects remotely. If the guest is on Wi-Fi in a noisy room with other apps running, expect a rougher feed — the tips above exist because those conditions degrade the experience. If you also want a recording, don't assume the experimental recording option will be your safety net.

Bottom line

VDO.Ninja is presented as free and is designed for getting live video into a studio workflow. Use it with people you trust, expect remote control to be possible, disable guest-to-guest video for smoother performance, and treat recording as experimental rather than guaranteed.