Mic Test
Last Updated:
This free mic test shows your microphone level live in dBFS, checks for clipping and plays back a 5 second recording. It runs in your browser and no audio is uploaded.
Quick answer: A mic test shows whether your browser can hear your microphone. Press start, allow access and speak: this microphone test shows your level live in dBFS and gives a verdict of no sound, very quiet, too loud or good level. You can also record 5 seconds and play it back. Everything runs on your device.
Using: —
Start the test and speak. Your verdict and levels appear here.
Verdict
—
| Setting | Applied | What it means |
|---|---|---|
| Sample rate | — | How many times per second the microphone signal is measured. |
| Channels | — | 1 is mono, 2 is stereo. |
| Echo cancellation | — | Removes your speaker sound from what the microphone picks up. |
| Noise suppression | — | Reduces steady background noise. |
| Automatic gain | — | Raises or lowers the input level for you. |
Your audio never leaves your device. No audio is uploaded or stored, and a recording lives in memory only until you record again, stop the microphone or leave the page.
📐 Formula
Level in dBFS = 20 × log10(signal size), where full scale is 1.0 and the page shows nothing lower than -100. The average level is RMS: the square root of the mean of the squared samples. Peak is the largest single sample. A sample counts as clipped at 0.999 of full scale or higher (our planning default).
How to Use the Mic Test
Press start and allow the microphone
Press Start microphone test. Your browser asks for permission, and you need to allow it for the test to run.
Check the device and the processing setting
Choose your microphone from the list if there is more than one. Untick the browser's audio processing box to test the signal with noise suppression, echo cancellation and automatic gain turned off.
Speak and read the level
Say the counting line or the pangram in the panel below at your normal volume. Watch the meter, the peak and the verdict.
Record 5 seconds and play it back
Press Record 5 seconds, keep talking, then press play on the recording to hear yourself. Press Stop microphone when you are done.
How does this mic test work?
Press the start button and your browser asks permission to use the microphone. Once you allow it, the page listens through the browser's Web Audio tools and measures the incoming sound on every screen refresh. It updates the numbers five times a second so you can read them. You get a level meter, the loudest peak, the quietest moment and a count of clipped samples. Setting up a headset for gaming? Check your reflexes on our reaction time test too.
The page makes no network request with your audio, stores none of it and plays none of it through your speakers while it listens. The only thing it can play is a 5 second recording you choose to make.
What do the dBFS numbers mean?
dBFS means decibels relative to full scale. 0 dBFS is the loudest value a digital signal can hold, so every reading is zero or negative: -12 dBFS is quieter than -3 dBFS. A drop of about 6 dB halves the size of the signal, which makes -20 dBFS one tenth of full scale. The scale here stops at -100 dBFS. That is what you see for silence, or for anything too quiet to register.
Peak and average are different measurements. Peak is the single highest sample in the stretch measured. The average level here is RMS, which tracks the sound over a short stretch, so for speech expect the peak to read higher than the average.
Why browser audio processing changes the meter
Noise suppression, echo cancellation and automatic gain all alter the signal before this page measures it. With them on, the meter shows what the browser hands to a web page, not the raw microphone signal. Untick the box to ask for all three to be off, and read the settings table to see what the browser says it applied.
Clipping happens when the signal reaches 0 dBFS. Anything louder than full scale is cut flat, which sounds distorted, and a clipped recording cannot be repaired afterward. This page counts a sample as clipped at 0.999 of full scale or higher.
| Verdict | Rule | What to try |
|---|---|---|
| No sound | Peak below -60 dBFS after 3 seconds | Check mute, the selected device and the input volume |
| Very quiet | Peak below -30 dBFS | Move closer or raise the input volume |
| Too loud | Any clipped sample, or a peak above -1 dBFS | Lower the input volume or sit further back |
| Good | None of the above | No change needed |
The average level only counts moments louder than -50 dBFS, which is also our planning default. These limits are rough guides for a first check. They are not a certified audio measurement.
Microphone test volume 0 or a flat bar: causes and fixes
If the number sits at -100 dBFS or the bar never moves, the browser is receiving silence or nothing at all. Work down this list and press Start again after each change.
- Check the browser's permission. Use the site permissions icon beside the address bar and make sure the microphone is allowed for this page.
- Check your computer's or phone's microphone privacy setting. A system can block the microphone for a browser even when the browser allows it.
- Choose the right device in the Microphone list. A laptop may offer a built-in microphone, a headset, a webcam and a virtual device, and the wrong one gives silence.
- Look for a mute: a switch on a headset or cable, a mute key on a laptop, or a mute setting in your system's sound input settings.
- Check the input volume in your system's sound input settings. At zero, the browser gets silence.
- Close other apps that may be using the microphone. On some systems an app holding the microphone can block the browser from it.
- Unplug and replug a wired headset, or reconnect a wireless one, then reload the page.
- Run the test once with the processing box unticked to see whether processing changes the result.
If none of that moves the bar, the cause is probably outside the browser: the microphone, its cable or its driver. Try a different microphone, or the same one on another device, to tell which.
Mic test with playback: how to hear yourself
The meter shows how loud you are, not how you sound. Press Record 5 seconds while the test is running, speak, and the recording appears in a player under the button. Press play to hear it. The recording is held in memory and the page adds no download button.
This page does not play your voice back live. A live loop from microphone to speakers can squeal, so hearing yourself here always means record first, then play.
What to say during a mic test
Read these aloud from where you normally sit, at your normal volume, then once more a little louder.
- Count: one, two, three, four, five, six, seven, eight, nine, ten.
- Pangram: The quick brown fox jumps over the lazy dog.
- Digits: zero, one, two, three, four, five, six, seven, eight, nine.
- Hard P and B sounds: Peter Piper picked a peck of pickled peppers. If the clipped count jumps here, you are close to the microphone or the volume is high.
Mic test on Windows 10, Windows 11, Mac, iPhone and Android
The test runs in the browser, so it works the same way on every system. Where you fix a problem differs. On Windows 10, Windows 11, a Mac or a MacBook, look in the system's sound input settings and its microphone privacy setting. On an iPhone, an Android phone or a Samsung phone, check the phone's microphone permission for your browser and the browser's own site permission. We do not give exact menu paths because they change between versions.
Recording needs browser support. On a phone the meter can work while recording does not. If so, the page says so and the meter keeps running.
Testing a laptop, headset, AirPods or Xbox microphone
Allow access first, then pick the microphone you want from the list. A laptop's built-in microphone, a USB headset and a wireless headset such as AirPods each show up as their own entry when your system lists them. If one is missing, check that it is connected and set as an input in your system's sound settings, then press Start again.
An Xbox console has its own audio settings, and this page tests the microphone of the device you open it on. Use the console's own settings to check a headset there. Testing the same headset on a computer shows that its microphone works, not what the console receives.
Mic test for Teams, Zoom and Discord
An online test shows what your browser hears. Teams, Zoom and Discord each have their own input selection, so an app can be set to a different microphone from the one you chose here. If the meter moves on this page but people cannot hear you in an app, open that app's audio settings and check which input it uses and that it is not muted. Keyboard noise reaches a microphone too, so type a few lines (the typing speed test gives you something to type) and watch the meter.
Is this microphone test private?
Yes, and here is exactly what the page does. Audio is processed in your browser, no audio is sent to us or anyone else, and the page stores none. A recording lives in memory until you record again, stop the microphone or leave the page. Like every page on this site, it sends a standard page view to Google Analytics, which carries no audio (see the privacy policy). Your browser's developer tools list every network request, so you can check this yourself.
Need another browser check? Try the reaction time test, the click speed test or the typing speed test, or see all of them on the online tests hub.
Frequently Asked Questions
Not on this page. We never route the microphone to your speakers, so there is no loop to squeal, and that holds for headphone users too. Record 5 seconds and play it back instead. The delay is a few seconds, not milliseconds, which is the trade for a test that cannot feed back.
Probably not. -20 dBFS is one tenth of full scale, which sits inside our Good level range (our planning default). The meter measures what goes in, and playback loudness is set by your speaker or headphone volume. Turn the output volume up before you judge the recording. If it is still faint at full volume, raise the input volume and record again.
The app and the browser can use different inputs. Check the Microphone list on this page against the input the other app uses, and check the browser's permission for this site. A second possibility is exclusive use: if another app has locked the microphone, the browser may get silence or an error. Close that app and press Start again.
The rule counts a single clipped sample, or one peak above -1 dBFS. A tap on the desk, a breath into the mic or a hard P sound can do that once. Say the counting line at a steady volume from where you normally sit. If the verdict still says too loud, lower the input volume.
Automatic gain can raise quiet speech and lower loud speech, so your level may drop or spread out once it is off. Noise suppression can lower the quiet floor, so that number may rise. Echo cancellation matters most with speakers on. Run one test with the box ticked and one unticked, and compare the settings table each time.
It works wherever the phone's browser allows microphone access. Recording and playback depend on the browser as well. If yours cannot record, the page tells you and keeps the level meter running. The meter alone is enough to show whether the microphone hears you.
Passing here only proves the browser hears the microphone. Zoom, Teams and Discord each keep their own input setting, so a headset you tested here can still be unselected there. Compare the name next to Using on this page with the device the app names, and clear the app's own mute before you call.
If your system lists it as an input, it appears by name once you allow access. A headset that is not connected yet will not appear, so connect it first and press Start. If a device is plugged in while the test runs, the list updates by itself. A wrong entry is the usual cause of a flat bar, so check the name next to Using.
The page offers no save button, and the recording stays in memory until you record again, stop the microphone or leave the page. Some browsers add a download option to their audio player menu, and if yours does, the file goes to your own device only. To keep a recording on purpose, use your computer's or phone's voice recorder.
On this page, a peak between -30 and -1 dBFS with no clipping gets a good verdict. Those limits are our planning default, not an industry standard. A call app may want something different, and a very quiet room with a high input volume can read well here and still sound hissy. Use the verdict as a first check, and your own recording as the second.
Sources & Methodology
This page uses your browser's own audio interfaces. The MediaStream API opens the microphone after you allow it, a Web Audio analyser node reads the waveform, and the MediaRecorder API makes the 5 second recording. Levels are our arithmetic from that waveform: RMS is the square root of the mean of the squared samples, and dBFS is 20 × log10 of the value against full scale of 1.0, with a floor of -100. The verdict limits (peak below -60 dBFS after 3 seconds, peak below -30, any clipped sample or peak above -1, and -50 dBFS for sound present) are our planning defaults, not an industry standard. No audio is sent anywhere, and the settings table shows what the browser reports for the microphone track.