OBS Black Screen on Game Capture: 9 Fixes That Actually Work

You hit Record, switch to your game scene, and OBS game capture shows a perfectly black rectangle. The game is running. OBS is running. Yet nothing appears. It is one of the most Googled OBS problems in existence, and it has been breaking setups since Windows 10 added hybrid GPU switching.

This guide walks through every real cause of the OBS game capture black screen, ranked from most common to most obscure. You will get the exact settings to change, the exact menus to navigate, and a plain explanation of why each fix works. If the first solution does not apply to your machine, the next one will.

🔍 Why Does OBS Game Capture Show a Black Screen?

Before diving into fixes, understanding the root cause saves you from randomly clicking through every setting. OBS game capture works by injecting a graphics hook (a small piece of code) directly into the game's rendering pipeline. This hook reads the frame data before it gets sent to your monitor. According to the OBS Project documentation, the hook must run inside the same GPU process as the game to capture frames successfully.

The hook fails, and you see black, in three broad scenarios:

• GPU mismatch: Your laptop or desktop uses two GPUs (an Intel/AMD integrated chip plus a dedicated Nvidia/AMD card). Windows runs OBS on one GPU and your game on the other. The hook cannot cross the GPU boundary.
• Permissions gap: Your game runs with elevated (Administrator) privileges. OBS, running as a standard user, cannot inject its hook into a higher-privilege process.
• Capture mode conflict: Windows fullscreen optimizations, HDR settings, or certain DirectX versions interfere with how OBS hooks into the frame buffer.

Most machines have only one of these issues. Identifying which one applies to you cuts the fix time from 30 minutes of guessing to under 5 minutes.

🛠️ Fix 1: Force OBS to Use Your Dedicated GPU (Fixes 70%+ of Cases)

This is the single most common cause on laptops and on desktops with both integrated and discrete graphics.

Why it works: Windows 10 and 11 use a feature called Microsoft Hybrid Graphics, which dynamically assigns apps to either the integrated GPU (for battery saving) or the dedicated GPU (for performance). When Windows puts OBS on the integrated Intel/AMD chip but the game runs on the Nvidia/AMD dedicated card, the game capture hook has no path between them.

According to Nvidia's developer documentation, the game capture hook in OBS operates within a single GPU's memory space and cannot read framebuffer data from a separate graphics adapter.

Steps:

1. Open Windows Settings (Win + I)
2. Go to System > Display > Graphics settings (on Windows 11: System > Display > Graphics)
3. Click Browse, navigate to your OBS install folder (typically C:\Program Files\obs-studio\bin\64bit\), and add obs64.exe
4. Click on obs64.exe in the list, select Options
5. Choose High performance (this assigns OBS to your dedicated GPU)
6. Click Save, then fully close and relaunch OBS

🔑 Fix 2: Run OBS as Administrator

Why it works: Games that run launchers (Battle.net, Epic Games Launcher, Steam with certain configurations) or that require elevated permissions will run as Administrator. A standard OBS process cannot hook into an elevated process. Windows blocks cross-privilege injection as a security boundary. Running OBS as Administrator places both processes at the same privilege level, letting the hook work.

Steps:

1. Close OBS completely
2. Right-click the OBS shortcut or .exe
3. Select Run as Administrator
4. Launch your game, then switch back to OBS. The game capture source should populate.

If this fixes the issue, make it permanent: right-click OBS.exe > Properties > Compatibility tab > check "Run this program as an administrator" > Apply.

🖥️ Fix 3: Disable Windows Fullscreen Optimizations

Windows applies "fullscreen optimizations" to games running in exclusive fullscreen mode. Microsoft introduced this in Windows 10 to improve Alt+Tab performance, but it effectively converts exclusive fullscreen into a borderless windowed mode. Some versions of this optimization interfere directly with OBS's DirectX hook.

Steps:

1. Find the game's main .exe file (not the launcher)
2. Right-click > Properties > Compatibility tab
3. Check "Disable fullscreen optimizations"
4. Click Apply, relaunch the game

Alternatively, run the game in Borderless Windowed mode from the in-game graphics settings. Borderless Windowed reliably works with OBS game capture because Windows is not managing the fullscreen state at all.

⚙️ Fix 4: Switch the Capture Method in OBS

OBS offers three capture methods under the Game Capture source:

Steps:

1. In OBS, right-click your Game Capture source > Properties
2. Under Capture Method, try switching from Auto-detect to Windows 10 (1903+). This is particularly effective for games installed via Xbox Game Pass or the Microsoft Store.
3. If that does not work, try Force Direct Hook and select the game from the Window dropdown that appears.

The Windows.Graphics.Capture API was introduced in Windows 10 version 1903 as a supported path for third-party capture software. OBS added native support for it in OBS Studio 26.1.

🎮 Fix 5: Add the Game Manually and Disable "Allow Transparency"

Two small settings inside the Game Capture source cause silent failures that look identical to a GPU mismatch.

Steps:

1. Open Game Capture source properties
2. Under Mode, switch from "Capture any fullscreen application" to "Capture specific window"
3. Set the Window dropdown to your running game
4. Uncheck "Allow Transparency". This setting tells OBS to capture the alpha channel, which some games do not expose, resulting in a black output.

🔄 Fix 6: Check for OBS and GPU Driver Updates

