Why Does Bluetooth Audio Lag Behind Video?
Short answer
The delay is the time taken to compress, buffer, transmit and decode the audio — typically 100 to 250 milliseconds depending on the codec. Video apps hide it by delaying the picture to match, which is why films look fine and games do not. If it bothers you, switch from a high-quality codec like LDAC to AAC or SBC, or use wired headphones for anything interactive.
On this page
Bluetooth audio is not a wire with the copper removed. Between the moment your device produces a sound and the moment you hear it, the audio is compressed into a different format, split into packets, buffered, transmitted over a shared radio band, buffered again, decoded and converted back to analogue.
Each of those stages takes time, and the total is typically between 100 and 250 milliseconds. That is long enough to see a speaker’s mouth move before the words arrive.
The interesting part is why some things look perfectly fine despite this and others are unusable.
Where the delay comes from
The chain is roughly the same on every device, and the codec stage dominates it.
| Stage | What happens | Typical cost |
|---|---|---|
| Encoding | Audio is compressed to SBC, AAC, aptX or LDAC | 20–150ms |
| Transmit buffer | Packets are queued to survive interference | 20–100ms |
| Radio transmission | The actual hop across the air | Low single-digit ms |
| Receive buffer | The headphones hold packets to smooth out losses | 20–80ms |
| Decoding | Back to a playable audio stream | 10–40ms |
The radio hop itself is nearly instant. Almost all of the delay is encoding and buffering, and the buffers exist for a good reason: Bluetooth runs at about one milliwatt on the crowded 2.4GHz band, where packets are regularly lost. Without a buffer to absorb those losses, you would hear a dropout every time something interfered. The buffer is a deliberate trade of latency for reliability.
This is why “low latency” codecs sound worse in difficult conditions. They shrink the buffer, so there is less margin before a lost packet becomes an audible gap.
The codec is the main variable
Which codec your phone and headphones agree on sets most of the delay. They negotiate at connection time and settle on the best one both support, which is not always the one you would choose.
- SBC is the mandatory baseline every Bluetooth audio device supports. Latency is moderate and variable; quality is adequate.
- AAC is what iPhones use. On Apple hardware it is well optimised. On Android, AAC encoding quality and latency vary considerably between phones, because the encoder is the phone manufacturer’s rather than a standard one.
- aptX sits broadly similar to SBC, with aptX Low Latency a distinct variant designed to come in near 40ms. Both ends must support that variant, and it is not common.
- LDAC targets high bitrate and sound quality, and it is the worst for latency of the mainstream options. Its adaptive mode can also raise latency further when the connection is poor.
- LC3, part of LE Audio, is the genuine structural improvement — better quality at lower bitrate with lower latency. It requires LE Audio support in the phone, the headphones and often a firmware update, so it is still far from universal in 2026.
Manufacturers’ “gaming modes” generally work by forcing a simpler codec and shrinking buffers, which is why they trade audible stability for responsiveness.
Why films are fine and games are not
The difference is not the headphones. It is whether the software can see the delay coming.
A video player knows roughly how long the audio pipeline will take, because the operating system reports the output latency. It simply holds the picture back by that amount, so sound and image arrive together. The whole stream is delayed by a fifth of a second and you never notice, because there is nothing to compare it against.
A game cannot do that. The sound is a response to something you just did — a shot, a jump, a menu selection. Delaying the picture to match would delay your own actions on screen, which is far worse than the audio being late. So the game plays the sound as soon as it can, and you hear it after you see it.
Video calls have the same structural problem for a different reason: the delay is added to a round trip that is already being measured in hundreds of milliseconds, and the conversation starts stepping on itself.
The practical consequences:
- Streaming and downloaded video — synchronised automatically. Nothing to fix.
- Games — noticeable. Low-latency mode helps; a cable solves it.
- Video calls — noticeable, and the latency also feeds the echo cancellation in ways that degrade call quality. This is one of several reasons Bluetooth audio sounds poor on calls.
- Playing an instrument through them — unusable. Monitoring needs single-digit milliseconds and Bluetooth is an order of magnitude away.
- Live TV through a Bluetooth soundbar — frequently out of sync, because the broadcast chain cannot compensate for your particular headphones.
What actually reduces it
In descending order of how much difference it makes.
Force a lower-latency codec on Android. Settings → System → Developer options → Bluetooth Audio Codec, and select AAC or SBC rather than LDAC. If Developer options are not visible, tap Build number in Settings → About phone seven times. Note that this setting resets when the headphones reconnect on some versions, so check it again if the improvement disappears.
Turn on the headphones’ low-latency or gaming mode in the manufacturer’s companion app, where one exists. This usually forces a simpler codec and reduces buffering.
Disable multipoint. Headphones maintaining two connections split their attention and add latency to both. It is also a frequent cause of headphones that keep disconnecting.
Reduce 2.4GHz congestion. A struggling connection triggers retransmissions and larger adaptive buffers, so the delay grows exactly when conditions are worst. Move your Wi-Fi devices to the 5GHz band and keep the phone out of a back pocket, where your own body absorbs the signal.
Use a transmitter with aptX Low Latency for a TV or games console. A dongle on the optical or USB output, paired with headphones that support the same variant, gets close to usable. Both ends must support it; one alone does nothing.
Use a cable. For anything genuinely interactive this is not a fallback, it is the correct answer. Analogue audio has no encoding, no buffering and no packet loss.
What will not help
- Buying a Bluetooth 5.3 adapter. The version number improves range and efficiency and does not change the audio pipeline’s timing.
- “Latency reducer” apps. The delay is in the codec and in the headphones’ firmware. An app on the phone cannot reach either.
- Turning the volume up or changing EQ. Unrelated to timing.
- Resetting the headphones. Worth doing for dropouts, irrelevant for latency, which is a property of the design.
- Expecting a wireless earbud to match a wired one. No current consumer Bluetooth product is latency-free, and marketing copy about “virtually no delay” is describing something well above a cable.
What to expect
With a typical phone and typical earbuds on AAC or SBC, you are living with roughly 150 to 200 milliseconds. Video looks right because the player compensates; games feel slightly detached; video calls feel a beat behind.
Switching from LDAC to AAC on Android, and turning on a gaming mode where the headphones offer one, usually takes a clearly noticeable lag down to something you stop thinking about. It will not reach zero, and no setting gets a standard Bluetooth headset into the range where you could play a rhythm game on it.
If you need true synchronisation — music production, competitive gaming, monitoring anything live — use wired headphones. That is not a failure of your equipment; it is the price Bluetooth pays for being wireless on a band it shares with everything else in the building.