7 Fixes for Capture Card OBS Won’t Detect (September 2026)

So your capture card won’t show up in OBS Studio, and you are staring at an empty Video Capture Device dropdown with no idea what went wrong. You are not alone. This is one of the most common problems streamers and content creators run into, whether they are using an Elgato HD60S+, a generic USB HDMI capture card, or an internal PCIe capture solution.

OBS Studio fails to detect a capture card as a video device when the card’s drivers are outdated or missing, another application is locking exclusive access to the device, the USB port lacks sufficient bandwidth, OBS settings are misconfigured, or system permissions are blocking OBS from accessing camera-class devices. The good news is that nearly every detection problem can be traced back to one of these root causes, and all of them have straightforward fixes.

In this guide, I will walk you through how to fix a capture card that OBS won’t detect as a video device. I have pulled solutions from OBS community forums, Reddit threads, real user reports, and my own testing across multiple capture cards and operating systems. Whether your card is completely invisible in OBS or shows up but displays a black screen, you will find the fix here. We will cover everything from quick 30-second checks to advanced troubleshooting with OBS log analysis and USB bandwidth diagnostics.

Quick Diagnostic Checklist: Start Here First

Before diving into detailed fixes, run through this rapid checklist. These are the most common solutions that resolve capture card detection issues in under five minutes.

1. Restart OBS Studio completely (not just minimize and reopen, fully quit and relaunch).
2. Unplug and replug the capture card into a different USB port, preferably a USB 3.0 port directly on the motherboard.
3. Close all other apps that might be using the capture card: Zoom, Discord, Teams, Skype, OBS Virtual Camera, browser tabs, or manufacturer software like Elgato 4K Capture Utility.
4. Check Device Manager (Windows) or System Information (Mac) to confirm the capture card is recognized by your operating system at all.
5. Open the Windows Camera app or Photo Booth on Mac and see if the capture card shows up there. If it works outside OBS, the problem is OBS-specific.
6. Update your capture card drivers from the manufacturer’s official website rather than relying on Windows Update.
7. Check Windows privacy settings under Settings > Privacy > Camera and make sure desktop apps like OBS are allowed to access cameras.
8. Try a different HDMI cable connected to the input side of the capture card.
9. Restart your computer after making any driver or USB changes.

If none of these quick checks solve the problem, do not worry. The detailed fixes below cover each of these areas and several more advanced scenarios.

Understanding the Problem: Not Detected vs Black Screen

One of the biggest mistakes I see people make is treating every capture card issue the same way. There are actually two very different failure modes, and they require completely different fixes. Understanding which one you are dealing with will save you hours of frustration.

Complete Detection Failure

This is when your capture card does not appear at all in the OBS Video Capture Device source dropdown. When you click the dropdown under Properties, there is nothing there, or you only see your webcam. This typically points to a driver issue, a USB connection problem, or a system permission block. Your operating system either does not recognize the device at all, or it recognizes it but has not registered it as a video input device that OBS can enumerate.

Black Screen (Device Detected But No Video)

This is when OBS detects the capture card in the dropdown, you can select it, but the preview shows nothing but a black screen. The device is communicating with OBS, but no video signal is coming through. This usually means there is a resolution or FPS mismatch, a problem with the HDMI input signal, or a buffering issue. Sometimes it also means the capture card is receiving a signal in a format OBS cannot decode by default, such as HDCP-protected content.

Figuring out which scenario applies to you is the first step toward a fix. If your card is completely invisible in OBS, start with Fix 1 through Fix 5. If you can see the card but get a black screen, jump to Fix 3 and Fix 6.

Fix 1: Update or Reinstall Capture Card Drivers

Outdated, missing, or incorrectly installed drivers are the number one reason OBS cannot detect a capture card. OBS relies on the operating system to enumerate video input devices using DirectShow on Windows or AVFoundation on Mac. If the capture card’s driver does not properly register the device as a video source, OBS will never see it.

