Skip to main content
16 min readgrowth

By Paul d'Anjou, Twitch growth expert

OBS Game Capture Black Screen on Twitch: 3-Question Diagnostic Before You Try Random Fixes (2026)

By Paul d'Anjou, Twitch growth expert May 30, 2026

TLDR

  • 70% of cases: laptop dual-GPU, OBS runs on the integrated chip while the game runs on the discrete one. Fix: force OBS to the discrete GPU in Windows Graphics settings.
  • 20% of cases: OBS is not running as administrator, so it cannot hook the game. Fix: relaunch elevated (and automate it at logon).
  • 10% of cases: Auto HDR on Windows 11 25H2+ breaks Game Capture. Fix: disable Auto HDR or enable HDR Capture in OBS 30+.

Verdict: diagnose first, fix once

You hit Start Streaming, Game Capture is selected, and your Twitch stream shows a black screen while you see your game running perfectly on your monitor. Worse: you already tried run as admin, reinstall OBS, restart your PC. Nothing changed.

This guide flips the 90% pattern: we diagnose first, we hand you one targeted fix. Three short questions, one solution, ten minutes max. If the answer to question 1 is "laptop", you go straight to the GPU fix and skip the rest. No random listicle, no five stacked fixes hoping one will land.

3-Question Diagnostic

Before touching anything, answer the three questions below. Each answer points to one solution section.

Question 1: laptop or desktop?

  • Laptop: 70% chance this is a GPU mismatch. Jump straight to Solution 1 (discrete GPU). Do not try anything else first.
  • Desktop: continue to question 2.

Question 2: Windows 11 24H2 or newer?

  • Yes: 50% chance this is Auto HDR. Jump to Solution 3 (Auto HDR).
  • No: continue to question 3.

Question 3: does the game use an anti-cheat (Valorant Vanguard, Fortnite EAC, CS2 VAC, Apex BattlEye)?

  • Yes: jump to Solution 4 (Anti-cheat). Window Capture is often mandatory.
  • No: start with Solution 2 (admin), and if that is not enough, check the Game / Display / Window Capture disambiguation below.

One path, one action, no soup of edge cases.

Solution 1: force OBS to the discrete GPU (laptops, 70% of cases)

On a gaming laptop or a recent ultrabook, you have two GPUs. An integrated GPU (Intel UHD/Iris or AMD Radeon Vega) that handles the Windows desktop to save battery, and a discrete GPU (NVIDIA GeForce or AMD Radeon RX) that wakes up when a game asks for power.

The catch: by default, Windows pins OBS to the integrated chip (it is categorized as a "classic app") and the game to the discrete one. Game Capture tries to hook the render output, but since both GPUs do not share video memory, OBS sees black.

Step by step on Windows 11

  1. SettingsSystemDisplayGraphics
  2. Click Browse
  3. Add obs64.exe (usually in C:\Program Files\obs-studio\bin\64bit\)
  4. Click OBS in the list → Options → pick High performance
  5. Close OBS completely (check Task Manager that no obs64.exe process is lingering)
  6. Relaunch OBS

Step by step on Windows 10

Same path (Settings → System → Display → Graphics Settings, the menu has been there since 1903). Otherwise, vendor driver route:

  • NVIDIA: NVIDIA Control Panel → Manage 3D Settings → Program Settings → add OBS → Preferred graphics processor → High-performance NVIDIA processor.
  • AMD: Radeon Software → Graphics → Profiles → add OBS → Graphics performance preference → High performance.

Why it works

OBS must see the game on the same GPU that renders it. Otherwise, the capture API (DXGI Desktop Duplication or the Game Capture hooks) finds no framebuffer to read. With both processes pinned to the discrete GPU, the hook lands and you see the game in OBS the same way you see your desktop in your Windows session.

Verification

Task ManagerDetails tab → right-click the column header → Select columns → check GPU and GPU Engine. You can now see which GPU obs64.exe is using. If it shows GPU 1 (the discrete one), you are good.

Solution 2: run OBS as administrator (20% of cases, mostly desktops)

Modern games often run with elevated privileges because of kernel-mode anti-cheats and recent GPU drivers. If OBS runs as a standard user, it cannot hook those processes, and you end up staring at a black source.

Step by step

  1. Close OBS completely (Task Manager, kill every obs64.exe).
  2. Right-click the OBS shortcut → Run as administrator.
  3. Test right away: launch the game, check if the Game Capture source shows anything.

Automate at logon (5 minutes, set and forget)

To skip the right-click ritual every session:

  1. Open Windows Task Scheduler (Win + R → taskschd.msc).
  2. Click Create Task (not "Create Basic Task", the full version).
  3. General tab: name it "OBS Admin", check Run with highest privileges.
  4. Triggers tab: new → At log on.
  5. Actions tab: start a program → C:\Program Files\obs-studio\bin\64bit\obs64.exe, with Start in C:\Program Files\obs-studio\bin\64bit\.
  6. Conditions tab: uncheck "Start the task only if the computer is on AC power" if you are on a laptop.
  7. Save, log out, log back in.

Next session, OBS launches elevated automatically, no UAC pop-up.

