Why Test Your Microphone?
Microphone problems are surprisingly common and often invisible until it's too late. The most frequent issues include:
- No signal — The microphone isn't selected in the operating system, or the physical connection is faulty.
- Clipping — The input gain is too high, causing the audio waveform to hit the digital ceiling and distort. Clipped audio sounds harsh and can't be recovered in post.
- Wrong sample rate — A mismatch between the microphone's output sample rate and your recording software's expected rate can cause pitch issues or resampling artifacts.
- Low signal level — The mic is working but the recorded level is too quiet, forcing you to amplify in post and bring up background noise along with your voice.
- Wrong device selected — Your system defaulted to a built-in mic instead of your studio microphone or audio interface.
What a Good Microphone Test Checks
A proper microphone test should verify at least four things:
| Check | What It Means |
|---|---|
| Microphone detected | Your browser has permission to access a mic and found one |
| Signal present | Audio is coming through — the mic is physically working |
| No clipping | Input gain isn't too high — audio stays below 0 dBFS |
| Sample rate OK | Your interface or mic is running at a standard rate (44.1 kHz or 48 kHz) |
How to Test Your Mic in the Browser
AudioLab's Mic Test tab uses the Web Audio API to access your microphone in real time. Here's how to use it:
- Open audio.rswaver.com and click the Mic Test tab
- Click Start Mic Test and allow microphone access when prompted
- Speak or make noise — you should see the VU meter respond
- Check the pass/fail results: detected, signal, no clipping, sample rate
- The device info card shows your microphone name, sample rate, and current RMS level
Privacy note: The Mic Test uses your browser's Web Audio API for real-time analysis only. No audio is recorded or transmitted anywhere — it's all processed locally.
Reading the VU Meter
The VU (Volume Unit) meter shows your microphone's current signal level in decibels. Here's what the zones mean:
- Green zone (below −12 dB) — Safe signal level. Good for conversation and recording.
- Yellow zone (−12 to −6 dB) — Moderate level. Fine for most applications, approaching loud.
- Red zone (−6 to 0 dBFS) — Near maximum. Risk of clipping on peaks. Consider lowering gain.
- Peak hold indicator — Shows the highest level reached. If it's consistently in the red, your gain is too high.
Common Problems and How to Fix Them
Mic not detected
First, check that you've given the browser permission to access your microphone (look for a camera/mic icon in your browser's address bar). If permission is granted but no mic is found, check that your microphone is connected and selected as the default input device in your OS audio settings.
No signal despite being detected
Your mic is connected but producing no audio. Try: speaking louder, checking the mute button on the mic itself, or increasing the input gain in your OS audio settings or audio interface software.
Clipping detected
Your input gain is too high. Reduce the gain on your audio interface or in your OS sound settings until the VU meter stays mostly in the green/yellow zone during normal speech, with occasional peaks into yellow.
Sample rate mismatch
Your microphone or interface is running at an unexpected sample rate (e.g., 96 kHz when 44.1 or 48 kHz is standard). Check your audio interface software or OS audio settings and set the sample rate to 44100 Hz or 48000 Hz.
Before Every Recording Session
Make a habit of running a quick mic test before any recording. Catching a clipping issue or wrong device selection before you start saves the frustration of discovering unusable audio after the fact. A 30-second check in AudioLab's Mic Test is all it takes.