Let's check your mic, together.
One tap and your buddy listens — telling you exactly how you sound, and how to fix it if you don't. Audio never leaves your browser.
Tap Start and say hi — your audio never leaves this device.
How the microphone test works
Press Start and your browser asks for permission to use your mic — that's the
getUserMedia prompt. Once you allow it, we feed the live signal into the Web
Audio API and measure it many times a second. The big number is your peak level in dBFS
(decibels relative to full scale), where 0 dB is the loudest a digital signal can be.
The verdict uses honest, fixed thresholds: sustained peaks below −50 dB mean no signal is arriving; below −30 dB you're working but too quiet; peaks slamming −1 dB (or samples pinned to the ceiling) mean clipping. Everything in between reads as working, with the comfy zone around −18 to −6 dB. A short hold keeps the verdict steady, so a pause between words never reads as a dead mic.
And the promise on the tin: audio never leaves your browser. The analysis runs in memory on your device, and the optional 5-second recording is an in-memory clip that disappears when you leave the page.
What the readings mean
- Peak dB — the loudest moment right now. Aim for peaks around −12 dB.
- Noise — your background level, estimated from the quiet gaps between words. Below about −50 dB is a nicely quiet room.
- Clipping — whether the signal is hitting the digital ceiling and distorting. It should say "Nope".
- Mic score — a 0–100 blend of signal-to-noise, headroom (ideal peak near −12 dB) and cleanliness. No clipping plus a quiet background scores highest.
Microphone test FAQ
Does this mic test work in Safari on iOS?
Yes. Safari on iPhone and iPad supports microphone capture, and the Web Audio analysis this test relies on is solid in Safari 14.1 and later. The page must load over HTTPS — if your browser can't run the test, it tells you instead of failing silently.
Is my audio recorded or uploaded anywhere?
No. Your microphone signal is analysed live inside your browser using the Web Audio API. Even the optional 5-second recording is kept in memory on your device and is gone when you leave the page — nothing is ever sent to a server.
Why does my browser ask for permission to use the microphone?
Browsers require your explicit consent before any page can hear you — that's the getUserMedia permission prompt. Choose Allow to start the test; you can revoke access at any time from the lock icon in the address bar.
The test says "Too quiet" — what should I do?
Your mic works, but speech is peaking below −30 dB. Move closer, speak up, or raise the input gain in your system sound settings until peaks land around −12 dB. Our Windows 11 and macOS guides walk through it step by step.
What's the difference between "Browser processing" and "Raw signal"?
With processing on, the browser applies echo cancellation, noise suppression and auto gain — roughly how you'd sound on a call. Flip on Raw signal and those are turned off, so you hear what your hardware actually captures.