Church Livestream Audio Out of Sync or Lagging? The Five Causes and the Fix

The stream looks fine for the first minute, then the pastor’s mouth stops matching the words coming out of the speakers. By the end of the sermon the gap has grown to a full second or more, or the audio cuts out and catches up in little jumps. Viewers notice immediately, and it is one of the fastest ways to lose an online congregation’s patience. The good news: this is a well-understood problem with a short list of usual causes, most of which can be checked from the booth without new equipment.

Cause 1: upload bandwidth versus bitrate

Bitrate is how much data your stream sends out every second, measured in Mbps (megabits per second), and your encoder, the device or software that compresses the camera and microphone feeds into a stream, is told to send a fixed amount. The problem is upload bandwidth: the portion of your internet connection that sends data out, usually much smaller than the download speed most plans advertise. If your upload is close to or below the bitrate you are sending, the encoder has to drop frames or let its output queue build, and the whole stream falls further behind real time.

This shows up as stuttering or frozen video and the stream falling further behind what is happening in the room, a growing lag, not the audio and video inside the stream drifting apart from each other. Video data is larger than audio data, so picture is usually squeezed first when bandwidth runs short.

Cause 2: audio and video on different paths

Inside most church systems, video and audio start out as separate signals: a camera feed and a board feed from the sound system. Embedded audio means the audio is carried inside the same cable as the video, usually HDMI or SDI, so the two stay locked together automatically. Separate audio means the board sends its own feed into the encoder or switcher on its own cable, which is common because it lets the stream mix differ from the room mix. The tradeoff: video commonly takes longer to process than audio, so the two arrive at the encoder a fraction of a second apart, with picture usually arriving later.

Delay compensation is the fix built into most switchers and streaming software: a small, deliberate delay added to whichever signal arrives first, so both land together. If your system takes picture from the camera but sound from the board on its own cable, check whether delay compensation is on and set correctly. A small, consistent offset is invisible once applied. A mismatch that stays the same size all service long, whether 50 milliseconds or half a second, usually means this setting was never tuned or was reset after an update. A gap that grows over the service is a different problem (see the first FAQ below).

Cause 3: the encoder or computer is overloaded

If you stream from a computer, the software encoder shares the processor with everything else running: the browser, presentation software, maybe a second camera feed. When the processor runs short, the encoder skips frames or lags on encoding, and the sync between the two slips. A dedicated hardware encoder, a small box built only to compress and send the stream, avoids this: nothing else competes for its processing power. If the drift starts partway through a service, often right when a second application opens, overload is the likely cause.

Cause 4: Wi-Fi instead of a wired connection

Wi-Fi shares radio spectrum with every other device in the building, including phones in the congregation’s pockets, and its latency (the delay before data actually moves) varies from one moment to the next. A wired connection, an ethernet cable running from the encoder to the router or switch, has steady, predictable latency because it is not competing for airtime with anything else. That variability causes stutters, frozen frames, and a stream that falls behind live, rather than audio and video drifting apart from each other, and it is often worse when more phones are active in the room.

Cause 5: buffering on the platform’s side

Some sync complaints are not sync problems at all, they are buffering. YouTube, Facebook, and most platforms deliberately hold a few seconds of your stream before showing it to viewers, smoothing out small network hiccups so the picture does not freeze constantly. If a viewer’s own connection is slow, their player may rebuffer and fall further behind, which can look like a mismatch but is really the whole stream catching up at once. This is worth ruling out because the fix sits on the viewer’s end, not the church’s; checking the stream from a second, wired connection tells you whether the problem is in your system.

What to do first

Work through these in order before assuming you need new equipment:

• Check upload speed, not download. Run a speed test on the actual connection the encoder uses, at the same time of day as the service, and compare the upload number to your streaming bitrate. Aim for roughly double the bitrate in upload headroom.
• Confirm the audio path. Trace whether sound reaches the stream through the camera (embedded) or straight from the board (separate), and check the delay compensation setting for that path in your switcher or software.
• Move the stream to a wired connection. If the encoding device is on Wi-Fi, that is worth testing before anything else, since it is the easiest cause to rule out.
• Watch the encoder during the service, not just before it. Most software shows a dropped-frame counter and a separate encoding-lag indicator: dropped frames point to the connection (causes one and four), encoding lag points to the computer running out of headroom (cause three).
• Match the sample rate across every device. If the gap keeps growing over the service, check that every camera, audio interface, and the streaming software agree on one sample rate, usually 48 kHz.

Frequently asked questions

The gap between picture and sound gets worse the longer the service runs. What does that point to?

That is lip-sync drift, and it most often means the audio and video are running on different clocks: a camera and a separate audio interface disagreeing about the sample rate, how many times a second audio is measured. The checklist above covers how to check and match it. The other common cause is cause three, the encoder losing processing headroom over the service. A stream that instead falls further behind real time, picture and sound still together but landing late, points to cause one, upload bandwidth falling short, not to drift.

We stream fine most weeks, but it falls apart on busy Sundays. Why?

Busy Sundays mean more phones on the building’s Wi-Fi and, if the church shares one connection between office, guest Wi-Fi, and streaming, more competition for the same upload bandwidth. A connection that comfortably carries your bitrate on a quiet Tuesday rehearsal can fall short on a full Sunday. Putting the encoder on a wired connection, with its own dedicated bandwidth where possible, removes that variable.

Is a hardware encoder worth buying instead of streaming from a laptop?

For a church that streams weekly, a dedicated hardware encoder is usually a sound investment, in the $2,500 to $6,000 livestream budget range alongside cameras and a switcher. It removes cause three entirely, since nothing else competes with it for processing power, and most units keep audio and video locked together automatically if the inputs are wired correctly. A laptop encoder can still work well for a lower-traffic stream if the machine is dedicated to streaming and nothing else runs during the service.

Can we fix sync after the fact in the recording, even if the live stream was off?

Usually, yes, if you are also recording locally rather than relying only on the platform’s copy. Most video editing software can nudge an audio track to realign it with picture for a one-time offset, but a drift that grows over the course of the service (rather than starting off by a fixed amount) is much harder to correct after the fact, because the gap is not constant. That is the practical reason to find and fix the live cause rather than planning to patch it in editing.

If you have worked through this list and the stream still will not stay in sync, that is exactly the kind of problem a short call can sort out faster than more trial and error. For the room and platform side of a worship system, our worship AV mistakes guide covers the planning issues behind problems like this one, and our companion piece on how to livestream a church service walks through the equipment list end to end. If your stream is already built and just needs troubleshooting, visit our page for churches or request a free first conversation and describe what you are seeing. We can usually narrow it down over a call and a few photos.