Why Does My Capture Card Show No Signal in OBS? (September 2026) Fix Guide

You plug in your capture card, fire up OBS Studio, add your Video Capture Device source, and instead of your gameplay you see the dreaded “No Signal” message. If you are wondering why does my capture card show no signal in OBS, you are not alone. This is one of the most common issues streamers and content creators face, and the good news is that most causes are fixable in under 10 minutes.

A “No Signal” message means your capture card is powered on and recognized by your computer, but it is not receiving a valid video feed from your source device. The capture card is essentially saying, “I am here, but I do not see anything to capture.” This is different from a black screen, which usually means the signal is arriving but is being blocked or scrambled, often by HDCP encryption.

In my experience testing capture cards across PS5, Xbox Series X, Nintendo Switch, and PC setups, the no-signal problem almost always traces back to one of a handful of causes: a swapped HDMI cable, HDCP blocking the feed, a USB 2.0 port instead of USB 3.0, a resolution mismatch, or an OBS source that needs to be recreated from scratch. I have spent hours debugging each of these myself, and this guide walks through every fix in the order that works for the most people.

If you are new to streaming and need a complete streaming setup guide for beginners, understanding how capture cards integrate into your overall rig will help you avoid many of the issues covered here.

By the end of this article, you will know exactly how to fix no signal on your capture card in OBS, regardless of whether you are using an Elgato HD60 X, HD60 S+, Cam Link, a generic USB capture card, or a PCIe internal capture card. I will also cover how to prevent the issue before your next stream and how to tell if your capture card is actually defective versus just misconfigured. For a broader overview of the best capture cards for streaming, check our comparison guide.

Quick Troubleshooting Checklist: Top Fixes Ranked by Success Rate

If you want the fastest path to a fix, start with these five solutions. I have ranked them based on community success rates from forum threads, support articles, and my own testing across dozens of capture card setups. These are the fixes that resolve the no-signal problem for the largest percentage of users. This is the most common question: why does my capture card show no signal in OBS, and the answer is almost always one of these five causes.

1. Check your HDMI In and HDMI Out ports. The most common cause of no signal is plugging the HDMI cable from your console into the wrong port on the capture card. The cable from your console or PC must go into the HDMI In port, and the cable to your TV or monitor must go into HDMI Out. Swapping these two ports produces an instant no-signal message.

2. Disable HDCP on your console. PS5, Xbox, and other devices use HDCP encryption to prevent unauthorized recording. Capture cards cannot decrypt HDCP, so the video is blocked. Disabling HDCP on your console fixes no signal for a large percentage of users, especially after console firmware updates that re-enable HDCP.

3. Switch to a USB 3.0 port. USB capture cards require USB 3.0 bandwidth to process video. Plugging into a USB 2.0 port causes no signal, black screen, or severe signal degradation. Look for the blue plastic insert inside the port or the “SS” symbol next to it.

4. Replug the HDMI cables. Sometimes the HDMI handshake fails during initial connection. Unplug both HDMI cables from the capture card, wait five seconds, and plug them back in firmly. This simple reset resolves intermittent signal loss surprisingly often.

5. Delete and recreate the OBS source. Remove the Video Capture Device source from your OBS scene and add it again from scratch. This forces OBS to re-detect the capture card and re-establish the video pipeline, fixing issues that persist even when the hardware is working correctly.

If none of these quick fixes work, do not worry. The detailed steps below cover every possible cause, from cable quality and resolution mismatches to firmware updates and OBS-specific configuration issues.

Step 1: Verify Your Video Source Is Working

Before touching any capture card settings, confirm that your source device is actually outputting video. This sounds obvious, but I have seen cases where a console was in rest mode, a PC was outputting to a different display, or a game had crashed to a black screen with no active signal.

Disconnect the HDMI cable from your capture card’s HDMI In port and connect it directly to a TV or monitor. If you see your game or desktop on the TV, your source is working and the problem is with the capture card or OBS. If you see nothing on the TV either, the issue is with your source device, not the capture card.

For consoles, make sure the console is fully powered on and actively running a game or dashboard. A PS5 or Xbox in sleep mode may not output a signal at all. For PC sources, confirm that the display output is set to the correct monitor or that the game is running on the primary GPU.