Step-by-Step Driver Update on Windows

Open Device Manager by right-clicking the Start button and selecting Device Manager. Expand the “Sound, video and game controllers” section and the “Cameras” or “Imaging devices” section. Look for your capture card listed there. It might appear under a generic name like “USB Video Device” or under its brand name.

If you see a yellow exclamation mark next to the device, the driver is not working properly. Right-click the device, select “Update driver,” and choose “Browse my computer for drivers” to point it to the driver file you downloaded from the manufacturer. Do not rely on “Search automatically” because Windows Update often installs a generic UVC driver that does not fully support capture card features.

If updating does not work, right-click the device, select “Uninstall device,” check the box that says “Delete the driver software for this device” if available, then restart your computer. After the restart, install the manufacturer’s official driver fresh.

Brand-Specific Driver Sources

For Elgato capture cards (HD60, HD60S, HD60S+, 4K60 Pro), download the latest Game Capture software or 4K Capture Utility from elgato.com. Even if you plan to use OBS exclusively, installing Elgato’s software installs the proprietary USB driver that registers the device as a DirectShow video source. Multiple Mac users on the OBS forums confirmed that the HD60S simply will not appear in OBS on macOS without Elgato’s software installed, even though it works as a generic UVC device on Windows.

For AverMedia cards (Live Gamer Portable, Live Gamer 4K, AVerMedia Capture Card), download RECentral or the specific driver package from avermedia.com. AverMedia cards often require their own driver rather than the generic UVC driver to function properly in OBS.

For Razer Ripsaw, download the latest Ripsaw driver from razer.com. Razer Synapse may also need to be installed for the device to register properly.

For generic USB HDMI capture cards (often branded as UGREEN, or sold unbranded on Amazon and eBay), these typically use a standard UVC (USB Video Class) driver that Windows installs automatically. If yours is not being detected, try plugging it into a different USB port or using a tool like Zadig to check which driver is currently assigned to the device.

Fix 2: Close Software That May Be Locking the Capture Card

Capture cards are not designed for concurrent access. Only one application can use the device at a time. If another program has already claimed the capture card, OBS will either not detect it at all or will show an error saying the device is in use.

This is one of the most confusing problems because it is invisible. You might not realize that a background process is holding onto your capture card. I have seen cases where OBS could not detect a card simply because a browser tab had accessed it earlier through a web-based camera test tool.

Common Apps That Lock Capture Cards

• Zoom, Microsoft Teams, Skype, Google Meet – These video conferencing apps can claim camera devices, including capture cards, even when minimized.
• Discord – Discord can lock a capture card if it is set as a webcam source in Voice and Video settings.
• Elgato 4K Capture Utility, AverMedia RECentral – Manufacturer software that came with your card. If it is running, OBS cannot access the device.
• Browser-based camera tools – Any website that requests camera access can hold onto a capture card.
• OBS Virtual Camera – If you previously started the Virtual Camera feature in OBS and OBS crashed or was force-closed, the virtual camera process may still be running and locking the capture device.
• Windows Camera app – If you used the Camera app to test your capture card, close it completely before launching OBS.

To fix this, fully close all of the above applications. On Windows, open Task Manager (Ctrl + Shift + Esc) and look for any of these processes still running in the background. End any processes related to video conferencing or capture card software, then restart OBS.

A Reddit user shared a reliable workaround for stubborn locking issues: fully quit OBS, start a stream or recording for about 30 seconds with no capture card source, stop the stream or recording, then add the Video Capture Device source. This forces OBS to re-enumerate available devices and often makes the capture card appear.

Fix 3: Configure OBS Video Capture Device Settings Correctly

Even when OBS detects your capture card, incorrect settings can cause a black screen or poor performance. The Video Capture Device source in OBS has several configuration options that need to match what your capture card and input source are actually outputting.

Adding the Video Capture Device Source

