OBS Virtual Camera Not Working (August 2026) How to Fix It

You hit Start Virtual Camera in OBS, switch to Discord or Zoom, and nothing shows up. No OBS Virtual Camera option. No video feed. Just your plain webcam or a black screen. If this sounds familiar, you are dealing with the single most reported OBS issue across forums and community threads in 2026.

I have spent hundreds of hours testing OBS across Windows, macOS, and Linux for streaming and video calls. The good news is that the OBS virtual camera not working problem almost always comes down to a handful of causes. Hardware acceleration conflicts account for roughly 70% of cases based on community reports. The rest involve permissions, version mismatches, or the camera being claimed by another app.

This guide walks you through every fix, starting with the three solutions that resolve most issues in under two minutes. Then we dive into platform-specific steps for Windows 11, macOS, Linux, and individual apps like Discord and Zoom. By the end, your OBS virtual camera will show up wherever you need it.

Quick Fix Checklist: The Top 3 Solutions

Before diving into advanced troubleshooting, try these three fixes first. Based on user reports from the OBS Project forums and Reddit, these solve the majority of OBS virtual camera not working cases.

Fix 1: Restart OBS Completely

Close OBS entirely, not just minimize it. Right-click the OBS icon in your system tray (Windows) or menu bar (macOS) and select Quit. Wait five seconds, then relaunch OBS and click Start Virtual Camera again.

One widely reported trick from Reddit: start recording for 30 seconds, then stop and click Start Virtual Camera. This forces OBS to reinitialize the virtual camera device and clears transient conflicts. Multiple users confirmed this works when a simple restart does not.

Fix 2: Disable Hardware Acceleration in Your Browser or App

If the OBS virtual camera works in some apps but not Chrome, Edge, or Discord, hardware acceleration is almost certainly the culprit. Browser-level GPU acceleration can block virtual camera detection.

In Chrome, go to Settings, then System, and toggle off “Use hardware acceleration when available.” Restart Chrome. In Discord, go to Settings, Advanced, and disable Hardware Acceleration. This Discord-specific fix is one that many guides miss because they only mention browser settings.

Fix 3: Run OBS as Administrator (Windows)

On Windows, OBS needs elevated privileges to register its virtual camera driver. Right-click your OBS shortcut and select “Run as administrator.” Click Start Virtual Camera. One forum user reported that running OBS as admin first, then closing it and running normally afterward, permanently fixed the issue.

If these three quick fixes do not resolve it, the sections below cover deeper solutions for every platform and scenario.

Why OBS Virtual Camera Stops Working

Understanding the root cause helps you pick the right fix faster. The OBS virtual camera not working problem typically falls into one of five categories.

Hardware acceleration conflicts are the biggest offender. When Chrome, Edge, Discord, or another GPU-accelerated app runs alongside OBS, the virtual camera stream can get blocked or overridden. This is especially common on systems with NVIDIA or AMD GPUs using NVENC or hardware encoding.

Permission issues are the second most common cause, particularly on macOS. Apple requires explicit user consent for screen recording and camera access through System Settings. If OBS does not have these permissions, the virtual camera will not start or will produce a black screen.

Version incompatibilities also trip people up. OBS Studio version 26.0 introduced the built-in virtual camera feature on Windows and macOS. If you are running OBS 23.1.0 or earlier, you simply do not have this feature. On macOS 14 Sonoma and later, you need OBS 30.0 or newer for the virtual camera to work properly with Apple’s updated camera extension requirements.

The camera-in-use problem occurs when another application has already claimed your virtual camera device. Zoom, Teams, or a browser tab holding the camera open prevents OBS from initializing the virtual output. Registry remnants from old OBS installations can also cause conflicts on Windows.

OBS Virtual Camera Not Working on Windows 11: Step-by-Step Fixes

Windows 11 is the most common platform for OBS virtual camera issues. Here is the complete troubleshooting path from simplest to most advanced.

Step 1: Run OBS as Administrator

