If audio does not line up with the picture during a recorded-video YouTube Live stream, first find where the mismatch appears: in the file, the encoder output, or only in viewer playback. A stable delay on one OBS audio source may be corrected with that source’s Sync Offset; a large or changing mismatch needs diagnosis before you add delay.
Audio-picture sync and the time it takes a live event to reach a viewer are separate issues. Compare a local recording, the OBS preview or recording, and the stream as a viewer sees it, then change only the setting that corresponds to what you found.
Separate lip-sync from stream latency
A sync problem means the sound and picture do not describe the same moment together. A singer’s mouth may move before the note is heard, or a hand may strike a drum before its sound arrives. Stream latency, by contrast, is the time between an event being captured by the camera or encoder and that event appearing to a viewer. YouTube describes latency in this capture-to-viewer sense in its live stream settings guidance.
The distinction matters because both problems can exist independently. A stream may take a noticeable time to reach a viewer while the lips and voice remain aligned. Conversely, a stream can arrive quickly but still show a clapper’s hand moving well before the clap is heard. Changing the YouTube latency mode affects how quickly playback catches up and the trade-off with buffering; it is not a lip-sync control.
Start by describing what you see rather than guessing at a setting. If every visible action consistently comes before its sound, that is an audio-picture offset. If picture and sound match but a viewer sees a delayed version of events, that is end-to-end latency. If the offset changes during the stream, or only appears intermittently, treat it as a stability or source-path problem, not a fixed delay to compensate for.
For a recorded loop, look for a moment with a sharp visible action and a clear sound: a clap, drum hit, door close, or a word with an obvious consonant. A devotional channel might use a visible cymbal strike; a local news loop could use a presenter speaking directly to camera. Use the same moment in each test. Do not start by adjusting YouTube latency because the audience says the stream feels late; ask whether the audio and picture are late relative to each other.
Compare the archive, OBS preview and viewer output
A controlled comparison tells you where the fault first appears. Use a short representative section of the actual file and capture the output you intend to broadcast. Compare three points: the source file or a local archive, what OBS produces, and the YouTube playback seen by a viewer. Keep the test material and action the same each time; otherwise a different cut, loop point, or source can make the comparison misleading.
| What you observe | Where to investigate first | What it does not prove |
|---|---|---|
| The source file and local recording both have the same mismatch | The media file, its tracks, or how the source is timed | That YouTube introduced the offset |
| The source looks aligned, but the OBS recording is not | OBS source timing, routing, or encoder setup | That a viewer latency setting will correct it |
| The local output is aligned, but viewer playback is not | Stream health, delivery path, and viewer playback conditions | That the issue is necessarily the audio source |
| The offset varies between checks | Source stability, encoder load, or connection | That one fixed Sync Offset is appropriate |
| Picture and sound align, but playback starts late | YouTube stream latency or delivery buffering | That there is a lip-sync problem |
First inspect the original recorded file in a media player. Then make a local recording of the OBS programme output, using the same scenes and sources as the live stream. Finally, check YouTube playback from a separate viewer session rather than relying only on the OBS audio monitor. A monitor is useful for hearing a source, but it does not establish that the final encoded output or viewer playback is aligned. OBS community guidance also cautions that the configured offset may not be apparent in monitoring, so verify the recording or stream output rather than trusting that preview alone (discussion).
YouTube’s troubleshooting guidance recommends reviewing source quality as routed to the encoder, encoder errors, CPU load, and the local archive. If the local source and OBS output already share the same offset, focus upstream on the file, source timing, and routing. If OBS output is aligned but the viewer stream is not, look downstream at the stream health and connection before changing a source-level setting. For broader media preparation issues, see how to resize pre-recorded video for a 24/7 stream.
Find out whether one audio source is offset
Before opening an offset control, list the audio sources that feed the scene. A simple loop may have one embedded audio track. A more involved scene might combine the video file’s sound with a microphone, a mixer input, or music from another source. If only one source is late or early while the others line up with the picture, a per-source correction may be suitable. If all sound is wrong in the same way, the cause is more likely shared by the file, scene, or output path.
Test each source in isolation where practical. In OBS, mute all but one source, make a short local recording, and compare a known sharp sound with its visible action. Restore the other sources and test the full mix. Be careful about the mute method: a source that is muted in a way that changes how it is routed is not necessarily a fair test of the live output. The goal is to identify which source carries the mismatch, not merely to hear a cleaner mix.
Write down the result in plain terms: source name, whether sound is early or late, and whether the gap appears consistent across repeated checks. For a song video, compare the embedded track with the picture; for a separate microphone, compare speech with the speaker’s mouth. If the song track is aligned but the microphone is not, do not move the song and the picture to compensate. That would fix one symptom while creating another.
Also distinguish a source-specific offset from a source that drifts. If the sound starts aligned and becomes increasingly separated from the picture over a long playback, a single fixed delay cannot correct both the beginning and the end. A loop boundary that repeats the mismatch, an audio device that reconnects, or a source whose timing varies calls for further investigation. Do not treat a one-time observation as proof that a per-source offset is the right remedy.
Apply an OBS Sync Offset only to a stable source
OBS provides a per-source audio sync offset. The practical interface is in the mixer’s Advanced Audio Properties; menu wording can differ between versions. OBS documents per-source sync-offset capability in its source reference. Community support describes the Advanced Audio Properties workflow and the millisecond unit, but verify the effect on your installed version rather than treating an old forum reply as definitive UI documentation (OBS forum guidance).
Use it only after a controlled test shows a repeatable mismatch isolated to that audio source. In OBS, open the audio mixer’s Advanced Audio Properties, locate the identified source, and adjust its Sync Offset in a small step. If audio is consistently ahead of the picture, the usual correction is to make that audio arrive later; a positive delay is commonly used for this purpose. Confirm the sign and effect with a fresh recording on your own version, because a setting label is less useful than a measured result.
Do not copy a value from someone else’s setup. The correct adjustment depends on the source path and the measured gap in your own output; the source notes and primary documentation do not establish a universal correction. Change one source and one setting at a time. Record the old value before you edit so you can revert cleanly if the output becomes worse.
After the change, record the same test passage locally and compare the action and sound again. Then check the live stream output from a viewer session. Do not conclude the correction worked just because the OBS monitor sounds different. If the source becomes aligned in the local recording but the stream remains wrong, the remaining fault is later in the chain. If a small change moves the result in the wrong direction or has no clear effect, restore the previous setting and return to diagnosis rather than stacking more delay.
This setting is not a general repair for file timing problems, changing offsets, or multiple sources with different errors. It can also conceal a source-path issue temporarily: for example, a camera feed that arrives late while the soundtrack is on time. If the discrepancy is large, variable, or not isolated, pause adjustments and inspect the underlying route.
Inspect routing and source timing when sync is unstable
Trace the audio and picture paths separately. Ask where the video comes from, where its audio comes from, and whether either passes through an extra device or application before OBS. A file’s picture and sound may be combined in one media source, while a microphone or mixer feed arrives independently. If you have duplicated the file audio through another source, check whether both copies are active; an echo or comb-filtered sound can be mistaken for a timing shift.
Check that the intended audio source is actually routed to the programme output and that there is not a second, delayed copy. Review OBS scene and mixer settings after changing scenes or media sources. For a channel assembled from clips, play several points in the file, including a loop transition. An offset that appears only at one clip boundary may be in the media edit or source transition rather than a persistent encoder delay. A local recording helps separate those cases; the guide to OBS settings for looping Hindi bhajan videos is relevant when the stream repeatedly cycles through prepared material.
If video comes from a network-connected camera or a separate capture path, note that route and test it independently if possible. A different device or connection is a diagnostic comparison, not a guaranteed fix. Check whether the fault follows the camera, the audio input, or the scene. Do not buy hardware based on a single anecdote or assume that a particular capture card resolves sync in general.
YouTube also distinguishes active live streaming from an uploaded video. For a saved upload whose audio and video tracks have different durations, YouTube advises correcting the media in editing software; that is not a control for an active live stream. See its upload troubleshooting guidance if the problem is in a published file rather than the live encoder output.
For an always-on channel, repeated manual restarts can hide a source problem without correcting it. If you use a desktop encoder, keep a short local recording from a representative period and inspect whether the offset is present at startup, after a scene change, or after a loop. If operating a computer overnight is itself a source of interruptions, StreamNeo removes that particular need by running an uploaded video as a YouTube live stream while your own computer is off; it does not make a mistimed source file correct, so validate the file and output first.
Check encoder load, stream health and connection
A mismatch that appears only under load or changes over time deserves a health check. Review OBS status and logs for encoding or rendering warnings, dropped frames, and signs that the computer is struggling. YouTube asks creators to inspect encoder errors and CPU load as part of live troubleshooting, alongside source quality and the local archive. The YouTube live streaming troubleshooting page is the appropriate place to check its current guidance.
Separate local encoder problems from outbound delivery problems. If the OBS recording is already wrong, reducing the stream’s viewer latency will not address the cause; check the encoder configuration and source handling. If a local output appears aligned and stable but viewers report a problem, inspect the Live Control Room’s health messages and the outbound connection. If the issue coincides with a weak or changing connection, resolve that instability and repeat the test before applying a fixed audio delay. A guide to OBS disconnections when switching from hotspot to broadband can help if connection hand-offs are part of the problem.
Review the current stream configuration and Live Control Room messages. YouTube’s live streaming error guidance includes checks for supported video and audio formats, audio sample rate, and the number of audio streams. Follow what the current dashboard and official help page say for your stream; do not assume a setting mentioned in an older checklist remains the requirement. A configuration error may cause broader output trouble and is not necessarily a timing offset.
Only after the encoder output is stable should you decide whether viewer latency needs attention. YouTube explains that latency settings trade response time against buffering, with lower latency useful when interaction matters but potentially more vulnerable to buffering. Choose according to whether you need quick audience replies or can tolerate a longer wait for steadier playback, as set out in its latency guidance. That choice concerns when viewers receive the stream, not whether the picture and sound line up once they do.
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
Does changing YouTube latency fix audio that is out of sync with the picture?
No. Latency changes how long it takes captured events to reach viewers and can affect buffering, but it does not correct relative audio-picture timing. First compare the local file, OBS output, and viewer playback to find where the mismatch begins.
Which way should I adjust OBS Sync Offset if audio comes before the picture?
For a repeatable offset isolated to one source, making that audio arrive later is the usual direction of correction. Change it in a small step, record the output, and verify the effect in your OBS version rather than relying on the monitor or a value from another setup.
What if the sync is fine at the start but drifts later?
A fixed offset only shifts timing; it does not correct a mismatch that grows or changes. Check the source, routing, encoder load, and stream health, then compare another local recording before changing the setting.
Should I adjust OBS if only YouTube viewers report a delay?
Not until you know whether they mean delayed playback or audio-picture mismatch. If the sound and picture align but arrive later, review YouTube latency and connection health; if they do not align, compare encoder output with viewer playback to locate the stage where the problem appears.