First identify where the media is looping: in YouTube, in a browser or media player, or in an OBS scene or source. Each path has a different playback chain, so the useful fix depends on where audio and picture begin to diverge.
Audio may already be out of sync when playback starts, or the gap may grow as a loop continues. That distinction, and whether other Windows apps are affected, gives you a practical way to narrow the fault without treating any Windows setting or hardware purchase as a universal cure.
Identify what is looping
“Looped YouTube stream” can describe several different arrangements. You might be watching a YouTube video with the repeat option enabled, leaving a browser tab to play continuously, repeating a file in a desktop media player, or sending a loop from OBS to YouTube Live. Before changing settings, write down which application actually repeats the content and which application sends it to viewers.
If you are simply watching YouTube, the chain is the browser, Windows audio and video playback, and the YouTube player. If a separate media player is involved, it may decode and repeat a local file before sound and picture reach the output device. If OBS is creating the broadcast, its sources and scene are part of the chain as well; YouTube receives the resulting stream rather than controlling the original loop.
This matters because the same symptom can come from different places. A mismatch in one browser tab does not establish that Windows audio is wrong. A mismatch that appears only in the OBS output does not establish that the YouTube player is at fault. Treat those as questions to test, not conclusions.
Make a short note of the setup: loop location, source file or page, whether OBS is involved, and whether the audio leads or trails the image. Also note whether the offset is present immediately or becomes more noticeable over time. If you need to build or configure the live event separately, the guide to enabling live streaming in YouTube Studio covers that distinct part of the workflow.
Determine whether the drift is in the source or stream
Start with a simple comparison. Play the same file or content locally, outside the live setup, and listen for a recognisable event such as a spoken word, a hand clap, or a drum hit that coincides with visible movement. Then compare that event with what you hear in the YouTube player. Use the same passage each time; a different point in a song or video makes the comparison less useful.
A gap that is already present in the local file points you towards the source or the player handling it. If local playback is aligned but the live output is not, investigate the broadcast path, including any OBS source and scene configuration. If the YouTube player is wrong but a local preview appears aligned, compare the preview and the viewer playback before changing the source file.
Next, distinguish a fixed offset from accumulating drift. If speech begins late by roughly the same amount at the start and later in the clip, you are looking at a steady mismatch. If it begins aligned but becomes increasingly late or early, note that pattern and the elapsed playback time. This does not prove which clock or component is responsible, but it helps you avoid applying a static correction to a problem that changes over time.
VideoLAN’s VLC clock architecture documentation explains generally that audio and video have synchronisation clocks which can differ and drift. That is useful context for why a long playback path may need diagnosis, but it is not evidence that VLC, Windows, or YouTube is responsible in your particular setup. Keep the source, app and stream comparisons separate.
Compare local playback with the YouTube player
If the loop is ordinary browser playback, test the same content in another browser before changing the original setup. Check whether the same passage is out of sync there and whether the symptom starts immediately or develops as playback continues. A second browser is a comparison, not proof that the first browser is defective; extensions, browser settings and the playback path may differ.
YouTube’s green screen troubleshooting page suggests trying a different browser, turning off hardware acceleration in Chrome, and updating graphics drivers for a green player with audio. Its guidance addresses a related playback symptom, not a guaranteed fix for audio drift during a loop. If you test hardware acceleration or a driver update, change one thing at a time and repeat the same comparison, so you know whether anything actually changed.
Also check whether the mismatch follows one video or appears on other YouTube content. If only one item is affected, compare its local version, if available, and inspect whether the audio and picture are already misaligned in the source. If multiple unrelated videos behave the same way in one browser but not another, focus your next test on the browser playback path rather than editing the source file.
Avoid judging sync from a live preview alone. A preview can represent a different point in the chain from the stream a viewer receives. When possible, compare a local playback, OBS preview and YouTube playback using the same visible event. If you are sending a pre-recorded file as a continuous live programme, the guide on looping a long video file on YouTube Live without re-encoding helps clarify the broader loop arrangement; it does not replace this sync check.
Check the OBS scene and media source
When OBS creates the loop, identify the source type first. A local file in an OBS Media Source is not the same playback path as a browser source, a VLC playlist source or a capture of another application. Open the scene used for the broadcast, select the source that supplies the content, and verify that it is the source you think is looping. Check its loop option and whether the scene contains another audio source that could be playing at the same time.
OBS documents a loop control for Media Source, which can play a local media file, and loop playback for VLC Video playlists. Its Media Sources documentation also explains that VLC Video requires VLC to be installed; where applicable, the VLC installation architecture needs to match 64-bit OBS. Use the documentation for the source type actually present in your scene rather than changing options from another source type.
For ordinary video and audio files, OBS recommends Media Source or VLC Source in its encoding performance troubleshooting guide. The same guide cautions that many browser sources can significantly affect system resources. That is a reason to inspect the scene and its sources if the broadcast behaves differently from local playback; it does not establish that browser sources cause every sync problem.
Check for duplicated sound paths. For example, a file might provide audio through its media source while an application capture or another source also sends the same sound. A duplicate can sound like an echo or timing mismatch. Mute one candidate source at a time in a controlled test and listen to the local preview, then restore it before proceeding if it was not the source of the issue. Do not remove an audio source permanently just because muting it changes what you hear.
If the source is a playlist or changes at scene transitions, test the exact point where the mismatch appears. A transition can expose a different clip, source or audio track than the one you checked at the beginning. For practical transition checks in an OBS loop, the guide to smooth transitions in an OBS YouTube live loop may help with scene behaviour, while the sync diagnosis here still depends on comparing the same audio and picture event.
Check Windows output and player timing
Before adjusting a player, make sure Windows is sending sound to the intended device. Open the sound controls and verify the selected output is the speakers or headphones you are actually using. Check physical connections as well, especially if you have changed devices since the last working session. This is a basic routing check, not a specific cure for drift in a looped broadcast.
Microsoft’s Windows sound troubleshooting guidance recommends checking the output device and hardware connections, and provides the Get Help audio troubleshooter. Use it if sound problems affect unrelated applications, not only the YouTube tab or OBS output. If other Windows audio is normal and only one playback path drifts, record that distinction and continue testing the relevant app.
If you are testing in VLC and the source file itself appears to be involved, consult VideoLAN’s VLC FAQ. It discusses trying another audio output plugin and inspecting audio desynchronisation compensation for file-related sync problems. Do not enter a fixed compensation value by guesswork: first determine whether audio leads or trails and whether the measured gap stays consistent. A setting that shifts audio in one direction cannot be assumed useful when the direction or size of the mismatch is unknown.
Keep a record of each change and its result. If you try a different output device, restore the original device if the comparison is inconclusive. If you test an app setting, note the source, the passage, and whether the offset changed at the beginning or later. This avoids layering several speculative changes together and losing track of what the test showed.
Test playback and capture timing changes carefully
A useful test changes one variable at a time. First reproduce the problem with the current configuration and note the symptom. Then change a single relevant setting or path—such as the browser used for playback, a source configuration in OBS, or an audio output choice in a media player—and repeat the same passage. If there is no clear improvement, revert that change before testing another one.
Do not start by changing Windows system-wide audio options or buying a different speaker, headset or capture device. The sources for this problem do not establish that any particular Windows toggle or piece of hardware reliably fixes sync drift across looped-stream setups. A new device may change the output path, but unless a comparison points to that path, it adds another variable rather than diagnosing the fault.
If the stream uses OBS, compare the source preview with the program output and a YouTube playback of the test. Confirm that audio monitoring itself is not confusing the comparison: listening to a monitored source and the same sound through another route can create an apparent delay. For a clean test, use one listening route at a time and keep the same source and passage active.
If the issue appears in every application, broaden the check to Windows output selection and connections, then use Microsoft’s troubleshooter. If it appears only in a browser, compare browsers and playback settings. If it appears only in a particular OBS source or file, inspect that source and test the file outside the scene. These branches are a way to isolate the chain, not a guarantee that one symptom always maps to one cause.
Retest a short loop before resuming
After a change appears helpful, do not immediately leave the full channel running overnight. Run a representative test that includes the beginning and at least one loop boundary or scene transition, since a source can behave differently when it restarts. Check the same recognisable audio-video event at the start and later in the test, and note whether alignment holds or drifts.
Where your workflow permits, make the test private or unlisted and view the actual YouTube playback rather than relying only on the OBS preview. A local preview verifies one part of the path; the viewer-side player verifies another. Keep the test short enough to repeat, but long enough to see whether the mismatch grows rather than remaining fixed.
If the test passes, restore any temporary mutes or settings you used only for diagnosis, then make one final check with the intended scene and output device. If it fails, preserve your notes: loop location, source type, browser or player, whether the audio leads or trails, when the mismatch begins, and whether it affects other apps. Those details make the next troubleshooting step more useful than a list of settings already tried.
For channels that need a pre-recorded programme to keep running after the operator’s computer is turned off, StreamNeo removes the specific burden of keeping that local playback machine running; it does not establish that a source file is in sync, so test the file and viewer playback before relying on it. If you are still deciding how to handle a continuous prerecorded channel, the comparison of Astra Streaming and OBS for 24/7 prerecorded YouTube video may help you weigh the operating trade-offs separately from this audio diagnosis.
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 does audio go out of sync only after a loop has been running for a while?
A growing gap is different from an offset that is already present at playback start. Note when the mismatch first appears and compare the same passage locally, in the app creating the loop, and in YouTube playback. The pattern helps locate the part of the chain to investigate, but it does not by itself identify a cause.
Should I turn off hardware acceleration in my browser?
You can test it as a browser playback check, but YouTube’s cited guidance discusses a green player with audio rather than a universal fix for looped-stream drift. Change only that setting, repeat the same comparison, and revert it if the result is unclear. A browser test is less useful if OBS or a separate player is creating the loop.
Can I fix the problem by adding audio desynchronisation compensation in VLC?
Only consider compensation after establishing that the input file or VLC playback is where the mismatch occurs and whether audio leads or trails. VideoLAN’s FAQ discusses the setting, but the correct direction and amount depend on the observed offset. Do not apply an arbitrary value and assume it will transfer to another player or stream path.
What information should I collect before asking for help?
Record where the loop runs, whether OBS is involved, which source type is used, and whether the problem affects other Windows applications. Note if the mismatch is present immediately or accumulates, and whether sound leads or trails the picture. Include what you compared and the result of each single change.