Mic Test
This free mic test checks your microphone right in your browser. Speak, and you'll see it on the waveform in real time — no download, no sign-up, nothing installed.
RUNS ENTIRELY IN YOUR BROWSER · YOUR AUDIO IS NEVER UPLOADED OR STORED
Last updated: · Reviewed for accuracy against current browser APIs
Headphones only for both "Hear yourself" buttons, with the volume low. Through speakers the sound re-enters the mic and howls. The delayed version plays you back one second late, so you can judge your tone without your own voice drowning it out.
Room and level check
Two 5-second readings in dBFS (0 is the digital ceiling, lower is quieter). Do the quiet one first, then the voice one.
On this page
- Room noise and clipping check
- USB mic noise and level
- How to test your microphone
- How this mic test actually works
- What the result does and does not prove
- Troubleshooting: no waveform
- Permissions by operating system
- Troubleshooting: still sounds wrong
- Who tests a microphone, and why
- Microphone problems at a glance
- Understanding your microphone's settings
- Microphone types compared
- Headset mic vs. standalone microphone
- Frequently asked questions
- More tools on ProDeviceTest
Room noise and clipping check: what the numbers mean
The waveform tells you the mic is alive. It doesn't tell you whether the recording is any good. So the room and level check under the meter takes two 5-second readings and puts numbers on the two problems people actually complain about: hiss or fan noise underneath your voice, and distortion when you get loud.
Levels are in dBFS, where 0 is the loudest the digital signal can go and everything real is negative. Room noise is the typical (median) level while you say nothing. Voice level is how loud you are for most of a sentence, and voice peak is your single loudest instant. A clip event is a moment where the signal hit the ceiling and got flattened, which is the crackle you hear on a shouted word. Rough guide: room noise below -60 is quiet, -50 to -60 is a normal home, and above -40 means you can probably hear it yourself. For the voice, a peak somewhere between -18 and -3 is comfortable. Higher than that and you're a loud laugh away from clipping, lower and you'll be boosting noise later to make up for it. The gap between voice and room noise is the number that matters most. Over about 35 dB sounds clean, under 20 dB sounds like a call from a kitchen.
This catches things a simple pass/fail look misses. A headset that looks fine on the waveform but sits at -38 dBFS of constant hiss. A USB mic with the gain knob turned up so far that every plosive clips. Or the opposite, a laptop mic whose voice peak is -30 and needs the system volume pushed up, which drags the noise up with it.
- Start the test
Allow the mic, and pick the one you actually use.
- Press button 1 and go silent
Don't type, and stay still. Leave the fan, the AC or the window the way they normally are, since that's the noise you're measuring.
- Press button 2 and talk
Read a few sentences at your normal call volume, from your normal distance. Say something emphatic once so any clipping shows up.
- Read the verdict
Adjust the input volume in your system settings (or the gain knob), then repeat step 3 and compare.
Limits, honestly. Most browsers apply noise suppression and automatic gain by default, and both change the numbers: suppression can make a noisy room read much quieter than the raw mic hears it, and gain control can stop clipping before it happens. The info panel shows whether they're on. Also, the readings are relative to your input volume, so -55 on one setup and -55 on another aren't the same hardware quality. And clip events are counted from short snapshots of the audio, so treat them as "some" or "none" rather than an exact count. Nothing here leaves your browser.
Mic test for a USB microphone: noise floor and voice level
Say you plug in a USB mic for a weekly call and run the two readings. Room noise comes back at -44 dBFS, which the page calls noisy. Then you talk: voice level -14, voice peak 0, and 3 clip events. The verdict says clipping, and since voice sits 30 dB over the noise (-14 minus -44), the gap itself is acceptable. So the main fault isn't a noisy room. The gain is simply too high, and it lifts the hiss along with the voice.
The fix is to turn the gain down by roughly 10 dB, in the system input volume or on the mic's own knob, and run both readings again. Everything shifts down together: noise around -54, voice level around -24, peak around -10, no clip events. The gap stays near 30 dB, but now the page reads it as a normal room with a healthy level, and nothing is flattened on a loud word. That -54 isn't the room getting quieter. It's the same room, measured with less gain.
A counter-case: you stay quiet and the room noise reads "≤ -100 dBFS". That looks perfect, but the page flags it as digital silence, not a measurement. Noise suppression or a noise gate is probably cutting everything while you're silent. Switch suppression off if your browser or app allows it and measure again before trusting the number.
How to test your microphone
Here's how to test your microphone online in under a minute — no software, no account, just your browser.
- Click "Start test."
Your browser will ask for microphone permission — click "Allow." If you don't see a prompt, check the address bar for a blocked-permission icon.
- Speak or make some noise.
Watch the waveform above — it should move as soon as it picks up sound. The level bar underneath gives you a quick read on how loud your input is.
- Switch microphones if you have more than one.
The device list appears once permission is granted. Pick a different mic from the dropdown to test it without reloading the page.
- Hear yourself back.
Click "Hear yourself" to listen to your mic live through your speakers or headphones — headphones are strongly recommended here to avoid feedback.
- Record a short clip.
Record five seconds and play it back to hear exactly how you sound on a call or recording, separate from the live monitoring.
How this mic test actually works
This tool uses your browser's built-in getUserMedia API to request temporary access to your microphone, then feeds that live audio stream into the Web Audio API's AnalyserNode, which reads the raw waveform data dozens of times per second and draws it straight onto the canvas you see above. Every part of that pipeline — capture, analysis, and drawing — runs inside your browser's own sandbox.
That's also why the privacy claim on this page isn't just a promise: there's no upload step in the code at all. The audio data goes from your microphone into the browser's audio graph and back out to your screen or speakers, and nowhere else, unless you explicitly click "Record," which saves a clip only to your own device's memory for that session.
What this result tells you, and what it does not prove
A mic test answers a narrow question: does this browser receive sound from this microphone right now? It is easy to read more into a result than it supports, so here is the honest version.
| What you see or hear | What it tells you | What it does not prove |
|---|---|---|
| The waveform and level move when you talk | The browser has permission and is receiving sound from the selected microphone | That Zoom, Teams, Discord or any other app can use it, since each has its own permission and device setting |
| The playback sounds clear to you | The microphone and the signal path to this page work well enough for speech | That other people will hear you the same way, because call apps add their own processing and compression |
| The level is low or the clip is quiet | Input volume, distance or the chosen device may be the issue | That the microphone is faulty. A volume or device setting is the more common cause |
| Noise appears between your words | The room or the signal chain adds noise at that moment | Where the noise comes from. It can be the room, a fan, a cable or the mic itself |
| The delayed playback sounds fine | Your tone and level are reasonable without hearing yourself live | That you will sound that way on a call with network lag or heavy noise suppression |
| Nothing moves at all | No usable signal reaches the browser | That the microphone is broken. Permission, the device choice or another app holding the mic are all more likely |
For a device-specific walk-through, the guides for Windows 11, Mac, iPhone and Android cover each system's own settings.
Troubleshooting: no waveform at all
Follow these in order — most people are back up and running by step 2 or 3.
- Make a genuinely loud sound.
Some mics have a short activation delay or a noise gate. Clap or speak loudly right next to the mic before assuming it's broken.
- Check the address bar for a blocked-mic icon.
In Chrome and Edge, a crossed-out camera/mic icon appears on the left side of the address bar if permission was denied. Click it, set microphone to "Allow," and reload.
- Reload the page.
This alone fixes a surprising number of cases, especially if you plugged in a mic after the page was already open.
- Open the device dropdown and pick your mic explicitly.
Browsers sometimes default to the wrong input device, particularly right after connecting a new one.
- Confirm the mic is connected and powered.
Reseat a USB or 3.5mm connection, check a wireless mic is paired and charged, and look for a physical mute switch on the mic or cable.
- Check your system's privacy settings.
See the OS-specific steps just below — this is the most common cause after permission and connection issues.
Checking microphone permissions by operating system
Windows 10 & 11
Open Settings → Privacy & Security → Microphone. Confirm "Microphone access" is turned on, then scroll down and make sure your specific browser is toggled on in the app list below it. Both switches need to be on — the global one and the per-app one.
macOS
Open System Settings → Privacy & Security → Microphone. Your browser should be listed here with a toggle — if it's off, switch it on. If the browser isn't listed at all, trigger the permission prompt again from this page and click "Allow" when macOS asks.
Linux
Permission handling varies by desktop environment, but the two things worth checking are: your user account has access to the audio group (groups $USER in a terminal should include audio), and that PulseAudio or PipeWire shows your mic as an available input source in your system's sound settings.
ChromeOS
Click the status area in the bottom right, then the gear icon for Settings, and look under Privacy and security → Microphone. Chromebooks handle this at the OS level similarly to how individual sites request permission in any other browser.
Android & iOS
On Android, check Settings → Apps → [your browser] → Permissions → Microphone. On iOS, check Settings → [your browser] → Microphone, or under Settings → Privacy & Security → Microphone for a list of every app that has requested access.
Troubleshooting: waveform moves, but something still sounds wrong
- Sounds too quiet.
Raise the input volume in your system's sound settings, and move closer to the mic — proximity affects levels more than most people expect.
- Sounds distorted or clips at loud moments.
Your input gain is likely set too high. Lower it in your system sound settings until the level bar stops pinning at maximum during normal speech.
- Crackling or static.
Try a different USB port, reseat the cable, and check for a pending audio driver update in Device Manager (Windows) or System Information (Mac). Most onboard audio ships as a customized build from your computer's own manufacturer rather than a generic download, so check your PC's support site directly — Dell, HP, and Lenovo all have one.
- Works here, but not in Zoom, Teams, or Discord.
Since this test confirms the mic and browser-level permission are fine, the remaining issue is almost always that specific app's own microphone setting — check its audio settings menu for the correct input device.
If everything above checks out but you want to confirm the rest of your audio setup too, our Sound Test checks that your speakers or headphones play back correctly, and Voice Recorder lets you record a quick clip to actually hear how you sound.
Who tests a microphone, and why
Streamers and podcasters run this before every session, since dead air because of a muted or disconnected mic is the kind of mistake you only want to make once. Remote workers reach for a quick mic test before an important call or interview, especially on a new laptop or a headset they haven't used yet — better to catch a problem two minutes early than mid-meeting. Gamers check their mic after a driver update or a Windows update, both of which have a habit of quietly resetting audio settings. Anyone who's just bought a new microphone, headset, or webcam runs it once out of the box to confirm it actually works before the return window closes — pair this with our Webcam Test to check both sides of your call setup at once. And when a mic "stops working" out of nowhere, this is usually the fastest way to tell whether it's the hardware, the app, or a permission setting that's actually at fault.
Microphone problems at a glance
Match what you're seeing to what's probably actually going on.
| Symptom | Likely cause | Quick fix |
|---|---|---|
| Waveform's completely flat | Permission's blocked, or the wrong mic is picked | Check the site's mic permission first, then check the device dropdown |
| Browser never even asks for permission | You already said no once, and it remembered | Reset the site's permission from the address bar and reload |
| "Mic already in use" error | Something else has it open — Zoom, Teams, Discord | Close whatever else might be using it and try again |
| Sound's barely audible | Gain's too low, or you're too far from the mic | Bump up input volume in system settings and lean in a bit |
| Crackly or distorted at loud moments | Gain's cranked too high | Pull the input level down until it stops clipping |
| Random crackling or static | Loose cable or an outdated driver | Reseat the cable, try another port, check for driver updates |
| Works in the browser, not in some other app | That app's own mic permission is off, separate from your browser's | Dig into that specific app's audio settings and check its input device |
Understanding your microphone's settings
The mic info panel above shows a few settings that are worth understanding, since they quietly shape how you sound on every call.
Echo cancellation stops the sound coming out of your speakers from being picked back up by your microphone and looping into an echo. It matters most if you're on speakers rather than headphones — with headphones, there's nothing for the mic to pick back up in the first place.
Noise suppression filters out steady background sound — a fan, an air conditioner, traffic outside — without touching your voice. It's genuinely useful in a noisy room, but can occasionally make a voice sound slightly processed or "underwater" if it's being too aggressive.
Automatic gain control (AGC) continuously adjusts your input volume so you don't sound too quiet or too loud as you move or change your speaking volume. Most of the time this is helpful, but some people — musicians and podcasters especially — prefer to turn it off for more consistent, predictable audio levels.
You can use this page to test microphone echo cancellation, noise suppression, and AGC by toggling them in your system or app settings and refreshing the mic info panel to confirm the change actually took effect.
Microphone types compared
Not every microphone is built for the same job, and knowing which type you're testing helps explain what "normal" sounds like for it.
| Mic type | How it connects | Typical sound | Best for |
|---|---|---|---|
| Built-in laptop mic | Internal, no setup needed | Thin, picks up room noise easily | Quick calls, casual use |
| USB condenser | Plug-and-play USB | Detailed, sensitive to background noise | Podcasting, streaming, voiceover |
| XLR dynamic | Via an audio interface or mixer | Warm, naturally rejects room noise | Broadcast-quality streaming, studios |
| Wireless / Bluetooth | Paired over Bluetooth or RF | Convenient, sometimes compressed | Calls on the move, casual gaming |
| Headset mic | Wired or wireless, attached to headphones | Consistent distance from your mouth | Gaming, long call sessions |
Testing a headset mic vs. a standalone microphone
This mic tester works the same way for either one, but what a "good" result looks like differs a bit.
A headset mic sits at a fixed distance from your mouth, so its levels tend to be consistent test after test — if it suddenly sounds quieter or more distant than usual, that's a real change worth investigating rather than just you sitting differently. A standalone microphone is more sensitive to positioning, so it's worth testing from roughly the same distance and angle you'd actually use while talking or recording, since a "quiet" result up close can just mean the mic was further away than usual during the test.
If you're deciding between the two for calls or streaming, run this test with each and compare the waveform and recorded playback side by side — the level meter alone won't tell you about tone or background pickup, but listening to a recorded clip will.
Frequently asked questions
How do I know if my mic is actually working?
Hit "Start test" above and let the browser grab mic permission. If the mic is picking up sound, you'll see the waveform jump around as you talk — the fastest way to check without opening any other app.
Why won't my browser detect my mic at all?
Nine times out of ten it's a permissions thing, not a dead mic. Check your browser's site settings and make sure mic access is switched on for this page, and that nothing else has it locked up in the background.
Does this site record or upload my voice anywhere?
No. The waveform and level bar are drawn straight from your browser's own audio engine. Even if you record a clip, it stays local — there's no upload step anywhere in the code.
Can I test a Bluetooth or USB mic here too?
Yep. Doesn't matter if it's USB, Bluetooth, or something plugged into an XLR interface — as long as your OS sees it, it'll show up in the dropdown once you approve the permission.
Why do I sound delayed when I hear myself back?
That little lag is normal — it's just your system processing audio before it plays back. If it's bad enough to be distracting, close other audio apps running in the background or switch to wired headphones instead of Bluetooth.
What do echo cancellation, noise suppression, and AGC actually do?
Quick version: echo cancellation stops your speaker sound from looping back into the mic, noise suppression scrubs out constant background stuff, and AGC automatically rides your volume up or down. See the settings section above for the full breakdown of each.
My mic works on Zoom but not here (or the other way round) — why?
Each app handles mic permissions on its own, so it's pretty common for one to work and another not to. Check that specific app's own audio settings — there's a good chance it's just pointed at the wrong input device.
Will this work on my phone?
Should work fine as long as you're on a reasonably current mobile browser and tap allow when it asks for mic access. Built-in mic, wired earbuds, Bluetooth — all fair game.
There's zero sound, not even background hiss — what does that mean?
Usually means the browser isn't getting any signal at all from whatever device is selected. Worth checking you've picked the right mic in the dropdown, that it isn't muted at the hardware level, and that your input volume isn't sitting at zero.
What is a good noise floor for a microphone?
Measured here as the median level in a silent 5-second reading, anything below about -60 dBFS is quiet and -50 to -60 is a normal home. Above -40 you can usually hear the noise yourself. It depends on your input volume though, so compare before and after on the same setup rather than against someone else's number.
More tools on ProDeviceTest
Troubleshooting a whole setup rather than just the mic? These run the same way — instant, no download, right in your browser.
- Keyboard Test — check every key for stuck or unresponsive presses
- Mouse Test — check clicks, scroll, and cursor tracking
- Sound Test — confirm your speakers or headphones play correctly on both channels
- Hearing Test / Frequency Test — compare your ears across seven pitches and find your highest audible tone
- Speaker Cleaner / Water Eject — push water and dust out of a speaker with a low tone
- Webcam Test — verify your camera before a call
- All Device Tests — the full category
- Mic not working? Find the cause fast — a step-by-step guide
- Check your mic before a call or interview — a short routine
- Mic guides by device: Windows 11, Windows 10, Mac, iPhone, Android, Bluetooth headsets
- Mic guides by app: Discord, Zoom, Teams, Google Meet
- Mic sound problems: too quiet, echo, hiss and noise, distorted, cutting out
- Mic not detected or shared: USB mic, headset jack, browser blocked, OBS, apps fighting for the mic
