Microphone Test
| Peak level | Reading | Action |
|---|---|---|
| 50-70% | Healthy conversational input | None - record away |
| Pins 95-100% | Clipping, waveform flattening | Lower OS input gain to ~80% peaks |
| Flat near 0% | Silence in the chain | Permission > input device > input volume |
A microphone test used to mean recording yourself and playing it back; the browser can do the diagnosis live instead - the meter here reads your mic's signal level in real time, so you know in two seconds whether the mic hears you at all.
Bottom line: press Start, allow the permission, and talk at your normal distance. A healthy mic pushes the bar past half at conversational volume. Flat at zero means the chain is broken upstream - permission, input device selection, or the OS input volume slider, in that order.
The honest part: the meter measures level, not quality. A mic can show a fat bar and still sound terrible (clipping, room echo, a fan two feet away) - which is why the peak hold matters: if the bar slams full and sticks, you are clipping, and backing off the OS input gain fixes recordings no software can.
How to use
- Press Start test and allow the microphone permission when the browser asks - nothing is recorded or uploaded; the level is measured in your browser and discarded.
- Speak at the distance you normally sit: the bar shows live level, the peak marker holds the loudest moment. Aim for a bar that reaches half to two-thirds on your louder words without slamming the top.
- If the bar stays flat: check the browser permission (padlock icon in the address bar), then the OS input device and its volume slider - Windows Settings > Sound > Input, macOS System Settings > Sound > Input - then retest; the meter follows the device the OS feeds it.
Frequently asked questions
Why does the browser ask for microphone permission?
Because a page that reads your mic could eavesdrop, browsers gate it behind an explicit per-site permission that you can revoke any time from the padlock icon in the address bar. This test only reads level numbers in memory - nothing is recorded, stored, or sent anywhere; the audio stream is closed the moment you press Stop or leave the page.
My meter shows level but people say I sound quiet - which setting is wrong?
Two volume sliders are in play: the OS input gain (what your mic feeds the system) and the app's input level. If the meter here reaches half but call apps hear you faintly, the app's own input slider sits low; if this meter is also weak, raise the OS input volume or move closer - every doubling of distance costs about 6 dB.
Does a stereo microphone matter for calls?
Most call apps downmix to mono anyway, but a stereo USB mic can arrive with only one channel active - and if the app listens to the dead channel you sound gone while the meter here (which reads the mix) looks alive. If this meter moves but one app hears nothing, check that app's input channel setting: set it to channel 1 or mono.
What is clipping and how do I know I am doing it?
Clipping is input so loud it exceeds the converter's ceiling - the waveform flattens at the top and distortion sets in. The peak hold here makes it obvious: a bar that slams 100 percent and pins there on loud words is clipping. Lower the OS input gain until peaks land around 80 percent, and your recordings stop sounding crunchy no matter the software.