Open OBS Studio. In the Sources panel at the bottom, click the plus (+) button and select “Video Capture Device.” Name it something recognizable like “Capture Card” and click OK. In the Properties window that appears, click the Device dropdown and see if your capture card is listed.

If it is not listed here, go back to Fix 1 and Fix 2. If it is listed but shows a black screen, continue with the settings below.

Resolution and FPS Type Settings

This is where most black screen issues get resolved. By default, OBS sets the Resolution/FPS type to “Device Default.” This means OBS asks the capture card what resolution and frame rate it wants to output, and tries to match it. The problem is that many capture cards report an incorrect default, especially generic USB cards.

Change the Resolution/FPS type from “Device Default” to “Custom.” Then manually set the Resolution and FPS to match your input source. For most console gameplay capture, this means 1920×1080 at 30 FPS or 1280×720 at 60 FPS. An OBS Forums user reported that their 1080p 30Hz capture card was completely failing because OBS was defaulting to 1080p 60Hz. Switching to Custom and setting 1920×1080 at 30fps immediately fixed the black screen.

If you are not sure what resolution and FPS your source outputs, check your console or device display settings. The PlayStation 5 and Xbox Series X typically output at 4K60 HDR or 1080p60. The Nintendo Switch outputs at 1080p60 in docked mode. Older consoles like the PS3 and Xbox 360 output at 720p or 1080i.

Video Format and Buffering

Under the Video Format dropdown, most capture cards default to MJPEG or YUYV. If you are getting a black screen or choppy video, try switching between these options. MJPEG is more bandwidth-friendly but compresses the image. YUYV (also called YUY2) provides better quality but requires more USB bandwidth.

If your video is stuttering or dropping frames, check the “Use buffering” option and set it to “Auto.” Buffering adds a small delay but smooths out frame drops caused by USB bandwidth limitations. A community expert on the OBS forums recommended enabling buffering for almost all USB capture cards, especially when connected through USB 2.0 ports.

The “Use hardware decoding when available” checkbox can also help with performance. If your system has a dedicated GPU, enabling hardware decoding offloads video processing from your CPU, which reduces frame drops and encoding load during streaming.

Fix 4: Check USB Port, Cable, and Hardware Connections

Hardware connection problems are surprisingly common and often overlooked. A capture card that is loose, connected to the wrong port type, or using a faulty cable will simply not be detected by OBS or your operating system.

USB 3.0 vs USB 2.0: Why It Matters

Most modern capture cards require a USB 3.0 port (also called USB 3.1 Gen 1 or USB 3.2 Gen 1). USB 3.0 provides up to 5 Gbps of bandwidth, which is necessary for uncompressed or lightly compressed 1080p video at 60 frames per second. USB 2.0 only provides 480 Mbps, which is not enough bandwidth for high-quality video capture.

If you plug a USB 3.0 capture card into a USB 2.0 port, one of three things will happen. The card may not be detected at all. It may be detected but show a black screen or heavy artifacts. Or it may work at reduced quality with significant frame drops and input lag.

USB 3.0 ports are usually marked with a blue plastic insert inside or an “SS” (SuperSpeed) logo next to the port. If you are using a desktop PC, prefer ports on the back of the computer that connect directly to the motherboard rather than front panel ports or USB hubs.

Avoid USB Hubs and Extensions

USB hubs, especially unpowered ones, are a frequent cause of capture card detection failures. A capture card needs both bandwidth and power. An unpowered USB hub splits both across multiple devices, which often leaves the capture card without enough of either. Always connect your capture card directly to a USB port on your computer.

If you absolutely must use a hub, use a powered USB 3.0 hub with its own AC adapter. Even then, direct connection is always better for capture cards.

Try a Different HDMI Cable

The HDMI cable connecting your video source to the capture card input is another common failure point. A damaged or low-quality HDMI cable can result in no signal, intermittent black screens, or flickering. Try swapping in a different HDMI cable, ideally one rated for 4K at 60Hz, even if you are only capturing 1080p.

