← Back to the FAQ

Audio-Visual Latency & Sync

Why is my Bluetooth microphone out of sync with my video feed?

Quick answer: Bluetooth audio is compressed, transmitted wirelessly and decompressed at the other end, and all three stages take real time — typically tens to well over a hundred milliseconds. For recording or streaming, a wired microphone removes the problem rather than compensating for it.

Bluetooth audio has meaningfully higher latency than wired audio by design — the codec used to compress audio for wireless transmission takes real processing time on both ends.

The harder issue is not the size of the delay but its variability. A delay that changes between sessions cannot be fixed with a single offset.

Try It Yourself

Measure how much delay your headset adds

Reports the offset in milliseconds so you can compare your Bluetooth device against a wired one with a real number rather than an impression.

Run the Audio/Video Sync Test

Understand the inherent limitation

Bluetooth audio is compressed, transmitted wirelessly and decompressed at the other end, all of which takes measurable time — typically tens to well over a hundred milliseconds depending on the codec in use.

A wired connection adds effectively none of this, which is why the same headset used over a cable often sits perfectly in sync.

Check which Bluetooth codec your device is using

Newer, lower-latency codecs reduce this delay meaningfully compared with older, more universally compatible ones. Both your headset and your computer must support the same codec for it to be used.

This is usually not directly user-adjustable, but it is worth knowing, because it explains why the same headset behaves differently on two machines.

Get a real figure for your headset with the Audio/Video Sync Test before deciding what to do about it.

Bluetooth audio latency panel showing codec encode as a high contribution and highlighted, above wireless transmission, decode at receiver and a near-zero wired equivalentBluetooth audio — latency by stageCaptureEncodeTransmitDecodePlaybackWhere the delay accumulatesCodec encodeHigh contributionWireless transmissionModerateDecode at receiverModerateWired equivalentNear zero!Most of the delay is codec encode and decode, not the wireless hop itself.
Because the delay comes mostly from compression rather than transmission, moving closer to the receiver does not help.

Check for a gaming or low-latency mode

Some Bluetooth headsets have a specific low-latency mode, often intended for gaming, that trades some audio quality for reduced delay.

Look in the device's companion app or for a physical switch on the headset itself. Where it exists, it often halves the offset.

Apply a manual sync offset if your software allows it

Many recording and streaming tools let you apply a fixed millisecond delay to a specific audio track to compensate for a known, consistent lag.

To check whether the microphone is also adding processing latency, run the Advanced Microphone & Room Acoustics Test.

  1. Measure the actual delay first rather than estimating it.
  2. In OBS, enter the figure under Advanced Audio Properties → Sync Offset.
  3. Re-measure afterwards, since a variable delay will not stay corrected.

Switch to wired for anything precision-sensitive

For recording, streaming, or anything where sync genuinely matters, a wired USB or 3.5mm microphone removes this entire category of variable delay rather than compensating for it afterwards.

This is the recommendation for any work you will publish, because a variable offset cannot be corrected reliably in post-production either.

Do not assume all Bluetooth devices have the same delay

Latency varies significantly between headset models, and even between firmware versions of the same model.

If changing device is an option, check reviews specifically for latency performance rather than audio quality, since the two are largely independent.

If you hear echo alongside the delay, the Echo & Feedback Loop Detector identifies the loop.

Bluetooth latency handling across operating systems and tools

Codec negotiation happens at the OS level, which is why the same headset performs differently on different machines.

Windows

Settings → Bluetooth & devices → the device → Properties

Windows exposes almost no codec information, so measuring the offset directly is more informative than checking settings.

macOS

Bluetooth Explorer, part of Additional Tools for Xcode

macOS gives more visibility than Windows, though the tooling is developer-oriented rather than user-facing.

OBS Studio

Advanced Audio Properties → Sync Offset (ms)

Corrects a consistent delay well, but cannot follow a delay that changes during the session.

Zoom and Teams

Settings → Audio or Devices → device selection

Neither offers correction, so switching to a wired device is the only effective step on a live call.

The table below shows how much codec visibility and sync-offset control each platform actually gives you over Bluetooth latency:

Practical ceiling and manual control available per app
AppPractical ceilingManual control
WindowsLimited codec visibilityLittle user control over codec
macOSCodec visible and partly adjustableSome codec preference control
OBS StudioPer-source millisecond offsetFull manual correction
Zoom and TeamsNo manual offset controlDevice choice only

Troubleshooting checklist: Bluetooth microphone out of sync

Measure, then decide whether to correct or replace.

  1. Measure the offset with your Bluetooth device connected as you normally use it.
  2. Repeat the measurement in a second session to see whether the delay is consistent.
  3. Check the headset's companion app or body for a low-latency or gaming mode.
  4. Move closer to the receiver and reduce nearby wireless interference, then re-measure.
  5. If the delay is consistent, enter it as a sync offset in your recording software.
  6. Re-measure after applying the offset to confirm it landed rather than overshot.
  7. For anything you intend to publish, switch to a wired USB or 3.5mm microphone.
  8. If replacing the headset, compare models on latency specifically, not audio quality.