Audio out of sync in a YouTube gaming VOD can come from your local capture chain, the live playback path, or the archived recording. Start by comparing a local OBS recording with the YouTube stream or VOD, rather than changing bitrate or adding delays immediately.
The key distinction is whether the audio is displaced by a stable amount or gradually moves further out of sync. A fixed offset can usually be measured and adjusted; progressive drift needs investigation of device timing, sample rates, monitoring and the complete signal chain.
Start with a local recording and the YouTube VOD
Make a short local OBS recording using the same scene, game capture, microphone, capture device and audio routing as the affected livestream. Do not create a simplified test that leaves out the part of the setup most likely to be involved. If the gaming stream normally uses a capture card, USB microphone, mixer or virtual audio device, include it.
Choose a clear sync point. A hand clap on camera is useful if a camera is involved. In a gaming VOD, look for a visible event with a sharp sound: a weapon firing, a menu click, a door closing or a sudden hit effect. The cue should be easy to find in both files.
Compare three things:
| Comparison | What it can tell you |
|---|---|
| Local recording against the OBS preview | Whether the mismatch is already present before YouTube receives the stream |
| Local recording against the YouTube live playback | Whether the delivered stream differs from the local output |
| Local recording against the archived VOD | Whether the issue appears only after the broadcast is processed as a VOD |
The local recording is not automatically the truth, but it gives you a reference outside the YouTube player. If the local file is already wrong, changing YouTube-related settings is unlikely to solve the original problem. If the local file is aligned but the stream or VOD is not, document that difference instead of assuming YouTube is responsible.
Keep the affected VOD segment, the test recording and the OBS log. Also note your OBS version, operating system, audio sample rate, capture hardware, source routing and whether the mismatch affects live playback, the archive, or both. This information prevents repeated tests that quietly change several variables.
If you are building a long prerecorded channel rather than gaming live, the same discipline applies to the source file. The encode checklist for a month-long loop explains why the file itself should be checked before it is placed into a continuous broadcast.
Check whether the mismatch is already in OBS
A local OBS recording can contain an audio problem even when the preview appears acceptable. Check each source separately rather than treating “the stream audio” as one signal.
Trace the route from the original source to OBS:
- Game audio may arrive through desktop audio, a capture card or a virtual audio device.
- Microphone audio may pass through a USB interface, mixer, software effects or a monitoring application.
- Console video and audio may enter through a capture device with its own buffering.
- Camera video may use a separate USB connection from the microphone.
- Monitoring may return audio through headphones, speakers or another device before you hear it.
Only one of these paths may be delayed. For example, the game capture could be aligned while the microphone is late, or the microphone could be correct while console audio arrives behind the video. Shifting every source in response to one bad source makes the rest of the programme worse.
Create a test scene that still uses the production sources but makes them easy to identify. Speak a short phrase while making a visible hand movement, then trigger a game sound with a clear on-screen action. If a capture card is involved, test its audio against the video it supplies, not only against your microphone.
Open OBS’s Advanced Audio Properties and review the source-level sync controls. Also inspect video-source filters and any delay settings in the capture path. An OBS forum discussion describes using measured sync delays for audio and video sources, but this is community troubleshooting guidance rather than a universal setting. The useful part is the method: measure first, adjust the source implicated by the evidence, and record again.
Do not rely on the sound you hear through monitoring as the only reference. Monitoring can have its own route and buffer. Compare the recorded file, where OBS has written the actual output, with the visible cue. If the monitoring sound is late but the recording is aligned, changing the broadcast delay would create a new error.
For a broader production check, the guide to adding captions to a prerecorded live stream is also useful because it encourages you to inspect the relationship between the finished picture and its audio before sending it to YouTube.
Measure the offset at the beginning and end
Once you have a local file and a YouTube copy, measure the same cue near the beginning and near the end of the test. You do not need a special statistic or a guessed setting. You need two observations made with the same visible and audible event.
An editor that displays the video frames and audio waveform can help. Place the playhead on the visible event and identify when the corresponding sound begins. Write down the direction in plain language, such as “the gunshot is heard after the muzzle flash” or “the microphone arrives before the mouth movement”. If the editor shows time values, record the measured difference for your own test.
Then repeat the comparison later in the recording. The interpretation is more important than the exact number:
- If the displacement is about the same at both points, you are looking at a stable offset.
- If the displacement grows, shrinks or changes direction, you are looking at drift or another time-varying problem.
- If the relationship changes suddenly, look for a source restart, dropped section, monitoring change or connection event.
- If only one source is displaced, adjust that source rather than the complete mix.
A short clip can miss drift. A long clip can introduce unrelated events and make the comparison harder. Use a test long enough to expose whether the relationship changes, then repeat the final setting with a representative gaming session.
Compare the start and end of the local recording separately from the start and end of the YouTube version. This tells you where the change occurs. Drift in both files points towards the local chain. A clean local file with a changing YouTube copy requires more evidence before you alter OBS.
YouTube’s official upload troubleshooting guidance says that audio and video tracks with different durations may not stay synchronised in an uploaded video and recommends correcting the tracks in editing software. That is relevant when checking a local file, but it is not a complete diagnosis for a live-stream archive. Do not treat it as proof that YouTube processing caused a gaming VOD mismatch.
Fix a stable offset one source at a time
A stable offset means the audio is consistently early or late by roughly the same amount. A fixed delay can align one point and remain aligned later, provided the underlying clocks are not drifting.
First identify the source that is wrong. If the microphone is early relative to the camera, adjust the microphone path. If capture-card audio is late relative to the game picture, adjust that audio source or the relevant video path according to the measured result. If only the camera is late, do not delay the game, microphone and other audio to compensate for it unless the final output requires that arrangement.
OBS exposes audio sync controls in Advanced Audio Properties. Video sources can also have delay-related filters or settings, depending on how the source is configured. The OBS forum discussion on video and audio sync describes this distinction between an audio sync delay and a delay associated with a video source. Use the discussion as a troubleshooting lead, not as a promise that one value works for every setup.
Make one change, then record the same cue again. If you change a microphone delay, capture-card settings, monitoring route and bitrate together, you will not know which change mattered. Keep a short note after every test:
- source changed
- direction of the original error
- measured adjustment
- result near the beginning
- result near the end
If the audio was early, the required correction may be a delay in that audio path. If it was late, the required correction may instead involve the video path or another source timing decision. Do not copy a millisecond value from another creator’s setup. Different capture devices, interfaces, drivers and routes can produce different delays.
After the local recording is aligned, compare it with the live playback and the archived VOD again. If only the VOD appears displaced, save the evidence and test playback on another device or player where possible. A browser, mobile device and television app may not present the same playback conditions, so one player is not enough to establish a platform-wide cause.
Investigate drift and clock timing
Progressive drift is not solved by applying a larger fixed offset. A delay can make the beginning look correct while leaving the end wrong, or make the end look correct while damaging the beginning.
Check the timing relationship between devices first. Audio and video may be produced by separate clocks. A camera, capture card, USB interface, mixer and virtual audio route can each buffer or resample differently. Verify that the relevant devices and OBS are configured consistently with the sample-rate arrangement used by your system. Change one device or route at a time and repeat the comparison.
Pay particular attention to:
- capture-card audio being used with video from a different capture path
- a microphone passing through software monitoring before it reaches OBS
- virtual audio devices that resample or buffer the signal
- a USB interface and camera operating through separate timing paths
- audio monitoring being enabled when it is not needed
- device drivers or applications changing the active route during the session
An OBS forum case discusses a monitoring-device clock or buffer issue as one possible explanation for increasing drift. Treat that as a hypothesis, not a general diagnosis. The practical test is to simplify the route, disable an unnecessary monitoring stage, or use a single known path, then see whether the local recording remains aligned from start to finish.
If the local recording drifts, continue with the local chain before testing YouTube again. Check whether the drift follows one device by recording with that device removed or replaced by an existing alternative. Do not buy a new capture card or interface solely because it is a possible category of cause; the evidence should first show which part of the chain is changing timing.
If the local file is stable but the YouTube stream or VOD drifts, preserve the files and timestamps. Compare playback more than once and on another device if possible. The available guidance does not establish one definitive YouTube-side explanation or a guaranteed post-stream repair for this pattern.
Separate sync problems from connection problems
Some creators notice bad sync at the same time as buffering, frozen pictures, dropped frames or a stream that reconnects. Those symptoms should be recorded separately from the audio timing measurement.
OBS’s official connection troubleshooting guide describes dropped frames as a connection that is unstable or unable to sustain the configured bitrate. Its remedies are aimed at network stability and connection symptoms. They are not direct audio-sync repairs.
Therefore, do not lower bitrate simply because audio and video appear out of sync. Investigate bitrate or network settings when OBS shows dropped frames, disconnections or related connection evidence. A reported case in which changing bitrate coincided with sync returning does not establish that bitrate caused or fixed the audio timing problem.
Likewise, do not use dynamic bitrate as a substitute for diagnosing the signal chain. It may change how the stream responds to network conditions, but it does not correct a microphone that is consistently late in a local recording or a clock mismatch that grows over time.
If the stream has both symptoms, run two checks: review the OBS log and network indicators for delivery problems, and compare local and YouTube recordings for timing. Keeping those investigations separate stops a network adjustment from masking a production-chain fault.
Retest with a real gaming session
Once a test recording looks aligned, use a representative gaming session before returning to an overnight or continuous broadcast. Include the sources that normally create trouble: the game, microphone, camera, alerts, capture card, voice chat and any scene changes.
Start with a short recording and then inspect an early cue and a later cue. If the setup uses several scenes, test each one. A microphone may be present in one scene but not another, while a capture-card source may have a different audio configuration after a scene transition.
Watch for changes that occur after the session has been running for a while. Drift that is invisible in a brief clip may appear later. Also note whether the problem begins after a device sleeps, a game changes audio output, a USB device reconnects or a virtual audio application is opened.
If your channel is based on prerecorded material, use a representative section with dialogue, music and sharp effects rather than a quiet section. The guide to running a continuous YouTube playlist covers continuity concerns, but the same principle applies here: test transitions and source changes, not only the first minute.
For an always-on channel, separating content diagnosis from machine operation can remove one practical failure point. StreamNeo can take a prepared video, a YouTube stream key and the broadcast operation, so your computer does not need to remain switched on; it does not, however, repair a gaming recording whose local audio and video are already out of sync.
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
Should I change the bitrate when my YouTube VOD is out of sync?
Not as a first step. Compare a local OBS recording with the YouTube stream or VOD, and change bitrate only when you also have dropped frames, disconnections or other network evidence. Bitrate guidance addresses connection stability, not a proven audio timing error.
How do I know whether the problem is a delay or drift?
Compare the same clear cue near the beginning and end of a recording. If the displacement stays about the same, it is a stable offset; if it increases or changes, investigate device clocks, sample rates, monitoring and the source chain instead of applying a larger fixed delay.
Why is the OBS preview aligned but the VOD is not?
The preview and the YouTube player are different points in the chain, so the difference needs to be measured rather than assumed to be a YouTube fault. Keep the local recording, compare playback on another device where possible, and document whether the mismatch affects live playback, the archive or both.
Should I delay all audio to fix one bad source?
No. Identify whether the microphone, game audio, capture-card feed or another source is displaced, then adjust that source or its corresponding video path. Delaying the complete mix can make sources that were already correct fall out of sync.