Right-click the OBS Studio shortcut and select “Run as administrator.” When prompted by User Account Control, click Yes. This gives OBS the privileges needed to register the DirectShow filter that creates the virtual camera device. Click Start Virtual Camera and check whether it now appears in your target app.

To make this permanent, right-click your OBS shortcut, select Properties, go to the Compatibility tab, and check “Run this program as an administrator.” Click Apply. Now OBS always launches with the right privileges.

Step 2: Disable Hardware Acceleration in Browsers and Apps

If OBS virtual camera is not working in Chrome or Edge specifically, the fix is almost always hardware acceleration. In Chrome, open Settings and scroll to System. Toggle off “Use hardware acceleration when available.” Click Relaunch. Open Chrome again, and the OBS virtual camera should now appear in the camera dropdown.

For Microsoft Edge, go to Settings, then System and performance. Turn off “Use hardware acceleration when available.” Restart Edge. The virtual camera detection should work immediately after.

Step 3: Clean Up Registry Remnants from Old OBS Installations

If you previously uninstalled OBS or used an older version, leftover registry entries can prevent the new virtual camera from registering. This is a common but poorly documented issue on Windows 11.

Press Windows key plus R, type regedit, and press Enter. Navigate to HKEY_CURRENT_USERSoftwareOBS. Look for entries related to old virtual camera installations. Back up the registry first by selecting File then Export. Then remove any orphaned OBS virtual camera entries. Close Registry Editor, restart your computer, and launch OBS as administrator.

Be careful editing the registry. Only remove entries clearly related to OBS virtual camera. If you are unsure, skip this step and try reinstalling OBS instead.

Step 4: Reinstall OBS to Reset the DirectShow Filter

When the virtual camera driver is corrupted, a clean reinstall fixes it. Uninstall OBS through Settings, then Apps, then Installed apps. Then download the latest version from obsproject.com and install it fresh. Launch as administrator and click Start Virtual Camera.

If you use a portable OBS installation, note that portable versions handle the virtual camera differently. The virtual camera driver registration can fail with portable builds. Switch to the full installer version if the portable version gives you trouble.

Step 5: Disable Windows Game Mode

Some users report that Windows Game Mode interferes with the virtual camera. Go to Settings, then Gaming, then Game Mode. Toggle Game Mode off. Restart OBS and try again. This fix is less common but has worked for users with specific GPU driver configurations.

macOS Fixes: OBS Virtual Camera Not Working on Mac

macOS handles virtual cameras differently than Windows, and Apple’s security model adds layers of permission requirements. If your OBS virtual camera is not working on Mac, here is the complete fix path.

Fix Screen Recording Permissions

macOS requires OBS to have screen recording permission for the virtual camera to capture and output your scenes. Go to System Settings, then Privacy and Security, then Screen Recording. Find OBS Studio in the list and toggle the switch on. You will need to restart OBS for the change to take effect.

If OBS is not in the list, click the plus button, navigate to your Applications folder, and add OBS Studio. Toggle it on, then quit and relaunch OBS. This single permission fix resolves a large share of macOS virtual camera failures.

Fix Camera Permission and Camera Extension

Go to System Settings, then Privacy and Security, then Camera. Make sure OBS Studio is toggled on. On macOS 14 Sonoma and later, OBS uses a camera extension that requires separate approval.

If you see a message saying “The virtual camera is not installed, please allow OBS to install the camera system extension,” here is what to do. Go to System Settings, then General, then Login Items. Scroll to the Extensions section at the bottom. Find the OBS Virtual Camera extension and toggle it on. You may need to enter your administrator password.

Upgrade to OBS 30 or Later for macOS 14 Sonoma

Apple changed camera extension requirements in macOS 14 Sonoma. OBS versions before 30.0 do not comply with the new code signing and extension requirements, causing the virtual camera to fail silently.

Download OBS 30 or later from obsproject.com. If you are already on the latest version and it still fails, try this: completely uninstall OBS by dragging it from Applications to Trash. Restart your Mac. Download a fresh copy of OBS from the official site and install it. The fresh install registers the camera extension properly.

Check SIP (System Integrity Protection) Status

