check-mic

Home / Microphone test / My Microphone

Microphone test

My Microphone

A live microphone test that runs entirely in your browser. Level meter, oscilloscope, spectrum, recorder and playback — no download, no account, nothing uploaded.

The short answer

Not sure what your microphone is or whether it works? The Report panel above names the active device, its sample rate and channel count, and whether the signal it produced was healthy.

My Microphone: step by step

  1. Pick the right input

    Open the device list at the top of the console. Every microphone the system can see is listed by name. Choose the one you actually intend to use — the default is often a webcam or a virtual cable.

  2. Press Start test and allow access

    The browser shows a permission prompt. Choose Allow. Nothing is recorded until you press Record, and even then the audio stays on your machine.

  3. Speak at your normal distance

    Say a full sentence at conversational volume, sitting where you normally sit. The meter should swing between -24 dB and -6 dB. A flat meter means no signal is arriving.

  4. Check the waveform for damage

    Open the Waveform panel. A healthy voice looks like rounded peaks with space above and below. Flat tops touching the edges mean the signal is clipping and words will sound crunchy.

  5. Record and play it back

    Levels can look perfect while the audio sounds terrible. Record five seconds, play it back, and listen for hiss, hum, echo and keyboard noise.

  6. Read the report

    The Report panel names the device, its sample rate and channel count, whether echo cancellation and auto gain are active, and gives a plain verdict you can copy into a support ticket.

If the meter does not move

  • Something else has the microphoneZoom, Teams, Discord, OBS and Camera apps can hold an input exclusively. Quit them completely, including from the system tray, and try again.
  • A hardware mute is engagedMany headsets mute when the boom is rotated up, and most USB mics have a mute button that stays lit. Check the physical control before touching any software.
  • The browser was never allowedClick the padlock or slider icon at the left of the address bar, set Microphone to Allow, then reload the page. A blocked prompt never appears twice on its own.
  • The wrong device is selectedChange the input in the dropdown and the test restarts automatically. Laptops frequently default to a webcam mic rather than a plugged-in headset.

What a good result actually looks like

Three numbers describe a healthy microphone. Peaks between -12 dB and -6 dB, meaning you are loud enough without touching the ceiling. A noise floor below -50 dB, meaning the room is quiet when you are. Zero clipped frames, meaning nothing has been squared off and destroyed.

Miss any one of them and the fix is different. Low peaks mean move closer or raise the input volume. A high noise floor means the room, not the microphone, is your problem. Clipped frames mean you are too loud and no amount of processing will restore what was lost.

Privacy: every measurement on this page happens inside your browser. No audio is uploaded, and recordings exist only in the tab until you download them or close it.

Questions people ask

Why does the browser ask for permission every time?

Some browsers only remember the choice for the session, and private or incognito windows always forget it. Allowing the site in your browser's site settings makes the choice permanent.

The test works but people still cannot hear me

Then the microphone is fine and the app is not. Open that app's audio settings and select the same device you chose here.

Does this work on a phone?

Yes. Chrome on Android and Safari on iOS both support the test, though iOS restricts which of the phone's microphones a browser can reach.

Is my audio uploaded anywhere?

No. The test uses the Web Audio API inside your browser. Nothing is sent to a server, and recordings live in memory until you close the tab or download them yourself.

Tested and updated · Written and maintained by check-mic.com · Report a problem with this page