Special case: Microsoft Store / Xbox Game Pass

Games from the Microsoft Store (Sea of Thieves, Forza Horizon, etc.) run inside a UWP container. OBS must be admin AND use the Capture specific window mode in Game Capture; otherwise the UWP hook does not land. The Streamlabs team documents this on their official Game Capture guide, and it is a classic trap on Forza and Sea of Thieves.

Solution 3: disable Auto HDR on Windows 11 25H2+ (10% of cases)

Windows 11 25H2, deployed in October 2025, ships an aggressive Auto HDR behavior: the OS flips into HDR on its own as soon as a game declares a compatible format, no user prompt. The problem: Game Capture cannot follow the color-format change mid-stream, and your output snaps to black.

This is a confirmed bug discussed on the OBS community forum and on a handful of specialist Windows 11 25H2 threads (OBS official forum thread tag), but almost nobody mentions it in mainstream OBS tutorials. If you upgraded to 25H2 recently and the black screen appeared after the update, you are almost certainly here.

Step by step

  1. SettingsSystemDisplayHDR
  2. Turn off Auto HDR (the toggle under "Play games and apps in HDR")
  3. Relaunch OBS and the game.

Keep HDR on your game

Enable the HDR Game Capture option in OBS 30 and newer:

  • Game Capture source → Properties → check Capture HDR
  • Your stream still goes out as SDR (Twitch does not accept HDR output anyway), but Game Capture can now read an HDR framebuffer without breaking.

Solution 4: anti-cheat (competitive games)

Kernel-mode anti-cheats in competitive games block OBS hooks to prevent cheating. Behavior varies by engine:

GameAnti-cheatGame CaptureRecommended fix
ValorantVanguardBlockedWindow Capture mandatory
FortniteEACBorderless onlyGame Capture in borderless
CS2VACOKGame Capture + disable HDR
Apex LegendsBattlEyeUnstableWindow Capture recommended
RobloxHyperionOften blankWindow Capture
Minecraft Java(none)No DXGI hookWindow Capture mandatory

Switch to Window Capture cleanly

  1. In OBS, add a Window Capture source.
  2. Select the game window in the dropdown.
  3. Capture method: try Automatic first, then Windows 10 (Windows Graphics Capture) if nothing shows, then BitBlt as last resort.
  4. Important: the game window must be visible (not minimized), otherwise Window Capture returns a blank frame. Borderless or windowed fullscreen, never minimized.

Disambiguation: Game Capture vs Display Capture vs Window Capture

100% of competing guides conflate these three modes or present them as interchangeable. They are not. Quick reference:

ModeWhen to usePerformanceWhen it fails
Game CaptureDX9 / 10 / 11 / 12 or modern Vulkan games in fullscreen or borderlessOptimal (zero-copy GPU hook)Strict anti-cheats, Minecraft Java, very old 32-bit games, Auto HDR
Display CaptureYou failed with Game Capture and Window CaptureMedium (DXGI Desktop Duplication)Multi-monitor trap (records everything: Discord, notifications)
Window CaptureStrict anti-cheat, Minecraft Java, finicky UWP gamesGoodMinimized window = blank output

The Display Capture trap

Display Capture is often pitched as the "easy default" by lazy tutorials. Bad call: you capture everything on your screen, including Windows toasts, Discord pop-ups, and stray browser tabs. The day you receive an awkward DM mid-stream, you curse Display Capture. Reserve it for the case where Game Capture and Window Capture both failed.

Verify the fix worked

After every solution, run the three-step check:

  1. Test 1, OBS sees the game: the OBS preview shows your gameplay (not black, not a blank frame).
  2. Test 2, correct GPU: Task Manager → Details tab → GPU column → confirm obs64.exe is on GPU 1 (the discrete one).
  3. Test 3, Twitch private stream: start a private stream (Twitch account settings → Security → uncheck "List my stream"), check on your phone if the picture lands.

If the three tests pass, you are done. If one fails, you know exactly which step to re-check (not the whole stack).

Common Pitfalls Beyond the Big Four

A few subtle traps that wreck a perfectly good Game Capture setup:

  • Running OBS on a different monitor than the game while Display Capture is also active: the two sources compete for the swap chain. Pick one capture method per scene.
  • Antivirus quarantines the OBS hook DLL: Bitdefender and Kaspersky occasionally flag graphics-hook64.dll as suspicious. Add the OBS install folder to exclusions. Source: OBS forum recurring report.
  • Old browser source overlapping the game source: if a transparent browser source covers the canvas, you see black even though Game Capture is working. Toggle source visibility one by one to isolate.
  • Driver rollback after a Windows Update: Windows 11 sometimes downgrades GPU drivers silently. Reinstall the latest NVIDIA Studio or AMD Adrenalin driver after every cumulative update.
  • OBS 30+ on Windows 10 22H2: a known display compositor regression sends Game Capture into black for some setups. Workaround: use Game Capture method "DXGI Manual" instead of Auto in the source properties.

These are not the first thing to check, they only matter once the big four (GPU, admin, HDR, anti-cheat) are ruled out.