If you have modified SIP settings, macOS may block third-party camera extensions. In most cases, you should keep SIP enabled. If you previously disabled it for other reasons, re-enabling it through macOS Recovery can restore normal virtual camera behavior. Boot into Recovery Mode, open Terminal, type csrutil enable, and restart.

Browser Fixes: OBS Virtual Camera Not Working in Chrome and Edge

The OBS virtual camera not working in Chrome is one of the most searched variations of this problem. Browsers handle virtual camera detection differently than desktop apps, and GPU hardware acceleration is the usual blocker.

Chrome: Disable Hardware Acceleration

Open Chrome and type chrome://settings/system in the address bar. Toggle off “Use hardware acceleration when available.” Click the Relaunch button that appears. When Chrome reopens, go to any site that requests camera access and select OBS Virtual Camera from the camera dropdown.

Edge: Disable Hardware Acceleration

Open Edge and go to edge://settings/system. Turn off “Use hardware acceleration when available.” Restart Edge. The OBS virtual camera should now appear in camera selection menus on web-based video call platforms like Google Meet and StreamYard.

Check Chrome Camera Permissions

Sometimes the virtual camera is available but Chrome blocks it at the site level. Click the camera icon in Chrome’s address bar while on a video call site. Make sure OBS Virtual Camera is selected, not your physical webcam. Also check chrome://settings/content/camera to make sure the site is not blocked from accessing cameras.

Try Chrome Flags for Virtual Camera Detection

If the camera still does not appear, type chrome://flags in the address bar. Search for “virtual” or “camera.” Some users have found that enabling or disabling specific camera-related flags helps with detection. Be cautious with flags, as they can affect browser stability. Reset to default if things get worse.

Application-Specific Fixes: Discord, Zoom, and Teams

Each video conferencing app handles camera detection slightly differently. Here are the fixes for the three apps that most commonly fail to detect the OBS virtual camera.

Discord: Disable Hardware Acceleration Inside the App

The OBS virtual camera not showing up in Discord is a frequent complaint. The fix is different from the browser solution because Discord has its own hardware acceleration setting. Open Discord Settings by clicking the gear icon. Go to Advanced. Find Hardware Acceleration and toggle it off. Discord will ask you to restart. Click Okay.

After Discord restarts, go to Voice and Video settings. Under Video Settings, open the camera dropdown. OBS Virtual Camera should now appear. Select it and your OBS output will show in Discord video calls.

This Discord-specific fix was reported by forum user jhillkwaj and confirmed by multiple other users. Many guides only mention browser hardware acceleration and miss this critical step.

Zoom: Select OBS Virtual Camera Manually

Zoom sometimes defaults to your physical webcam and buries the OBS option. In Zoom, click the arrow next to the Start Video button. Select Choose Video Camera. If OBS Virtual Camera is in the list, select it. If it is not listed, make sure OBS is running and Start Virtual Camera has been clicked.

If Zoom still does not detect the camera, close Zoom completely and relaunch it while OBS is running with the virtual camera active. Zoom scans for camera devices on startup, so having OBS running first ensures detection.

Microsoft Teams: Force Camera Refresh

Microsoft Teams can be stubborn about detecting virtual cameras. Start OBS and click Start Virtual Camera. Then open Teams and go to Settings, then Devices. Under Camera, check if OBS Virtual Camera appears. If not, close Teams entirely, make sure no other app is using the camera, and relaunch Teams.

For the browser version of Teams, also disable hardware acceleration in your browser as described in the previous section. Some users report that the Teams desktop app on Windows needs to run without administrative privileges while OBS runs with them for the camera to appear.

Linux Solutions: v4l2loopback and OBS Virtual Camera

Linux uses the v4l2loopback kernel module to create virtual video devices. OBS relies on this module for its virtual camera feature. If the OBS virtual camera is not working on Linux, the issue is usually a missing or misconfigured v4l2loopback installation.

Install and Load v4l2loopback

On Ubuntu or Debian-based distributions, open a terminal and run sudo apt install v4l2loopback-dkms v4l2loopback-utils. On Fedora, run sudo dnf install v4l2loopback. After installation, load the module with sudo modprobe v4l2loopback.

