Am I Muted Check: Online Mic Test & Microphone Test

Hearing "you're on mute" a minute into talking is the worst way to find out. This am I muted check lets you test your microphone in seconds: speak, and a real-time waveform shows whether any audio input reaches the page at all. If the line stays flat, the check tells you where the silence comes from, so you can fix it before your next streaming session or meeting.

How the Am I Muted Check Reads Your Microphone

When you press start, the browser asks for permission, opens your microphone and hands the page a live audio track. Everything is measured locally: the tester reads the raw samples (usually 48,000 a second) and turns each short block into one loudness figure, the RMS level in decibels relative to full scale: The mic record and playback runs entirely in your browser via the Web Audio API — nothing is uploaded anywhere.

$$L_{\text{dBFS}} = 20 \times \log_{10}\left(\text{RMS}\right), \quad \text{RMS} = \sqrt{\frac{1}{N}\sum_{i=1}^{N} x_i^{2}}$$

Here \(x_i\) is each sample between −1 and 1, \(N\) is the number of samples, and 0 dBFS is the loudest value possible. Take a two-second check at 48,000 Hz, which is 96,000 samples. You say one sentence and the speaking RMS comes out at 0.0631, so 20 × log₁₀(0.0631) = −24.0 dBFS, with a peak of 0.354 (−9.0 dBFS). Between words the floor sits at 0.00028, or −71.1 dBFS. That 47 dB gap between talking and pausing proves your microphone is not muted.

Repeat it with mute switched on in your calling app and all 96,000 samples come back as exactly 0. The RMS is 0, the logarithm has no value, and the verdict is digital silence: silenced in software, not broken. Every reading lands in one of these bands:

• Every sample exactly 0: muted in the app, the browser or the system.
• Below −60 dBFS while you talk (−81.0 dBFS from an RMS of 0.000089): the stream is open but nothing of you arrives, so look for a switch or the wrong microphone.
• −60 to −40 dBFS (−43.0 dBFS from 0.0071): live but quiet.
• −40 to −6 dBFS: normal speech, like the −24.0 dBFS example.
• Peaks touching 0 dBFS: clipping.

Real-Time Waveform and Level Indicator

The moving line is a visualizer of those same samples, drawing your sound waves as they arrive, while the level indicator beside it works like a volume meter filling sound bars from left to right. That visual feedback answers the question faster than any number:

• A flat line that never twitches means nothing reaches the page.
• A thin fuzz that never grows when you speak points to a switch or the wrong source.
• Bars that jump with each syllable mean you're live; steady volume levels mean your distance is consistent.
• Bars pinned at the far right mean clipping.

Microphone Information the Mic Test Tool Reports

The mic test tool also reads what the browser reports about the device, here for the example above:

Using the Microphone Test Before a Google Meet Lesson

It's 7:18 pm and I teach a Spanish lesson on Google Meet at 7:30. Last week my student said I kept fading out, so the question tonight isn't only "am I muted?" but "am I loud enough to be understood?" The answer, it turns out, was not muted, but 22 dB too quiet.

I plug in the USB headset, open the check, click Allow and read one line from the lesson plan for three seconds. The verdict comes back live but quiet: a speaking RMS of 0.00317, which the page reports as −50.0 dBFS. I recompute it by hand, 20 × log₁₀(0.00317) = −49.98, so the meter isn't lying. The bars move, but only in the left third.

Windows Sound settings show why: the headset's input slider sits at 14 out of 100. I raise it to 62 and run the same line again:

That last run is 21.8 dB louder than the first. The pause floor is now −67.7 dBFS (RMS 0.000412), so speech sits 39.5 dB above the background, and my loudest word peaks at −13.5 dBFS, leaving 13.5 dB before clipping. Those two gaps are what move the verdict from live but quiet to live, normal speech. As an outside yardstick, EBU R 128's −23 LUFS broadcast target is a weighted measure rather than raw RMS, but it agrees: −28.2 dBFS sits in the check's normal-speech band, well clear of the quiet one.

The trap here is the middle row. Switching on automatic gain control would have "fixed" the reading to −37.9 dBFS without touching the slider, but it does that by turning up the noise in every pause too, and Meet runs its own gain stage on top. If you lean on it, a fading cable can sound fine on the meter and terrible to your student. My call is to fix the slider and leave gain control off. Next, I press the headset's cable switch and run the check once more. The bars go completely flat, so this headset sends true silence when it's switched off, and I know a flat line during the lesson means the switch rather than a dead mic. If speech ever peaks above −6 dBFS, I'll pull the slider back to 50.

Check Microphone Settings in Your Operating System

The browser only hears what the system passes it, so a mic silenced there looks like a software mute.

Sound Settings, Input Volume and Default Device

• Windows 11: right-click the speaker icon in the taskbar, open Sound settings, choose your mic under Input and make it the default device. Speak and watch the blue bar. An input volume slider at 0 is a mute in all but name.
• macOS: open System Settings > Sound, select the mic and watch the input level meter while you talk.
• Linux: in PulseAudio or PipeWire's control panel, check the capture stream isn't toggled off.

Site Settings and Privacy Settings in Chrome, Firefox, Safari and Edge

Browsers keep their own per-site microphone choice:

• Chrome and Edge: click the icon left of the address bar, open Site settings and set Microphone to Allow.
• Firefox: click the permissions icon in the address bar and clear the blocked entry.
• Safari: open Settings > Websites > Microphone and allow this site.
• On Android and iOS, the browser app itself also needs microphone permission, and the page must stay in the foreground.

Where the Online Mic Test Runs: Browser Support

This online mic test works in any current browser that supports media device access, on desktops and phones, with no software to install. Nothing is uploaded, and a recording exists only in the page's memory until you download it.

That makes a browser microphone test the cleanest way to test microphone hardware apart from any one app. If you check mic online and see a live signal while your conference app still shows you silent, the problem sits in that app's settings. A microphone test tool outside your calling app tells the two apart.