Problem
Hardware-accelerated applications appear black in capture while normal desktop content captures correctly.
Solution
Root Cause / Diagnostic:
Applications utilizing GPU hardware acceleration (such as Google Chrome, Spotify, Discord, or electron-based apps) bypass traditional BitBlt desktop capture APIs, rendering directly to private DirectX/OpenGL swapchains. When captured via legacy GDI/BitBlt window capture hooks, the switcher receives empty frame buffers, resulting in a solid black box on screen.
Actionable Fix:
1. Switch OBS Capture Method to Windows Graphics Capture (WGC): In the Window Capture source properties, set "Capture Method" to "Windows 10 (1903 and up)" to intercept modern GPU swapchains directly.
2. Disable Hardware Acceleration in Source App: In Chrome/Edge/Discord settings, navigate to System / Advanced settings and toggle "Use hardware acceleration when available" to OFF, then restart the application.
3. Capture via Desktop/Display Source as Fallback: If window hooking continues to fail, move the target window to an isolated physical or virtual display and utilize Display Capture (DXGI Desktop Duplication).
Pro Tip:
Keep a dedicated "Streaming Chrome Profile" where hardware acceleration is permanently disabled; this ensures seamless window capture without impacting your primary daily browser's GPU-assisted 4K video playback performance.
Applications utilizing GPU hardware acceleration (such as Google Chrome, Spotify, Discord, or electron-based apps) bypass traditional BitBlt desktop capture APIs, rendering directly to private DirectX/OpenGL swapchains. When captured via legacy GDI/BitBlt window capture hooks, the switcher receives empty frame buffers, resulting in a solid black box on screen.
Actionable Fix:
1. Switch OBS Capture Method to Windows Graphics Capture (WGC): In the Window Capture source properties, set "Capture Method" to "Windows 10 (1903 and up)" to intercept modern GPU swapchains directly.
2. Disable Hardware Acceleration in Source App: In Chrome/Edge/Discord settings, navigate to System / Advanced settings and toggle "Use hardware acceleration when available" to OFF, then restart the application.
3. Capture via Desktop/Display Source as Fallback: If window hooking continues to fail, move the target window to an isolated physical or virtual display and utilize Display Capture (DXGI Desktop Duplication).
Pro Tip:
Keep a dedicated "Streaming Chrome Profile" where hardware acceleration is permanently disabled; this ensures seamless window capture without impacting your primary daily browser's GPU-assisted 4K video playback performance.