One trick I learned from the OBS Project forum is to make sure your source is actively outputting video when you test. Press a button on your controller or move your mouse to wake the display. Some devices enter power-saving mode and stop sending signal after a period of inactivity, which can look like a no-signal problem on the capture card.

If you are using a retro console through an A/V to HDMI adapter, the adapter itself could be the culprit. Test the adapter with a direct-to-TV connection first. Cheap HDMI adapters can produce non-standard resolutions that capture cards cannot read, resulting in a no-signal message.

Step 2: Check HDMI Cable Connections

HDMI cable issues are the single most common cause of capture card no signal errors. The problem is usually one of three things: cables plugged into the wrong ports, a damaged or low-quality cable, or a cable that does not have enough bandwidth for your resolution and frame rate.

HDMI In vs HDMI Out: Get This Right First

Capture cards have two HDMI ports: HDMI In and HDMI Out. The HDMI cable from your console, PC, or camera must connect to the HDMI In port. The HDMI Out port sends the pass-through signal to your TV or monitor so you can play while capturing. If you swap these two cables, your capture card will show no signal because it is trying to read the output meant for your TV.

I cannot count how many times I have seen this exact mistake, including in my own setup when I was first starting. Double-check the labels printed on the capture card itself. On Elgato cards, the labels are clearly marked. On generic USB capture cards, the HDMI In port is sometimes labeled “Input” and the pass-through may not exist at all on budget models.

Use the Right HDMI Cable Speed

Not all HDMI cables are created equal. If you are capturing 4K60 video, you need an Ultra High Speed HDMI cable rated for HDMI 2.1. For 1080p60, a Premium High Speed HDMI cable rated for HDMI 2.0 is sufficient. Using an older HDMI 1.4 cable for a 4K60 signal will result in no signal or a downgraded image.

Elgato specifically recommends using the HDMI cable included with their capture cards, and for good reason. The included cable is rated for the card’s maximum specifications. If you are using a cable from an old DVD player or a no-name brand, it may not handle the bandwidth your capture card needs.

HDMI Cable Length Matters

HDMI signal degrades over distance. For 1080p60, cables up to 15 feet usually work fine. For 4K60, I recommend keeping cable length under 10 feet unless you are using an active HDMI cable or an HDMI signal extender. Long, thin cables are a frequent cause of intermittent signal loss during streams.

If your capture card works on the TV pass-through but shows no signal in OBS, the cable between your source and the capture card may be borderline. Try a shorter, higher-quality cable directly from the source to the HDMI In port.

The Re-Plug Technique

Sometimes the HDMI handshake fails during the initial connection. The source device and capture card negotiate resolution, frame rate, and HDCP settings through a process called EDID exchange. If this negotiation is interrupted or fails, you get no signal.

To fix this, unplug both HDMI cables from the capture card completely. Wait five full seconds. Plug the HDMI In cable first, then the HDMI Out cable. This forces a fresh EDID negotiation and resolves signal issues that appear after resolution changes, console updates, or system reboots.

Step 3: Disable HDCP on Your Console or Device

HDCP, or High-bandwidth Digital Content Protection, is an encryption protocol built into HDMI. Consoles like the PS5 and Xbox Series X enable HDCP by default to prevent piracy. The problem is that capture cards cannot decrypt HDCP-protected signals, so the video feed is blocked entirely. This results in a black screen or no signal in OBS.

HDCP issues are one of the most common reasons a capture card shows no signal in OBS. The frustrating part is that HDCP can re-enable itself after a console firmware update, which is why many users report their capture card “worked for years and then suddenly stopped.”

How to Disable HDCP on PS5

On your PS5, go to Settings, then System, then HDMI. Toggle HDCP off. The PS5 screen may flicker for a moment as the handshake renegotiates. Once HDCP is disabled, your capture card should detect the signal in OBS within a few seconds.

Note that disabling HDCP on PS5 does not affect gaming. It only prevents playback of copy-protected media like Blu-ray discs and certain streaming apps. For gameplay capture, HDCP should always be off.

How to Disable HDCP on Xbox Series X and Series S

