A black Game Capture preview in OBS usually points to a source setting, a conflict with another program, a mismatch between the GPUs used by OBS and the game, or a limitation in the game itself. Check the capture mode and target while the game is running before changing anything else.
Work through one change at a time and test the preview after each one. Game Capture is not compatible with every game, so if the usual checks do not help, move to a source the game supports rather than repeating the same fix.
Check the Game Capture Mode and Target
In OBS, select the Game Capture source in the Sources panel and open its properties. Check which mode it uses and whether it points to the game you are trying to capture. A source configured for a different window, or for a mode that does not match how the game is running, can leave you looking at a black preview.
OBS offers three modes: capture any fullscreen application, capture a specific window, and capture a window selected with a hotkey. The fullscreen option is useful when the game is running fullscreen and you do not need to bind the source to one particular title. Specific-window capture gives you more control, but you must select the correct running game. Hotkey mode can suit someone who switches between games, provided the hotkey is set and used as intended.
Also check the scene itself. The source needs to be present and visible, and it should not be obscured by another full-screen source layered above it. If you have several scenes, make sure you are viewing the one that contains the Game Capture source. A working source in a different scene will not appear in the preview you are watching.
For this first test, leave the other Game Capture options at their defaults unless you have a specific reason to change them. Changing multiple properties together makes it hard to tell which one mattered. If you are also setting up OBS for a live broadcast, keep capture diagnosis separate from output configuration; the OBS settings for YouTube keyframes and NVENC concern the stream sent to YouTube, not whether a game hook appears in the preview.
Select the Game While It Is Running
For specific-window mode, start the game first. Then open the Game Capture properties and choose the running game from the window list. OBS’s setup guidance makes this point because a game that is not open cannot be selected as the active target. After choosing it, keep the game open and bring it to the foreground to see whether the preview responds.
If the game does not appear in the list, do not assume the source is broken yet. Confirm that the game has finished launching and that you are selecting the actual game window rather than a launcher, settings utility or crash reporter. Some games move from a launcher to a separate process or window once they start. Reopen the properties after the game reaches its playable screen and check the available targets again.
A practical test is to open the game, reach a menu or safe pause point, select that live window in OBS, then switch back to the game. Avoid testing only on a loading screen: some titles render differently during startup, and an inactive or minimised fullscreen game may stop drawing frames. If the preview is black only after switching away from the game, return to it before deciding that capture has failed.
OBS documents that some games may require OBS to run as administrator. Treat that as a game-dependent check, not a default requirement. If the target is correct and other tests have not helped, close OBS, reopen it using “Run as administrator”, and try again. Return to normal launch behaviour if it makes no difference; elevated access is not a substitute for identifying a conflict or a game limitation.
Try Fullscreen, Specific-Window, or Hotkey Mode
Choose the mode that corresponds to how you play. Fullscreen mode asks OBS to find a fullscreen game, while specific-window mode binds capture to a selected application window. Hotkey mode is intended for a window chosen with a shortcut. Switching mode is a useful diagnostic because it tests a different selection path, but it does not make an unsupported game compatible.
| Mode | Useful when | What to check |
|---|---|---|
| Fullscreen application | The game is running fullscreen and you want OBS to capture it without choosing a named window | Keep the game active for the test; some games stop rendering when minimised |
| Specific window | You want to capture one particular game window | Start the game first and select its actual running window |
| Hotkey-selected window | You switch between games or want to choose a window on demand | Confirm the hotkey is configured, then use it with the intended game open |
Try one mode, then return to the game and observe the preview. If you use hotkey mode, make sure the shortcut does not conflict with a game action or another application. If the game is fullscreen and you need to watch OBS at the same time, use a second monitor where available, or make a brief test recording and review it afterwards. A black preview while the game is minimised can reflect the game’s rendering behaviour rather than a failed capture.
Some titles behave better in windowed or borderless fullscreen mode. If Game Capture remains blank, try those display modes as a test and, where appropriate, use Window Capture instead. OBS’s Game Capture source guide explains the available modes and notes that a small number of games do not work with Game Capture. The guide is a source overview, not a promise that any particular game can be hooked.
Check for Hook Conflicts
Game Capture works by attaching to a game’s rendering process. Another program that also draws over the game, monitors its performance or records it can interfere. OBS identifies overlays, performance displays and other capture applications as possible conflicts. Close likely candidates temporarily, then retest the same scene and game; this is more informative than uninstalling software or changing unrelated OBS settings.
Start with software that is visibly active over the game: FPS counters, graphics-card overlays, chat overlays, monitoring tools and recording or clipping utilities. OBS specifically calls out MSI Afterburner and RivaTuner as common conflict sources. Other overlays can also matter. Exit them fully for the test rather than merely hiding their on-screen display, then restart the game if it still appears to have retained a hook.
You do not need to remove an application just because it is installed. The point is to isolate whether it is involved. Close one likely conflict, test the preview, and reopen it if nothing changes before moving on to another candidate. If capture begins working after an application is closed, adjust that application's overlay or capture settings if possible, and verify the arrangement again before relying on it for a long session.
Security software can also interfere in some cases. Do not disable antivirus or firewall protection indiscriminately. Check the software’s own guidance and confirm that OBS is allowed to communicate or run as expected. If you are unsure what a rule does, leave it in place and consult the product’s support information rather than weakening protection as a broad troubleshooting step.
The OBS list of known conflicts is useful when you are unsure whether a particular overlay or capture utility is relevant. Keep a short note of what you closed and what changed. For a channel built around a repeatable scene or loop, that record helps separate a game-capture issue from unrelated audio or scene problems; the guide to preventing OBS audio clipping on a looped live stream covers a different symptom, but the same habit of testing one variable at a time applies.
Check GPU Selection and Mismatch
On a laptop or a computer with more than one graphics processor, OBS and the game may be using different GPUs. A common arrangement is for desktop applications to use integrated graphics while a demanding game runs on a discrete GPU. OBS warns that Game Capture may not work when OBS is running on the integrated GPU and the game on the discrete GPU.
Check which GPU is assigned to each application in Windows graphics settings or the relevant graphics control panel. For Game Capture, OBS’s laptop guidance recommends assigning OBS to the high-performance GPU on supported Windows versions. After changing the assignment, close and restart OBS before testing; a setting change may not affect an already-running process. If the mismatch remains, check the game’s assignment too so both applications are using compatible graphics paths.
Do not infer the GPU assignment solely from the name of the laptop or from a game’s graphics quality. Verify the actual application preference, and test again with the game running. If you change both OBS and game assignments, record the original choices so you can restore them if the change introduces another problem. GPU selection can also affect power use or which display an application can access, so choose deliberately rather than forcing every program to use the discrete GPU.
Display Capture is a separate fallback, not a way to repair the Game Capture hook. OBS describes a cross-GPU display-capture method for OBS 27 or later on Windows 10 version 1903 or later. Its laptop guide says to try the Windows 10 capture method manually if automatic selection fails; a yellow border may appear with that method. Check the current OBS laptop troubleshooting guide for the exact procedure and compatibility details before switching sources.
Display Capture includes the monitor image rather than targeting only the game window, so notifications or other desktop content may also be visible. Consider what will appear in the broadcast before using it. For a 24/7 video channel, running the encoding computer continuously also has practical power and maintenance implications; the comparison of a home PC and an Azure VM for a loop stream is relevant to that separate operating decision, not a fix for GPU mismatch.
Consider Game-Specific Limitations
After checking mode, target, conflicts and GPU selection, consider whether the title can be captured through Game Capture at all. OBS describes the source as a Windows method for capturing DirectX or OpenGL games, but its documentation also says that a small number of games do not work with it. Older games and emulators may be incompatible with modern game-hooking methods. A black screen in such a case is not evidence that you missed a universal setting.
Some games have a documented alternative. OBS recommends Window Capture for certain titles, including Counter-Strike 2 and Destiny 2. It also notes that some DirectX 12 games can crash OBS or show frame issues, and suggests trying DirectX 11 where the game offers it. Fortnite is among the examples with a DX12-to-DX11 workaround in OBS’s guide. These are examples, not a complete compatibility list, and the available options depend on the game and its current version.
If the game offers windowed or borderless display, try Window Capture with that mode. Window Capture targets an application window rather than hooking the game in the same way. It may not behave identically to Game Capture, and depending on the setup it can include window borders or be affected by how the window is rendered. Test the actual output rather than assuming the preview alone tells the whole story.
Use Display Capture only if capturing the whole display is acceptable and your setup supports it. It is broader than a game window and can expose anything shown on the desktop. For a console, the troubleshooting question is different: OBS describes using a Video Capture Source with a capture device, or capturing a console remote-play application window when the network is fast enough. A capture card is therefore a console-input option, not a general remedy for a blank PC Game Capture source.
If the game cannot be hooked and you need a hands-off 24/7 channel, repeated local restarts may not address the underlying limitation. StreamNeo removes the need to leave your own computer running for a file-based YouTube loop, but it is not a game capture workaround: it takes an uploaded video rather than a live game feed. Decide first whether your channel needs interactive gameplay capture or can use a prepared video.
Test the Preview After Each Change
Treat each adjustment as a test with a clear result. Start with the game open, confirm the source and scene, change one setting, then return to the game. If you alter the mode, GPU assignment and overlay settings all at once, you will not know which action helped, and a later failure will be harder to diagnose.
For a fullscreen title, do not judge the source only while the game is minimised. OBS notes that some fullscreen games stop rendering after Alt+Tab. Keep the game in the foreground while watching the preview on another monitor, or record a short test and review it. If capture is present in the recording but the live preview went black after switching applications, the issue may be minimisation behaviour rather than a failed hook.
When a test succeeds, verify more than a single frame. Check that motion continues, the correct game is shown, and the chosen source does not reveal desktop content you meant to exclude. Then try the same sequence after restarting OBS and the game, because a one-off preview does not prove the configuration will survive a normal launch. Avoid promising yourself that it will never fail; the point is to confirm the conditions that currently work.
If the preview remains black, write down the game, display mode, selected capture mode, GPU assignments and conflicting applications tested. Consult OBS’s current troubleshooting page and the game’s own settings or support notes for an API or window-capture alternative. The OBS troubleshooting path for Game Capture provides the primary reference for these checks. If this is part of a streaming workflow, diagnose the source locally before changing the live-output settings; the Windows 11 4K streaming setup guide addresses output demands, which are distinct from whether the game can be captured.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Why is Game Capture black while the game is open?
The source may be set to the wrong mode or target, another overlay or recording tool may conflict with it, or OBS and the game may be using different GPUs. Some games also do not work with Game Capture. Check those possibilities in sequence rather than assuming a single fix applies to every title.
Why does the preview go black when I Alt+Tab?
Some fullscreen games stop rendering when they are no longer in the foreground, so OBS can show a black preview while the game is minimised even if capture works when the game is active. Test with the game in front, watch OBS on another monitor, or make a short recording and review it. Windowed or borderless mode may be a more practical way to work.
Should I use Display Capture instead?
Use it only if capturing the entire display is acceptable and your Windows and OBS versions support the relevant method. It can include notifications and other desktop content, unlike a source aimed at a game window. For a cross-GPU laptop setup, check OBS’s current laptop guide for its stated version requirements.
Will running OBS as administrator fix every game?
No. OBS says some games require administrator access, so it is worth testing when the target and other basic settings are correct. It will not resolve every conflict, GPU mismatch or game-specific limitation, and it should not be treated as a universal fix.