Also make sure you are connecting the HDMI cable to the input port on the capture card, not the output or pass-through port. Many capture cards have both, and connecting to the wrong one will give you no signal.

Internal PCIe Capture Cards

If you are using an internal PCIe capture card (like the Elgato 4K60 Pro or AverMedia Live Gamer 4K) and it is not being detected at all, the card may not be properly seated in the PCIe slot. Power off your computer completely, open the case, remove the capture card, and reseat it firmly in the same or a different PCIe x4 or x16 slot. An OBS Forums user with an internal Solaris Japan SC-512N1-L card solved a total detection failure simply by reseating the card in a different PCIe slot.

You can use the free tool HWINFO to check whether your PCIe capture card is being detected by the motherboard at the hardware level. If HWINFO does not see it in the PCIe device list, you have a hardware seating or BIOS issue, not a driver problem.

Fix 5: Grant System Permissions for OBS

Operating system privacy settings can silently block OBS from accessing your capture card. This is especially common on Windows 11 and macOS, where camera access is locked down by default for security reasons. OBS may appear to function normally but simply not see the capture card in the device dropdown.

Windows 10 and Windows 11 Privacy Settings

On Windows, go to Settings > Privacy and Security > Camera. Make sure “Camera access” is turned on. Then make sure “Let apps access your camera” is also enabled. Scroll down further to “Let desktop apps access your camera” and verify that OBS Studio is listed and allowed.

One OBS Forums user on Windows 11 reported that OBS did not even appear in the camera app list, and the operating system showed no record of OBS attempting camera access in the Recent Activity section. If this happens, try running OBS as Administrator (right-click the OBS shortcut and select “Run as administrator”). This sometimes forces Windows to register OBS as a camera-capable application.

macOS Camera Permissions

On Mac, go to System Settings > Privacy and Security > Camera. Make sure OBS Studio is listed and the toggle next to it is enabled. If OBS is not listed, it may not have requested camera access yet. Delete OBS from the Applications folder, re-download the latest version from obsproject.com, and launch it fresh. macOS should then prompt you to grant camera access the first time you try to add a Video Capture Device source.

Antivirus and Firewall Interference

Antivirus software and firewalls can silently block OBS from communicating with your capture card. This is more common than most people realize. One guide from Wondershare’s DemoCreator confirmed that antivirus tools and firewall systems can prevent OBS from loading camera feeds.

To test whether your antivirus is the problem, temporarily disable it, then try adding the capture card source in OBS. If it works with the antivirus disabled, you have found the culprit. Add OBS to your antivirus exclusion or exception list, then re-enable your antivirus protection.

On Windows Defender, go to Windows Security > Virus and threat protection > Manage settings > Add or remove exclusions, and add the OBS Studio executable. For third-party antivirus like Norton, McAfee, or Bitdefender, check the manufacturer’s documentation for adding exceptions.

Fix 6: Adjust OBS Output and Source Settings

Sometimes the problem is not with the capture card itself but with how OBS is handling the video output. A few additional settings adjustments can resolve lingering detection or display issues.

Disable Power Saving for the Capture Card

Windows has a USB power saving feature that can turn off USB devices to save energy. This is a documented issue for UGREEN capture card users and many generic USB cards. Go to Device Manager, right-click your capture card under Universal Serial Bus controllers or Imaging devices, select Properties, go to the Power Management tab, and uncheck “Allow the computer to turn off this device to save power.”

Repeat this for all USB Root Hubs in Device Manager, because Windows can shut down the hub that your capture card is connected to even if the card itself is set to stay on.

Check OBS Output Settings

Go to Settings > Output in OBS. If your output mode is set to Simple, try switching to Advanced. In the Advanced output mode, check the Video Encoder setting. If you are using a hardware encoder (like NVENC for NVIDIA GPUs or AMF for AMD GPUs), make sure your GPU drivers are up to date. Encoder failures can sometimes cascade into source display failures.

