A Chromecast audio delay usually means the video reaches the screen before the sound chain catches up, or the device in the middle is adding its own processing lag. I would treat it as a lip-sync problem first, because the fix depends on whether the delay is constant, drifting, or limited to one app or one output path. In most home setups, the answer is not a factory reset; it is a short process of isolation, one change at a time.
The fastest path to a stable picture and sound
- Start with a full power cycle of the Chromecast, TV, and soundbar or receiver.
- Constant offset usually points to the TV, soundbar, or receiver; drift that changes mid-video usually points to the app or network.
- Set the TV audio output to Automatic, then turn off dialogue enhancement and volume levelling if they are enabled.
- Use the TV or soundbar's own audio offset control when the delay is fixed and repeatable.
- Do not use speaker-group delay correction for a single-TV lip-sync problem; it only affects group playback.
- For Chrome tab casting, keep the TV, router, and computer close together, ideally in the same room.
Why the sync drifts in the first place
What looks like one issue is usually two. A fixed delay means the audio path is consistently slower than the video path, which is common when a TV, soundbar, or AVR is processing the signal. A drifting delay means the timing changes while you watch, which is more often network buffering, app behaviour, or the browser casting path.
In practice, I also pay attention to the chain after the Chromecast. The more boxes you place between the device and the speakers, the more chances there are for format conversion, surround processing, or lip-sync compensation to kick in. That is why a soundbar connected through ARC or eARC is a frequent trouble spot in UK living rooms.
If I can describe the problem in one sentence, I use this rule: constant offset = processing problem, changing offset = playback path problem. That distinction saves time before I touch any settings, and it leads straight into the quickest fixes.
The quickest fixes I would try first
I start with the fixes that cost the least time and tell me the most. They are simple, but they also separate a temporary glitch from a real sync problem.
- Stop casting and start again. In a browser, close the tab, reopen it, and cast the same content again. In an app, fully exit the app before reopening it. A stale session can preserve the offset.
- Power cycle the Chromecast. Unplug the device from power for about one minute, then plug it back in. Pulling the HDMI cable does not reboot it.
- Restart the TV and any sound system. If a soundbar or receiver is in the chain, restart that as well. A lot of lip-sync problems live in the TV or sound subsystem, not the Chromecast itself.
- Test the same video in another app or on another device. If only one service misbehaves, the app is a stronger suspect than the hardware.
- For Chrome casting, shorten the wireless path. Keep the TV, router, and computer within 15-20 feet, or about 5-6 metres, and ideally in the same room.
If that still leaves me with the same delay, I move from quick repair to diagnosis. The next step is to identify where the lag begins instead of randomly changing settings.
How to tell whether the TV, app, or network is the real source
The fastest way to solve a sync issue is to stop guessing and look at the pattern. I ask three questions: is the delay always the same, does it change during playback, and does it happen in every app or only one?
| What you notice | Most likely source | Best first test |
|---|---|---|
| The delay is the same every time, on every app | TV, soundbar, or receiver processing | Use the TV or soundbar audio offset setting, then check output format and processing modes |
| The delay gets worse or better during playback | Network buffering or app behaviour | Restart the app, test another title, and try a stronger Wi-Fi connection |
| The delay appears only when casting from a Chrome tab | Browser or computer casting path | Reopen the tab, close heavy background apps, and keep the computer near the router |
| The delay appears only when a soundbar or AVR is connected | Audio return path or codec conversion | Bypass the soundbar briefly and test the TV speakers directly |
| The delay appears in a speaker group, but not on a single TV | Group playback timing | Use group delay correction in the Home app, not TV lip-sync settings |
The mistake I see most often is changing the TV's audio offset before proving the app is innocent. That can hide the real cause and make the next test harder to read, which is why I always isolate the source before I tune the output.
The TV and sound settings that usually matter most
Once the problem is clearly in the TV chain, I focus on the settings that actually change timing. That means audio format, post-processing, and any built-in sync offset on the television, soundbar, or receiver.
- Set audio output to Automatic. Manual codec choices are useful only when you know every device in the chain supports them. If the TV, receiver, or soundbar does not support the selected format cleanly, the result can be a visible delay or a broken handshake.
- Disable dialogue enhancement and volume levelling. These features are meant to improve speech clarity, but they can introduce extra processing. That matches the current Google TV guidance, which calls both out as possible sources of sync trouble.
- Try the TV or soundbar audio offset control. If the delay is constant, a lip-sync or audio delay slider is often the cleanest fix. I prefer this over harsher workarounds because it corrects the timing without changing the content itself.
- Check surround sound settings. If the chain is forcing surround processing when you only need stereo, the extra conversion can add delay. On some setups, switching to a simpler mode is enough.
- Make sure the HDMI chain is not the weak link. For current Google TV hardware, an Ultra High Speed HDMI 2.1 cable and an eARC-capable path matter more than people expect. Cheap splitters and old adapters are frequent sources of inconsistency.
When I see a setup with a soundbar, I assume the sound path can be slower than the picture until proven otherwise, which is why this is the section that often decides the outcome.
When speaker-group correction helps and when it does nothing
People often mix up video lip-sync with multi-room audio delay. They are related, but they are not the same problem, and the fix is different.
| Situation | Use group delay correction? | Why |
|---|---|---|
| Single TV playback | No | It does not change the video lip-sync on one screen |
| Speaker group or multi-room audio | Yes | It trims the lag between speakers that are heard together |
| Soundbar or receiver in a TV chain | Usually no | Use the TV or soundbar audio offset instead |
| Chromecast Audio or Cast speakers | Yes | These setups are exactly what group correction is for |
Google's delay-correction guidance also explains why this tool exists at all: typical speaker delays can sit around 0-40 ms, soundbars around 0-80 ms, and receivers around 0-70 ms. That is enough to feel wrong even when the difference looks small on paper. If you are watching video on a TV, I would leave group delay correction alone; if you are using a speaker group for music, it is the right tool, and the device that finishes playing last is usually the one that needs the adjustment.
That split matters, because once the TV path is clean, the next step is making sure the problem does not come back the next time you watch something.
How I would prevent the problem from coming back
The real prevention is consistency. If the chain changes all the time, the sync problem tends to return even after a good fix.
- Keep firmware current on the TV, soundbar, receiver, and Chromecast. Updates often include audio handling changes, codec fixes, and HDMI handshake improvements.
- Use one stable signal path. The fewer adapters, splitters, and extra boxes between the Chromecast and the display, the fewer chances there are for delay to creep in.
- Recheck lip-sync after switching between TV speakers and external audio. A delay setting that works perfectly on the TV speakers may be wrong once a soundbar or AVR takes over.
- Avoid heavy processing modes unless you really need them. Features like dialogue enhancement, virtual surround, and aggressive noise reduction can all add latency.
- Keep the wireless path simple when casting from a browser. A strong, local Wi-Fi connection is far more reliable than pushing a laptop, router, and streaming device to opposite sides of the house.
- Retest after any major change. A new HDMI port, a new sound mode, or a router restart can shift timing just enough to matter.
In practice, the most stable UK setups are the boring ones: Chromecast to TV, TV to soundbar through eARC, one audio mode, and no extra processing layered on top. That is usually more reliable than chasing a clever workaround.
What I would check before replacing the Chromecast
If the delay survives a clean reboot, a different app, another HDMI port, and a simpler audio path, I stop treating it as a one-click problem. At that point I test the chain one piece at a time: Chromecast direct to the TV speakers, then Chromecast with the soundbar, then another TV or monitor if possible.
The pattern tells me what needs attention. A delay that follows one app points to software; a delay that follows one soundbar or receiver points to the audio chain; a delay that appears everywhere points to the TV or the Chromecast path itself. That is also the point where I would consider a factory reset, because it is a last resort, not the first move, and it wipes the settings you may still want to keep.
When the whole chain is tested in order, the fix is usually clearer than it first looks, and the next video you cast should finally stay in step from the first frame to the last.
