Controlled signal
The tool generates the test inside your browser with a bounded app-level gain. Your operating-system and hardware volume remain separate.
Permission is requested only when you start. The live meter shows relative digital level, and an optional short recording stays in memory for immediate playback.
The meter is relative digital level (dBFS), not calibrated sound pressure. The optional recording stays only in this page memory.
The tool generates the test inside your browser with a bounded app-level gain. Your operating-system and hardware volume remain separate.
Output tests do not upload audio. Microphone tools request permission only when started and explicitly state what stays in memory.
The microphone test confirms that the browser can receive an input stream, displays its relative digital level and lets you review a short local recording. It is a signal-path check, not a calibrated measurement of how loud the room is.
Keep the level moderate and change one thing at a time so the result remains useful.
Choose Start microphone and approve the browser permission.
Speak at your normal distance and watch the relative level meter.
Record up to ten seconds and play it back locally.
Stop the microphone when finished; the track and recording are released.
Match what you heard or saw, change one variable, then use the linked check to verify the result.
| Observation | Likely cause | Next step | Retest |
|---|---|---|---|
| 01The meter stays at −∞ dBFS. | Permission may be blocked, the wrong input may be selected, or a hardware mute control may be active. | Review browser site permission and the operating-system input meter before reconnecting the device. | Check the meeting audio path |
| 02Normal speech repeatedly reaches the far right of the meter. | Input gain is too high or the microphone is too close, causing digital clipping before the browser receives the signal. | Reduce hardware or system input gain and increase the speaking distance, then record another sample. | Understand the dBFS meter |
| 03The meter moves, but the local recording is thin or heavily processed. | Browser processing, operating-system effects or a Bluetooth hands-free profile may be changing bandwidth and dynamics. | Compare a wired path, disable optional input enhancements and close other apps using the headset microphone. | Check Bluetooth microphone quality |
| 04Permission is granted but recording cannot start. | The browser may not support a compatible MediaRecorder format even though live Web Audio input is available. | Use the live meter for the functional check or repeat the local recording in a current Chrome, Edge, Firefox or Safari release. | Retest the microphone |
The generated signal stays controlled; the physical device, room and system path can still change what reaches you.
A laptop mic, webcam, USB interface and Bluetooth headset can all be present while only one is routed into the browser.
Moving closer raises direct level; excessive analog or digital gain raises noise and can clip before the meter is calculated.
Automatic gain control, echo cancellation and vendor enhancements may remain active even when a page requests minimal processing.
Opening a headset microphone can switch some devices from high-quality playback to a lower-bandwidth two-way voice mode.
No. The recording is held only in the current page memory and is discarded when replaced or the page closes.
Web browsers require explicit permission before a page can receive microphone samples.
Some browsers hide input labels until permission is granted to protect privacy.