Sound Analysis Tools
Pitch Detector Tools

Microphone Test Tool (Online & Free)

Click "Start" to allow access to your microphone and test the input.

Last updated: October 31, 2026 · Written by the Pitch Detectors Editorial Team

A microphone test checks that your mic works, shows your live input level, and reveals problems like clipping or background noise — before your recording, stream, or call. Press Start Mic Test and speak normally.

Key Takeaways

  • Healthy mic level: peaks between −12 and −6 dBFS, average around −18 dBFS.
  • Red = clipping. Back off the gain or the mic until peaks stay out of the red.
  • Silence should read near zero — a bouncing meter with no speech means background noise.
  • Disable auto gain control (AGC) in OS settings before testing, or readings lie.
  • This test checks function and levels, not frequency response or studio-grade quality.

What Is a Microphone Test?

A microphone test is a quick check that your microphone captures audio correctly: it verifies the browser can access the mic, displays your live input level, and exposes issues like clipping, low gain, or background noise. It takes thirty seconds and prevents the classic disaster of recording an hour of audio with a dead or distorted mic.

This tool uses the getUserMedia API to open your default recording device and draws a real-time level meter. Speak, watch the meter, run the 3-second silence check below — you'll know exactly where your setup stands.

How This Microphone Test Works

Clicking Start Mic Test asks the browser for microphone permission, then connects the live stream to an analyser that measures input amplitude many times per second and drives the on-screen meter. Stop Test releases the microphone so no other app is blocked.

Methodology: the meter maps instantaneous amplitude to a green–yellow–red scale — green for healthy signal, yellow approaching hot, red at digital clipping (0 dBFS). The 3-second silence protocol (below) separates your voice from the room's noise floor. Validation method: clap once loudly — the meter should spike into red momentarily, then fall back; if it never moves, the wrong input device is selected.

Last reviewed: October 2026. Capture follows the W3C getUserMedia specification; see MDN Web Docs for reference.

Target Levels and Worked Example

Digital audio measures level in dBFS (decibels relative to full scale), where 0 dBFS is the clipping ceiling and everything else is negative. Your targets:

Use case Peak target Average target
Music/podcast recording −12 to −6 dBFS ≈ −18 dBFS
Live streaming −12 to −6 dBFS −18 to −12 dBFS
Video calls −20 to −12 dBFS ≈ −20 dBFS

Worked example: your meter peaks at −24 dBFS while speaking normally — 12 dB too quiet for recording. Since +6 dB ≈ double the digital amplitude, you need roughly +12 dB of gain (about 4× amplitude). Raise the OS input level or interface gain until peaks kiss −12 to −6 dBFS, leaving headroom for laughs and emphasis.

TECHNICAL SPECIFICATION Where your mic level should sit. Suggested alt text: "Diagram of ideal microphone input levels on a dBFS meter" INPUT CRITERIA Standard Parameters BASELINE SPECS DSP COMPUTATION Algorithmic Conversion IN-BROWSER DSP OPTIMAL OUTPUT Calibrated Value ACCURATE RESULT vertical dBFS meter showing green zone (−18), yellow (−12 to −6), red (0), with "your targ
Where your mic level should sit. Suggested alt text: "Diagram of ideal microphone input levels on a dBFS meter"

How to Test Your Microphone

  1. Click Start Mic Test and choose Allow when the browser asks for microphone access.
  2. Speak normally — count "one, two, three" at your real recording volume and distance.
  3. Watch the meter: healthy speech lives in the green, occasionally touching yellow (−12 to −6 dBFS).
  4. Run the 3-second silence test: stop talking and stay quiet — the meter should fall near zero.
  5. Adjust gain in your OS sound settings or interface until both checks pass.
  6. Click Stop Test to release the microphone when done.

Reading Your Result: What the Meter Tells You

What you see What it means What to do
Green, peaking −12 to −6 dBFS Perfect gain staging Nothing — you're ready
Constantly red Clipping — distorted audio Lower input gain or move the mic back
Barely moves past 10% Gain far too low Raise OS/interface gain; check you're on the right device
Bounces above 20% in silence Background noise (fan, hum, room) Kill noise sources; move closer to the mic
Meter never moves at all Wrong device or blocked permission See the troubleshooting checklist below

Microphone Not Working? Troubleshooting Checklist

Work through these in order — they solve nearly every "mic not working" case:

  1. Permission: click the lock/camera icon in the address bar and set microphone to Allow, then reload.
  2. Default device: in OS sound settings, confirm your intended mic is the default recording device (not "default communications device" only).
  3. Browser device picker: some browsers let sites pick a device — check the site's mic selector if one appears.
  4. App conflicts: close Zoom/Teams/Discord — another app may be holding the mic exclusively.
  5. Hardware: unplug and replug USB mics; for XLR mics confirm +48V phantom power is on (condensers need it; USB mics never do).
  6. Privacy switches: many laptops have a physical mic mute key or shutter — check it isn't engaged.