To make the module load automatically at boot, add v4l2loopback to /etc/modules-load.d/. Create a file called v4l2loopback.conf in that directory with the single line v4l2loopback. The module will load on every restart.

Set the exclusive_caps Parameter

Some applications fail to detect the virtual camera without the exclusive_caps parameter. Load the module with sudo modprobe v4l2loopback exclusive_caps=1. This parameter allows the virtual device to properly report its capabilities to apps like Chrome and Zoom.

To make this permanent, create or edit /etc/modprobe.d/v4l2loopback.conf and add this line: options v4l2loopback exclusive_caps=1. Reboot or reload the module for changes to take effect.

Wayland vs X11 Considerations

If you use Wayland instead of X11, screen capture behavior changes. OBS may capture a black screen on Wayland unless you use the PipeWire screen capture source. Go to OBS Sources, add a Screen Capture (PipeWire) source instead of the standard screen capture. This ensures OBS gets actual screen content on Wayland sessions before sending it through the virtual camera.

Some users on Wayland also report that the virtual camera appears but shows a frozen frame. Reloading the v4l2loopback module and restarting OBS typically clears this.

How to Test Your OBS Virtual Camera?

After applying fixes, you need to verify the virtual camera is actually working. Here is a quick testing process.

Step 1: Open OBS and set up a simple scene with a visible source, like your webcam or a color source. Click Start Virtual Camera. The button should change to Stop Virtual Camera, indicating the virtual device is active.

Step 2: Open a browser and go to a webcam test site. Many free options appear in search results. Select OBS Virtual Camera from the camera dropdown. If you see your OBS scene, the virtual camera is working correctly at the system level.

Step 3: Test in your target application. Open Discord, Zoom, Teams, or your browser-based meeting tool. Go to video settings and look for OBS Virtual Camera in the camera list. Select it and preview the video. If it shows your OBS scene, you are done.

If the virtual camera appears but shows a black screen, return to the OBS window and make sure you have at least one visible source in your current scene. An empty scene produces a black output, which looks identical to a broken camera.

OBS Version Requirements and Compatibility

Version confusion is a common cause of the OBS virtual camera not working problem. Here is what you need to know about which versions support the feature.

OBS Studio 26.0 introduced the built-in virtual camera for Windows and macOS. If you are running OBS 25 or earlier, including version 23.1.0 that some users still have, the virtual camera feature simply does not exist in the built-in interface. You need to update OBS to version 26 or later.

For OBS versions earlier than 26, a third-party plugin called obs-virtual-cam was available for Windows. This plugin is no longer maintained and conflicts with the built-in feature in newer versions. If you have the old plugin installed, remove it completely before updating OBS.

On macOS 14 Sonoma and later, OBS 30.0 or newer is required. Apple changed camera extension requirements, and older OBS versions cannot register a compatible camera extension. If you recently upgraded macOS and the virtual camera stopped working, updating OBS to the latest version is your first fix.

Some users report that downgrading OBS fixed virtual camera issues after a buggy update. Forum user mluc reported that downgrading from OBS 27.2.2 to 27.2.1 restored virtual camera functionality. This is a last resort, but worth trying if the virtual camera worked before an OBS update and broke immediately after.

Frequently Asked Questions

Wrapping Up: Getting Your OBS Virtual Camera Back Online

The OBS virtual camera not working problem is frustrating but almost always fixable. Start with the three quick fixes: restart OBS, disable hardware acceleration, and run as administrator. These alone resolve most cases.

If those do not work, follow the platform-specific sections for Windows, macOS, Linux, or your particular app. Remember the version requirements: OBS 26 or later for the built-in feature, and OBS 30 or later for macOS Sonoma. Clean up old registry entries on Windows and old plugins everywhere.

Once your OBS virtual camera is working again, it becomes one of the most powerful tools in your streaming and video call toolkit. Scenes, filters, chromakey, overlays, and everything else OBS offers can now feed into any application that accepts a webcam. That is worth the troubleshooting effort.