Make the decision from the signal path
A black preview means one or more hops from source to OBS is missing. Diagnose in order: source output, permitted HDMI signal, cable direction, capture input, host USB/PCIe detection, supported capture mode and selected OBS source.
A working passthrough display proves only the display leg. It does not prove USB capture or OBS setup, and protected HDCP content remains uncapturable even when the cables are correct.
Eight decision factors
Check these in order. Source output and HDCP decide whether the route works; the remaining factors refine operation and convenience.
- Source output: Confirm the console/PC/camera produces a known supported signal.
- HDCP: Use only unencrypted capturable content and disable protected playback where legitimately supported.
- HDMI direction: Source output goes to capture input; capture output goes to display.
- Capture matrix: Set a source mode present in the product’s exact matrix.
- Host link: Confirm direct required USB speed or PCIe x4 detection.
- Operating system: Check exact device/mode support.
- Application ownership: Close other apps that may hold the capture device and select it explicitly in OBS.
- Audio clue: Audio without picture can narrow the fault but does not prove the video format is supported.
Constraints that change the answer
Start with Passthrough only. The conditions below can change the choice or the next troubleshooting branch.
- Passthrough only: Display success does not prove USB capture or OBS configuration.
- Camera overlays/power: Cam Link routes require clean HDMI and continuous operation.
- USB fallback: A slower negotiated link can remove higher modes.
- PCIe device: 4K Pro is Windows-only and requires a valid PCIe x4 path.
- Cable substitution: Change one known-good cable at a time and retain correct direction.
A practical connection and configuration workflow
Follow the steps in order. Confirm the hardware in the operating system before selecting it in OBS or another routing application, and change one cable, mode or route at a time.
- Step 1: Power-cycle source and capture after selecting a conservative supported mode.
- Step 2: Connect source → capture input and optionally output → display.
- Step 3: Verify the capture device in the operating system/device application.
- Step 4: Add a fresh OBS Video Capture Device source by exact name.
- Step 5: Raise modes one variable at a time after the baseline picture works.
Examples
For a console, first force a conservative SDR output that the capture matrix lists. Once OBS records it, restore display features one at a time while checking both passthrough and capture.
For a camera, prove a clean continuously powered HDMI feed with the correct camera connector. Cam Link has no display passthrough, so host preview is the relevant path.
Use capture-card guide and console setup for the adjacent checks.
Four common failure modes
Match the symptom below first, then change one hop at a time from the source toward OBS.
If the source preview is sound but the broadcast stutters, compare OBS network, rendering and encoding counters before changing the capture connection.
- No display and no preview: Start at source output, power, HDMI direction and cable.
- Display works, preview black: Inspect host data link, OS detection and OBS device ownership.
- Menu works, protected video black: HDCP is blocking capturable content; do not attempt bypass.
- Picture vanishes at high refresh/HDR: Return to a known matrix combination and add resolution, refresh and HDR separately.
Prove the result
Set the source to a conservative supported SDR mode, then check source output → HDMI cable and capture input → host detection → exact OBS device in that order.
If passthrough works but OBS stays black, leave the source and first HDMI cable in place and inspect the capture-to-host link, operating-system detection and application ownership. Raise resolution, refresh rate or HDR only after a baseline local recording succeeds.
Equipment for these connections
Start with the needed role. Check the complete profile before adding a product to your setup.
Play at 4K60 while streaming a 1080p60 source
Elgato Game Capture Neo
Use its HDMI output for a 4K60 HDR gaming display and its USB output for up to 1080p60 capture. Choose another card if the recorded stream must be 4K.
Connections & full profile →Check price on Amazon ↗A current external capture path for console streaming
Elgato Game Capture 4K S
Select a listed capture mode and a separate listed display mode. If HDR or high refresh is essential, match both exact modes before choosing this card.
Connections & full profile →Check price on Amazon ↗High-refresh HDMI capture on a fast direct USB port
Elgato Game Capture 4K X
Use a 10 Gbps USB connection for the full mode set. On a 5 Gbps port, choose one of the reduced capture modes or a different host connection before buying for high resolution.
Connections & full profile →Check price on Amazon ↗Internal capture in a compatible Windows desktop
Elgato Game Capture 4K Pro
Use a supported Windows desktop with a suitable PCIe x4 slot. Choose a USB capture device for a Mac or a laptop without an accessible compatible slot.
Connections & full profile →Check price on Amazon ↗Bring a suitable clean-HDMI camera into your computer
Elgato Cam Link 4K
There is no HDMI display output. Identify the unit’s revision before planning 4K frame rates, then test clean HDMI and continuous camera power; use a passthrough card for a separate gaming display.
Connections & full profile →Check price on Amazon ↗Capture a console over USB while keeping a separate gaming display
AVerMedia Live Gamer ULTRA S GC553Pro
Select the capture mode for your actual Windows or Mac host. Use an unencrypted HDMI source; protected video cannot be made capturable by choosing a different cable.
Connections & full profile →Check price on Amazon ↗