Mic Test
Click start and allow microphone access. Speak normally and watch the level meter and waveform respond.
Collect all your test results on one sheet: PC Checkup Report
What this test checks
If the meter doesn't move while you speak, work through it in this order: the physical mute switch on your headset, the input device selected above, your OS sound-input settings, and finally the browser's site permission. In most "my mic doesn't work" cases the wrong input device is selected — a laptop's built-in mic instead of the headset.
A meter that moves doesn't guarantee you sound good. Use the record button and listen to yourself: robotic or crackling audio usually means a failing USB port or cable, while a very quiet recording means the input gain is set too low in your system settings.
How this test works
Our mic test captures audio through getUserMedia, a standard capability built into every modern browser. Because a web page can only reach your microphone with your consent, the browser interrupts with a permission prompt the first time you press start. That prompt belongs to the browser, not to our site, and it is the same safeguard every video-call service goes through. Once you allow it, the browser hands over a list of the input devices it can see, which is exactly what appears in the device selector above the meter.
Audio from the device you choose flows into the Web Audio processing layer, where it is examined in short slices of a few tens of milliseconds. For each slice the level meter computes an RMS value: the samples are squared, averaged and square-rooted, which gives a figure that tracks perceived loudness far better than the raw peak does. That figure is then expressed in dBFS, a scale on which 0 is the loudest value a digital signal can hold and everything quieter is a negative number. A reading near 0 means the signal is hitting the ceiling; a reading around -50 means the room is close to silent.
The waveform canvas draws the same samples against time. The meter tells you how loud the last moment was, but the waveform shows the shape of the sound, which is what lets you spot clipping or persistent noise at a glance. The record button uses the browser's MediaRecorder to hold a few seconds of audio in memory so you can play it straight back.
None of this leaves your computer. Level calculation, waveform drawing, recording and playback all happen inside the browser tab, and the recording disappears when you close it. The only thing our server ever receives is the request that loads the page.
How to read the results
While you speak at a normal conversational volume, the meter should hover roughly between -18 dBFS and -6 dBFS. That range leaves headroom for louder moments without ever sounding thin. If the needle stays below -30 dBFS while you talk, other people will hear you as a whisper, and the fix is usually to bring the mic closer or raise the input level in your operating system. If it sits pinned near 0 dBFS whenever you raise your voice, the signal is clipping and will sound harsh and distorted on the far end.
The reading you see while staying silent is your noise floor: the hiss the microphone, its cable and its electronics produce on their own, plus whatever the room contributes. Below -60 dBFS in a quiet room is excellent, and around -50 dBFS is fine for calls. A silent reading of -40 dBFS or higher usually points to a fan, electrical interference, or an input gain set so high that it amplifies the noise along with your voice.
On the waveform, three shapes matter. A perfectly flat line while you are speaking means no audio is arriving at all, and if the meter is also stuck that almost always means the wrong device is selected. Peaks and troughs that look sliced off flat are clipping; lower the input level or move back from the mic. A dense, spiky fuzz that keeps trembling after you stop talking is noise leaking in, whether from the environment or from the electronics.
Playback is the readout that matters most. The meter and waveform give you numbers, but what the other side of a call hears is the recording. If your voice comes back boomy with room echo, breaks up, or takes on a metallic, processed quality, the microphone is not ready for a call even when every number looks acceptable.
When to use it: common situations
The most common reason to run the test is a video interview or an important meeting in the next few minutes. Testing inside the meeting app means signing in and hunting for a settings panel; here you can confirm in half a minute that audio is arriving, that the right device is selected and how you actually sound. Listening to a playback before the call is what catches a mic positioned too far away or a room that echoes.
It is equally useful when unboxing a new headset or USB microphone. One run tells you whether the hardware works, whether the operating system recognised it correctly and whether the default input level is sensible. If you have just bought a second-hand laptop or headset, running the test within the return window gives you concrete evidence: constant noise on the waveform or crackle in the playback is a reason to send it back.
After a Windows or macOS update breaks audio, the test helps narrow the cause. If the microphone works here but not in one particular program, the problem lies in that program's permissions or device settings. If it fails here too, the operating system's input device or driver is the place to look. Splitting the problem into inside-the-browser and outside-the-browser halves saves a lot of guesswork.
Bluetooth headsets deserve a specific check. Many of them switch from their music profile to a lower-quality call profile the moment a microphone is opened, and the difference is audible. Playing back a recording lets you hear the exact quality the other party will get. The test also makes a good first step when setting up a streaming rig: before launching broadcast software, confirm that the microphone chain is alive at the most basic level.
Limits of a browser test and what to check elsewhere
A browser only receives whatever audio the operating system passes along. Windows microphone boost, the macOS input volume slider, and the equaliser or noise-suppression features in a headset's own software are invisible to our test and cannot be changed from here. When the meter reads low or noisy, the cause is very often one of those settings, so the right next step is to open your system sound settings and check the input level and any boost directly.
Bluetooth adds another blind spot. The browser does not control the profile switch that happens when a microphone is opened, and if that switch is slow or fails, the device can appear in the list yet deliver no sound. Likewise, some applications claim the microphone in exclusive mode, and while they are running the browser cannot open the device at all. In that case the test can only tell you that the microphone would not open; it cannot tell you which program is holding it.
Our meter reports level and noise floor, but it is not a measurement instrument. It cannot plot frequency response, measure latency, or tell you whether a microphone matches its published specification; that requires a calibrated reference and dedicated software. The recording is also short, so an intermittent dropout that appears only after several minutes may never show up here. For that kind of fault, make a long recording with your operating system's voice recorder and listen for the gap.
Once the test has shown you the symptom, the related guides on this site take it from there. If the meter never moves, the mic-not-working guide and the separate Windows and Mac microphone guides walk through device selection and permissions in order. If you are too quiet, the mic-too-quiet guide covers input level and boost. For echo, hum or background noise, see the echo and noise guide, and for static or crackle, the static and crackling guide. If the microphone works here but fails in a specific application, the mic-not-working-in-app guide explains the per-app permission and device settings involved.
Frequently asked questions
- The permission prompt never appeared, or I blocked it by mistake.
- Click the padlock or settings icon at the left of the address bar, set microphone access for this site to Allow, and reload the page. If that does not help, check the operating system: on Windows go to Privacy & security > Microphone, and on macOS go to Privacy & Security > Microphone, and make sure the browser itself is allowed to use the microphone.
- My recorded voice sounds different from how I hear myself.
- That is normal. You usually hear your own voice as a mix of sound travelling through the air and vibration conducted through your skull, which makes it seem deeper and fuller. A recording captures only the airborne part, so it sounds thinner and higher. The recording is what other people hear, so use the playback when judging quality.
- How high should the level meter go?
- Speaking at your normal volume, the meter should reach between the middle and about two thirds of the way up. If it hits the top and stays there when you speak loudly, the input is clipping and will sound distorted, so lower the system input volume. If it barely moves, raise the input volume or move closer to the microphone.
- The meter moves a little even when I am silent.
- A small amount of movement from room noise and the microphone's own electrical noise is normal; PC fans, air conditioning and keyboard sounds are all picked up. If the meter sits noticeably high while you are quiet, the input volume or microphone boost is probably set too high. If playback has an annoying hiss, lowering the boost and moving the mic closer to your mouth gives better quality.
- Can I test Bluetooth earbuds such as AirPods?
- Yes — pick them from the input device list. Be aware that the moment a Bluetooth device's microphone is activated, it switches to a call profile, and both the sound you hear and the microphone quality fall to telephone level. That is a bandwidth limit of the Bluetooth standard, not a fault. For important meetings or recording, a wired or USB microphone will do better.
Related guides
- Mic Not Working? The 5-Minute Checklist That Finds the Cause
- Fixing Mic Echo and Background Noise: Sound Better on Every Call
- Microphone Too Quiet: Why Others Can Barely Hear You and How to Fix It
- Mic Static, Crackling or Buzzing: How to Find the Source and Fix It
- Mic Works in Browser but Not in Discord, Zoom or Games: Fix the App, Not the Mic
- Microphone Not Working on Windows 11 or 10: Every Fix, in Order
- Mac or MacBook Microphone Not Working: Permissions, Input Settings and Resets