On Xbox, go to Settings, then General, then TV and display options, then Video fidelity and overscan. Under the Overrides section, set the HDMI or Display port to “Allow.” Some Xbox models also have an HDCP toggle under Settings, Devices and streaming, Blu-ray, and you can disable it there.

Xbox HDCP settings can be less obvious than PS5 settings. If you cannot find a direct HDCP toggle, changing the video fidelity settings often resolves the encryption conflict with capture cards.

Nintendo Switch and HDCP

The Nintendo Switch does not use HDCP for gameplay, so HDCP is rarely the issue for Switch capture. However, certain streaming apps on Switch may trigger HDCP. If your Switch capture shows no signal only when using a specific app, check whether that app is the trigger.

For Switch capture, the more common issue is the dock. Make sure the dock is powered and the HDMI cable runs from the dock’s HDMI Out port to your capture card’s HDMI In port. The Switch handheld screen does not output HDMI, so the dock is essential.

Step 4: Try a Different USB Port

USB capture cards need significant bandwidth to process live video. A USB 3.0 port provides up to 5 Gbps of bandwidth, while a USB 2.0 port maxes out at 480 Mbps. If you plug a USB 3.0 capture card into a USB 2.0 port, you will likely see no signal, a black screen, or severely degraded video in OBS. If your capture card shows no signal in OBS despite working hardware, the USB 2.0 connection is often the hidden culprit.

This is one of the most overlooked fixes. Many users plug their capture card into the nearest available USB port without checking whether it is USB 2.0 or USB 3.0. On desktop PCs, front panel USB ports are sometimes USB 2.0, while rear ports connected directly to the motherboard are more likely to be USB 3.0.

How to Identify USB 3.0 Ports

USB 3.0 ports have two visual indicators. First, the plastic insert inside the port is usually blue, while USB 2.0 ports are typically black or white. Second, USB 3.0 ports often have an “SS” symbol next to them, which stands for SuperSpeed. On newer computers, USB 3.1 and 3.2 ports may have a red or teal insert and a “SS10” or “SS20” label.

If your capture card came with a USB 3.0 cable, use it. Do not substitute a USB 2.0 cable even if the connector fits. The cable itself needs to support USB 3.0 bandwidth, and older cables will bottleneck the signal.

Powered USB Hubs and Front Panel Ports

If you are using a USB hub between the capture card and your computer, make sure the hub is externally powered and rated for USB 3.0. Unpowered hubs cannot deliver enough power for capture cards, causing intermittent signal drops or complete no-signal errors.

I recommend connecting your capture card directly to a motherboard USB 3.0 port on the back of your PC. This avoids the power and bandwidth issues that front panel ports and hubs can introduce. If you must use a front panel port, verify it is actually USB 3.0 by checking your motherboard specifications.

Step 5: Check Resolution and Frame Rate Compatibility

Every capture card has a maximum supported resolution and frame rate. If your source device outputs a resolution or refresh rate that exceeds the capture card’s limits, the card cannot process the signal and shows no signal instead. This is especially common when capturing 4K120 or 1440p144 signals from a PS5, Xbox Series X, or high-end PC GPU.

For example, the Elgato HD60 X supports up to 4K30 passthrough and 1080p60 capture. If your console is set to output 4K60, the capture card may not be able to read the signal. Lowering the console’s output resolution to a supported level typically fixes the issue immediately.

Common Capture Card Resolution Limits

Elgato HD60 S supports 1080p60 capture and 1080p60 passthrough. The HD60 S+ supports 1080p60 capture with 4K30 passthrough. The HD60 X supports 1080p60 HDR capture with 4K30 HDR passthrough. The Cam Link 4K captures up to 4K30 from cameras. PCIe cards like the Elgato 4K60 Pro support 4K60 capture natively.

Generic USB capture cards based on the MS2109 or MS2110 chip typically support 1080p60 input but may struggle with certain resolutions or refresh rates. If you are using a budget capture card and experiencing no signal, check the chip specifications and try lowering your source resolution.

How to Lower Your Console Resolution

On PS5, go to Settings, Screen and Video, Video Output, and set Resolution to 1080p. On Xbox, go to Settings, General, TV and display options, and set the resolution to 1080p. Test the capture card in OBS after each change to see if the signal appears.

