How to Fix OBS Virtual Camera Not Working?
OBS Virtual Camera may fail to appear in Zoom, Google Meet, Discord, Teams, or browser-based calls. In other cases, it appears but opens to a black, frozen, green, or wrong-scene feed.
This is what makes the issue confusing. OBS itself may look normal and the scene may keep moving inside the program, while the receiving app still fails to detect the camera correctly or render the feed it receives.
The problem is usually caused by app launch order, the selected virtual-camera output, camera-permission settings, or a damaged virtual-camera registration.
1. Start OBS Virtual Camera Before Opening the Meeting App
Many meeting apps cache the camera list at launch. If OBS Virtual Camera starts after the app is already open, that app can keep stale device state and never refresh correctly.
This is also why some sessions keep defaulting back to the hardware webcam even after you switch to OBS in settings.
- In OBS, make sure the scene you want is visible, then click Start Virtual Camera in the Controls dock.
The meeting app should see the virtual camera after OBS has already started broadcasting it. - Fully close the target app or browser, not just the meeting tab. If it stays in the system tray, quit it from there too.
- Open the app again, go to Camera or Video settings, and manually choose OBS Virtual Camera.
Many meeting apps keep an old camera list until they are fully closed and reopened.
If OBS Virtual Camera appears and the preview moves normally, this part is resolved. If the camera is listed but the feed is blank or stuck, adjust the OBS output target next.
2. Change the OBS Virtual Camera Output Back to Program
When the camera appears but the image is black, frozen, or stuck on the wrong scene, OBS is often publishing a different output target than expected.
OBS can route virtual camera to Program, Preview, one Scene, or one Source. For most users, Program is the safest default because it follows the live output.
- In OBS, click the gear beside the virtual camera controls and open output settings.
If the camera appears but the feed is wrong, the output target inside OBS is often the real problem. - Set virtual camera output to Program unless you intentionally need Preview, one fixed Scene, or one fixed Source.
- Check the Program view and confirm the scene has a visible source, is not hidden, and is not parked on an empty preview.
- Stop the virtual camera, start it again, then reopen the app preview.
If the preview now follows your live scene, the output selection was the problem. If apps still report camera access errors, review OS permissions.
3. Turn On Camera Access for Desktop Apps in Windows
On Windows, OBS, browsers, Teams, and many meeting apps are treated as desktop apps. If desktop camera access is off, OBS Virtual Camera may never open correctly in the receiving app.
Before retesting, close any camera app, browser tab, or webcam utility that may still hold old camera state.
- Go to Settings > Privacy & security > Camera in Windows.
Browsers, Teams, and many conferencing apps are treated as desktop apps and need the desktop camera toggle enabled. - Turn on Camera access and Let desktop apps access your camera.
- Close Camera, Teams, Zoom, browser tabs, and any webcam utility app that might still be open, then launch OBS and the target app again.
When the camera chain is already busy or permissions are stale, a clean reopen works better than switching cameras inside a half-running app.
If OBS Virtual Camera appears after this reset, Windows privacy state was the immediate cause. If Windows cannot detect your physical webcam in normal apps either, use this Windows webcam guide before continuing with OBS-specific repair.
4. Reapprove the Virtual Camera Component on Mac and Update OBS
On Mac, virtual-camera failures often appear after a macOS update when the extension is not fully approved or the OBS version is no longer compatible with the current macOS build.
OBS states that virtual camera in OBS 29.1 and earlier is not compatible with macOS 14 Sonoma. OBS 30 and newer use the newer component path for Ventura and later.
- Update OBS Studio to a current release before changing anything else on macOS 13 or newer.
- Open System Settings > Privacy & Security and approve the blocked OBS virtual camera component where macOS shows it. On newer versions, that may be under Security or Camera Extensions.
On modern macOS versions, the virtual camera often fails until the OBS system extension is explicitly approved. - Still in Privacy & Security, open Camera and make sure both OBS and the receiving app are allowed to use the camera.
OBS and the app receiving the virtual camera both need camera access on macOS. - Restart OBS and the target app after approving the component.
If the camera still fails in Zoom after this while your regular webcam also fails there, use this broader Zoom camera guide before further OBS changes.
5. Repair the Virtual Camera Install or Fix ARM64 and Legacy Conflicts
If virtual camera never appears anywhere after restart and permission checks, repair the registration layer next.
On Windows, OBS includes an install script for the built-in virtual camera. On Windows on Arm, native ARM apps may not detect the older x64 registration path.
Legacy third-party OBS virtual-camera plugins can also leave duplicate devices such as OBS-Camera, OBS-Camera2, and OBS Virtual Camera, which can create selection problems in meeting apps.
- Close OBS and the app you are trying to use with the virtual camera.
- In File Explorer, go to C:\Program Files\obs-studio\data\obs-plugins\win-dshow, right-click virtualcam-install.bat, and choose Run as administrator.
If the virtual camera never appears, re-registering it is the quickest repair path on Windows. - Restart OBS and the receiving app, then test OBS Virtual Camera again.
- If you are on a Windows ARM PC and native ARM apps still cannot see the camera, follow OBS ARM64 instructions to switch registration from the x64 virtual-camera DLL to the ARM64 one.
- If an old virtual-camera plugin is still installed, remove its legacy devices and keep built-in OBS Virtual Camera as the only one you use.
If OBS Virtual Camera works in one app but fails only on one browser-based service, the remaining issue is usually site-side or browser-side compatibility rather than a broken OBS virtual-camera device.
