OBS Studio · Practical guide

Choose the Right OBS Game Capture Mode on Windows

Match fullscreen, specific-window or hotkey capture to the way you launch games, then test focus changes without exposing the desktop.

START HERE

Choose a Game Capture mode that matches your session: fullscreen detection, a named game window, or foreground selection by hotkey. Verify it while the game is active and inspect a saved sample.

Match fullscreen, specific-window or hotkey capture to the way you launch games, then test focus changes without exposing the desktop.

In this guide
Before you start
  • Windows and a game that supports OBS Game Capture.
  • A duplicate test scene and a short local recording path.

Choose how OBS should identify the game

A streamer who stays in one game and a creator who switches among several games need different selection behavior. Decide whether the source should follow a fullscreen game, remain attached to a named game window, or change only when you press a chosen key. The right mode reduces accidental capture changes.

OBS documents three Game Capture modes for Windows: fullscreen application detection, a specific game window, and foreground selection using a hotkey. Game Capture is intended for compatible games; an ordinary application window belongs in Window Capture instead.

Give the capture a clear identity

Name the source after its purpose, such as GAME — fixed title or GAME — hotkey selection. Avoid creating a new unnamed capture every time a game fails to appear. Several competing sources make it harder to tell which selection is being tested.

Open the actual game, not just its launcher, and reach a scene with visible movement. On a single-monitor setup, remember that switching away from an exclusive fullscreen game can stop its rendering. A blank or frozen preview while tabbed out is not sufficient evidence that the recording failed.

Configure and prove the selection behavior

  1. Select the matching mode

    Open the Game Capture source properties and choose the intended detection method. For a specific window, select the actual running game from the list.

    Look for: The source has one deliberate rule for finding the game.

  2. Assign a capture hotkey if needed

    For foreground-hotkey mode, set its capture key in Settings → Hotkeys. Return focus to the game and trigger that key during the local test.

    Look for: The intended foreground game becomes the selected capture without reopening its properties.

  3. Test game focus and playback

    Record while actively playing, then stop and inspect the file. Include a controlled focus change if that happens during your real session.

    Look for: The saved picture shows the expected game and reveals any focus-dependent interruption.

Test a multi-game session before relying on it

If you change games during a show, rehearse the whole handoff: leave the first game, open the next, reach its active window and select it by the chosen method. Keep a holding scene available while the new game loads. A source that captured yesterday’s title is not proof that today’s launcher behaves the same way.

For a fixed-window setup, inspect matching behavior after a game update changes its title or executable. Keep the test to the intended capture rule rather than enabling every compatibility option. A controlled selection change is easier to reverse than a collection of unexplained toggles.

Recognize when the game needs a different capture route

OBS lists games with known capture restrictions and alternatives in its troubleshooting guide. If the title is documented as incompatible with Game Capture, use that documented route instead of repeatedly forcing the same hook. Check a specific game’s current entry before copying another game’s workaround.

Once the mode works, record a short action sequence and verify both picture and the separate audio route. Game Capture selection alone does not prove the game’s sound reached the intended track. Keep the source name and capture rule in the scene notes for the next session.

Still stuck?

The preview disappears when you tab out of a fullscreen game.

Inspect a recording made while the game is active; fullscreen focus behavior can interrupt rendering before OBS receives a new frame.

Keep troubleshooting

Check the model and connection before trying another change. The device page gathers the related symptoms.

More help with OBS Studio ↗

Sources & references

Based on the linked first-party OBS documentation checked on 4 November 2026. The exercises and acceptance checks are editorial workflows for you to run; no hands-on OBS session or hardware benchmark is claimed.

  1. OBS — Game Capture Source ↗Checked 2026-11-04
  2. OBS — Game Capture Troubleshooting ↗Checked 2026-11-04

Spotted something out of date? Let Alex know.

How we put our guides together ↗
READ NEXT

A few places to go from here.

All stories

OBS Black Screen? How to Fix Game, Window and Display Capture

OBS shows black instead of your game or screen? Try these quick checks for Windows and Mac.

OBS Hotkeys Stop Working in Games: Check Focus and Conflicts

Compare the same shortcut in OBS, on the desktop and in the game before changing permissions.