For PC sources, right-click your desktop, select Display Settings, and lower the resolution and refresh rate to match your capture card’s capabilities. A quick test at 1080p60 will tell you whether resolution mismatch is the problem.

EDID Auto-Negotiation Failures

EDID, or Extended Display Identification Data, is the handshake protocol between your source device and the capture card. When you connect an HDMI cable, the source device reads the capture card’s EDID to determine what resolutions and frame rates it supports. If this negotiation fails, the source may output an unsupported signal, resulting in no signal.

EDID failures can happen after resolution changes, console updates, or cable swaps. The fix is to force a fresh negotiation by unplugging both HDMI cables, powering off the source device, powering it back on, and reconnecting the cables. Elgato’s 4K Capture Utility also allows you to override the EDID mode, which some Reddit users report fixes persistent no-signal issues.

HDR and YUV422 Issues

Some capture cards have trouble with HDR content or specific color formats. The Elgato HD60 S+ has a known issue where YUV422 color space needs to be disabled for proper signal detection. If you are using an HD60 S+ and seeing no signal, check the 4K Capture Utility settings and disable YUV422 if it is enabled.

HDR can also cause no-signal issues on certain capture cards. Try disabling HDR on your console or PC and test whether the capture card detects the signal. You can re-enable HDR after confirming the signal works.

Step 6: Reset or Re-Plug the Capture Card

A simple reset resolves a surprising number of no-signal issues. The approach differs slightly between USB capture cards and PCIe internal capture cards, but the principle is the same: clear the device state and force a fresh connection.

USB Capture Card Reset

Unplug the USB cable from the capture card entirely. Unplug both HDMI cables as well. Wait 10 seconds. Plug the USB cable back into a USB 3.0 port first, then connect the HDMI In cable from your source, then the HDMI Out cable to your TV. This full power cycle clears any stuck state on the capture card.

If the simple replug does not work, try plugging the capture card into a different USB 3.0 port. Sometimes a specific USB controller on the motherboard has issues with the capture card, and switching ports forces Windows to reassign the device.

PCIe Capture Card Cold Boot

For PCIe capture cards like the Elgato 4K60 Pro, a cold boot is more thorough than a restart. Shut down your PC completely. Turn off the power supply switch on the back of your PC. Wait 30 seconds to allow all capacitors to drain. Turn the power supply back on and boot the PC.

Elgato specifically recommends a cold boot after firmware updates for PCIe cards. A standard restart does not fully power cycle the PCIe slot, so firmware changes may not take effect. The cold boot ensures the capture card initializes with the updated firmware.

When to Reinstall Drivers

If replugging and cold booting do not work, the next step is to completely uninstall and reinstall the capture card drivers. Go to Windows Device Manager, find the capture card under Sound, video and game controllers or Imaging devices, right-click, and select Uninstall device. Disconnect the capture card, reconnect it, and let Windows reinstall the driver automatically.

For Elgato cards, download the latest driver from the Elgato website rather than relying on the Windows default driver. Generic USB capture cards may need a driver from the manufacturer or the included CD, although most modern ones are UVC-compliant and work with Windows’ built-in drivers.

Step 7: Update Capture Card Drivers and Firmware

Outdated drivers and firmware are a frequent cause of no-signal issues, especially after Windows updates, OBS updates, or console firmware updates. Manufacturers release firmware updates to fix compatibility issues, and skipping them can leave your capture card unable to process newer video formats.

Elgato 4K Capture Utility Updates

For Elgato capture cards, the 4K Capture Utility is the central software for both capturing video and updating firmware. Open 4K Capture Utility and check for updates in the settings menu. Install any available updates and restart both the software and your computer.

Elgato frequently releases firmware updates for newer cards like the HD60 X and Elgato Neo. These cards have had documented out-of-the-box no-signal issues that were resolved with firmware updates. If you just bought a new capture card and it shows no signal immediately, check for a firmware update before assuming the card is defective.

Generic USB Capture Card Drivers

Most generic USB capture cards use the standard USB Video Class driver built into Windows. If the capture card is not detected at all in OBS, it may need a specific driver from the manufacturer. Check the product packaging or listing for a driver download link.

