If you want several people on screen in a Zoom call, OBS Virtual Camera sends an OBS-composed picture into Zoom. If you want a Zoom meeting to appear on YouTube or another destination, you start a separate broadcast from Zoom’s meeting controls; Virtual Camera does not do that.
Choose the route before changing settings. The steps differ depending on whether hosts need to talk with one another, whether viewers should see the meeting, and whether you already have cameras or a production switcher.
Decide which direction the video needs to flow
There are three workflows that are easy to confuse:
| Goal | Video path | What viewers or participants receive |
|---|---|---|
| Put an OBS layout into a Zoom call | OBS scene → OBS Virtual Camera → Zoom | Zoom participants see the OBS output as a camera feed |
| Send an interactive Zoom meeting to a public platform | Zoom meeting → Zoom livestream controls → destination | The destination receives Zoom’s meeting broadcast, if the account is eligible and configured |
| Bring an OBS production into an eligible Zoom webinar | OBS production → incoming RTMP → Zoom Events webinar | Webinar attendees receive the production through a feature that must be available and configured |
The first route is useful when you want a branded layout, a title card, or a programme feed visible to people inside Zoom. The second is for people watching outside the meeting, such as a YouTube audience. In the third, OBS sends a finished production into an eligible webinar; this is not the same as selecting OBS Virtual Camera in an ordinary Zoom meeting.
Work out whether each host needs to speak and hear others. If so, a normal interactive Zoom meeting is likely part of the setup. Zoom’s broadcast configuration for an existing production system is a different, one-way arrangement: Zoom notes that two-way communication is not possible with those settings. Do not assume that an audience-facing broadcast also gives hosts a return conversation.
Write down the intended path in a sentence before you configure anything: “Our guests talk in Zoom, and the public sees the Zoom meeting,” or “Our producer builds the image in OBS and sends it into Zoom.” If that sentence is unclear, pause. Choosing the wrong direction can leave you with a clean OBS preview that is never reaching the audience you intended.
For a public YouTube programme made from prerecorded material rather than live hosts, the decisions are different; the guide to looping Indian music videos in OBS covers that use case. Here, the priority is keeping host interaction and the broadcast route clear.
Prepare Zoom and OBS
Install and open OBS Studio, and make sure the Zoom desktop application is available on the computer that will run the meeting. Sign in to the Zoom account that will host the event. Before preparing slides or inviting guests, check that the account can use the livestream feature you need and that its administrator has not disabled it.
Zoom’s account-level settings and destination options are described in its instructions for enabling livestreaming. For a custom streaming service, follow Zoom’s custom livestreaming setup and confirm that the correct URL and stream key are available to the host. Menu names can change, and an administrator may control these options, so check the current account rather than relying on an old screenshot or someone else’s meeting.
Choose one person to own the broadcast controls. The host should start and stop a Zoom livestream. A co-host can assist with participant management, but Zoom says a co-host cannot start the livestream. That means a producer should not assume that assigning a co-host is enough to hand over the go-live step. Review Zoom’s co-host permissions, then agree who will press the broadcast control and who will watch the audience-facing output.
Ask each remote host to join the Zoom meeting from their own device, with a camera, microphone, headphones where possible, and a stable place to speak. Give guests a short joining instruction: use the intended meeting link, choose the correct microphone and camera, and keep other devices muted if they are in the same room. For a modest remote panel, that is a simpler starting point than buying capture hardware.
OBS can show scenes and sources, but the Virtual Camera guide does not make each Zoom participant an independently selectable OBS source. If your plan relies on separately positioning every guest inside OBS, verify that your chosen capture method actually provides those separate feeds. Otherwise, use the Zoom meeting’s own participant layout as the picture you capture, or choose a production method that supplies individual camera feeds. Avoid promising a layout before you have proved its signal path.
Compose multiple hosts in an OBS scene
In OBS, create a scene for the picture you want to send. Add the available sources that your chosen workflow can actually provide: for example, a camera, a graphic, a title, or a captured meeting view. Arrange and resize them in the canvas, then check the scene at the same aspect ratio you intend to use in Zoom. Keep names, captions, and other useful details away from the edges, where they may be clipped or covered by interface elements.
If you are capturing the Zoom meeting as one source, you are composing the whole meeting view, not gaining control over each guest as a separate camera. You can still add a title or frame around it, but changes to who is visible in the underlying Zoom layout may affect the picture. Decide whether the Zoom host will control that layout or the OBS operator will simply present the meeting view as received.
A simple scene is easier to test under pressure. Put the main picture in the largest area, keep supporting text readable, and avoid changing several visual elements at once. If one host is speaking, consider whether a fixed gallery or a speaker-focused view best serves the people watching. The answer depends on the programme: a discussion may benefit from seeing all speakers, while a short interview can favour the active speaker. Test with the actual people and screens rather than judging the layout from the OBS preview alone.
OBS has multiple Virtual Camera output choices, including Program, Preview, Scene, and Source. Program is normally the finished output. If you use Studio Mode, Preview may show an uncommitted scene, so selecting it can expose a layout you did not mean to send. Read the OBS Virtual Camera guide and confirm the selected output before guests join.
Build a fallback scene as well. It might be a still title card with a note that the discussion is reconnecting, or a camera view that does not reveal private desktop content. The fallback does not fix a failed network connection, but it gives the operator an intentional picture to switch to if a source freezes or a guest drops. Keep it ready and rehearse the change so you are not searching through scene names during the programme.
Send OBS Virtual Camera into Zoom
Once the OBS scene is ready, start OBS Virtual Camera from OBS. In Zoom’s camera settings, choose “OBS Virtual Camera” and check the meeting preview. Ask another participant to confirm what they see; the local OBS canvas is not proof that Zoom is receiving the intended picture. A short private rehearsal catches a wrong camera selection before a public event does.
Keep the direction clear: OBS is providing video to Zoom as though it were a webcam. It is not sending the Zoom meeting outward to YouTube. If your goal is a public stream, you still need Zoom’s livestream controls, an eligible incoming RTMP route, or a separate broadcast workflow.
Video and audio are separate paths. Selecting OBS Virtual Camera supplies picture, not a universal audio connection. Decide whether Zoom should receive a host microphone directly, audio mixed by OBS, or another deliberate source. The appropriate virtual audio device and routing steps depend on the operating system and devices in use. OBS’s video-call audio routing tutorial discusses the call-and-audio problem, but there is no single device recipe that fits every computer.
Avoid sending the same microphone to Zoom through two paths, which can cause echo or doubling. Use headphones for monitoring where practical, and make sure sounds intended only for a recording or public programme are not unexpectedly sent into the call. Speak into the microphone and watch the Zoom audio indicator while another participant listens. A moving meter alone does not establish that the other person hears clean audio.
If OBS Virtual Camera is missing, close and reopen Zoom after starting the camera, then check the OBS troubleshooting guidance for your operating system. On macOS, permissions or extension approval may be relevant; on Linux, the virtual camera setup has its own considerations. Do not install unrelated tools or change several system settings at once. Make one change, reopen the applications, and confirm whether Zoom’s camera list has changed.
Broadcast a Zoom meeting to an external destination
For the route from a Zoom meeting to a public platform, first verify that the meeting host’s account has livestreaming enabled and that the intended destination is permitted. The host may need to configure a custom service with a stream URL and key before the meeting. Treat those values as credentials: share them only with the person configuring the destination, and do not put them in a public document or on screen.
During the meeting, the host uses Zoom’s meeting controls to start the configured livestream. A co-host may handle questions or participants, but cannot take over the livestream start action just by having the co-host role. Agree on the hand-off in advance: the host starts the broadcast, and another person checks the destination from a separate viewer device.
There can be a delay between what participants see in Zoom and what an outside viewer sees. Give the audience-facing player time to appear, check that the sound and picture are present, and use a private or otherwise controlled test when the destination supports one. Avoid announcing that the stream is live until the external view has been checked. If it fails, keep the Zoom meeting running while the host checks the account configuration, destination selection, and stream credentials.
You do not need OBS Virtual Camera merely to make Zoom’s own meeting livestream. OBS may be useful for a separate production or graphics workflow, but adding it without a clear role creates another signal path to troubleshoot. If your primary need is to publish a prepared video continuously rather than host a meeting, compare that process with a cloud playout workflow for a YouTube channel, which addresses a different kind of always-on programme.
Consider RTMP for eligible webinar setups
An incoming RTMP workflow can make sense when the programme is composed in OBS and needs to enter a Zoom webinar as a finished feed. It is not the default for every Zoom account, and it is not a synonym for Virtual Camera. Zoom Events documents incoming RTMP as a feature for integrating third-party streaming software into a webinar; its support page states the applicable Zoom app requirement and setup. Check current eligibility, account controls, and configuration before building a show around it.
This route suits a production team that already knows how to create its programme in OBS and has a webinar setup that supports the feature. It adds configuration and a need to monitor the feed entering the webinar. For a few remote guests who simply need to speak to one another, an ordinary meeting is usually the more direct starting point. Do not buy hardware or redesign the event around RTMP until you have confirmed that the specific account and event type can use it.
Existing studios may already have HDMI or SDI cameras, a switcher, and a finished audio mix. Zoom’s broadcasting guide describes capture hardware for bringing such a production into a streaming computer, including examples of HDMI and SDI capture devices. A USB HDMI capture card can be relevant when you need to convert an HDMI programme output for that computer; it is not a required purchase for a panel whose guests join remotely on Zoom.
The trade-off is between a prepared one-way programme and live interaction. Zoom’s broadcast hardware configuration is intended for broadcast and streaming; its warning about the lack of two-way communication applies to that configuration, not to every ordinary Zoom meeting. If guests must hear one another while the audience watches, design and test a separate return audio and display arrangement rather than assuming the broadcast path provides conversation. For a continuous prerecorded channel, the OBS and FFmpeg comparison for a church worship stream can help frame that separate decision.
Test audio, layout, and controls
Run a rehearsal with the host, co-host, OBS operator, and at least one person checking the receiving end. Use the same computers, cameras, microphones, and network connections planned for the event. Test the precise route you will use: OBS into Zoom, Zoom out to a destination, or eligible RTMP into a webinar. A successful test of one route does not verify another.
Use this short preflight:
- Confirm the host account can start the intended livestream and that the destination is configured.
- Confirm the OBS scene and Virtual Camera output mode, if that route is in use.
- Ask a participant to verify the picture and listen for echo, low level, or duplicated speech.
- Check the public destination or webinar view from a separate device, not only from the producer’s screen.
- Agree who starts and stops the broadcast, who watches the external output, and what to do if the connection drops.
- Keep a fallback scene and a way to tell guests what is happening if the producer needs time to recover.
Watch the whole chain rather than one status light. A camera can be active in OBS while Zoom is set to a different camera; Zoom can show the meeting while the public destination is still blank; and a video picture can work while audio is routed incorrectly. Have one person speak a test phrase and another report what arrives at the intended destination. If you make a change during the rehearsal, test the receiving end again.
For an event that must continue after the live hosts leave, separate the live discussion from the ongoing channel plan. OBS and Zoom are tools for producing or meeting; they do not by themselves turn a conversation into a hands-off 24/7 channel. A prepared, looping programme has its own requirements for source files, account access, and monitoring. StreamNeo can remove the need to leave a computer running for that specific uploaded-video-to-YouTube workflow, but it does not replace Zoom for interactive meetings and is YouTube-only.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Can OBS Virtual Camera send my Zoom meeting to YouTube?
No. OBS Virtual Camera sends OBS’s output into Zoom as a camera feed. To send a Zoom meeting outward, use an enabled Zoom livestream route or another appropriate production path.
Can a Zoom co-host start the livestream?
No. Zoom assigns the livestream start control to the meeting host, even if a co-host is helping with other meeting tasks. Arrange for the host to be present and responsible for that step.
Does every Zoom account support livestreaming or incoming RTMP?
No. Availability depends on account settings, administrator controls, destination configuration, and the specific feature or event type. Check Zoom’s current official guidance and your own account before relying on either route.
Do remote Zoom guests need a capture card to appear in OBS?
Not necessarily. A basic remote panel can meet in Zoom without HDMI or SDI capture hardware, but OBS’s Virtual Camera guide does not promise that every participant becomes an individually selectable OBS source. Test your capture approach, and buy a card only if your production actually has an external video output to capture.