OBS Restart Workaround

If nothing else works, there is a reliable workaround that multiple Reddit and forum users have confirmed. Fully close OBS Studio. Reopen OBS and start a stream or recording for 30 seconds. Stop the stream or recording. Then add your Video Capture Device source. This process forces OBS to fully initialize its video pipeline before trying to enumerate devices, which often resolves detection failures.

Advanced Troubleshooting

If you have worked through Fixes 1 through 6 and your capture card still is not being detected, it is time to dig deeper. The following advanced diagnostic methods will help you pinpoint exactly what is going wrong.

Verify the Capture Card in Device Manager

Device Manager is your first and most important diagnostic tool. Open Device Manager and check these three sections: “Sound, video and game controllers,” “Imaging devices” (or “Cameras” in Windows 11), and “Universal Serial Bus controllers.”

Your capture card should appear in at least one of these sections. If it appears with a yellow triangle warning icon, the driver is not installed correctly or has encountered an error. Right-click it, select Properties, and check the Device status box under the General tab for an error code.

If the capture card does not appear anywhere in Device Manager, Windows is not detecting the hardware at all. This points to a physical connection problem, a dead USB port, a faulty capture card, or (for PCIe cards) an improperly seated card or a BIOS configuration issue.

Verify the Capture Card Outside OBS

Before blaming OBS, confirm that your capture card actually works in other software. On Windows, open the built-in Camera app and check if the capture card appears in the camera switcher. On Mac, open Photo Booth or QuickTime Player and select the capture card as the camera source.

If the capture card works in the Camera app but not in OBS, you are dealing with an OBS-specific issue. This usually means a software conflict, a permissions problem, or an OBS settings misconfiguration. Revisit Fix 2 (software conflicts) and Fix 5 (permissions) carefully.

If the capture card does not work in any software, the problem is at the driver, hardware, or operating system level. Focus on Fix 1 (drivers) and Fix 4 (hardware connections).

Read Your OBS Log Files

OBS automatically generates a log file for every session. This log contains detailed information about what devices OBS tried to enumerate, what errors it encountered, and what settings it applied. Learning to read your OBS log is the most powerful diagnostic tool available.

To access your log files, open OBS Studio, click Help in the top menu, and select “Log Files” then “View Current Log.” The log will open in your default text editor. Look for lines containing “video capture device,” “DirectShow,” “DShow,” or the name of your capture card.

Common log entries to watch for include errors like “Failed to start capturing” (which usually means a driver or permissions problem), “Device not found” (which means OBS could not enumerate the device at all), or “No signal” (which means the device was found but is not receiving an HDMI input signal).

If you see a line mentioning a specific resolution or FPS value that does not match your capture card, that is likely your problem. The OBS Forums community uses log analysis as their primary diagnostic method, and expert users like Suslik V regularly provide resolution and FPS corrections based on log output.

Use USB Device Tree Viewer for Bandwidth Diagnosis

USB Device Tree Viewer (also called USBTreeView) is a free Windows tool that provides detailed information about every USB device and port on your system. It shows whether your capture card is connected at USB 3.0 speeds or has fallen back to USB 2.0, how much bandwidth it is using, and whether there are any USB power issues.

Download USB Device Tree Viewer from uwe-sieber.de. Run it and look for your capture card in the device tree. Check the “Speed” field to confirm it shows “SuperSpeed” (USB 3.0) rather than “High Speed” (USB 2.0). If it shows High Speed despite being plugged into a blue USB 3.0 port, the port, cable, or capture card may be faulty.

The tool also shows USB power draw. If your capture card is drawing more power than the port can provide, it may intermittently disconnect or fail to be detected. This is common with unpowered USB hubs and front panel ports on some desktop cases.

Brand-Specific Capture Card Troubleshooting

