A capture card showing no signal in OBS is one of the most frustrating problems for streamers and content creators. You fire up OBS Studio, add your video capture device, and instead of gameplay footage you see a black screen with “No Signal” staring back at you.
I have run into this exact issue more times than I would like to admit, both on my own setup and while helping our community on Free Stream Hosting troubleshoot their rigs. The good news is that most no signal errors come from a handful of common causes, and you can isolate the problem with a simple method of elimination.
In this guide I will walk you through nine tested fixes, starting with the easiest checks and moving toward advanced troubleshooting. By the end you will know exactly how to fix a capture card showing no signal in OBS, whether you are on Windows 11, Windows 10, or macOS, and whether you own an Elgato, AVerMedia, or a generic HDMI to USB capture card.
Table of Contents
- What does the OBS no signal error actually mean?
- Check your physical connections first
- Disable HDCP on your source device
- Verify Windows detects your capture card
- Fix the video capture device source in OBS
- Match resolution and refresh rate between source and capture card
- Close software that locks the capture card
- Test the capture card outside OBS to isolate the issue
- Advanced fixes for stubborn no signal problems
- Frequently Asked Questions
- Final thoughts on fixing a capture card showing no signal in OBS
What does the OBS no signal error actually mean?
When OBS shows no signal, it means the software has not received any video data from your capture card. The communication chain between your source device (console, camera, second PC), the capture card, and OBS is broken somewhere.
Three things must happen for a working video signal: the source must send a valid video stream, the capture card must successfully receive and decode that stream, and OBS must claim the device and render the frames. A failure at any point in that chain produces the same black screen and “No Signal” message.
That is why the troubleshooting steps below test each link in the chain one at a time. We start with the cheapest checks (cables and ports) and finish with hardware resets and firmware fixes. I have written it so you can stop at the first fix that solves your problem.
Check your physical connections first
Physical connection issues cause more OBS no signal errors than driver or software bugs. I always start here because it takes 30 seconds and fixes the problem roughly 40 percent of the time.
Inspect your HDMI cable and ports
HDMI cables can fail internally without showing any visible damage. If your capture card suddenly stopped working after months of use, the cable is a prime suspect. Unplug both ends of the HDMI cable, look for bent pins, and firmly reseat the connectors.
Make sure the source device is plugged into the HDMI IN port on the capture card, not the HDMI OUT or pass-through port. The pass-through port sends video to your monitor or TV; it does not send video into the capture card.
Try a different HDMI cable if you have one. Capture cards are sensitive to HDMI cable quality, especially for 4K or 1440p signals. Ultra High Speed HDMI cables rated for 48 Gbps are the safest pick for modern setups. Long cable runs over 3 meters also tend to cause signal drops.
Use a USB 3.0 port, not USB 2.0
This is the single most common mistake I see on our Free Stream Hosting community. Most capture cards require USB 3.0 (or USB 3.1/3.2) to pass enough bandwidth for uncompressed 1080p at 60Hz video. USB 2.0 simply cannot deliver the data fast enough, and the result is no signal or a stuttering feed.
USB 3.0 ports are usually blue inside or marked with the SS (SuperSpeed) symbol. Plug the capture card directly into a rear motherboard port, not into a front panel header, a USB hub, or a docking station. Front panel USB ports often provide less stable power, which is one of the top culprits in the streamer community.
If your laptop only has USB-C ports, use a USB-C to USB-A 3.0 adapter or a powered USB-C hub. Unpowered hubs and cheap pass-through docks will silently throttle the capture card.
Power on the source first
The capture card and OBS will not show a signal if the source device is off or in standby. Verify the console, camera, or second PC is fully booted and outputting a video signal before you start OBS. If you see the video fine on your pass-through monitor or TV, then the source is good and the problem lies downstream.
Disable HDCP on your source device
HDCP (High-bandwidth Digital Content Protection) is the single biggest gotcha for new streamers. HDCP is an anti-piracy protocol that blocks the video stream from being recorded. If your source device has HDCP enabled, the capture card will see a black screen and report no signal.
You need to disable HDCP on the source itself. Most modern consoles have this option buried in the settings, and the steps differ by platform.
How to disable HDCP on PS5
On PlayStation 5 go to Settings > System > HDMI > Enable HDCP. Toggle it off. Note that some 4K streaming apps will refuse to play in HDCP-off mode, but your capture card will work normally for games.
How to disable HDCP on Xbox Series X and Xbox One
On Xbox go to Settings > General > TV & display options > Video fidelity & overscan > Allow 4K > uncheck the option that says “Allow 4K” or set the display to 1080p. Some Xbox apps also have a hidden HDCP flag that gets reset on system updates, so check this every time you power on the console.
How to disable HDCP on Nintendo Switch
The Nintendo Switch does not have a user-facing HDCP toggle. HDCP is automatically disabled when the dock outputs to a non-HDCP display, so this is rarely the issue on Switch. If you suspect HDCP, try a different HDMI cable or test the Switch without the dock in handheld mode.
Camera and DSLR HDCP
Most cameras and HDMI output devices do not implement HDCP at all, so this is usually a console-only issue. If your camera source suddenly drops to black, check whether your camera has a clean HDMI output mode and whether any new firmware added HDCP.
Verify Windows detects your capture card
If cables and HDCP are correct, the next step is to confirm Windows actually sees the capture card. Open Device Manager (right-click the Start button and select Device Manager) and look under Sound, video, and game controllers. Your capture card should appear by name, such as Elgato Game Capture HD60, AVerMedia, or USB Video.
If the device shows up with a yellow warning triangle, Windows has detected a problem. Right-click the device, choose Update driver, and let Windows search for the latest driver. If the update fails, choose Uninstall device, unplug the capture card, reboot, and plug it back in so Windows reinstalls the driver fresh.
If the device does not appear at all, the issue is almost always USB bandwidth or power. Try every USB 3.0 port on your PC, ideally a rear port directly on the motherboard. Front panel headers and hubs frequently deliver unstable power that prevents the capture card from registering.
Reinstall the vendor driver cleanly
For stubborn driver issues, download the latest driver from the manufacturer’s website (Elgato, AVerMedia, Razer, etc.) and run their full installer with the capture card unplugged. Then reboot and plug the card in only after the driver has finished installing. This avoids Windows grabbing the wrong generic driver and locking out the vendor software.
Fix the video capture device source in OBS
Many OBS no signal errors are not actually signal errors at all. They are misconfigured sources. When you add a new source to a scene, OBS does not automatically pick the capture card. You have to choose it in the device dropdown.
Add a Video Capture Device source (not Display Capture, not Window Capture) by clicking the plus button in the Sources panel. In the properties window, open the Device dropdown and select your capture card from the list. If you see multiple entries, pick the one with the higher resolution and FPS, usually labelled with the card name.
Set the Resolution/FPS Type to Custom, then match the resolution and frame rate to your source output. If your console outputs 1080p at 60Hz, set OBS to 1920×1080 at 60fps. Mismatched values can produce a black screen even when the device is detected.
Click OK and you should see the video feed appear in the preview. If it stays black, right-click the source and choose Deactivate, then Activate. This forces OBS to renegotiate the device connection.
Match resolution and refresh rate between source and capture card
Resolution and refresh rate mismatches are a quiet cause of no signal errors. Not every capture card supports every resolution, and many older cards top out at 1080p at 60Hz. If your console is set to output 4K at 120Hz but your capture card only supports 1080p at 60Hz, OBS will show no signal.
Check your capture card’s supported resolutions on the manufacturer’s product page. Then go into your console’s display settings and force the output to a supported resolution, for example 1080p at 60Hz. The video will appear instantly in OBS once the resolutions match.
For PC sources, set the second PC’s display output to a standard resolution before streaming. Custom resolutions sometimes work, but the safest path is to match exactly what the capture card lists as supported.
Watch out for HDR and YUV422
Some capture cards, notably the Elgato Game Capture HD60 S+, do not support HDR or YUV422 color formats. If your source is set to HDR or 4:2:2 chroma, the capture card will fail to decode the stream and show no signal. Disable HDR in the source display settings and switch the color format to RGB or YUV420 if your capture card supports it.
Close software that locks the capture card
Only one program can hold a capture card’s data stream at a time. Discord, Zoom, OBS Studio, Streamlabs, the vendor capture software, and any video conferencing app will fight over the device. Whichever program locks the capture card first blocks all the others from accessing it.
Close every video and conferencing app before launching OBS. If you use Discord for voice chat, run it in a browser tab or on your phone instead of the desktop app. Zoom and Microsoft Teams are particularly aggressive about locking capture devices and rarely release them cleanly.
If a previous capture program crashed without releasing the card, restart the PC to clear the lock. This is the single fix that resolves the issue for roughly 20 percent of users in our support threads.
Test the capture card outside OBS to isolate the issue
If you have made it this far and still see no signal in OBS, the next step is to confirm the capture card works at all. Install the vendor’s capture software (Elgato 4K Capture Utility, AVerMedia RECentral, Razer Cortex, etc.) and try to view the video feed there.
If the vendor software shows a picture but OBS does not, the capture card is healthy and the problem is OBS-specific. You can fix this by resetting OBS scene cache, deleting the capture card source and re-adding it, or as a last resort, reinstalling OBS Studio cleanly.
If the vendor software also shows no signal, the problem is hardware or signal related. Work back through the cable, port, HDCP, and resolution checks until you find the broken link. This isolation step saves hours of guessing.
Advanced fixes for stubborn no signal problems
When the basic fixes do not work, there are a few advanced steps that resolve the remaining cases. These apply to specific hardware or firmware scenarios, so you can skip them if the simpler steps already restored your signal.
PCIe cold boot for internal capture cards
Internal PCIe capture cards such as the Elgato 4K60 Pro require a full cold boot any time the firmware updates. Shut down the PC completely (not a restart), unplug the power cable for 30 seconds, then plug it back in and boot. A warm reboot will not flash the new firmware and the card will not function until the cold boot completes.
Update the EDID on the capture card
EDID (Extended Display Identification Data) is the metadata your capture card uses to tell the source device what resolutions and refresh rates it supports. If the EDID is corrupted or out of date, the source may output a signal the capture card cannot handle. Most vendor capture utilities have an Update EDID option in the device settings. Run it, then unplug and replug the HDMI cable so the source re-reads the new EDID.
Reset the capture card to factory defaults
Some capture cards have a physical reset button or a software reset option in the vendor utility. Use it as a last resort before declaring the card defective. After the reset, plug the card into a rear USB 3.0 port, install the latest driver, and test with a single HDMI source before adding anything else.
Check whether the capture card is defective
After all of the above, if the capture card still shows no signal in OBS, in the vendor software, and on multiple cables and consoles, the card itself is likely defective. Look for warning signs: the card gets unusually hot, the LED status light does not power on, or the device disappears from Device Manager after a few minutes. Most reputable capture cards come with a 1 to 2 year warranty, so contact the vendor for a replacement.
Frequently Asked Questions
Why is OBS not detecting my capture card?
OBS often cannot detect a capture card because the device is plugged into a USB 2.0 port, a USB hub, or a front panel header that cannot deliver enough bandwidth. Try a rear USB 3.0 port directly on the motherboard, then reinstall the vendor driver and restart the PC before reopening OBS Studio.
Why does OBS say there is no signal?
OBS shows no signal when the capture card is not receiving a valid video stream from the source device. The most common causes are HDCP being enabled on the console, a failing HDMI cable, a resolution mismatch, or the source being plugged into the pass-through port instead of the HDMI IN port on the capture card.
How to fix OBS display capture not working?
Display capture not working is usually a different problem from a capture card no signal error. For Display Capture, run OBS as administrator, disable Game Mode in Windows, and uncheck the Capture Cursor option if it causes crashes. For a capture card, use a Video Capture Device source instead of Display Capture, and select the correct device in the dropdown.
When should I replace a capture card?
Replace a capture card after you have confirmed it works in the vendor software but not in OBS, after testing multiple working HDMI cables and USB 3.0 ports, and after the device gets unusually hot or disappears from Device Manager during use. If the card is still under warranty, contact the manufacturer for a replacement before buying a new one.
Final thoughts on fixing a capture card showing no signal in OBS
A capture card showing no signal in OBS almost always has a simple fix once you know where to look. Start with the cables, the USB port, and HDCP because those cover the majority of cases. Then work through drivers, OBS source configuration, and resolution matching until the signal returns.
If you try every fix in this guide and the capture card still shows no signal, the card is most likely defective and should be replaced. The method of elimination is your friend here, and testing the card in the vendor software will tell you quickly whether the problem is in OBS or in the hardware itself. For more streaming setup tips, the Free Stream Hosting Guides section has you covered.