START HERE
Record a short test while the game stays in the foreground, then inspect a fresh scene with one Game Capture source targeting the actual game window. If the game blocks capture, use its supported windowed or borderless capture route rather than trying to bypass the restriction.
Confirm whether the recording is actually black
This guide covers the Windows Game Capture source. On macOS and Linux, choose the platform's screen/window capture source instead; the same source name and Windows capture-hook fixes do not apply.
Make a short recording while actively playing, then stop and inspect the file. A fullscreen game can stop rendering when you switch away to inspect OBS. That makes a black or frozen preview while alt-tabbed a misleading test. If the saved gameplay is correct, avoid changing a working capture route to solve an inactive-window preview.
If you use Studio Mode, check which scene is on the program side. A source visible in preview is not automatically the source currently being recorded. Use a harmless scene label during diagnosis so the resulting file tells you which layout was active.
Separate scene layout from capture failure
- Create a temporary scene with a new Game Capture source and no overlays. Keep the production scene intact.
- Launch the game itself and use Capture specific window to select it. Do not select a launcher or a browser just because it started the game.
- Check the source's visibility and whether anything covers it. Use Transform > Reset Transform, then Fit to Screen if its bounds are wrong.
- Record again with the game foregrounded. Compare this simple scene with the original one.
If the test scene works, return to the production scene and inspect its selected source, ordering, filters, and transform. Reinstalling OBS is a poor first response to a layout problem: it changes more than the evidence requires and may leave the scene configuration untouched anyway.
Use the route the game supports
The OBS compatibility checklist lists games that need a different capture method or an elevated OBS process. Consult the entry for your game instead of copying settings from a different title. For a documented administrator requirement on Windows, close OBS and relaunch the installed, trusted copy with that option, then repeat the same test.
When a game prevents the capture hook, try borderless/windowed mode with Window Capture where the game's guidance permits it. Do not disable anti-cheat or security controls to force the hook. Window Capture and Game Capture are alternatives, not two sources that must both remain active.
On a multi-GPU laptop, compare the GPU assigned to OBS and the game in Windows graphics settings. Follow the linked OBS instructions for that hardware, restart both applications after a change, and keep a note of the previous assignment so it can be restored.
Test overlays without dismantling the setup
Close optional FPS counters, game overlays, and other capture applications you knowingly started, one at a time. Restart the game where needed and repeat the short recording. If capture begins working, re-enable the last component to see whether the failure returns; this distinguishes a reproducible conflict from a coincidence.
A game update that changes its executable or rendering mode can also invalidate an old selection. Reselect the active game window first. Avoid changing several rendering, capture, and driver options together: even a successful result then leaves you without a clear recovery procedure for next time.
Verify a fallback before using it live
If Window Capture works, check menus, loading screens, gameplay, and the return to the desktop. Use Display Capture only when the wider capture area is acceptable: it can show unrelated windows and notifications. Frame the source carefully and record the whole transition sequence before trusting it on a live channel.
Then check audio separately. A fixed picture does not prove the intended sound path is present. Use the game-only audio test, especially if you changed from one capture source type to another.
If every supported route fails, record the OBS version, game version, GPU model, capture method, and exact point where the picture disappears. Reproduce the issue once in a minimal scene and retain that session's log. That report is substantially more useful than a screenshot of an empty preview with no information about whether the game was running.
Sources & version notes
Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.