Bluetooth Latency Test for Headphones and Earbuds

How to test Bluetooth headphone latency

1. Run A on a wired path. This Bluetooth latency test needs one reference run first. Unplug or disconnect the Bluetooth headphones and use wired headphones or the device’s own speaker. Press “Step 1”, listen to the two higher count-in beats, then tap on every beat that follows.
2. Run B on Bluetooth. Connect the Bluetooth headphones, keep the same volume and beat speed, press “Step 2” and tap along the same way.
3. Read the difference. The page subtracts A from B. The result is the extra delay your Bluetooth connection adds compared with the wired path on the same device.

Why two runs? Nobody taps exactly on the beat. Most people tap a little early or a little late, and that habit stays about the same from one run to the next. Subtracting the wired run largely cancels that habit, and it also cancels the part of the delay that the device’s audio system adds on both paths. What remains is mostly the Bluetooth part. If you only run Step 2, you still get a figure, but it includes your own tapping habit and the device’s baseline delay, so the page labels it differently.

Taps far from any beat are dropped, and the first two count-in beats are never used. Each run keeps up to ten taps. Expect two runs of the same headphones to differ by some milliseconds; human tapping has a natural spread. Running both steps two or three times and comparing gives you a feel for that spread.

Results are estimates of the whole playback chain. They depend on the codec actually in use, the headphones’ firmware, the radio conditions and the device, not on the codec name alone.

Bluetooth codecs and latency

A codec is the method used to compress audio for the radio link. Both the phone or computer and the headphones must support the same codec, and they settle on one when they connect. The codec is only one part of the delay: buffering in the headphones and the device often matters as much. So treat the notes below as general tendencies, not numbers, and use the Bluetooth latency test above to see what your own pair does.

Because both ends must match, buying headphones with a low-latency codec helps only if your phone or computer supports the same codec. If they do not share it, the connection falls back to a common codec such as SBC or AAC.

Does your phone support low-latency codecs?

The reliable answer is on your phone maker’s specification page, which usually lists the supported Bluetooth codecs; the headphones’ page lists theirs. Compare the two lists. On Android, the developer options screen also shows which codec is in use while the headphones are connected, and some models let you pick one there. iPhone and iPad do not offer a codec menu, so check the manufacturer’s published specifications for both devices instead of guessing. On a Windows computer, the codec depends on the Bluetooth hardware and its driver, so the computer maker’s or adapter’s specifications are the place to look.

Whatever the lists say, measure it: run the test above with and without the headphones. A real measurement on your devices beats any codec name.

Gaming mode, 2.4 GHz dongles and other fixes

Game or low-latency mode. Many headphones have a mode, often switched in their companion app, that shrinks the audio buffer. It usually lowers delay at the cost of more frequent dropouts when the connection is weak. Turn it on, measure again, and see whether the difference is worth it.

2.4 GHz wireless dongles. Some wireless headsets come with a small USB receiver that uses its own radio link instead of standard Bluetooth audio. They are typically aimed at gaming. If you play on a computer or console, a headset with a dongle is worth considering; measure it with this page the same way.

Wired when it matters. For rhythm games, playing an instrument through an app or recording, wired headphones remove the wireless delay completely. Phones without a headphone socket can use a USB-C or Lightning adapter.

Fewer stages. Disconnect other Bluetooth audio devices, keep the phone close, and switch off spatial audio or effects you do not need. Each extra stage may add a little delay.

What to look for in low-latency headphones

• A published latency figure, and a note on how it was measured; figures without a method are hard to compare.
• A codec your phone or computer also supports, or a 2.4 GHz dongle for a computer or console.
• A game or low-latency mode you can switch on and off.
• A wired option, such as a cable socket, for times when delay must be zero.
• A return policy long enough to measure them at home with this test.

How to reduce Bluetooth audio delay

Start with the cheapest fix: the one that removes a step from the chain. Measure again after each change so you know which one helped. Menu names below vary by brand and system version, so look for similar words if yours differ.

Windows

• Turn off sound enhancements and spatial sound for your output device in the sound settings.
• Pick the stereo headphones entry, not the hands-free headset entry, so the headphones are not stuck in call mode.
• Close other apps that are playing or recording sound.

macOS

• Use wired headphones or the built-in speakers when timing matters.
• Check the sound output in System Settings and avoid routing audio through extra virtual devices.

Android

• Turn off sound effects or equaliser features you do not need.
• If your headphones have a companion app, look for a game or low-latency mode; the name varies by brand.
• Developer options show the active Bluetooth codec, and some phones let you choose it there.

iPhone and iPad

• Turn off spatial audio or head tracking for the headphones if you do not need it.
• Use the headphones’ app, if it has one, to check for a low-latency or game setting.
• For games and music apps, wired headphones through an adapter avoid wireless delay entirely.

TV, soundbar and receiver

• Switch the TV to game mode, which usually cuts picture processing and therefore the picture delay.
• Look for an AV sync, audio delay or lip sync setting and use the number you measured here.
• Set the correction in one device only, ideally the last one in the chain, so two corrections do not fight each other.

Your privacy

The tests on this page never touch your microphone. They play beeps and show flashes, and every calculation happens in your browser. Nothing is uploaded and there is nothing to sign up for. We only count anonymous events such as “a test finished with a result between 100 and 200 ms”, never the exact number.

Details are in the privacy policy.