On Mac, capture card support depends on the macOS version and the card’s UVC compliance. Some generic capture cards that work on Windows may not be recognized on Mac without third-party drivers. If you are on Mac and your capture card shows no signal or does not appear in OBS, check the manufacturer’s Mac compatibility page. For a guide on OBS settings on Mac, see our dedicated article.

Cold Boot After PCIe Firmware Update

If you updated the firmware on a PCIe capture card, perform a cold boot as described in Step 6. The PCIe slot needs a full power cycle to load the new firmware. Without a cold boot, the old firmware may still be active, and you will continue to see no signal despite the update.

OBS-Specific Troubleshooting: Fixing No Signal Inside OBS Studio

Most troubleshooting guides focus on hardware, but many no-signal problems are caused by OBS Studio itself. If your capture card works fine in manufacturer software like 4K Capture Utility but shows no signal in OBS, the issue is with your OBS configuration, not the hardware. This section covers every OBS-specific fix I have encountered.

Recreate the Video Capture Device Source

This is the single most effective OBS-specific fix. Right-click the Video Capture Device source in your OBS Sources panel and select Remove. Then click the plus button under Sources, select Video Capture Device, name it, and select your capture card from the Device dropdown.

Recreating the source forces OBS to reinitialize the video pipeline from scratch. Over time, OBS source settings can become corrupted or stale, especially after driver updates or resolution changes. A fresh source eliminates these issues. I have seen this fix work when every hardware troubleshooting step failed.

Deactivate and Reactivate the Source

If you do not want to delete the source entirely, try deactivating it temporarily. In OBS, click the eye icon next to the Video Capture Device source to hide it, wait three seconds, then click it again to show it. This forces OBS to re-query the capture card for a signal.

You can also right-click the source, select Properties, and toggle the Device dropdown to a different device and back to your capture card. This has the same effect as a reconnection and can jog OBS into detecting the signal.

Run OBS as Administrator

On Windows, OBS may not have permission to access certain capture devices or GPU resources when running as a standard user. Right-click the OBS shortcut and select Run as Administrator. This grants OBS elevated privileges and can resolve no-signal issues caused by permission conflicts.

This fix is particularly relevant for Game Capture mode, which hooks into the graphics pipeline. Running OBS as Administrator ensures it can access the necessary DirectX and GPU resources for capture.

OBS Game Capture vs Video Capture Device: Which to Use

OBS offers two different capture methods: Game Capture and Video Capture Device. Game Capture hooks directly into a game’s rendering pipeline on the same PC, while Video Capture Device reads an external video feed from a capture card or webcam. For capture card users, Video Capture Device is the correct choice.

Using Game Capture for a capture card source will not work because Game Capture looks for local game processes, not external HDMI inputs. If you accidentally added a Game Capture source instead of a Video Capture Device, delete it and add the correct source type.

Some users report that OBS Game Capture works for their gameplay but the Video Capture Device shows no signal. This typically means the game is running on the same PC and the capture card is being used for a second source. In this case, verify that the capture card is receiving a signal from a different device or a dual-GPU output configuration.

Check OBS Video Capture Device Properties

Double-click your Video Capture Device source in OBS to open its properties. Check the following settings:

Device: Make sure your capture card is selected, not a webcam or other device. If the capture card is not listed, it is not being detected by Windows or the driver is missing.

Resolution: Set this to Device Default or match your source’s resolution. Setting an incorrect resolution can cause no signal.

Video Format: Leave this on Device Default unless you need a specific format. Changing it to an unsupported format can break the signal.

Buffering: Try toggling buffering off and on. Some capture cards have buffering issues that can cause signal detection problems.

OBS Not Detecting the Capture Card at All

If your capture card does not appear in the Device dropdown when adding a Video Capture Device source, OBS cannot see the device. This usually means the driver is not installed, the device is disconnected, or there is a USB controller conflict.

Check Windows Device Manager to confirm the capture card appears under Sound, video and game controllers or Imaging devices. If it has a yellow warning icon, the driver needs to be reinstalled. If it does not appear at all, try a different USB port or cable.

On Mac, OBS may not detect certain capture cards if the macOS privacy permissions are not granted. Go to System Settings, Privacy and Security, Screen Recording, and make sure OBS has permission. Also check Camera permissions, as some capture cards register as cameras.

Console-Specific Tips: PS5, Xbox, and Switch