Conclusion: offload what does not depend on the live

OBS bugs come back. GPU driver updated, Windows updated, anti-cheat updated: every cycle ships a new edge case. That is the cost of live broadcasting.

One question is worth asking: should your entire content workflow depend on a flawless live? If you lose 30 minutes before every stream debugging OBS, your TikTok and Shorts pipeline take the hit too. Snowball, the app I'm building to automate Twitch clip extraction and distribution to TikTok and Shorts, attacks that exact angle: clips ship from your VODs even when one stream in five blows up mid-session. The live broadcast remains a single point of failure; the clipping and distribution layer has no reason to be one too.

In the meantime, keep this 3-question diagnostic handy. Next time the black screen hits, you know what to check, in what order, and you skip the five-random-fixes loop.

For more on hardware and OBS setup:

FAQ

Why does OBS show a black screen with Game Capture?

Three causes cover almost every case. Roughly 70% of the time you are on a laptop with two GPUs and OBS is running on the wrong one (the integrated Intel or AMD chip) while the game runs on the discrete NVIDIA or AMD card: the two never see each other, guaranteed black screen. About 20% of the time OBS is not launched as administrator and lacks the rights to hook the game process. The remaining 10% comes from Auto HDR on Windows 11 25H2 or newer, a bug introduced in late 2025 where the OS toggles HDR mid-session and Game Capture fails to follow.

How do I force OBS to use my dedicated GPU (NVIDIA or AMD laptop)?

On Windows 11: Settings → System → Display → Graphics. Click Browse, add obs64.exe (usually in C:\Program Files\obs-studio\bin\64bit\), then pick High performance. Restart OBS and you are done. On Windows 10 the menu lives at the same spot (it has been there since 1903) or you can route through the NVIDIA Control Panel / AMD Radeon Software if you prefer the vendor driver path. Verification: Task Manager → Details tab → right-click the column header → add GPU. You can now see which GPU obs64.exe runs on.

Game Capture, Display Capture, or Window Capture, which one should I pick?

Game Capture is the default for almost every modern DirectX or Vulkan game in fullscreen: best CPU performance, lowest latency, cleanest output. Window Capture targets a specific window and works even when Game Capture fails (strict anti-cheats, Minecraft Java, very old 32-bit games). Display Capture records the whole screen: middling performance, and you will also record your Discord pop-ups and Windows notifications. Rule of thumb: try Game Capture first, fall back to Window Capture if you get a persistent black screen, keep Display Capture as last resort.

Why is OBS black on Valorant, Fortnite, or CS2?

Kernel-mode anti-cheats block OBS hooks on purpose, which is why Game Capture is hard to land on these games. Vanguard (Valorant) blocks Game Capture outright, you must use Window Capture. EAC (Fortnite) accepts Game Capture only if the game runs in borderless windowed mode, not exclusive fullscreen. VAC (CS2) lets Game Capture through but you must disable HDR. BattlEye (Apex Legends) tolerates Game Capture but Window Capture is more reliable in practice. Default reflex on competitive games: Window Capture first, Game Capture as a bonus if it happens to work.

Do I always need to run OBS as administrator?

Yes, and it is the first thing to do before going deeper into diagnostics. Modern games often run with elevated privileges (kernel anti-cheats, recent GPU drivers), and OBS needs to hook those processes from at least an equivalent context. To avoid right-clicking every time, automate the elevated launch through the Windows Task Scheduler (create a scheduled task triggered at logon, with Run with highest privileges enabled). Five minutes of setup, never bothered again.

OBS black screen after the Windows 11 25H2 update: what should I do?

Turn off Auto HDR. Settings → System → Display → HDR → toggle Auto HDR off. Windows 11 25H2 (rolled out in October 2025) introduced a behavior where the OS flips into HDR on its own for compatible games, and Game Capture cannot follow the color-format change mid-stream. If you want to keep HDR on your game, enable the HDR Game Capture checkbox in OBS 30 and newer (Game Capture source → Properties → check Capture HDR). Clean fix for both worlds.

Minecraft Java black screen with Game Capture: is that normal?

Yes, it is expected. Minecraft Java runs on the JVM and does not use DXGI, the mechanism Game Capture relies on to hook DirectX rendering. So Game Capture sees nothing but black. Solution: Window Capture in Java mode (Capture method: BitBlt or Windows 10/11 Windows Graphics Capture, depending on what works on your build). Minecraft Bedrock is the opposite, Bedrock goes through DirectX and Game Capture works fine. If you play both, keep two OBS scenes with the right sources mapped.

OBS Game Capture black screen on Roblox: fix?

Roblox runs in a sandbox close to a UWP container, and its anti-tamper layer (Hyperion since late 2024) routinely blocks the Game Capture hooks. The reliable fix is Window Capture targeting the Roblox window with Capture method set to Windows 10 (Windows Graphics Capture). Keep the Roblox window visible (not minimized), otherwise the capture frame stays blank. Game Capture may work on some setups for a few days then break after a Roblox update, so Window Capture is the stable long-term path.

OBS Game Capture Black Screen Twitch: 1 Fix in 3 Questions | Snowball