Skip to content
PeriphCheck Guides

Mic Test

Check your microphone with a live waveform, level meter and instant playback.

Everything runs locally in your browser. Nothing you do here — audio, video or input — ever leaves your device.

Click the button below and your browser will ask permission to use the microphone. The audio is analyzed locally on this page — nothing is recorded on a server or uploaded anywhere.

How it works

When you start the test, the page requests microphone access through your browser's standard permission prompt — audio only flows after you approve, and it flows only into this page. The stream feeds a Web Audio analyser that draws the live waveform and computes your input level in decibels. Speak normally: a healthy setup shows a clearly moving waveform and peaks around −12dB. A flat line means the wrong device is selected or the input level is muted in your OS.

The record-and-playback loop captures five seconds into your browser's memory and plays it straight back, so you can judge clarity, noise and echo exactly as others would hear you on a call. The clip is held in memory only — closing the page destroys it. Use the device picker to test every microphone connected to your machine, and check the reported sample rate matches what your recording software expects. If your mic doesn't appear at all, our mic troubleshooting checklist covers Windows 11 and macOS privacy settings step by step.

How to read your result like a sound engineer

Aim for speech peaking between −18dB and −6dB. Peaks constantly hitting 0dB mean the gain is too high and you'll clip (distort) on calls — lower the input level in your OS or on the mic's own gain dial. Peaks below −30dB mean you'll be inaudible and apps like Discord will amplify noise trying to compensate. Also glance at the sample rate: 44.1kHz or 48kHz is expected; if a USB mic reports 8kHz or 16kHz, Windows has it in "telephone quality" mode — set it to 48kHz under Sound → Device properties → Additional settings.

Common results and what they mean

What you see or hearMost likely causeFix
Flat line, no waveformWrong device selected, or OS privacy blockPick the right mic in the device list; check Windows Settings → Privacy → Microphone allows browser access
Waveform moves but playback is silentOutput going to another deviceCheck the playback device — headsets often register as two devices, and audio may route to the idle one
Very quiet even at max volumeMic boost off, or speaking into the wrong sideEnable +10/20dB boost in OS sound settings; address the front of a side-address mic (logo side)
Robotic or crackling soundSample-rate mismatch or USB bandwidthMatch OS and app sample rates (48kHz both); move the mic off a USB hub
Echo of your own voice on callsSpeaker sound re-entering the micUse headphones, or enable echo cancellation in the calling app — the mic itself is fine
Constant hiss or humElectrical interference or high gainLower gain, try a rear USB port, keep the cable away from power cables

If the mic passes here but a specific app still can't hear you, the problem is that app's input device setting — this test proves the hardware, driver and browser stack all work. Testing a headset? Verify the other half too with the headphone test.

Making sense of your microphone levels

The live waveform and level meter show your microphone's input in real time. Audio is analyzed in your browser and never uploaded; the optional playback clip lives only in memory. Speak normally and watch the meter — the level, not just "is there sound", is what tells you whether your mic is set up well.

Target input levels

Peak levelMeaningAction
Around −12 dB while speakingHealthy headroomLeave it — this is the target
Constantly hitting 0 dBClipping — distorted, harsh audioLower input gain in OS sound settings
Below −40 dBToo quiet — others strain to hear youRaise gain, or move closer to the mic
Meter flat while you speakWrong device selected or mic mutedPick the right input; check the hardware mute

Permission and device problems

Getting cleaner sound

Position the mic slightly off-axis (just to the side of your mouth) to reduce plosive pops. A stable −12 dB peak with a quiet background is better than a loud, clipping signal — quiet audio can be boosted later, but clipped audio is permanently distorted.

Troubleshooting

The browser says microphone access is blocked

Click the camera/mic icon in the address bar and allow access, then reload. On Windows also check Settings → Privacy → Microphone; on macOS check System Settings → Privacy & Security → Microphone.

The meter barely moves when I speak

Select the right device in the input picker — many laptops expose several inputs. Then raise the input level in your OS sound settings and make sure the mic isn’t hardware-muted.

I hear an echo during playback

Playback replays the clip you just recorded, so hearing yourself is expected. Echo during live monitoring means your speakers are feeding back into the mic — use headphones.

Frequently asked questions

Is my voice recorded or uploaded?

Never. Audio is analyzed live in your browser; the optional playback clip lives only in memory and is gone when you leave the page.

Why does the site ask for microphone permission?

Browsers require your explicit consent before any page can access a microphone. The prompt comes from your browser and applies only to this test.

What does the dB level mean?

It shows your peak input level. Around -12dB while speaking normally is healthy; constantly hitting 0dB means clipping (too loud), and below -40dB is too quiet.

Can I test multiple microphones?

Yes — use the device picker to switch between any connected inputs without reloading.

Related tools