Different consoles have different quirks when it comes to capture card signal issues. The forums are full of console-specific problems, and I have tested each console with multiple capture cards to identify the common pitfalls.

PS5 Capture Card No Signal

The PS5 is the most common source of capture card no-signal issues, primarily due to HDCP. Go to Settings, System, HDMI, and disable HDCP. If your PS5 was recently updated, HDCP may have been re-enabled automatically.

The PS5 can also output 4K120 or 1080p120, which exceeds many capture cards’ capabilities. If your PS5 is set to 4K120 and your capture card supports only 4K30 or 1080p60, you will see no signal. Lower the PS5 resolution to 1080p and the refresh rate to 60Hz to test.

One Reddit user reported that their PS5 showed signal during the safe mode repair scan but not during normal operation. This suggests an HDCP or resolution negotiation issue that only manifests during active gameplay. If you see this pattern, focus on HDCP and resolution settings.

Xbox Series X and Series S Capture

Xbox HDCP settings are found under Settings, General, TV and display options, Video fidelity and overscan. Setting the override to “Allow” can resolve capture card signal issues. Xbox also has a tendency to output at non-standard refresh rates like 120Hz, which some capture cards cannot handle.

If your Xbox capture shows no signal, try setting the video output to 1080p at 60Hz with HDR disabled. This is the most universally compatible setting for capture cards. Once you confirm the signal works, you can gradually increase resolution and enable HDR to find the highest setting your capture card supports.

Nintendo Switch Capture

The Switch does not use HDCP for games, so HDCP is rarely the issue. The most common Switch capture problem is the dock. The Switch must be docked to output HDMI, and the dock must be powered. Make sure the dock’s power adapter is plugged in and the HDMI cable runs from the dock’s HDMI Out port to the capture card’s HDMI In port.

The Switch outputs at 1080p60 in docked mode, which is compatible with virtually all capture cards. If your Switch shows no signal, check the dock connection and try a different HDMI cable.

Retro Console Capture via HDMI Adapter

Retro consoles like the PS2, GameCube, or SNES require an A/V to HDMI adapter or upscaler. These adapters can produce non-standard resolutions that capture cards cannot read, resulting in no signal. If your retro capture shows no signal, test the adapter on a TV first.

The OBS Project forum had a case where a PS2 connected through an A/V to HDMI adapter showed no signal in OBS. Testing the adapter with other software like Discord’s webcam test helped isolate whether the issue was OBS or the adapter itself. In many cases, a higher-quality upscaler resolves the problem.

How to Know If Your Capture Card Is Actually Defective

One of the most common questions on forums is how to tell if a capture card is broken versus just misconfigured. I have seen users replace capture cards only to discover the problem was a USB cable all along. Before assuming your card is defective, run these tests. Understanding why does my capture card show no signal in OBS is the first step, but knowing whether the card itself is faulty is equally important before spending money on a replacement.

Test With Different Software

If your capture card shows no signal in OBS, try it in a different application. Open the manufacturer’s software like Elgato 4K Capture Utility, or try a generic viewer like VLC Media Player, OBS Studio alternative, or even Discord’s camera test. If the capture card works in other software but not OBS, the problem is with OBS configuration.

To test in VLC, go to Media, Open Capture Device, and select your capture card as the video device. If VLC shows video, the capture card hardware is working and the issue is software-side. If VLC also shows no signal, the problem is with the hardware or the source device.

Test on Another Computer

If possible, connect your capture card to a different computer. This isolates whether the problem is with your PC’s USB controller, drivers, or operating system versus the capture card itself. If the card works on another computer, the issue is with your system configuration.

Test With a Known-Working Source

Connect a different source device to your capture card. If your PS5 shows no signal, try connecting an Xbox or a PC GPU output instead. If the second source works, your original source device may have an HDCP or resolution issue. If neither source produces a signal, the capture card is likely defective.

Signs of Hardware Failure

Capture cards do fail, though it is relatively rare. Signs of genuine hardware failure include the capture card not being detected by any computer, the USB connection constantly dropping, physical damage to the HDMI ports, or the card producing garbled video even with a known-working source and cable.

