If audio and video are out of sync after encoding a video for YouTube Live, first find where the mismatch appears: in the local file, the encoder output or the YouTube player. That comparison tells you whether to correct the file or investigate the live delivery path; there is no single offset setting that fixes every case.
Use the same visible and audible event at each stage, such as a spoken word with clear lip movement or a clap. Check the local archive before changing encoder settings, then compare it with the encoder preview and YouTube playback.
Check the local file before changing anything
Play the exact file you intend to stream, on the device and player you will use for the check. Find a few clear moments where a sound and picture should coincide. A spoken syllable, hand clap, drum strike or door closing can work. Watch and listen more than once; a player can pause, seek or buffer in a way that makes one moment misleading.
If the mismatch is audible in the local file, the live stream did not create that defect. The file itself, its tracks, or the way your player handles it needs attention. YouTube’s advice for upload sync problems notes that unequal audio and video track durations can cause sync issues, and recommends editing the tracks before uploading again. See YouTube’s guidance on audio and video that are out of sync.
Check the beginning, middle and end of the file. If the same event is consistently early or late, you may be dealing with a steady offset. If alignment worsens as playback continues, suspect a difference in track timing or duration rather than assuming a simple fixed delay. These are clues, not a diagnosis by themselves: verify against more than one event.
For a useful record, note the event and what you see: “clap at 02:14; sound follows the hand movement,” for example. Do not adjust audio by a guessed number of milliseconds. The correction depends on the actual file and playback, and a change that improves one point can make another worse if the tracks drift over time.
If you stream a recorded programme rather than a live camera, preserve the checked file as your reference. This is useful for devotional recordings, lesson loops and other scheduled content, where the same source may be played repeatedly. A guide to streaming recorded services continuously from a Mac also discusses the role of the source file in a continuous broadcast.
Choose a sync marker you can see and hear
A sync marker is a shared event that is easy to identify in both image and sound. The goal is not laboratory calibration. It is to compare the same moment in different versions of your programme without relying on memory or on a vague impression that the sound “feels late”.
A clap is useful because the hands meet at a visible instant and the impact is usually distinct. A person saying a short word works if the mouth is visible and the word has a clear starting consonant. A sharp percussion hit or a visible object striking a surface may also be suitable. Music with sustained notes, a voice-over without visible speech, or a scene with no obvious action gives you less to compare.
Use several markers spread across the programme. One event can be obscured by a cut, a quiet sound, or a player’s display delay. If the beginning is aligned but a later marker is not, record that change. If each marker has about the same relationship between sound and picture, record that too. Your notes should describe what you observed, rather than prescribe a fix before you know the source.
Keep the programme and playback conditions as consistent as practical. Use the same segment, avoid switching audio devices midway, and give the player time to settle after seeking. For YouTube playback, remember that the player may be behind the event happening at the encoder. That delay is not itself evidence of audio/video desynchronisation: what matters here is whether the sound corresponds to the image at the player.
Compare the archive with the encoder preview
Once the local file has been checked, inspect the encoder preview or output using the same marker. YouTube’s troubleshooting guidance specifically advises checking the look and sound of the stream directly in the encoder, along with the local archive and stream health. Follow its current live-stream troubleshooting steps.
The comparison narrows the search. If the local file and encoder preview show the same mismatch, the encoder may simply be passing through a defect already present in the file. If the file is aligned but the encoder preview is not, investigate how the encoder is reading, processing or combining the video and audio sources. If both appear aligned, keep the file and encoder settings unchanged while you compare with YouTube playback.
Avoid comparing unrelated moments. If the preview has a small buffer or the stream has just started, find the same clap or spoken word in the output rather than trying to compare what is happening at that instant on the source screen. For a loop, identify a distinctive point in the loop so that you do not mistake one repetition for another.
This is also where you can note whether the issue is limited to a single source or affects everything. If a prerecorded file is out of sync in the encoder preview but a microphone and camera check appears aligned, the file path deserves closer attention. If all sources show a similar mismatch, inspect the encoder’s composition and source timing. Neither observation proves a cause on its own, so confirm it with the next comparison.
Compare encoder output with YouTube playback
If the local file and encoder preview look and sound aligned, check the YouTube player. Use a private or otherwise controlled test when possible, and compare the same identifiable events rather than judging the stream from a different section. A delay before the event appears on YouTube is expected in live delivery; compare the audio with the picture once that event reaches the player.
There are three useful outcomes. The mismatch already present in the local file points towards file correction. A clean local file but mismatched encoder preview points towards the encoder or source path. A clean file and encoder preview but a mismatch in YouTube playback means you should investigate the delivery and playback stages before altering the original file.
Repeat the observation in another player or device if you can do so without changing the test. A playback device, browser or audio output can affect what you perceive. If one player shows a mismatch and another does not, note the difference rather than applying a global offset to the programme. A change to the source could create a defect for viewers whose playback is already aligned.
Keep latency separate from sync. YouTube describes stream latency as the time between capture by the encoder or camera and the event appearing in the stream. A stream can take time to reach a viewer and still have sound and picture that correspond correctly. Read YouTube’s explanation of latency and stream settings when the concern is delay from the event to the player; it is not a substitute for checking whether audio and video match at playback.
Check encoder load, health and settings
When the mismatch appears after the file stage, inspect encoder health during a controlled retest. Note any dashboard errors, reconnects or signs of high CPU load, and check whether the encoder preview remains stable. YouTube’s troubleshooting flow includes updating the encoder and checking its output, errors and CPU load. Do not treat a dashboard warning as proof that it caused a sync issue; line up the warning with the point at which the mismatch begins.
If the encoder output looks and sounds healthy but YouTube playback does not, check the outbound connection as part of the diagnosis. YouTube recommends checking internet strength and contacting your internet service provider if connection problems are present. A weak upload path can disrupt delivery, but sync alone does not establish that the connection is the cause. For a separate connection issue such as repeated disconnections, the Airtel broadband troubleshooting guide may help you investigate upload stability without conflating it with timing.
For a controlled retest, verify that the encoder’s settings match YouTube’s current recommendations for your stream. The official encoder settings page lists AAC or MP3 audio for RTMP/RTMPS, 44.1 kHz for stereo and 48 kHz for 5.1, and recommends a two-second keyframe interval, not exceeding four seconds. It also lists recommended audio bitrates of 128 kbps for stereo or 384 kbps for 5.1. Check the current page and the encoder version you use; these are settings to verify, not a promised correction for a measured offset.
Change one relevant setting at a time, then repeat the same marker test. If you alter audio format, sample rate, keyframe interval and network conditions all at once, you will not know which change mattered. YouTube’s preflight advice is simple: test before starting the live stream. Test with audio and movement similar to the planned programme and monitor stream health, rather than relying on a static screen or silence.
Apply a fix only after locating the source
Choose the remedy according to where the mismatch first appears. A file defect calls for editing and re-exporting the file. A live-source problem calls for checking the encoder’s source timing and settings. A mismatch that only appears at YouTube playback calls for a delivery-path check. The comparisons are more valuable than a universal setting because they prevent you from correcting the wrong stage.
| What you observe | Where to investigate | Next practical step |
|---|---|---|
| Local file and later versions share the same mismatch | File and track alignment | Compare track durations, edit and export a new file, then check that export locally |
| Local file is aligned but encoder preview is not | Encoder or source path | Check how the sources are combined and processed; retest after a focused change |
| File and encoder preview are aligned but YouTube playback is not | Live delivery or playback | Check stream health, encoder errors and outbound connection; compare another player if available |
| Alignment worsens across the programme | Track timing or duration | Compare the tracks across the timeline rather than applying a single fixed offset |
For a file that is consistently out of sync, inspect the audio and video tracks in editing software and compare their start points and durations. Correct the alignment there, export a new version and play that export locally before using it again. YouTube’s recommendation is to edit the tracks and upload again when their lengths differ; do not assume that adjusting the stream can rewrite timing already baked into a file.
For a live source offset, use a control that acts on that source, and confirm its scope in the software documentation. In OBS, the Render Delay filter delays rendering of a source image and can be useful for syncing a webcam with microphone audio; it is not a repair for an already encoded recording. See the OBS Render Delay filter documentation. Do not add a delay simply because a YouTube player is behind the room: that may be latency, not desynchronisation.
If a cloud-run broadcast is useful because your own computer should not have to remain on, StreamNeo removes the need to keep that computer running for a file-based channel, but you should still verify the source file’s sync before sending it to YouTube. For a closer look at the distinction between local equipment and a cloud-run channel, see whether a cloud service can run a 24/7 YouTube channel from India while your PC is off.
A stable connection is still relevant to reliability, not a cure for a fixed offset. YouTube’s streaming tips recommend leaving 20% upload-bandwidth headroom. Treat that as network planning guidance, not a number to apply to audio delay. If the file is clean and the encoder output is healthy, check the connection and stream-health indicators; do not buy audio hardware or replace equipment unless the evidence points to a particular part of your signal chain.
For a long-running loop, keep the verified export and the marker notes together. If you later replace the file, alter the encoder, change audio routing or move to another playback device, repeat the check. A change can move the problem to a different stage, and a previous successful test does not prove that a new combination is aligned.
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
How can I tell whether the file or the live stream is out of sync?
Play the local file first and compare a clear shared event, such as a clap, with the encoder preview and YouTube playback. If the defect is already in the local file, fix and verify that file; if it first appears later, investigate the relevant live stage.
Is it the encoder or the stream?
It depends on where the mismatch first appears. A clean file but faulty encoder preview suggests checking the encoder or source path, while a clean preview but mismatched YouTube playback warrants checking delivery and playback conditions as well as stream health.
Will OBS Render Delay fix an encoded video?
No. OBS documents Render Delay as a filter that delays a source image in a live scene, useful for aligning sources such as a webcam and microphone. It does not change timing already present in an encoded file.
Is stream latency the same as audio being out of sync?
No. Latency is the delay before an event reaches the viewer; sync is whether the sound and image correspond when the event appears. A stream can be delayed and still be synchronised.