Microphone Echo Test: Free Microphone Test & Online Mic Test
Overview
Microphone Echo Test. The Microphone Echo Test routes your microphone to your headphones through an adjustable delay, so you hear your room's echo the way call participants actually experience it. Put your headphones on first to avoid feedback, then use the delay control to compare how different amounts of echo sound on a call. Try the free android mic test for a quick, no-install way to check this yourself.
Other people on the call keep hearing their own voice bounce back, and you are not sure whether the problem is your setup or theirs. A microphone echo test settles it in under a minute: the echo detector listens through your headset or desk mic in real-time and reports echo loops, feedback risk, signal clarity and the noise floor, so you know your audio is clean before meetings, podcasts or streaming.
How to Run a Microphone Echo Test in Your Browser
This is a browser microphone test, so there is nothing to install. It works with a built-in laptop mic, a USB microphone, a Bluetooth headset or the mic inside your webcam. To test your mic: The bluetooth headset microphone input test takes under a minute and needs nothing but your browser.
- Click the start button and allow the browser to use your microphone.
- Speak at your normal call level for 10 to 15 seconds.
- Read the echo, feedback and clarity readings in the visualizer panel.
- Switch devices from the selector and repeat to compare microphones.
- Record a short clip if you want to hear exactly how you sound.
Unlike a basic online mic test that only shows a moving line, this one also checks whether your voice is coming back into the input.
Allow Microphone Access and Speak Normally
Your browser asks for microphone access the first time. Click Allow; if you blocked it earlier, reset it from the padlock icon in the address bar. Then talk the way you would on a real call. If the input level barely moves, check that the mic is not muted and that its gain is not turned all the way down.
Hear Yourself with Echo Playback
The live waveform and oscilloscope show your signal as it arrives. Below them, the correlation visualizer compares the signal with a delayed copy of itself using cross-correlation: a flat line means nothing repeats, while sharp spikes mean a sound is entering the mic a second time, which is the signature of an echo loop.
Echo playback lets you hear yourself with an adjustable delay, feedback amount and wet mix, so you can recognise what a 250 ms echo sounds like compared with a short room reflection. Always wear headphones for playback, or the test creates the very feedback it is trying to find.
What the Echo Detector Measures
A free echo test that only replays your voice tells you little. This online echo test reads six things at once, from feedback risk to the reverb tail your room adds after each word. The free condenser mic test runs entirely in your browser via the Web Audio API — nothing is uploaded anywhere.
Microphone Echo vs Room Reverb
Echo is a distinct repeat of your voice. On video calls it usually comes from the far end: your voice plays through someone else's speakers, their mic picks it up, and it returns over the network a few hundred milliseconds later. Room reverb is different: an acoustic reflection off hard surfaces that arrives so quickly it blurs into the original sound and hurts speech intelligibility rather than repeating.
The delay of a single reflection depends on how far the sound travels to the surface and back:
$$t = \frac{2d}{c}$$where \(d\) is the distance to the reflecting surface and \(c\) is the speed of sound, about 343 m/s at room temperature. If your desk mic sits 1.9 m from a bare wall, the reflection arrives \(t = \frac{2 \times 1.9}{343} = 0.0111\) s, or 11.1 ms late. That is far too short to hear as an echo, so a test that flags it is telling you about room sound, not a loop.
| Distance to surface | Reflection delay | What you hear |
|---|---|---|
| 0.6 m | 3.5 ms | Colouration, slightly hollow tone |
| 1.9 m | 11.1 ms | Roomy, less clear speech |
| 4.0 m | 23.3 ms | Noticeable reverb |
| 8.6 m | 50.1 ms | Edge of a separate repeat |
| 17.2 m | 100.3 ms | Clear, distinct echo |
Most home offices are smaller than 5 m, so any distinct repeat you hear on a call is almost always a speaker loop, not your walls.
Feedback Loop and Speaker Bleed
A feedback loop forms when your mic hears your own speakers and the sound circles back, growing each time until it becomes a squeal. Low-level speaker bleed starts the loop long before you can hear it, which is why the feedback detector watches for repeated patterns at low levels rather than waiting for a howl.
Noise Floor, Sample Rate and Noise Suppression Readings
The test also reads your device's settings and the quiet level between words, which helps when background noise is the real complaint. The spectrum analyzer shows which frequency bands carry that noise.
| Reading | What it tells you |
|---|---|
| Echo cancellation | Whether the browser's built-in echo filter is on |
| Noise suppression | Whether steady hum and fan noise are being removed |
| Automatic gain control | Whether the volume is levelled automatically |
| Audio channels | Mono or stereo input |
| Sample rate | Usually 44.1 or 48 kHz |
| Latency | Estimated input delay in milliseconds |
Hearing Range and Frequency Response
A short tone check plays sine tones from low to high pitch. The highest one you can still hear marks both your own hearing limit and the frequency response of your output device. Play the tones out loud with the mic still live and watch the echo readings: if each tone shows up in the input, your output is bleeding back into the mic, and that same path carries other voices back into a call. If a tone sounds doubled to your hearing, the room is adding reflections the test will pick up too.
Tracing a Podcast Guest's Complaint with the Feedback Detector
The decision is simple: before next Thursday's remote interview, I need to know whether the echo my guest heard last week came from my desk or from their end. The short answer turned out to be my desk. With my studio monitors at their usual level, the echo test showed a repeating signal and a high feedback risk; after two changes it read clear.
What I know going in: my cardioid mic sits 0.42 m from the left monitor, I monitor through speakers rather than headphones during prep, and the call app reported a one-way delay of 168 ms to the guest. That last figure matters, because ITU-T G.114 treats 150 ms one-way as the point where delay starts to hurt conversation. Any of my voice that leaks back to the guest returns to them roughly 336 ms late, far beyond the 50 ms where a reflection stops blending in and becomes a separate repeat.
I run the test twice on purpose. First with the browser's echo cancellation off, because the filter can hide raw bleed and make a leaky setup look clean. I play a spoken clip through the monitors and read the correlation spikes: steady, sharp, and lined up with every word. Then I switch the filter on, and the spikes drop. That tells me my own setup leaks, and the filter is only covering it.
The fix I test is distance first, because sound level falls with distance by \(20\log_{10}(d_2/d_1)\) dB:
| Monitor distance | Bleed reduction | Reading |
|---|---|---|
| 0.42 m | 0 dB | Echo loop detected |
| 0.74 m | 4.92 dB | Weaker spikes |
| 1.15 m, behind the mic | 8.75 dB plus rear rejection | Clear |
I check the 8.75 dB figure by hand against the formula before trusting it, and it matches. The edge case worth knowing: a clean result with the filter on proves nothing about a guest whose app has AEC turned off. Test with it off first. My judgement after this run is that placement matters more than volume here, because the cardioid's rear sits toward the monitors only once they move behind it. Next step: rerun the same clip at 1.15 m with the filter off on Wednesday, and switch to headphones for the call regardless.
Fixing Echo After a Mic Test
Once the mic test shows where the echo comes from, work through these fixes in order and rerun the echo test after each one to confirm the audio quality improved.
Switch to Headphones or Earphones
Headphones or earphones separate what you hear from what your mic captures, so the loop has no path. This is the fastest fix whenever your speakers sit only a few centimetres from the mic.
Turn On Acoustic Echo Cancellation
Acoustic echo cancellation (AEC) subtracts whatever is being played back from what the mic hears. Check that it is on in each app:
- Zoom: Settings, Audio, keep the echo filter on and set background noise reduction to High.
- Microsoft Teams: Settings, Devices, Noise suppression.
- Google Meet: Settings, Audio, Noise cancellation.
- Discord: Voice and Video, Echo Cancellation toggle.
Lower Speaker Volume and Use a Directional Microphone
Drop speaker volume to around half so less sound reaches the mic across the room. Most laptop mics are omnidirectional and pick up sound from every side. A directional microphone with a cardioid pattern, pointed away from your speakers, rejects most of what comes from behind it.
Soften the Room
Room acoustics drive reverb. Rugs, curtains, a full bookshelf or a couple of acoustic panels behind your chair absorb the reflections that bare walls and floors send back to the mic.
Disable Input Monitoring and Sound Effects
Recording software with input monitoring switched on sends your mic to your speakers on purpose, which creates a loop everyone else hears. On Windows, also open Sound settings, choose your device, and turn off audio enhancements and sound effects that add reverb. Then run the echo test online again to confirm the problem is gone.
Why a Microphone Test Fails
If the microphone test shows no signal at all, the problem is access or hardware, not echo. Test your microphone again after checking each cause below, and check microphone settings in the app you plan to use.
Permission, Driver and Connection Problems
- Browser permission denied: allow the mic in the browser's site settings and reload.
- Another app holds the mic: close Zoom, Discord or recording software and retry.
- Blocked by the system: enable mic access in Windows or macOS system settings.
- Outdated drivers: update them from Device Manager or the maker's site.
- Loose connection: reseat the USB cable or try another port or jack.
- Hardware fault: if the mic fails on a second computer too, replace it.
Privacy and Browser Support
All analysis runs locally through the Web Audio API, so your voice is processed in memory and never uploaded, which protects your privacy. Any current version of Chrome, Edge, Firefox, Safari or Opera supports it on desktop and mobile.
Frequently Asked Questions
- Is this echo test free, and do I need to sign up?
- It is free, with nothing to install and no account. It runs in any modern browser using the Web Audio API, and you only need to allow microphone access when your browser asks.
- Why do I hear my own voice echoing on video calls?
- Usually because someone else on the call is using speakers without echo cancellation. Your voice plays through their speakers, their mic picks it up, and it comes back to you after a delay. If your own echo test reads Clear on Echo Loop and Low on Feedback Risk, the source is on their end, and they should switch to headphones or turn on echo cancellation.
- Is my voice recorded or uploaded?
- No. The audio is analysed in your browser's memory and discarded. Nothing is sent to a server or stored.
- What does Echo Playback do?
- It sends your mic signal through a delay and plays it back so you can hear what an echo sounds like. Delay sets how long after the original the echo arrives, Feedback makes it repeat, and Wet Mix sets how loud the echo is compared with your direct voice. Wear headphones while it is on, or you will create the feedback you are testing for.
- What is the difference between echo and reverb?
- Echo is a distinct repeat that arrives roughly 100 ms or more after the original sound. Reverb is many short reflections, each under about 50 ms, that blur into the original instead of repeating. Call echo is usually a speaker loop, while reverb comes from hard surfaces in your room.
- How do I stop echo in Zoom, Microsoft Teams, Google Meet or Discord?
- Switch to headphones first, as it removes the speaker-to-mic path entirely. Then check the app's audio settings: keep echo cancellation on in Zoom and Discord, and turn on noise suppression or noise cancellation in Teams and Meet. Run the test again afterwards to confirm the echo loop reads Clear.
- Why does the echo correlation reading spike?
- The reading compares the current mic signal with a delayed copy of itself. It stays low for background noise and jumps when a sound such as a word or clap enters the mic a second time, either reflected off a wall or played back through a speaker. Sustained high readings while you talk point to an active echo loop or strong room reverb.