If a pre-recorded Restream stream is out of sync on YouTube, first find where the mismatch begins: in the original file, in the version Restream plays, or only in YouTube’s live output. Correct the earliest point where it appears; do not assume that a documented encoder audio-offset control is also available for Restream’s prerecorded Upload & Stream events.
Use the same recognisable moment to compare each version, such as a spoken word, a clap, or a drum hit. If the file is already wrong, repair and upload it again; if it is right until delivery, test the event and destination before changing the source.
Compare the source, Restream and YouTube
A useful diagnosis is a sequence, not a guess about which platform is at fault. Compare the original file on your computer with the file as uploaded or previewed in Restream, then compare that with the YouTube live output. You are looking for the first version in which sound and picture stop matching.
Choose a short, easy-to-recognise event. A singer’s mouth opening on a clear syllable works better than a long instrumental passage. For a bhajan with a visible singer, check a line with a hard consonant; for an ambience loop, use a bell strike or another sharp sound. Note whether sound leads the image or follows it, and whether the difference stays constant or grows as playback continues.
| Comparison | What it can tell you | Next step |
|---|---|---|
| Original file versus local playback | Whether the media file itself appears wrong | Check another player, then inspect or repair the file in an editor |
| Original versus Restream version or preview | Whether the problem appears during preparation or preview | Confirm the uploaded file and event selection; ask Restream if the comparison is available but unclear |
| Restream version versus YouTube live output | Whether the mismatch is introduced along delivery or destination playback | Run a controlled private or unlisted test and record the result |
| YouTube live preview versus saved replay, if both are available | Whether the issue differs between live viewing and the archived result | Preserve both links and timestamps for support |
This method separates a bad source from an event or delivery issue, but it does not prove which internal component caused a change. Keep the original file unchanged while testing. If you edit it before establishing the baseline, you lose a useful comparison point.
Restream’s Upload & Stream file requirements list MP4, MOV, M4V or MKV containers, H.264 video, AAC audio and a keyframe value of 2 as mandatory requirements. Those are compatibility checks, not evidence that any deviation caused a particular sync problem. Its article also recommends Full HD 1080p, 30 or 60 fps, constant bitrate and suitable lead-in and tail material. Check the current help page before preparing a replacement, as specifications can change.
If your regular channel uses a local encoder rather than Upload & Stream, keep the workflows separate. A guide to running a 24/7 channel with FFmpeg may help you understand a different file-to-live path, but settings for that arrangement do not establish that Restream has the same controls for an uploaded event.
If the original file is out of sync
If sound and picture do not match when you play the original locally, fix the file before scheduling another event. Restream cannot make a misaligned source correct merely by delivering it to YouTube. A local file may appear wrong because of its encoding, an edit, or the player used to check it, so verify the result in a second player before making changes.
When editing, work from a copy. Find the point where the mismatch begins and check whether it stays the same for the whole programme. A fixed offset may be corrected by moving an audio track relative to the video in an editor. If the difference changes over time, a simple shift may only align one passage; the media may need to be conformed or re-exported. Avoid guessing a correction based on one moment near the beginning.
After export, play the replacement from the start and check a point near the end as well. This matters for a long devotional set or an ambience video: a file that starts in sync but drifts later is not fixed by aligning its opening. Confirm that the replacement still meets Restream’s supported upload requirements, then upload it as a new test rather than overwriting your only copy.
Do not treat format conversion as a guaranteed synchronisation fix. Converting a file can make it compatible with an upload workflow, but it will not necessarily repair timing that is already wrong. If you need to build a loop from several clips, the checks in this guide to preserving video quality when looping files in OBS are relevant to that separate preparation task; they do not replace checking the finished file’s sound and picture together.
If sync is lost after upload or delivery
If the original is in sync but the YouTube output is not, preserve the source and narrow down the point of change. Confirm that the scheduled Restream event references the intended upload, that you are watching the correct YouTube event, and that no alternate audio track or playback version is being compared by mistake. If Restream provides an upload preview or recording for the workflow you are using, compare it with the source. Do not assume every account or event exposes the same comparison view.
Restream documents an audio-sync procedure for encoder workflows. Its encoder sync troubleshooting guide advises checking selected audio and video devices and making a local recording. Where that recording is out of sync, it describes adjusting audio sync offset in the encoder’s mixer or advanced audio settings, with positive and negative trial values such as 200 and -200. Those values are examples for tuning an encoder control, not a fix to apply blindly, and not confirmation of a control in a prerecorded Upload & Stream event.
That distinction matters if you are searching for “audio delay on a Restream prerecorded stream”. Do not spend time looking for an encoder mixer setting inside an event workflow unless Restream’s current documentation or support confirms it is available there. The reviewed guidance does not establish an equivalent prerecorded-event offset procedure. For the exact event, establish a clean test and ask support what adjustment options apply to that workflow.
If an external encoder is in fact involved, check its selected devices and make a local recording before changing anything. If the recording is also out of sync, the encoder’s audio offset may be the relevant control. If local recording is in sync while the outgoing stream is not, Restream’s encoder guidance points to network or CPU conditions for investigation. This advice applies to that encoder path; it is not a diagnosis of an Upload & Stream event.
You can also check the audio format and channel layout for the actual stream path. YouTube’s encoder settings recommendations list AAC or MP3 audio and specify sample rates by channel layout, including 44.1 kHz stereo and 48 kHz for 5.1. Restream’s encoder troubleshooting advice recommends AAC at 44.1 kHz in its own context. These recommendations differ in scope; match the configuration you are actually sending rather than treating one sample rate as a universal sync remedy.
Run a private or unlisted test
Before changing a scheduled public event, test with the same source and the same route to YouTube. Restream describes testing by recording without going live or by sending an unlisted stream. Check that the chosen method represents the workflow you need to diagnose: a local recording can tell you about a source or encoder, while a YouTube test checks the destination output.
YouTube recommends testing with audio and movement similar to the real stream, then watching stream health. Its live encoder setup guidance is aimed at encoder streams, so do not assume every instruction maps exactly to a prerecorded event. For a scheduled video, the practical principle is to test the actual event path and use a representative section rather than a still image or silent opening.
Make the comparison repeatable. Write down the event name, source filename, start time and the timestamp of the chosen sound-picture cue. Watch the YouTube output rather than judging only from an editor preview. If a saved replay is available, compare it separately with the live viewing result; one can appear different from the other, and the comparison may not be available in every account.
Use one change per test. If you replace the file, alter an encoder setting, and change the event setup at the same time, a better or worse result will not tell you which change mattered. Repeat the same cue after each change and note whether the offset is fixed, variable, or absent. A short test is often sufficient to establish whether a clear cue is aligned, but include a later point if you suspect drift.
If your channel normally runs from a desktop setup, separate computer load from this test rather than changing software at random. The article on lightweight streaming software for older PCs discusses encoder-side constraints. Those constraints matter when your PC is encoding; they are not proof that a prerecorded cloud delivery event has a PC performance problem.
Read YouTube stream-health messages carefully
If YouTube exposes stream-health messages for the test, save them with the event details. The YouTube Live Streaming API health documentation describes issues such as audio codec or sample-rate problems, multiple audio streams, keyframe frequency, video codec and insufficient video ingestion. A warning can point towards a configuration or delivery issue worth checking; it does not, by itself, prove why a particular word or beat is out of sync.
Read the warning as evidence about the stream, not as a verdict on the source file. For example, an audio codec warning gives you reason to confirm the audio encoding; it does not tell you that shifting audio by a fixed amount will correct the mismatch. Likewise, a keyframe or ingestion warning may warrant a closer look at the stream path, but cannot identify a lip-sync offset without comparing the actual output.
Also distinguish delivery latency from audio/video sync. YouTube’s latency settings explanation discusses delay from capture to viewer and notes trade-offs around buffering. A viewer receiving the whole stream later than expected is not the same as audio arriving out of step with its picture. Low-latency choices can affect the delivery experience, but a lip-sync mismatch should not be diagnosed from a latency setting alone.
Record what you can observe: the exact warning text, whether it appeared during the test, the time it appeared, and whether the same moment is misaligned in the saved replay. Avoid changing several output settings just because a warning exists. Check the relevant official YouTube and Restream instructions for the workflow in use, then test a single adjustment.
When to contact Restream support
Contact Restream if the source is demonstrably in sync, the mismatch appears only after the Restream-to-YouTube path, and a controlled test reproduces it. Be explicit that the event is a prerecorded Upload & Stream workflow rather than an encoder stream. That helps avoid receiving an otherwise reasonable encoder procedure that does not answer whether the event workflow has an audio-offset control.
Send a concise evidence pack: the source filename and format, the event time and time zone, the YouTube test link or replay if available, a timestamp showing the mismatch, and a brief note on whether the mismatch stays constant or grows. Include the comparison result for the original and any Restream preview or recording you could access. Add the YouTube stream-health message text if there was one. Do not post a private stream key or other account credentials in a public support forum.
Ask a bounded question: can support confirm whether the uploaded event output differs from the source, and what troubleshooting controls are supported for this specific workflow? If you need to repeat the test, note any changes made and preserve the original upload. A clear record is more useful than a long description that does not identify where the first difference appeared.
If the source itself is defective, an editor or transcoding tool may be relevant because the repair belongs at the file stage. If the source is clean and the problem arises only in the event output, buying a cable, microphone or capture device is not an evidence-based next step. The issue is timing in a file delivery path, not necessarily a shortage of recording hardware.
For an always-on channel, a failed overnight test can cost more than a few minutes of troubleshooting. A hosted workflow that removes the need to leave your own computer running can address that specific operational burden; StreamNeo turns an uploaded file into a YouTube live stream, but it does not diagnose a Restream sync fault or make a defective source file correct. Keep the platform choice separate from the sync evidence you have collected.
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 is my YouTube stream audio out of sync when the original video is fine?
The mismatch may be introduced somewhere after the source file, including event setup or delivery, but the comparison alone does not identify the cause. Compare the same cue in the source, any Restream version you can inspect, and YouTube’s output; then run a private or unlisted test and retain any health messages.
Can I use Restream’s audio-offset advice for Upload & Stream?
Restream documents its audio-offset procedure for encoder mixer or advanced audio settings. The reviewed documentation does not confirm an equivalent control for prerecorded Upload & Stream events, so do not assume the encoder procedure is available there. Ask Restream support about controls for your exact workflow.
Could YouTube latency cause a lip-sync problem?
Latency describes how long the stream takes to reach a viewer; it is not by itself a measure of the relative timing of sound and picture. Check the same visual and audio cue in the output rather than treating a latency setting as proof of a sync fault.
What should I send Restream support?
Provide the source format, event time and time zone, a test or replay link if available, and a timestamp where the mismatch is clear. State whether the original file is in sync, whether the offset is constant or grows, and include any relevant YouTube health message.