How to Diagnose and Reduce WebRTC Audio Latency

Before you start

WebRTC audio latency is the delay between sound reaching your input device and that sound being played on the other side, or between remote audio arriving and your output device playing it. Some delay is normal: the browser, operating system and network all add processing time. The useful check is whether latency is stable and low enough for conversation, not whether it is zero.

For a local diagnosis you do not need a service. You only need a browser that supports WebRTC, one input device such as a microphone, and one output device such as speakers or headphones. A second device or another person is useful when you need to measure end-to-end delay over a network, but local checks can be done alone.

Before changing settings, close other applications that may use the microphone or speakers. Also note which device is selected in your operating system, because an application may have its own separate device selection.

Step-by-step instructions

Work through these steps in order. Keep changes reversible so you can compare the effect instead of changing several settings at once.

• 1. Open the browser page or web app where you want to check audio latency.
• 2. Start the audio session or call and confirm that the browser asks for microphone permission.
• 3. Select the intended input device if the page shows a device menu.
• 4. Select the intended output device if the page exposes one; otherwise check the default output device in the operating system.
• 5. Speak or play a short test sound and listen for how quickly it returns through monitoring or the other side.
• 6. If the delay seems high, disconnect unused audio paths such as a second tab, screen share with audio, or Bluetooth device that is no longer needed.
• 7. Test again after each change rather than making all changes together.

If browser or site settings show an input level, set it so your normal speech sits around the middle of the meter. A very low input level can make the signal harder to process, while clipping from too high a level can add distortion that makes delay harder to judge.

A mismatch between the sample rate used by the device and the rate used by the page can require resampling. In many browsers this is handled automatically, but if the page or device control panel exposes the sample rate, try a common value such as 48 kHz and keep the same setting on related inputs where possible.

Wireless audio can contribute noticeably to latency. Bluetooth headsets and some wireless microphones add processing on top of browser and network delay. A wired analog or USB device is a useful comparison point when you are trying to isolate the cause.

Check the output

A practical local check is to play a short, distinct sound near the microphone and compare when it is heard with when it was made. Without a calibrated setup this is a rough comparison, not a precise measurement. It is enough to show whether the delay is stable or changing and whether a change made the result better or worse.

For a more useful end-to-end check, use a known reference: start a call, speak a clear syllable, and have the other person confirm when it arrives. If the page shows audio statistics, look for round-trip time and audio delay figures, but treat the numbers as indicators rather than exact audio end-to-end delay unless the page clearly defines them.

A good result is conversational audio with no obvious echo and no progressive buildup of silence. The exact acceptable number depends on the application, but if the delay is consistent and low enough that natural turn-taking works, the setting is usually usable.

Common problems and next steps

• High or growing delay on a wireless device: switch to a wired device and repeat the check.
• Background noise making audio harder to hear or judge: reduce nearby noise and move closer to the microphone instead of raising the input level too far.
• Audio goes to the wrong device: check both the browser or app selection and the operating system default.
• Echo or doubled sound: lower speaker volume, move the microphone away from the speakers, or use headphones.
• Delay only appears with a specific page or profile: test the same input and output devices in another browser or a clean profile to separate the page from the device path.

If local changes do not help, the cause may be network routing or the service itself. In that case repeat the test with another network or service where possible, and keep a record of which device, sample rate and browser were used so the comparison remains clear.

Do not rely on a single quick test to declare a device faulty. A stable wired device comparison is more informative than repeated adjustments while background noise and wireless conditions are changing.