Different capture card brands have their own quirks. Here are the most common brand-specific issues and solutions I have encountered and found in community discussions.

Elgato (HD60, HD60S, HD60S+, 4K60 Pro)

Elgato is the most popular capture card brand, but its cards have specific requirements. On Windows, Elgato cards generally work as UVC devices, but installing the official 4K Capture Utility or Game Capture HD software ensures the proprietary driver is properly registered. On Mac, the Elgato software must be installed even if you only use OBS, because it includes the USB driver that registers the HD60S and HD60S+ as video sources.

The HD60S+ has a known issue with HDR content. If your console is outputting HDR, the capture card may show a black screen or distorted colors in OBS. Go into your console settings and disable HDR output to test whether this is the problem.

AverMedia (Live Gamer Portable, Live Gamer 4K)

AverMedia cards require their own driver package rather than the generic UVC driver. Download RECentral or the standalone driver from avermedia.com. The Live Gamer Portable II has a PC-Free mode that can interfere with OBS detection. Make sure the mode switch on the card is set to PC mode, not PC-Free recording mode.

Razer Ripsaw

The Razer Ripsaw HD requires Razer Synapse to be installed for the device driver to register properly. If Synapse is not running or is outdated, OBS may not detect the Ripsaw. Update Synapse through Razer’s website and restart your computer after installation.

Generic USB Capture Cards (UGREEN and Unbranded)

Generic USB HDMI capture cards, including those sold by UGREEN and many unbranded sellers, use the standard UVC driver. They should work without additional drivers on Windows 10 and 11. However, they are particularly sensitive to USB power management settings and USB 2.0 connections. UGREEN capture card users on Facebook groups reported that disabling USB power saving mode in Windows Settings resolved detection failures.

These generic cards also frequently report incorrect resolution and FPS defaults. Always set the Resolution/FPS type to Custom in OBS and manually specify the correct values for your input source.

USB vs PCIe Capture Card: Troubleshooting Differences

The troubleshooting approach differs significantly depending on whether you are using an external USB capture card or an internal PCIe capture card. Here is a quick comparison of the key differences.

USB capture cards are more prone to connection and bandwidth issues. Common problems include USB 2.0 bandwidth limitations, USB hub power delivery failures, cable faults, and power saving interference. The fixes focus on port selection, cable quality, and power management settings. USB cards are also more susceptible to concurrent access locking by other software.

PCIe capture cards are more prone to hardware seating and BIOS issues. If a PCIe card is not detected at all, the first step is always to reseat the card in the slot. Check BIOS settings to make sure the PCIe slot is enabled and not disabled for power saving. Use HWINFO to confirm the card is being detected at the hardware level. PCIe cards generally do not have USB bandwidth or power issues, but they can have driver conflicts if multiple capture cards are installed on the same PCIe bus.

For both types, driver installation is the critical first step. But USB cards add a layer of physical connection troubleshooting that PCIe cards do not require, while PCIe cards add BIOS and slot-level diagnostics that USB cards skip entirely.

FAQs

Conclusion

Fixing a capture card that OBS won’t detect as a video device comes down to a methodical process of elimination. Start with the quick diagnostic checklist, determine whether you are dealing with a complete detection failure or a black screen, then work through the fixes in order. Driver updates, software conflict resolution, OBS Video Capture Device settings, USB port selection, and system permissions cover the vast majority of cases.

If you have tried every fix in this guide and your capture card still will not show up, the card itself may be defective. Test it on another computer if possible. If it fails on a second machine, contact the manufacturer for a warranty replacement. For capture cards that work on another computer but not yours, the issue is likely at the motherboard or operating system level, and a clean Windows reinstall or a BIOS update may be necessary.

The most important takeaway: always verify whether your capture card appears in Device Manager and works in the Windows Camera app before spending hours troubleshooting OBS. Knowing exactly where the detection chain breaks will save you time and point you directly to the right fix.