If audio and video are out of sync in a continuous YouTube stream, first check which one reaches the viewer early, then adjust the relevant OBS source. Use Audio Sync Offset when the audio source needs to move later; delay the video when the picture is early. There is no universal millisecond value that fits every playback chain.
OBS can also record several separate audio tracks while sending one chosen mix to YouTube Live. Those are different outputs: viewers do not get OBS’s separate recording-track layout. Build the stream mix deliberately, then test both timing and the mix in actual YouTube playback.
How OBS tracks differ from the stream mix
OBS audio tracks are routing choices, not a promise that a live audience can select separate versions of your audio. In OBS, a source can be assigned to one or more tracks. Recording can preserve those assignments as separate tracks, which is useful when you want to edit music, voice, or other sources independently later. The live output, by contrast, uses a selected streaming track: it is the mix delivered to YouTube.
For example, a devotional channel might record a bhajan programme with the song audio on one track and a spoken introduction on another, while also assigning both to a third, complete mix track. You could then send that complete mix as the stream track and retain the separate material in a local recording. YouTube viewers hear the chosen live mix, not a set of track choices they can switch between.
This distinction matters when correcting sync. A source may be assigned to several OBS tracks, but its timing adjustment affects the source in the OBS mix path; it does not create a different offset for each recording track. If you need a clean edit later, record the useful separate tracks and also verify that the full mix is present on the track selected for streaming.
Keep the routing simple enough to inspect. A guide to OBS media source settings for a 24/7 stream can help when the continuous video itself is a playlist or loop. The sync question is narrower: which sound source is late or early against the picture that viewers actually see?
Assign sources in Advanced Audio Properties
Open OBS’s Audio Mixer and use the gear menu to open Advanced Audio Properties. The track checkboxes show which output tracks receive each source. Treat each row as a routing decision: for example, a music source can feed the live mix and a recording track, while a microphone can feed both the live mix and its own isolated recording track.
Before changing offsets, identify the sources that actually carry sound. A media source might contain its own audio; a desktop-audio capture may also pick up the same playback. If both are active, you may hear doubling or an echo and mistakenly treat it as a sync delay. Mute or disable duplicate paths during diagnosis so you are measuring one intended signal rather than two copies.
Use the Sync Offset control on the audio source that needs adjustment. OBS describes the control as a source audio sync offset in its source reference documentation. Do not copy an offset from a different scene or another creator’s setup: source routing, capture devices, and playback chains differ. Make a small measured change, then listen and watch the same cue again.
If several sources share the same problem, find out whether they share a source or a timing path before changing each one. Applying offsets separately to multiple copies can make later edits confusing. Keep notes about which source you changed and why; for an always-on channel, this makes it easier to undo a test setting after a scene or source is replaced.
A visible event paired with a distinct sound is more useful than general impressions. A clap, a drum hit with a visible strike, or a spoken word with a clear mouth movement can help establish whether sound or image arrives first. Check a few examples from the actual programme, not only the scene used to set up OBS.
Enable recording tracks in Output settings
To retain separate tracks in a local recording, check the recording section in OBS Output settings. With Output Mode set to Advanced, the Recording tab lets you choose which audio tracks are written to the recording file. Select the tracks you intend to keep, then confirm the matching source assignments in Advanced Audio Properties. A track selected for recording will not contain a source that was never routed to it.
A practical arrangement might reserve one recording track for the full programme mix and other tracks for selected isolated sources. The full-mix track gives you a ready-to-review version; the isolated tracks can help with later editing. The exact layout depends on your editing workflow and file format support, so make a short local recording and inspect it in the software you plan to use before relying on it overnight.
Do not confuse a track number in recording settings with the stream output. The number is just an OBS routing label. If you assign the complete mix to a recording track but choose a different, incomplete track for streaming, your local file may sound right while the public broadcast lacks a source. The reverse can happen too: the live mix is complete, but your recording does not preserve the separate material you expected.
For a repeatable workflow, keep a simple routing note with the scene name, track purpose, and sources assigned. This is especially useful when a channel alternates between playlists, announcements, and live segments. Test the resulting recording as well as the public stream after changing the layout.
Choose one streaming track with the full mix
In OBS Output settings, inspect the Streaming audio track selection and choose the track that contains the complete intended programme. That track needs every audible source viewers should receive: music or video audio, voice-over, and any other deliberate programme sound. This is not the same as enabling several recording tracks. A stream sends a selected mix rather than exposing your separate local recording layout.
Use a table to check the intent before going live:
| Output or destination | What to configure | What to verify |
|---|---|---|
| Local recording, full mix | Route the complete programme to a recording track | Playback contains all intended sound |
| Local recording, isolated sources | Route selected sources to separate recording tracks | Editing software can open and distinguish them |
| YouTube Live | Select one streaming track carrying the complete mix | A viewer hears all intended sources together |
A common mistake is assigning the music to one track and the voice to another, then choosing only the music track for streaming. The local recording may preserve both, but the audience will not hear the voice if it is absent from the selected stream mix. Another mistake is monitoring the mixer and assuming that everything audible there is necessarily routed to the stream track.
After selecting the stream track, inspect each source checkbox and make a short private or otherwise controlled test where appropriate. Listen from YouTube playback, not only from OBS monitoring. If the channel runs a long video loop, use the same media and scene path planned for the continuous broadcast. Advice on keeping a recorded-video stream stable may help with a different failure mode, but dropped frames and source-level audio sync are not the same diagnosis.
Check YouTube's single-audio-stream requirement
YouTube Live's ingest is not a way to deliver OBS's independent recording tracks as selectable audience tracks. Configure OBS to send the complete programme mix on its chosen streaming track, and treat any additional tracks as local recording material unless YouTube's current documentation for your specific workflow says otherwise. Do not promise viewers a choice among the isolated tracks simply because OBS can record them separately.
YouTube’s live streaming latency guidance also describes a separate concern: latency is the time between capture and what viewers see. Reducing latency can make interaction feel quicker, but a smaller player buffer is more exposed to encoder or playback disruptions. A stream can have well-synchronised sound and picture yet arrive late overall; changing an OBS source offset will not make the audience receive the whole broadcast sooner.
If the whole stream is delayed, review the latency mode and the path to YouTube rather than shifting audio against video. For example, YouTube documents that HLS has higher latency than RTMP because it sends video in segments, and that ultra-low latency is not available with HLS in its HLS setup guidance. That is protocol context, not a diagnosis of a sync offset, and changing protocols is not automatically the right answer for a channel whose priority is stable playback.
A continuous station without live audience interaction may value resilience more than the shortest possible delay. A call-in or live discussion has a stronger reason to consider a lower-latency mode, while accepting the trade-off YouTube describes. Decide based on the programme and viewer experience you need; do not use latency settings as a substitute for checking source sync.
Test representative audio and stream health
Start with the actual YouTube viewer playback. OBS preview and monitoring help you inspect the production, but they do not prove that the public audience receives the same timing, especially if the broadcast has a configured delay. Google’s LiveBroadcasts API reference distinguishes monitor stream settings and broadcast delay. If those are relevant to your setup, compare what the monitor shows with what a viewer sees rather than treating one as proof of the other.
Pick representative moments from the programme: speech, music with a clear beat, transitions between clips, and any announcement or overlay that triggers sound. A playlist can behave differently across files, so test more than the opening seconds of one video. Use the same audio path, scene, and source settings that will run continuously. Note whether sound leads or trails the visual cue, and whether the mismatch is consistent or changes between clips.
If you need a measurement aid, the community project obs-audio-video-sync-dock describes a way to measure audio/video latency and interpret which side is early. It is optional software, not an official OBS guarantee; check its current availability and compatibility before relying on it. A careful repeated visual cue can still be enough to establish direction and make a measured adjustment.
After changing Sync Offset or a video delay, recheck the public playback. Make one purposeful change at a time, so you can tell whether it improved the relationship. If the picture is early and sound arrives later, an audio offset is not the obvious correction; OBS’s Render Delay filter is described as delaying the source image to bring a webcam into sync with microphone audio in the OBS filter documentation. The control should follow the signal that leads, not a habit of always delaying audio.
If audio and video stay aligned but the stream itself buffers, disconnects, or falls behind, investigate network and encoder health separately. A stream can have a good average bitrate and still encounter congestion, and YouTube’s latency guidance notes that congestion can affect delivery. For connection-specific troubleshooting, see what to check when YouTube Live disconnects on ACT Fibernet. That issue is about delivery stability, not a reason to add an arbitrary audio delay.
For a 24/7 channel, leave the test running long enough to include ordinary programme changes and inspect it again after any source replacement or OBS update. Keep a record of the test cue, the observed lead, and the offset or delay applied. If the mismatch returns only in one file, investigate that media item and its audio path before changing the timing of every source in the scene.
Know the limits of 24-hour archiving
A continuous broadcast is not automatically a promise of a complete replay archive. YouTube’s live stream, DVR behaviour, and saved archive are separate concerns from OBS’s local recording tracks. Do not assume that a multi-track local recording arrangement will appear in the YouTube replay, or that a replay will preserve every minute of a long-running stream. Check YouTube’s current guidance and the settings for the specific broadcast, then make a local recording if you need material for editing or retention.
OBS can produce a local recording while it streams, but that requires the computer and recording process to keep operating. A long recording also needs suitable storage and a format and workflow you have tested. If the machine stops, the local file may not cover the missing time. Decide whether a local copy is essential, and check a sample file from your actual settings before depending on it for the whole programme.
If the specific pain is keeping a file-based programme running when your own computer should be off, StreamNeo turns an uploaded video into a YouTube live stream, with automatic monitoring and restarts if it drops. It does not change YouTube’s audience track behaviour or guarantee an archive, so keep the distinction between broadcast, recording, and replay clear.
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 YouTube show viewers each OBS recording track?
No. OBS’s separate track assignments are useful for local recording; YouTube viewers receive the chosen live mix, not a selectable layout of OBS recording tracks. Route the complete intended programme to the streaming track and confirm it in viewer playback.
Should I delay audio or video in OBS?
First establish which signal is early using a repeatable cue in the YouTube playback. Adjust the audio source’s Sync Offset when audio needs to move later; if the video is early, use an appropriate video delay instead. There is no universal starting offset.
Why is my stream late if the audio and picture match?
That suggests whole-stream delivery latency rather than a source-level sync problem. Review YouTube latency settings, network conditions, and the ingest protocol; do not shift one source and make the audio and picture disagree.
Can I count on YouTube to archive all 24 hours?
Do not assume a complete archive for every continuous broadcast. Check current YouTube guidance and the broadcast’s replay behaviour, and make a tested local recording if preserving the programme matters.