Skip to content

Mic test

Check your microphone works and how loud it is.

Sound from the microphone is analyzed in this tab and the page does not upload it.

Level (RMS)

–dBFS

Peak

–

The signal appears here once the test starts.

−1 to +1, full scale

Loudness ladder

Rule of thumb

  1. −6 to 0 Clipping risk
  2. −12 to −6 Loud, close up
  3. −30 to −12 Normal talking
  4. −40 to −30 Quiet voice
  5. −50 to −40 Whisper or far away
  6. below −50 Room tone

Start the test, then talk the way you do on a call.

dBFS is measured against the digital maximum, not real sound pressure, so the bands shift with your microphone gain. They are our own guide for speech, not a standard.

View
Browser processing

Turn these off to hear the raw microphone. Changes restart the test.

Hear yourself

Kept in this tab's memory only and deleted when you leave or record again.

Current Chrome, Edge, Firefox and Safari run it on desktops and phones. The page needs your permission each time you press Start.

How does the mic test work?

Press Start and the page feeds the live microphone signal into the browser's Web Audio analyser, which measures its strength on every screen refresh. For a longer take than the five-second check, use our voice recorder.

The big number is the RMS level, a running average that tracks how loud your voice sounds; the peak tells you whether the loudest syllables hit the ceiling.

Reading the meter in dBFS

dBFS, decibels relative to full scale, measures everything against the largest number digital audio can store, so 0 dBFS is the maximum and every real reading is negative. Each 6 dB down halves the amplitude.

What dBFS readings mean
ReadingShare of full scaleWhat it sounds like
0 dBFS 100% The ceiling. Anything louder is cut off (clipped) and sounds harsh.
−6 dBFS 50% Loud. Fine for peaks, but there is little room left.
−12 dBFS 25% Healthy peak level for a voice close to the mic.
−20 dBFS 10% A comfortable average for speech.
−40 dBFS 1% Quiet. Others will struggle to hear you without turning up.
−60 dBFS 0.1% Near silence: room noise, a fan, a distant voice.

Source: calculated, dBFS = 20 × log10(amplitude ÷ full scale).

dBFS is not the same as the decibels on a sound level meter. A quiet room might read −70 dBFS on one microphone and −50 on another, depending on sensitivity and gain, so use the meter to compare: your voice against the background, or a setting before and after a change. Speech RMS usually sits 10 to 20 dB below its peaks, and every microphone's own noise means silence still reads around −60 to −90 dBFS.

Why is my microphone blocked or silent?

A blocked or silent microphone usually means one of two separate gates is closed: the operating system must let the browser use the microphone, and the browser must let this site use it. If you blocked the prompt once, the browser stops asking until you reset the permission.

Where the microphone settings live
Device or browserAllow accessPick the mic and its level
Windows 11 Settings > Privacy & security > Microphone: turn on Microphone access and Let desktop apps access your microphone Settings > System > Sound > Input, then Input volume
macOS System Settings > Privacy & Security > Microphone: turn on your browser System Settings > Sound > Input, then the input volume slider
iPhone Settings > Privacy & Security > Microphone (for Chrome, Firefox and other apps) In Safari, the page menu in the address bar > Website Settings
Android (Chrome) Chrome > More > Settings > Site settings > Microphone The app permission for Chrome in Android settings
Chrome, Edge More > Settings > Privacy and security > Site settings > Microphone Same page: choose the default microphone from the drop-down
Firefox Settings > Privacy & Security > Permissions > Microphone, Settings… Pick a device in the prompt when the site asks
Safari on Mac Safari > Settings > Websites > Microphone: Ask or Allow macOS Sound settings (above)

Source: Microsoft Support, Apple Support, Google Chrome Help and Mozilla Support, checked November 2026. Menu names vary slightly between versions.

On Windows, browsers count as desktop apps, so with Let desktop apps access your microphone turned off, Chrome, Edge and Firefox hear nothing even though the site permission looks fine.

If the meter sits around −50 dBFS while you talk, the problem is gain: raise the input volume, move closer, or check you picked the headset rather than the laptop's built-in microphone.

What do the microphone error messages mean?

Once the microphone works, run our speaker test to check the other half of a call, or our webcam test for the camera.

Microphone errors and what to try
Message on this pageBrowser errorUsual cause
Microphone access was blocked NotAllowedError You or the system said no, or the prompt was dismissed. Reset the permission (table above).
No microphone found NotFoundError Nothing is plugged in, a headset is switched off, or the system has disabled the device.
Microphone could not start NotReadableError Another app holds it, often a call app, or the driver failed. Close other apps and retry.
Needs a secure connection SecurityError Browsers only allow microphones on HTTPS pages.

Source: MDN Web Docs, MediaDevices.getUserMedia().

Echo, noise and auto gain

Browsers clean up microphone audio by default: echo cancellation removes your own speakers' sound, noise suppression filters steady sound such as fans, and automatic gain evens out loudness, which is why the meter may creep upward when you stop talking.

Switch all three off to hear what the hardware really picks up. A microphone that sounds fine processed but hisses raw is noisy hardware being rescued by software. Not every browser honors every switch.

The 5-second playback check

Record a sentence at the distance you normally sit, then play it back on headphones. Listen for a hollow, roomy sound (move closer), a constant hiss (lower the gain or try another port) and chopped words (noise suppression cutting in too hard).

Common questions

Is my audio recorded or uploaded?

No. The page has no upload code for audio; the playback recording stays in this tab's memory until you record again or leave. The site does count page views.

The test works, but people on calls can't hear me. Why?

The call app may use a different microphone from the one your browser picked; check the audio settings inside it.

Why does my device list say "Microphone" with no name?

Browsers hide device names until a site has permission. Once you allow access, the list fills in with real names.

Sources

Last reviewed November 9, 2026.