If game audio is missing from a YouTube VOD rerun made with OBS, first identify which output is silent: the live stream, YouTube’s archived stream, or a local OBS recording. Those are different outputs, and a setting that fixes a local recording does not necessarily explain how YouTube handles an archive.
For OBS itself, start by checking whether the game’s audio reaches the mixer, then verify the tracks on any local recording you intend to replay. The official material reviewed here explains OBS capture and local track behaviour, but does not establish exactly how YouTube selects or preserves audio tracks in every livestream archive.
Identify which replay or recording is missing audio
Make a short note of where you can reproduce the problem. Is the game silent while you are live, silent only when you watch the archived stream on YouTube, or silent in a file recorded to your computer by OBS? If you are replaying a prerecorded video through OBS, that is another path: the video file’s audio and the OBS output both need to be checked.
This distinction matters because OBS can send audio to more than one destination. Its mixer can show that a source is active, while a recording track, stream output, or later playback behaves differently. A local file that plays music but not game sound is not proof that YouTube dropped the game audio. Conversely, audible game sound in the live programme does not by itself establish how the resulting archive will behave.
Use the simplest check available: listen to the live output, open the local recording if you made one, and play the YouTube archive separately. Note whether only the game is absent or all programme audio is absent. Also note whether the game can be heard in OBS’s mixer while it is running. These observations narrow the fault without changing several settings at once.
If the live broadcast itself ends or loses output, handle that separately from audio-track troubleshooting. The checks in our guide to a YouTube live stream ending unexpectedly cover a different failure path. Here, keep the question narrow: where does the game sound disappear?
Check OBS game-audio capture
For a PC game, OBS documents two ways to capture its sound. In OBS Studio 30.1 or later, edit or add a Game Capture or Window Capture source and enable Capture Audio (BETA). This ties audio capture to the game or window source. Check that the intended game is selected and that the source is active in the scene you are actually using.
Alternatively, add an Application Audio Capture (BETA) source and choose the game’s window. OBS lists per-application audio capture for Windows 10 version 2004 or later and Windows 11. In most cases, matching by application type is the recommended approach; if the game’s window title changes, matching by executable name can be useful. The OBS Project’s Application Audio Capture guide has the supported setup details.
After adding either source, look at the OBS audio mixer while the game is producing sound. A moving meter is evidence that OBS is receiving audio at that point; it does not prove that the desired output track or YouTube archive contains it. If the meter is still, check that the source points to the right game, the game is not muted in its own settings, and the game is sending sound to the playback device OBS is capturing.
If you use Application Audio Capture alongside global Desktop Audio, OBS warns that capturing both can cause echo. For that particular configuration, its guide advises disabling the global Desktop Audio source in Settings → Audio. Do not treat this as a universal rule for every scene: if your setup relies on Desktop Audio for other applications, first make sure those sounds are captured another way before disabling it.
A useful comparison is to test one capture method at a time. If Game Capture audio works, there may be no need to add another application source. If Application Audio Capture works on its own but the combined setup echoes, remove the duplicate path rather than lowering a fader until the symptom is less obvious. The aim is one clear path for the game’s sound.
Verify audio tracks and output settings
OBS sources can be assigned to audio tracks. That is useful when you want separate audio components in an editing workflow, but a track assignment does not automatically mean every player will combine all the tracks for you. The OBS Project’s Multiple Audio Track Recording Guide says standard video players play one audio track at a time. For a file intended to play directly, OBS recommends putting all the audio you need on track 1 and enabling track 1 in Settings → Output.
Open Advanced Audio Properties from the mixer and inspect the track boxes for the game capture source and any other audio you need, such as microphone or background music. Then open Settings → Output and check the recording track selection. The exact combination depends on whether you want a simple mixed file or separate tracks for editing. For straightforward playback, make sure the same track contains the game and the other sounds that should be heard together.
| Recording need | Track approach | What to check |
|---|---|---|
| Play the file directly in a standard player | Put all required audio on track 1 | Track 1 is assigned to the sources and enabled for recording |
| Edit game, microphone and music separately | Assign sources to separate tracks as needed | The editor can access the selected tracks; do not assume a standard player mixes them |
| Diagnose a silent local file | Keep the test simple, with required sources on one track | Confirm the track is enabled in Output and listen to the resulting file |
The trade-off is convenience against editing control. A single mixed track is usually easier to check and play. Separated tracks are more flexible in an editor, but if the player chooses a track that contains only the microphone, the game can appear to be missing even though it was recorded elsewhere in the file.
These settings address an OBS recording. They are useful evidence about the sound OBS captured and how a local file was written, but they are not a guarantee about a YouTube livestream archive. In particular, do not infer YouTube archive behaviour from track assignments alone.
Test with a short local recording
Before relying on a long session, make a short local recording with the game running. Include only the sources you need for the test, and speak or make another clear microphone sound if you are also checking the microphone. Stop the recording and play it in a standard video player. This separates capture problems from issues that appear later in the live or archive path.
Listen for the game itself, not only the overall volume. If the game is absent but your microphone is present, revisit the game capture source and its track assignment. If neither is audible, check the selected output track and whether the sources are muted. If you hear the game but also hear it twice or with an echo, look for duplicate capture through both an application source and Desktop Audio.
When the local test plays correctly, keep a note of the scene, source and output settings you tested. That gives you a known-good baseline if a later YouTube archive is different. Avoid changing capture method, track assignment and output settings together: if the result changes, you will not know which change mattered.
For a prerecorded video that you are replaying through OBS, test the source file directly as well as the OBS recording. If the source file has no game audio, OBS cannot restore it. If the source file sounds correct but the OBS recording does not, check that the media source is audible in the mixer and included on the recording track. This is not the same as replaying an already-published YouTube archive.
Confirm what reaches the live output
Once the local capture is understood, check the actual live programme. Listen from a separate playback device or browser rather than relying only on the OBS mixer. A mixer meter shows audio reaching OBS, but the live output is the relevant test when you are asking whether viewers can hear the game.
YouTube’s encoder setup help describes encoders such as OBS as a way to broadcast gameplay. It does not, in the material reviewed for this article, specify which OBS audio track a YouTube archive will preserve or how a later rerun handles it. Treat the live listening check and the archive check as separate observations.
If the live programme is missing only game sound, return to the capture source and confirm it is active in the scene used for the broadcast. If the whole programme is silent, check the broader audio path and output selection rather than focusing on a game-specific source. If the live output is correct but the YouTube archive differs, record that distinction and avoid applying Twitch-only guidance as a YouTube fix.
An always-on channel adds a practical constraint: you may not want to interrupt a working broadcast to experiment. Make configuration changes during a planned test where possible, and use a short local recording first. If you are building a loop from a prerecorded file rather than capturing gameplay live, the relevant questions about file audio and loop continuity are closer to those in our guide to streaming a 24/7 ambience video.
Separate OBS recording behaviour from YouTube archives
OBS’s multi-track guide is about recording and playback of recordings. Its advice to put all required sound on track 1 is practical when you intend to open the file in an ordinary player. It should not be recast as a setting that controls a YouTube livestream archive.
There is a platform-specific feature that can confuse this issue: OBS has a Twitch VOD Track guide describing separate feeds for a live Twitch stream and its Twitch VOD. That documentation is explicitly about Twitch. It is not evidence that selecting a Twitch VOD Track changes the audio in a YouTube archive. If you want to read it for a Twitch setup, use the OBS Project’s Twitch VOD Track guide, but do not copy its behaviour over to YouTube.
The official YouTube encoder page confirms broadcast setup at a high level, not the complete archive audio-track pipeline. The reviewed sources therefore leave an important limit: they do not establish a universal reason for game audio to be missing from a YouTube VOD rerun, or a single OBS multi-track setting that fixes every such report. A local recording test can establish what OBS captured locally; a live check can establish what you heard from the broadcast. Neither alone explains every difference in an archive.
If your OBS recording and live output both contain game sound, but the archive does not, preserve the evidence: note the stream, the time, which outputs you checked, and whether the local test was audible. Check YouTube’s current official help for the relevant live-stream or archive issue, and avoid repeatedly changing OBS tracks on the assumption that they govern YouTube’s archive. For an issue that appears only after publication, YouTube-side handling needs to be checked as its own stage.
If instead the local recording is the deliverable you will replay or upload later, the answer is more concrete: use a tested capture source and make sure the audio you need is on the track that your intended player or editor will use. For creators comparing ways to keep a continuous channel running, our article on overnight OBS restarts covers a separate operational risk; it does not replace this audio test.
For this particular problem, StreamNeo removes the need to keep a local OBS computer running for a file-based 24/7 YouTube stream, but it does not diagnose an OBS game-capture or YouTube archive-track issue. Keep those questions separate: test the audio in the file and the live output before changing how the channel is operated.
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 my game audio missing from a YouTube stream replay?
First check whether it was missing from the live output, only from the YouTube archive, or also from a local OBS recording. OBS capture and local track settings can be tested directly, but the reviewed official sources do not establish one universal cause for missing audio in a YouTube archive.
How do I capture game audio separately in OBS?
On OBS Studio 30.1 or later, you can enable Capture Audio (BETA) on a Game Capture or Window Capture source. You can also use Application Audio Capture on supported Windows versions; if you use that alongside Desktop Audio, check OBS’s advice about disabling the duplicate global capture to avoid echo.
Why can’t I hear the game in my OBS recording?
Check that the game appears in the mixer, that its source is active, and that the recording track is enabled in Settings → Output. For direct playback in a standard player, put all required audio on track 1; separated tracks may be intended for editing rather than automatic mixing.
Should I use OBS’s Twitch VOD Track for a YouTube archive?
No conclusion about YouTube follows from OBS’s Twitch VOD Track guide, which describes Twitch live and VOD audio. Check YouTube’s current official guidance for archive-specific issues, and use OBS track advice to troubleshoot local recordings rather than treating it as a guaranteed YouTube archive fix.