system
Published by SMCS AI Factory · Content reviewed:
Microphone test online — check mic level
Check your mic level in the browser — audio never leaves your device.
Start to open the mic and watch the level meter. Speak or tap the desk.
Level: 0%
Browser-only diagnostics. Grant permissions when the browser asks. Stop mic/camera when finished.
Mic access is local only while the test runs. We do not record or upload audio.
What can fix this
Partners · affiliate links
Other tools
The number on the bar, defined exactly
We ask the browser for microphone access, feed the stream into an analyser, and compute the root mean square of the waveform on every animation frame. That value is scaled into the percentage you see.
It is a relative loudness indicator, not decibels. The scaling factor means the bar reaches 100% well before the signal clips, which makes quiet microphones readable at the cost of an absolute scale nobody could calibrate from a browser anyway.
Confirming a microphone is capturing
Start the test: Press start and allow microphone access when the browser asks.
Speak normally: Use call volume, not a shout, and watch the bar.
Read the movement: Movement means capture is working; a flat bar isolates the fault.
Stop when done: Stopping releases the device and turns off the system recording indicator.
"They can't hear me" is usually not the microphone
Before a call, the useful question is narrow: is this device capturing anything at all? Everything downstream — the meeting app, the output device, the mute button someone forgot — is a separate problem.
If the bar moves when you speak, the hardware and the browser permission are both fine, and the fault is downstream. If it stays flat, you have isolated the problem to capture, which is a much shorter list of causes.
Isolating the fault
- Close other applications first — some systems grant one application exclusive access to the device.
- Check the hardware mute switch on headsets; it works below the operating system and no page can see it.
- If the browser never asks for permission, a previous denial is probably remembered for this site.
- Microphone access requires a secure connection, so a page served over plain HTTP will fail silently.
- Speak at your normal call volume rather than shouting; a bar that pins at 100% tells you nothing useful.
- Test in a second browser before concluding the device is at fault.
Why the reading is not in decibels
A decibel value only means something against a reference level, and a browser has no access to the microphone's gain, its sensitivity, or the operating system's input boost. Presenting a number in dB would be inventing precision.
Root mean square over the waveform is honest by comparison: it rises with signal energy and falls with silence. Use it to answer whether the device is capturing, not to compare two microphones.
What the permission prompt is really asking
The browser asks for audio only — this test never requests the camera, so a page that triggers a camera prompt is not this one. The stream is created when you start and every track is stopped when you stop or leave the page.
A permission granted here applies to this site in this browser. Revoking it later is done in the browser's own site settings, not here.
What this test does not do
There is no playback loop, so you will not hear yourself; that would need speaker output and would produce feedback in most rooms. There is no recording, no waveform history, and no frequency display.
Those are deliberate omissions. The test answers one question well rather than four questions vaguely.
When the microphone really is the weak link
If the bar moves but callers still complain about noise or thinness, capture is working and quality is the issue — that is a hardware conversation about the microphone itself, not a settings one. A flat bar is the opposite: fix capture before spending anything.