If audio is out of sync in a prerecorded video streamed through StreamYard to YouTube, first check the original file, then compare the StreamYard output with YouTube playback. That sequence helps you find where the mismatch becomes noticeable without assuming that the file, StreamYard or YouTube is at fault.
Check whether the audio starts late or early by a steady amount, or gradually drifts further out of sync. Then compare the audio and video track durations, try the file in a local player, and make a short test after any re-encoding before scheduling the full stream.
Find where the mismatch begins
Think of the video in three stages: the original file on your device, the prerecorded output produced through StreamYard, and the version you hear while watching on YouTube. Compare those stages in order. The first stage at which the sound and picture disagree narrows down where to investigate; it does not, on its own, prove what caused the problem.
Start with an event that is easy to recognise, such as a person clapping, a drum hit or a word with a clear consonant. Check whether the sound leads the visible action or follows it. Repeat the check near the start and later in the file. If the difference is similar at both points, note it as a roughly consistent offset. If it grows, note that it appears to drift. These are useful observations, not diagnoses.
Write down what you actually tested: the filename or version, the player and device, where you watched each stage, and whether the mismatch was present in the original file. For the YouTube version, record whether you watched a live broadcast or its replay, and which browser or app you used. That makes a later comparison more useful than relying on memory after a long stream.
This is also a reason to keep source files and exports distinct. If you are assembling a continuous playlist, a change made to one clip can alter the rendered file without changing the originals. The guide to an FFmpeg concat playlist for a continuous YouTube stream explains that kind of file workflow; here, the important point is to test the exact exported file you plan to upload.
Check whether the source file is out of sync
Open the exact file you supplied to StreamYard in a local media player. Do not use a proxy, an earlier export or a copy with a similar name. A simple test is to watch an event with an obvious sound and matching movement, then check another event later in the same file. If the mismatch is already there locally, focus first on the source or export rather than on the later streaming and playback stages.
If the original plays in sync locally, that is helpful evidence, but it does not settle the question. Continue by checking the StreamYard output and the YouTube playback separately. The output might not be available in the same form as a local file, so compare the same moment in the prerecorded broadcast and its YouTube version, rather than comparing unrelated points in a looping programme.
Keep the comparison controlled. Use the same segment and, where possible, the same device and player. A browser, app or device can present playback differently; if one YouTube view sounds wrong, check the same point in another player or on another device before treating that single view as conclusive. Conversely, hearing the same symptom in multiple environments is useful evidence to include when you ask for help.
For channels that run recorded material repeatedly, a repeatable file check matters more than a one-off glance at the live page. The workflow in running prerecorded videos on a YouTube live stream is relevant to the broader publishing process, but it cannot identify the cause of a particular sync issue. Preserve the file you tested and note its version so that the next upload can be compared fairly.
Compare audio and video track durations
Check the media file’s audio and video tracks in an editor or media information tool. YouTube’s troubleshooting guidance says to make sure the track durations match, and to use video-editing software to edit the tracks before uploading if they do not. Read the current YouTube Help instructions for audio and video sync before making a change, as official guidance can be revised.
A duration mismatch is a concrete file property to investigate, not proof that it explains every audible offset. A file can report matching track lengths and still appear out of sync in a particular playback environment. Likewise, seeing different durations should prompt you to examine the file and edit it; it does not establish which step created the difference.
When checking track details, record the video duration, audio duration, video codec, frame rate and audio codec if your tool shows them. Look at the beginning and end as well as the reported totals: a track that ends early is different from a track that starts late. If you are not comfortable editing tracks, keep these details and make a copy before changing anything. Never overwrite the sole source file as a first troubleshooting step.
If the file was exported from a project, return to the project only after confirming the tested file’s details. Inspect whether the audio and picture begin together and whether the full programme was rendered, rather than inferring a project problem from YouTube playback alone. Export a new version with a distinct name, then run the local check again before uploading it.
Play the file locally and note the pattern
Local playback is a useful isolation step because it lets you check the file without relying on a live broadcast or a YouTube player. Use a player you know can handle the file, and make sure the sound is not being routed through a separate device with its own processing. If the file is in sync in one player but not another, keep both results in your notes; do not assume that either one represents every viewer’s experience.
Check at least one clear audio-and-picture event near the start and another later on. Record whether the offset seems steady or increases. A steady-seeming difference and a growing difference can suggest different lines of investigation, but neither pattern identifies the cause by itself. The useful outcome is a repeatable description that you can compare after a new export or upload.
If you are preparing a long-running channel, do this check before committing a full programme to the schedule. A channel built around church services, for example, has a different content workflow from a music loop, but the same file-first test applies. The article on continuous streams for multilingual church sermons is useful for thinking about that broader workflow; it is not a substitute for checking the media file itself.
Re-encode a copy using StreamYard’s guidance
If you find a file issue, or the source needs a fresh export for a controlled test, re-encode a copy rather than repeatedly uploading the same file. StreamYard’s guide to optimising a video for prerecorded streaming recommends MP4, H.264 (x264) video, a constant frame rate of 30 fps, AAC audio, “Align A/V Start” and “Web Optimized” or faststart. It also says total bitrate should be below 10,000 kbps. Treat these as StreamYard’s recommendations for its prerecorded workflow, not a guaranteed cure for every sync fault.
StreamYard describes HandBrake as a tool for the conversion. Follow the current instructions in its help article and check the available settings in the version you use; software menus can change. Preserve your original, choose an output filename that makes the re-encoded copy easy to identify, and avoid changing several unrelated settings at once. If the next test differs, you will then know which file you tested, even if the cause remains uncertain.
The frame-rate recommendation is specific to this StreamYard prerecorded guide. YouTube’s upload guidance lists preferred frame rates including 24, 25, 30, 48, 50 and 60 fps. Those two facts serve different purposes: do not read YouTube’s list as a reason to disregard the StreamYard guide’s constant-30-fps recommendation for this workflow. If you need a different export for another purpose, check the current platform instructions rather than guessing.
Keep the audio setting in context. StreamYard’s general audio-quality guidance says its audio is optimised for 48,000 Hz (48 kHz), but that is a general audio note, not a finding that your prerecorded file’s sync issue comes from its sample rate. The dedicated prerecorded-video encoding guide is the more direct reference for this file-based test. If you change audio settings, use the editor’s documented options and check the resulting file locally.
A re-encode can change how a file is packaged and prepared for upload. It cannot establish that a particular mismatch was caused by the original encoding, nor does it promise that every later playback will be correct. The point is to make a controlled new copy using the vendor’s stated settings and compare it with the version you already tested.
Upload and test a short segment
After the local copy plays as expected, upload that new file and test a short segment before scheduling the whole programme. StreamYard’s prerecorded streaming troubleshooting guidance recommends re-encoding with HandBrake and uploading again for prerecorded-stream lagging or upload problems. Use the current help page for its steps, and treat the short-segment check as a practical way to limit the cost of another full run.
Choose a test portion with a clear sync event and, if possible, enough duration to check whether the offset changes over time. Compare the locally tested file with the StreamYard result at the same point. Then check the YouTube version when available. Keep a note of which version was used at each stage; an old upload can otherwise be mistaken for the new test.
If the short test looks right, you have evidence that this version behaves differently under the tested conditions. It still is not a guarantee that a long broadcast or every device will behave identically. If it remains out of sync, do not make a succession of unrecorded edits. Go back to the stage comparison and track details, then repeat one change at a time.
General StreamYard audio checks can help when the symptom involves the browser or selected device rather than only one prerecorded file. StreamYard suggests trying Chrome or Firefox, disabling extensions that may affect audio, and checking the selected device and its settings. These are secondary checks for a file-based sync problem: start with the source, durations and dedicated encoding advice before treating a browser setting as the explanation.
Compare StreamYard output with YouTube playback
When the local file appears in sync, compare the StreamYard output and YouTube playback at the same timestamp or recognisable event. If both later stages show the same mismatch, record that. If the StreamYard view appears in sync but a YouTube view does not, repeat the YouTube check in another player or device. This comparison helps isolate where the symptom is observed; it does not prove YouTube is responsible.
Distinguish what you observed from what you infer. “The original file is in sync in my local player, the StreamYard output appears in sync, and the YouTube replay sounds late in one browser” is more useful than “YouTube broke the audio”. Include whether the issue is consistent or grows, and whether another device reproduces it. If the replay has not finished processing, check again when it is available rather than comparing a live view and a replay as though they were the same playback path.
If you need to escalate, gather the original file’s codec, frame rate and audio details; the track durations; whether the local file is already out of sync; and approximate observations near the beginning and end. Include the device, browser or app used for YouTube playback and whether another player shows the same result. These are useful diagnostic details, not a published official checklist for this exact case. Ask StreamYard or YouTube support with a concise reproduction and the evidence you have, without claiming a cause that your comparisons have not established.
For a continuous channel, keep the troubleshooting test separate from decisions about the wider broadcast workflow. A cloud-run service such as StreamNeo can remove the specific burden of leaving your own computer running for the ongoing broadcast, but it does not diagnose or repair an out-of-sync source file. Confirm the media behaves as intended before relying on it in any always-on schedule.
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 prerecorded video audio out of sync on YouTube after streaming it with StreamYard?
The cause cannot be identified without checking the file and the playback stages. Start with the original file, compare audio and video track durations, then check the StreamYard output and YouTube playback at the same point.
Does the original video file have the same audio and video duration?
Check the audio and video track durations in a media tool or editor. YouTube advises that they should match; if they do not, edit the tracks in video-editing software before uploading. Matching durations alone do not prove that playback will be in sync.
What settings should I use to re-encode a prerecorded video for StreamYard?
StreamYard’s prerecorded guide recommends MP4, H.264 (x264), constant 30 fps, AAC audio, Align A/V Start and Web Optimized or faststart, with total bitrate below 10,000 kbps. Use the current StreamYard guide and test the re-encoded file locally and in a short upload before scheduling the full programme.
What should I send support if the issue persists?
Share the file’s track durations and available codec, frame-rate and audio details, plus whether the original is in sync locally. Describe what you observed at the start and later in the programme, and identify the YouTube device or player you tested, including whether another one behaved differently.