You plug your capture card into your Mac, open OBS Studio, add a Video Capture Device source, and instead of your console or camera feed you get a black rectangle. Sometimes the audio meters jump even though the video is dark, sometimes there is nothing at all, and occasionally the feed flickers in for a second before dying. The Mac itself usually behaves normally, which makes the problem feel like it is inside the capture card even when it usually is not.
The good news: a black screen from a capture card on macOS is almost always a settings, permissions, or handshake issue rather than a dead device. Most fixes take under five minutes, and working through them in order from easiest to hardest resolves the vast majority of cases. Only the small handful of situations involving HDCP, bandwidth, or genuine hardware failure require deeper troubleshooting or replacement, so there is no need to panic or assume your card is broken.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| OBS lacks camera/screen recording permission | OBS shows the source but the preview stays black; check System Settings > Privacy & Security > Camera | Easy |
| HDCP handshake on the source device | Audio works but video is black; the feed appears when you open the console’s home menu or play non-protected content | Easy |
| Wrong input resolution or format selected | The device properties in OBS show a resolution/color format your source cannot output, such as 4K60 on a 1080p card | Easy |
| HDMI cable, adapter, or port problem | Feed appears intermittently, drops when cables move, or works on another computer | Easy |
| Insufficient USB bandwidth on a hub or USB-C port | Black screen or heavy artifacting when the card shares a hub with other devices; works when moved to a direct port | Moderate |
| Outdated or missing driver/firmware for the card | The card never appears as a device at all, or disappears after macOS updates; manufacturer utility reports old firmware | Moderate |
Fix 1: Grant OBS Camera and Screen Recording Permissions
What causes it
macOS treats capture cards as camera devices. If the app has not been granted camera access, macOS delivers no video frames, and OBS renders an empty black preview even though the device is detected.
How to check
Open System Settings > Privacy & Security > Camera and look for OBS in the app list. If the toggle is off, that is your problem. Also check Privacy & Security > Screen Recording, since some capture workflows and virtual camera plugins require it.
What to do
Turn on the toggle for OBS (and any other capture app you use, such as QuickTime Player). macOS will say the app must be restarted — quit OBS completely with Command+Q, then reopen it. If OBS never prompted you for permission, reset the prompt by launching Terminal and running tccutil reset Camera, then relaunch OBS and click Allow when asked.
How to undo it
Return to System Settings > Privacy & Security > Camera and toggle the app off. No restart is needed to revoke access.
Fix 2: Bypass HDCP on the Source Device
What causes it
Consoles and some streaming devices encrypt their HDMI output with HDCP (High-bandwidth Digital Content Protection). Capture cards cannot decrypt this signal, so they output pure black while audio may still pass through.
How to check
Check the OBS preview while navigating your console’s dashboard or settings menu. If the picture appears in menus but goes black the moment a game or streaming app launches, HDCP is the cause. Some cards also show an HDCP warning in their own utility software.
What to do
On a PlayStation 5, go to Settings > System > HDMI and turn off Enable HDCP. On Xbox Series X|S, open Settings > General > TV & display options > Video modes and uncheck “Allow HDCP” (it only appears while the console is in a non-protected app). On a Nintendo Switch, HDCP is always active and cannot be disabled, which is why the Switch docks poorly with capture setups without workarounds. For cable boxes and Apple TV, use the device’s display settings to disable HDCP where offered, or accept that protected content cannot be captured.
How to undo it
Re-enable the HDCP toggle in the same console settings menu. You will need it on again to watch protected streaming apps in 4K.
Fix 3: Match the Capture Resolution and Format in OBS
What causes it
If the capture source is configured for a resolution, frame rate, or color format the incoming signal does not match, some devices output no frames at all instead of a scaled image.
How to check
In OBS, right-click your Video Capture Device source, choose Properties, and inspect the Resolution/FPS Type, Resolution, and Video Format dropdowns. If Resolution/FPS Type is set to Custom and does not match your source (for example, 3840×2160 selected while your console outputs 1920×1080), black video is common.
What to do
Set Resolution/FPS Type to “Device Default” first, then set Video Format to match your signal — typically “XRGB” or “Any” works on Mac, or “NV12” for devices that require it. If the device offers a “Buffering” or “Low latency” checkbox in properties, try toggling it. Click OK, then check the preview. If still black, reopen properties and manually select the exact resolution your source outputs, such as 1920×1080 at 60 fps.
How to undo it
Reopen the source properties and restore your preferred custom resolution and format. Settings are stored per-source in your OBS scene collection.
Fix 4: Swap Cables, Adapters, and HDMI Inputs
What causes it
HDMI cables degrade, cheap passive adapters fail to carry full signal, and some capture cards have multiple HDMI ports labeled In and Out where plugging into the wrong one (usually the pass-through Out port) yields nothing.
How to check
Trace the full chain: source console > HDMI cable > capture card input (labeled In or HDMI In) > USB to Mac. Swap in a known-good short HDMI cable, ideally under 6 feet and rated High Speed or Ultra High Speed. Confirm the source cable goes to the In port, not the Out/passthrough port.
What to do
Replace the HDMI cable with a certified one, remove any HDMI-to-mini-HDMI adapters from the chain, and try a different HDMI input if your card has more than one. Test the console on a TV with the same cable to verify the cable itself is good. If your card uses a USB-C to USB-C cable to the Mac, try the alternate cable shipped with the device.
How to undo it
Reconnect your original cable arrangement. There is no persistent setting to change.
Fix 5: Plug the Capture Card Directly Into the Mac
What causes it
USB capture devices consume large amounts of bandwidth — a 1080p60 card needs roughly a sustained stream that hubs shared with keyboards, drives, or webcams can choke on. Underpowered or bandwidth-saturated hubs deliver a signal that collapses to black.
How to check
If the card is connected through a hub, dock, or your display’s USB ports, unplug it and connect it directly to a port on the Mac itself. If the picture appears, the hub was the problem. Prefer Thunderbolt or USB-C ports on Apple Silicon Macs, and note which ports are on separate buses on your model.
What to do
Connect the card directly to the Mac. If you must use a hub, choose a powered Thunderbolt dock, plug nothing else into the same bus, and use the port closest to the host connection. For desktop Macs, prefer rear ports over front ports on enclosures and displays.
How to undo it
Move the card back to your hub or dock once other bandwidth-heavy devices are removed or reallocated to a different port.
Fix 6: Update or Reinstall the Card’s Driver and Firmware
What causes it
macOS updates occasionally break driver compatibility for cards that rely on vendor extensions, and cards with pending firmware updates can fail the HDMI handshake with newer sources entirely.
How to check
Open the manufacturer’s utility app (for example, the Elgato app or AVerMedia utility) and look for a firmware or software update section. Also open System Information (hold Option, click the Apple menu, choose System Information) and check USB or Thunderbolt to confirm the card enumerates at all. If the card is missing there, the Mac is not seeing it electrically or the driver is dead.
What to do
Download the current macOS software package for your specific card model from the manufacturer, run the installer, and restart. Apply any firmware update the utility offers with the card connected directly to the Mac, and do not unplug it during the update. If the card is still missing from System Information, test it on another computer to distinguish driver failure from hardware failure.
How to undo it
Firmware downgrades are generally unsupported. If an update causes new problems, reinstall the previous driver package if the manufacturer still offers it, or contact their support for a rollback tool.
Fix 7: Reset the USB Device and NVRAM
What causes it
macOS can latch onto a failed handshake state with a USB device, keeping it black even after you reconnect it. Clearing the device and low-level boot settings forces a fresh enumeration.
How to check
If the card appears in System Information but no app can pull video, and a simple replug does not help, a stale device state is likely.
What to do
Quit all capture apps, unplug the card, then shut down the Mac completely (Apple menu > Shut Down) — do not just restart. On Apple Silicon, let it sit powered off for 30 seconds, then boot and reconnect the card before opening OBS. On Intel Macs, reset NVRAM by powering on while holding Option+Command+P+R until you hear the startup chime twice, then reconnect the card. As a last software step, run killall -9 coreaudiod in Terminal to restart the audio subsystem if audio also vanished.
How to undo it
Nothing to undo — this is a state reset. NVRAM resets simply restore default boot settings.
Fix 8: Rule Out HDCP Stripping, EDID, and Hardware Failure
What causes it
Sources occasionally fail to negotiate display capabilities (EDID) with a capture card, sending a signal format the card cannot read. Separately, failed HDMI ports and dead internal cards produce a permanent black screen no software change fixes.
How to check
Test the card with a different source — a laptop’s HDMI output or a different console. If it works with one source and not another, the problem is the source’s EDID or HDCP behavior, not the card. If it is black with every source on every cable and port, the card has likely failed. An EDID emulator or HDCP-aware splitter between the source and the card resolves stubborn negotiation failures.
What to do
For EDID issues, insert an HDMI EDID emulator into the chain or route through a powered HDMI splitter that presents a fixed 1080p EDID to the source, then feed the splitter output to the card. For suspected hardware failure, check the card’s warranty — most major brands carry a two- to three-year limited warranty — and pursue replacement. If you are capturing protected content and hoping for a workaround, there is no legitimate one; the fix is to capture from an unprotected source instead.
How to undo it
Remove the emulator or splitter from the chain to return to a direct connection.
If Nothing Works
At this point you have eliminated software, permissions, settings, cables, bandwidth, and drivers. Test the capture card on a second computer — a friend’s laptop is fine — since this is the single fastest way to separate a broken card from a Mac-specific conflict. If it fails there too, the card or its power supply is faulty and needs warranty replacement. If it works elsewhere, back up your Mac, then create a new macOS user account and test the card there; if the feed appears in the fresh account, a per-app preference file is corrupted, and deleting the affected app’s container in ~/Library/Containers (for sandboxed apps) or its preferences in ~/Library/Preferences typically resolves it. Finally, check the manufacturer’s support forums for your exact card model plus your macOS version, because model-specific compatibility bugs do surface after major system updates and are often fixed in a vendor patch within weeks.
FAQ
Why does my capture card show audio but a black screen on Mac?
Audio and video travel on separate portions of the HDMI signal, and HDCP protection only blocks the video. Black video with working audio almost always means the source is outputting protected content. Disable HDCP in your console’s settings (see Fix 2) or pause the protected app and test in the dashboard menu.
Do capture cards work natively on Apple Silicon Macs?
Most modern USB 3.0 UVC-class capture cards work natively on Apple Silicon because macOS includes built-in drivers for UVC devices. Cards requiring vendor kernel extensions have had patchier support, so check the manufacturer’s compatibility page for your specific model and macOS version before buying. Cards confirmed as UVC-compatible are the safest choice.
Can OBS record my Mac’s screen and the capture card at the same time?
Yes. Add a macOS Screen Capture source (in OBS 28 and newer, use macOS Screen Capture rather than the older Display Capture) alongside your Video Capture Device source. Make sure both the Camera and Screen Recording permissions are granted to OBS, or one of the two sources will render black while the other works.
Why does my capture feed drop to black randomly during long sessions?
Random mid-session dropouts usually point to thermal or bandwidth issues: the card overheating in an enclosed hub, USB power sag, or another device on the same bus grabbing bandwidth. Move the card to a directly connected port, keep it in open air, and check the manufacturer’s utility for firmware updates addressing stability. A card that drops only after the Mac sleeps may also need “Prevent automatic sleeping” enabled in System Settings > Battery or Energy Saver during recordings.