This one sounds obvious but gets overlooked. A specific combination of OBS 28.x and Nvidia driver versions 531.xx caused widespread game capture failures in early 2023, documented in the OBS Project GitHub issue tracker (#8792). The fix was a driver rollback or an OBS patch update.

• Update OBS: Help menu > Check for Updates (or download from obsproject.com)
• Update GPU drivers: Open GeForce Experience (Nvidia) or AMD Software: Adrenalin Edition and check for updates
• If a recent driver update broke your capture: Device Manager > Display Adapters > right-click your GPU > Properties > Driver tab > Roll Back Driver

🚫 Fix 7: Exclude OBS and Your Game from Antivirus

Real-time antivirus scanning can block OBS's hook injection because the injection technique is mechanically similar to what malware does: writing code into another running process's memory. Windows Defender and most third-party AV tools can silently block this without showing any error in OBS.

1. Open Windows Security > Virus & Threat Protection > Manage Settings
2. Scroll to Exclusions > Add or remove exclusions
3. Add the full OBS installation folder (e.g., C:\Program Files\obs-studio\://gpu/)
4. Add the game's .exe folder as well
5. Restart OBS and retest

🌐 Fix 8: Use Display Capture as a Short-Term Workaround

If none of the above fixes work and you need to go live right now, switch from Game Capture to Display Capture. Display Capture records your entire monitor rather than hooking into the game process, which means it bypasses the hook entirely.

Drawbacks of Display Capture:

• Captures everything on the monitor (notifications, popups, alt-tabs)
• Slightly higher CPU/GPU overhead than Game Capture
• Cannot capture HDR content correctly in most configurations

Display Capture is not a permanent solution for most streamers, but it lets you get live while you troubleshoot the Game Capture issue. If you are already dealing with the complexity of managing capture sources, game audio, overlays, and multi-platform streaming simultaneously, a browser-based tool like Yostream handles the stream delivery side without any local software, which removes one entire layer of potential conflict from your setup.

🖥️ Fix 9: Disable Hardware-Accelerated GPU Scheduling (HAGS)

Hardware-Accelerated GPU Scheduling (HAGS) is a Windows 10/11 feature that offloads GPU scheduling from the CPU. It was introduced in Windows 10 version 2004 and can conflict with OBS's frame capture timing, particularly on older Nvidia cards (pre-RTX 20 series).

Steps:

1. Open Windows Settings > System > Display > Graphics settings
2. Turn off "Hardware-accelerated GPU scheduling"
3. Reboot your PC (this change requires a restart)
4. Retest game capture in OBS

📊 Summary: Which Fix to Try First

Streamers Also Ask:

1. Why does OBS show a black screen only for some games?

Different games use different graphics APIs (DirectX 9, 11, 12, Vulkan, OpenGL) and different launcher privilege levels. OBS's hook works differently across each API. A game using DX12 with UAC elevation will fail with the same OBS settings that work perfectly for a DX11 game running without elevation. The fix is usually changing the Capture Method in OBS's Game Capture source to match the game's API.

2. Does this issue happen on Mac?

Mac has its own version of the problem but for different reasons. OBS on macOS uses the ScreenCaptureKit API (since OBS 28.0 on macOS 12.5+). The black screen there is usually caused by missing Screen Recording permission in macOS Privacy & Security settings, not a GPU mismatch.

3. OBS game capture black screen. Does reinstalling OBS fix it?

Rarely. A fresh OBS install will fix the issue only if your existing installation has corrupted hook files, which is uncommon. The black screen is almost always a configuration issue (GPU assignment, admin rights, capture method) rather than a broken OBS installation. Try all nine fixes before reinstalling.

4. Should I use Game Capture or Display Capture in OBS?

Use Game Capture when possible. It hooks directly into the game's render pipeline, which gives you lower CPU overhead, cleaner capture (only the game, no desktop), and the ability to capture games in exclusive fullscreen. Display Capture is a fallback for situations where the Game Capture hook refuses to work, particularly with anti-cheat-protected games.

5. Anti-cheat software (EAC, BattlEye) is blocking OBS game capture. How do I fix it?

Anti-cheat systems like Easy Anti-Cheat and BattlEye actively block code injection, which is exactly what OBS's Game Capture hook does. For these games, you must use Display Capture or Window Capture. There is no workaround that bypasses anti-cheat without risking a ban. Most competitive games that use anti-cheat officially support OBS's Display Capture path.

6. OBS game capture black screen after a Windows update. What changed?

Windows updates sometimes reset Graphics Settings assignments, re-enable fullscreen optimizations, or toggle HAGS. After any major Windows update, revisit Fix 1 (GPU assignment) and Fix 3 (fullscreen optimizations) first. These are the two settings Windows updates most commonly reset without warning.

7. Can I stream directly without dealing with OBS capture issues?

Yes. Browser-based streaming platforms like Yostream let you go live on multiple platforms simultaneously directly from your browser, without any capture software, hooks, or driver dependencies. If your primary goal is getting your stream live fast rather than local recording, it is worth testing as a zero-setup alternative.

8. Why does OBS game capture work in windowed mode but not fullscreen?

Exclusive fullscreen mode gives the game direct GPU output access, which Windows manages differently from windowed rendering. OBS's hook can struggle to intercept this direct output path. Running the game in Borderless Windowed mode (not exclusive fullscreen) almost always resolves this because Borderless Windowed goes through the standard Windows compositor, which OBS can capture cleanly.

Continue Reading:

• Go live without the extra gear: How to Stream Console Games Without Using a Capture Card
• The real fix for OBS freezing: How to Fix OBS Freezing During Live Stream
• Start streaming vertical in OBS: How To Set Up Vertical Video In OBS
• Invite your first guest to OBS: How to Add a Guest to Your OBS Live Stream