AGC: The Setting That Silently Ruins Your Levels

Automatic gain control (AGC) is an OS feature that rides your mic gain up and down to "normalize" speech. It makes testing meaningless — the meter dances on its own — and it pumps background noise up during pauses. Turn it off before any serious test or recording: Windows → Sound settings → Input → disable "Automatically adjust microphone settings"/"audio enhancements"; macOS → no system AGC, but check individual apps (Zoom's "automatically adjust volume" is a common culprit); Chrome → chrome://settings/content/microphone has no AGC toggle, so fix it at the OS level.

Limitations

  • Checks function, not fidelity. The test confirms signal path and levels — it cannot measure frequency response, self-noise specs, or "studio quality."
  • Browser processing applies. Some browsers apply noise suppression to getUserMedia streams; for a raw check, prefer Chrome/Edge with OS enhancements off.
  • One device at a time. The test uses your default input; to check a second mic, switch the OS default and re-run.
  • No recording. Nothing is captured or stored — if you need a sample, record a voice memo separately after the level check.

Microphone Types Compared

Type Best for Notes
USB mic Beginners, calls, streaming Plug-and-play; no phantom power or interface needed
XLR + interface Podcasts, music, pro streaming Best quality ceiling; needs interface and +48V for condensers
Built-in laptop mic Emergency calls only Noisy, distant, picks up keyboard — test will show it
Headset mic Gaming, calls Close placement helps, but thin sound for recording
PROCESS WORKFLOW The gain staging chain. Suggested alt text: "Diagram of microphone signal chain showing ideal gain staging levels" 1 signal chain from mouth 2 mic 3 interface gain knob 4 dBFS meter, with the −.. signal chain from mouth → mic → interface gain knob → dBFS meter, with the −12 to −6 dBFS targe
The gain staging chain. Suggested alt text: "Diagram of microphone signal chain showing ideal gain staging levels"

Frequently Asked Questions

Press Start Mic Test above, allow microphone access, and speak normally. If the level meter moves with your voice, your mic works and the signal path is good. Then run the 3-second silence check: quiet should read near zero. If the meter never moves, work through the troubleshooting checklist above — it's almost always a permission or wrong-device issue.

Aim for peaks between −12 and −6 dBFS, with your average speech around −18 dBFS. That leaves headroom for laughs, emphasis, and plosives without clipping. For video calls you can run slightly lower (−20 to −12 dBFS peaks); for music recording, never let peaks touch 0 dBFS.

The usual causes: wrong input device selected (you're testing the laptop mic instead of your USB mic), the mic is too far away (every doubling of distance drops level 6 dB), or a condenser mic without +48V phantom power. Check the OS default recording device first — it fixes most quiet-mic cases instantly.

That's clipping — your input gain is too high and peaks are hitting 0 dBFS. Lower the gain until peaks stay under −6 dBFS. If distortion persists at low levels, suspect a failing cable, a USB port without enough power (try another port), or a sample-rate mismatch between the mic and your OS.

Get closer to the mic (proximity beats any filter), then kill noise at the source: fans, AC, mechanical keyboards. A cardioid mic rejects sound from behind — face the noise away. Software noise suppression (RTX Voice, Krisp, Discord's) helps last, but it can't rescue a 20 dB noise floor; fix the room first.

No — never. USB microphones power themselves through the USB connection. Phantom power (+48V) is only for XLR condenser microphones connected via an audio interface or mixer. Sending +48V to the wrong place won't help a USB mic and can damage some ribbon mics, so only enable it for XLR condensers.

Permissions are per-site: Zoom got OS-level access while Chrome's site permission is blocked or set to the wrong device. Click the lock icon in Chrome's address bar, set Microphone to Allow, and check that the selected device matches your mic. Also close Zoom — it may be holding the mic exclusively.

Stop talking and stay silent for three seconds while watching the meter. It should fall near zero. If it keeps bouncing above 20%, you have measurable background noise — fan hum, room tone, or electrical interference — entering your recordings. Fix the loudest source before reaching for software noise removal.

For calls, streaming, and starting out, a good USB mic wins on simplicity — one cable, no interface. For podcasts or music where quality matters long-term, XLR plus an interface gives lower noise, better preamps, and upgrade paths. Either way, test the level with this tool before you record anything important.

That's monitoring latency: audio travels mic → OS → browser → back to your ears, typically adding 20–100 ms. It's distracting, so most people monitor through their interface's direct/hardware monitoring (zero latency) instead of software. This test doesn't play your mic back, so latency never affects your readings here.

Note: this tool checks microphone function and input levels only. It does not record, store, or transmit your audio.

Related tools: decibel meter for room noise levels, loudness meter for LUFS mastering, waveform visualizer to see recordings, and pitch detector for vocal pitch tracking.