If you have tried every troubleshooting step in this guide and the capture card still shows no signal on multiple computers with multiple sources, contact the manufacturer’s support. Elgato, AVerMedia, and other major brands offer warranty replacements for defective units. For tips on recording gameplay without a capture card as a temporary workaround, check our guide.

Preventing No-Signal Issues Before You Stream

No competitor covers prevention, and this is a gap worth filling. After dealing with no-signal issues mid-stream more times than I care to admit, I developed a pre-stream checklist that catches problems before they cost you viewers. Here is how to prevent capture card no signal issues before they happen.

The Pre-Stream Signal Verification Checklist

Before every stream or recording session, run through this 60-second checklist:

1. Confirm your source device is powered on and outputting video to a TV or monitor directly. Disconnect the capture card HDMI and test direct first.

2. Verify the HDMI cable from your source is plugged into the HDMI In port on the capture card, not HDMI Out. Check the labels on the card.

3. Confirm your capture card is plugged into a USB 3.0 port, identifiable by the blue insert or SS label.

4. Open OBS and verify the Video Capture Device source shows your gameplay, not a no-signal message. Do this at least 10 minutes before going live.

5. Check that HDCP is disabled on your console if you updated the console firmware since your last stream.

6. Verify your console resolution and refresh rate are within your capture card’s supported limits.

Keep Firmware and OBS Updated

Manufacturers release firmware updates to fix compatibility issues with new consoles and OS updates. Check for firmware updates monthly, especially after major console or Windows updates. Elgato releases updates through the 4K Capture Utility, and other brands typically offer updates through their respective software.

OBS Studio also receives regular updates that fix capture device issues. Keep OBS updated to the latest version. If a new OBS update causes a regression, you can download a previous version from the OBS Project website while waiting for a fix.

Use Certified HDMI Cables

Invest in high-quality, certified HDMI cables rated for your capture resolution. For 4K60 capture, use Ultra High Speed HDMI cables certified by the HDMI Forum. Avoid no-name cables from discount stores, as they often fail to meet their advertised specifications.

Label your cables to avoid confusion. Use small adhesive labels on the HDMI cable ends to mark which one goes to the source and which goes to the TV. This prevents the common mistake of swapping HDMI In and HDMI Out cables when setting up at a new location or after moving equipment.

What to Do When Signal Drops Mid-Stream

If your capture card loses signal during a stream, do not panic. Your audience will see a frozen frame or no-signal screen, but your audio may still be working. Here is the fastest recovery procedure:

First, check if the source device crashed or entered sleep mode. Press a button on your controller to wake it. If the source is fine, unplug the HDMI In cable from the capture card and plug it back in. This forces a fresh EDID handshake and often restores the signal within seconds.

If the HDMI replug does not work, hide the Video Capture Device source in OBS by clicking the eye icon, wait three seconds, and show it again. If that fails, delete the source and recreate it. Have a “be right back” scene ready in OBS so your audience sees a professional screen while you troubleshoot. For a complete guide on recording gameplay on PS5 with OBS, see our dedicated walkthrough.

Label Everything

If you travel with your streaming setup or attend events, labeling your cables and ports saves enormous amounts of time. Use colored tape on HDMI cables to distinguish HDMI In from HDMI Out. Label USB cables as USB 3.0 so you do not accidentally plug your capture card into a USB 2.0 port at a new venue.

I keep a small label maker in my streaming kit specifically for this purpose. The five minutes spent labeling cables before an event prevents hours of troubleshooting when something goes wrong in an unfamiliar environment.

FAQ’s

Conclusion

Figuring out why does my capture card show no signal in OBS comes down to systematically checking the signal path from your source device through the HDMI cable, into the correct capture card port, over a USB 3.0 connection, and into a properly configured OBS Video Capture Device source. The vast majority of no-signal issues are resolved by checking HDMI In versus Out ports, disabling HDCP, switching to USB 3.0, and recreating the OBS source.

If you have worked through every step in this guide and your capture card still shows no signal on multiple computers with multiple sources, your card may be defective. Contact the manufacturer support for your brand. Elgato, AVerMedia, and other major manufacturers offer warranty service and can help confirm whether your unit needs replacement.

Bookmark this page and run the pre-stream checklist before your next broadcast. A 60-second check saves the frustration of discovering a no-signal error when you are already live.