A microphone test should answer a simple question: is the browser receiving sound from the device you think you selected? This page asks for permission with the standard getUserMedia call, then connects the stream to an AnalyserNode in the Web Audio API. It computes a running RMS (root-mean-square) on the time-domain samples and shows that level as dBFS, decibels relative to full scale. If the samples were a full-scale signal of amplitude 1, the meter would read 0 dBFS. A constant amplitude of 0.5 reads about −6.0 dBFS, which is a known answer baked into the tests for the maths — not something you must reproduce with your voice.
Nothing is recorded to disk and nothing is sent to a server. When you press stop, the tracks are ended and the audio context is closed. Other tabs or apps may still use the mic if the operating system allows it; this page only controls its own stream. Use a headset if you want to avoid the loudspeaker feeding back into the mic, and watch your privacy if you are in a shared room before you click start.
Browsers differ in how they handle default devices, echo cancellation and automatic gain. Those constraints sit in the browser and the OS, not in this script. A quiet meter is not proof that a headset is broken; the wrong input may be selected, or a hardware mute key may be on. Conversely, a moving meter is not a studio calibration and will not tell you that a podcast will pass a loudness spec. If you need alignment, use an audio interface and documentation from that interface’s maker.
The MDN documentation for MediaDevices.getUserMedia and AnalyserNode describes the APIs this page calls. Permission prompts, secure-context rules (HTTPS) and the exact shape of a rejected promise are defined by the browser, not by this site. If getUserMedia is missing entirely, the page says so and does not pretend to listen.
Sources
- <
- a
- h
- r
- e
- f
- =
- "
- h
- t
- t
- p
- s
- :
- /
- /
- d
- e
- v
- e
- l
- o
- p
- e
- r
- .
- m
- o
- z
- i
- l
- l
- a
- .
- o
- r
- g
- /
- e
- n
- -
- U
- S
- /
- d
- o
- c
- s
- /
- W
- e
- b
- /
- A
- P
- I
- /
- M
- e
- d
- i
- a
- D
- e
- v
- i
- c
- e
- s
- /
- g
- e
- t
- U
- s
- e
- r
- M
- e
- d
- i
- a
- "
- >
- M
- D
- N
- :
- M
- e
- d
- i
- a
- D
- e
- v
- i
- c
- e
- s
- .
- g
- e
- t
- U
- s
- e
- r
- M
- e
- d
- i
- a
- <
- /
- a
- >
- ;
- <
- a
- h
- r
- e
- f
- =
- "
- h
- t
- t
- p
- s
- :
- /
- /
- d
- e
- v
- e
- l
- o
- p
- e
- r
- .
- m
- o
- z
- i
- l
- l
- a
- .
- o
- r
- g
- /
- e
- n
- -
- U
- S
- /
- d
- o
- c
- s
- /
- W
- e
- b
- /
- A
- P
- I
- /
- A
- n
- a
- l
- y
- s
- e
- r
- N
- o
- d
- e
- "
- >
- M
- D
- N
- :
- A
- n
- a
- l
- y
- s
- e
- r
- N
- o
- d
- e
- <
- /
- a
- >
- (
- W
- e
- b
- A
- u
- d
- i
- o
- A
- P
- I
- )
- .
If two apps open the same mic, Windows or macOS may duck or lock one of them; close the other app and press start again.
A USB mixer that exposes several inputs will need the correct device chosen in the browser’s permission bubble or in OS sound settings.
This page does not apply a noise gate, a compressor or a beauty filter.