Check that your microphone works and that your input level lands where it should. Pick the right device, press Start preview, and watch the level bar move while you speak. The audio is analysed in your browser and never leaves it.
Confirm the app will hear you and that the headset you grabbed is the input the browser uses, not the laptop array.
When nobody can hear you, walking the permission, device, mute and gain list finds the cause in a couple of minutes.
Keep peaks near -12 dBFS so a sudden laugh does not clip, and set a gain you can leave untouched.
A working microphone never produces exact digital zeros, because electronics and room tone always contribute something. Pure silence means the signal is blocked before it reaches the browser: a mute switch, zero input volume, a revoked privacy permission, or an input with nothing attached.
Yes. Every audio input the operating system exposes to the browser is listed: built-in arrays, webcam mics, USB microphones, headsets and virtual devices. Selecting one here does not change your system default, and the list refreshes automatically when you plug in or remove hardware.
Open the tool, press Start preview and allow microphone access in the browser prompt. Device names appear after permission is granted, so pick the input you want to check from the dropdown and speak in your normal voice. The level bar responds in real time and shows the reading in dB.
No. The stream is analysed frame by frame inside the page and discarded immediately. Nothing is recorded, uploaded or stored, and the microphone is released as soon as you press Stop. No account is needed to run the test.
For speech, peaks between -12 and -6 dBFS are the healthy range, with an average around -30 to -20 dBFS. Below -30 dBFS you sound distant, and anything that reaches 0 dBFS is clipping. Raise or lower your input gain until normal speech peaks near -12 dBFS.
The browser only lists audio inputs after you grant permission, so a blocked or dismissed prompt leaves the list empty or generic. Check the padlock icon in the address bar, set the microphone to Allow, then reload the page. A device that is physically unplugged will not appear either.
0 dBFS is digital full scale, the loudest value the audio system can represent, so every reading sits below it. Hitting the top of the bar means the loudest parts of your voice are being flattened, which sounds harsh and cannot be repaired afterwards. Lower the input gain and retest.
A flat meter is almost never a broken microphone. The usual causes are a blocked browser permission, the wrong input device selected in the dropdown, a system-level mute or privacy toggle, a hardware mute switch, or another application holding the device. Check those five in that order.
The percentage and the dB value point at the same thing, so the only decision left is your input gain.
The audio is analysed in the tab and discarded, so no voice sample leaves your machine or lands on a server.
Thirty seconds at the meter beats discovering a muted microphone while everyone waits for you to speak.
Audio is analysed locally and discarded frame by frame, with no recording, upload or account required.
Every audio input exposed to the browser is listed, so you can test the headset instead of the laptop array.
The meter works from the root mean square of 1024 samples, which tracks perceived loudness better than a raw peak.
Test every audio input device in your browser: enumerate microphones, verify each one against a live dB meter, and find out which input really carries sound.
Run a microphone test on Windows 11: where input settings and app permissions hide, why the level stays at zero, and how to see the live signal.
Run a mic test in your browser: pick the right input device, watch the live dB level meter, and fix a flat signal before your next call starts.