START HERE
Use one application-specific audio capture path for the game, then remove broad Desktop Audio and output-device capture from that scene. Test with a browser sound and a notification while recording; the absence of an extra OBS meter is not enough to prove they were excluded.
Start with a game-only test scene
First choose Scene Collection > Duplicate, name the copy, and confirm it is active. Create a small test scene inside that copy before modifying your production layout. Include the game's video and one intended game-audio source. Leave microphone, alerts, music, and chat out until this first recording behaves correctly. This makes an unexpected sound easier to trace than it would be in a scene containing several nested overlays.
Global audio sources are saved with the scene collection. Disabling Desktop Audio below affects every scene in the active collection, not only this test scene. A new scene alone is not an isolated sandbox; keep the original collection unchanged so you can switch back.
These steps require Windows 10 version 2004 or later, or Windows 11, for application audio capture. They do not isolate a console connected through a capture card, and they do not promise to split different sounds generated inside one game. If the game's music, effects, and voice chat are already mixed together, selecting the game does not separate them afterward.
Choose one capture method for the game
OBS supports a standalone Application Audio Capture source from version 28. From 30.1, supported Game Capture and Window Capture sources can include application sound through Capture Audio. These Windows features are described in the official application-capture guide; labels may still include “BETA.”
- Launch the actual game and reach a screen with repeatable sound. A launcher may be a different process from the running game.
- Choose either the video source's audio option or a separate application-audio source. Do not enable both for the same sound.
- Select the game window and give the audio route a recognizable name. Keep the game's ordinary headphone output working.
- In the duplicated collection, disable global Desktop Audio in Settings > Audio. Remove or disable any scene-level output-device capture that would still record all headphone sound.
Your scene can still contain intentionally added alert audio later. “Game only” describes the selection you build, not a global privacy switch that overrides every other source.
Test sounds that should be excluded
Make a local recording with four short segments. First play the game's menu sound. Next pause the game sound and play a harmless browser clip. Then trigger a known notification. Finally return to the game and confirm capture resumes. Listen to the recording after stopping it, rather than judging the headphones you used during the test.
| Recording result | What to investigate |
|---|---|
| Only the game is audible | Repeat in the production scene, including scene transitions. |
| Browser or notification is audible | A broad device capture or another source still includes it. |
| Game audio sounds doubled | Look for both video-source audio and an application-audio source. |
| Game effects work but voice chat is missing | The game may use a separate voice process or output device. |
Handle launchers, menus, and unsupported audio
Repeat the test after entering a match, returning to the lobby, and relaunching the game. A source matched to a splash screen or launcher can appear correct until the real game opens. If selecting the current game window fixes it, document the working selection and check it at the start of future sessions.
Application capture is not compatible with every audio path. If the game stays silent, confirm the selected process before adopting a cable-based alternative. Follow the VB-CABLE guide or the desktop-app to OBS routing helper for a separate route. Record your original output selections so the experiment is reversible, and plan a test that proves you can still hear the game locally.
If the problem is the picture rather than sound, use the black-screen checklist. Changing the audio source will not repair a failed video capture.
Add the rest of the stream deliberately
Once game-only capture passes, add your microphone and alerts one at a time, repeating the exclusion test after each addition. Keep a short note beside your scene setup: game route, microphone route, alert route, and sounds intentionally excluded. This is especially useful when returning to a scene collection after an update.
Test every scene used during a broadcast, including starting-soon and intermission scenes. They may contain a different collection of audio sources. Before sharing a multitrack recording, listen to its other tracks too; a clean mixed track does not establish that excluded sounds are absent everywhere. Restore your previous configuration if a new route fails, then test that restored mix before going live.
When combining Application Audio Capture with multitrack recording or a Twitch VOD track, verify that Desktop Audio is cleared and every source maps to the right track in the OBS multitrack audio planner. Next, balance your isolated game fader against your mic, Discord, and alerts, or duck loud gameplay under your microphone when speaking.
Sources & version notes
Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.