Skip to the test
Camera TestPre-call check

Mic test

See and hear what your microphone picks up: live level and peaks, clipping, background noise and hum, and what the browser's echo cancellation and noise suppression actually do.

Your browser will ask for the microphone

Only after you press the button. Sound is analysed on this device and is never uploaded.

Access is already allowed: the test starts right away.

Access was blocked earlier. Press start to see how to unblock it.

Result

Press start to get a result. Nothing starts on its own.

What we measured

Live readings
Readings appear here once the test is running.

Short answer

To test a microphone, press Start mic test, allow access and talk: the level bar should move. Normal speech peaks between −18 and −6 dBFS without clipping. Then measure background noise: below −45 dBFS (A-weighted) is usually fine for calls. Record a few seconds and play it back to hear yourself.

What to fix

  1. The bar does not move Check the mute switch on the headset or keyboard, pick the right microphone in the list, and raise the input volume in the system sound settings.
  2. Too quiet Move closer (a hand's width for headsets, 20–30 cm for desk mics) or raise the input level until speech peaks reach about −12 dBFS.
  3. Clipping or distortion Lower the input gain until peaks stay below −6 dBFS. Turn off any “boost” option in the driver.
  4. Hum or buzz Try another USB port, unplug the laptop charger, or move away from power supplies. Hum at 50/60 Hz usually comes from a ground loop.
  5. Others hear echo Use headphones, or keep echo cancellation on in your call app.

Questions

How do I test my microphone?

Press Start mic test, allow access and speak. The level bar shows the signal; record a clip and play it back to hear how you sound.

What is a good microphone level?

Speech peaks between −18 and −6 dBFS with no clipping. Average levels around −30 to −20 dBFS are typical.

What background noise level is good for calls?

Below about −45 dBFS (A-weighted) the room rarely bothers anyone. The reading comes from 8 seconds of quiet, so it reflects your room and your input gain as much as the microphone itself: turning the gain down lowers the noise number and your voice together.

Why does my microphone sound different in Zoom or Discord?

Call apps add their own noise suppression and gain. The comparison here shows how the browser's own processing changes your sound; the webcam and mic test lets you rehearse with both devices at once.

My level looks fine here, so why do people say I am quiet?

The call app may be using a different microphone or turning the gain down. Check the input device in the app's audio settings and switch off its automatic volume adjustment if the level jumps around.

Can this measure decibels of my room?

No. A microphone needs calibration against a reference before it can give sound pressure in dB SPL, so the readings here are digital levels in dBFS, taken from every sample by an audio worklet. They tell you whether your voice sits well in the recording, which is what a call cares about.

I hear a faint buzz, but the test finds no hum. Why?

Hum is detected as peaks at 50 or 60 Hz and their harmonics. Very faint hum can hide under the room's own noise, and a buzz from a fan or a whining charger sits at other frequencies. Record a clip in silence and listen on headphones to find it.

Why does switching off noise suppression change nothing in Safari?

Safari often keeps its voice processing on even when a page asks to turn it off. The comparison shows what the browser reports it applied, and a note appears when a request was ignored, so you know the levels include that processing.

Can the spectrum show my microphone's frequency response?

No. The live spectrum shows what is in the sound right now — your voice, the room, any hum. A frequency-response curve needs a calibrated reference source, which a browser test does not have.

Also check before the call

How this stays on your device

Your voice is measured by an audio worklet inside this tab. A recording lives in the tab's memory and disappears when you close it, unless you press download. The Network box below shows the page fetching nothing while you talk.

NetworkSent from this device: 0 · requests after load: 0
Requests after load

    Want proof? Open the browser's developer tools on the Network tab and run a test: the list holds only this site's own files.