Skip to content
CheckItWorks

Microphone & Speaker Test

Microphone

Off
Level over timeTarget −18 dBFS

Draws while the microphone is listening

Peak
Not measured yet
Average
Not measured yet
Clipped
Not measured yet
Quietest
Not measured yet

Speakers

Off

Volume level

Choosing a specific output device isn't supported in this browser — sound plays through your system default.

Step 1 of 2Play one side at a time — you'll be asked which side you actually heard.

Record & play back

Off

Records 5 seconds from your microphone, then plays it back through your speakers — the one step that uses both at once.

  • Microphone testedNot yet
  • Speaker channel playedNot yet

One instrument, two jobs: check that your microphone is actually picking up your voice at a healthy level, then confirm your speakers or headphones are producing sound from the correct side. Everything runs locally in your browser — your voice is analyzed on your own device and never uploaded anywhere.

How it works

  1. Turn Your Volume Down First. This test plays tones through your speakers — turn your system volume down before you start, especially on headphones.
  2. Allow Microphone Access. Click Allow microphone and grant permission when your browser asks; the stream is processed locally and never leaves your device.
  3. Speak Normally and Watch the Level. Talk at your normal volume and watch the meter — you're aiming for a level that sits comfortably in the middle, not pinned to the top.
  4. Test Left, Then Right. Play the left channel and note which side you actually heard it from, then do the same for right.
  5. Run the Frequency Sweep. Play the sweep to listen across the audible range for buzzing, rattling, or a dead spot at either end.
  6. Record and Play Yourself Back. Once both halves have a result, record a few seconds and play it back through your speakers to close the loop.

How to Test a Microphone in Your Browser

This test uses the Web Audio API to analyze your microphone's input directly in your browser — no download, no app, and no signup. Click Allow microphone, grant the permission prompt, and start talking; the level meter responds within a fraction of a second.

  • Nothing is uploaded, transmitted, or recorded to any server — the stream is analyzed locally and discarded when you leave the page.
  • If you have more than one microphone, a device picker lets you choose which one to test — device names only appear after you grant permission.
  • The meter keeps working as long as the tab stays open and visible; it releases the microphone automatically if you switch away.

Reading the Level Meter: dBFS, Peak, RMS, and Clipping

The meter reports level in dBFS (decibels relative to full scale), where 0 dBFS is the loudest a digital signal can go before it distorts. Everything on this meter is negative — the closer to 0, the louder.

  • Peak: the single loudest sample in the last moment — spikes on plosives (p, b) and sudden sounds.
  • Average (RMS): a smoothed sense of your typical speaking level — the number that matters most for "is my mic loud enough".
  • Target range: roughly -24 to -9 dBFS while speaking normally is a healthy range for most calling and recording apps.
  • Clipping: when a signal is pushed past 0 dBFS, the peaks get chopped flat — this is permanent, audible distortion, not just "loud". Louder is not better once you're clipping.

Why Your Microphone Sounds Quiet, Muffled, or Distorted

A mic that tests as "working" can still sound bad for reasons that have nothing to do with the hardware being broken.

  • Gain staging: your OS or app's input gain (sometimes called "microphone boost") set too low or too high is the single most common cause of a quiet or distorted mic.
  • Distance and off-axis positioning: most laptop and headset mics are directional — speaking too far away, or to the side of the mic rather than into it, thins out the sound.
  • Plosives: a "p" or "b" sound aimed straight at the mic causes a burst of low-frequency wind noise; angling the mic slightly off-axis fixes this without a pop filter.
  • Laptop array mics vs. headset mics: built-in laptop microphones apply aggressive noise suppression that can make a voice sound processed or muffled — a headset or USB mic is closer to the source and needs less processing.
  • Connection type: USB mics carry a clean digital signal; 3.5mm TRRS jacks are more prone to interference and a loose connection; Bluetooth mics drop audio quality sharply the moment the microphone is active (see below).

Speaker and Headphone Faults This Test Finds

  • Dead channel: nothing plays from one side at all.
  • Swapped left/right: audio panned left plays from the right speaker, or vice versa — surprisingly common with a mislabeled cable or dock.
  • Mono downmix: a system-level setting is combining both channels into one, so "left" and "right" sound identical from both sides.
  • Buzzing or rattling on the low end of the sweep: often a loose speaker mount, a blown driver, or something physically vibrating against the enclosure.
  • A dead spot at the high end of the sweep: age-related driver wear, or simply the top of your hearing range — this is normal above roughly 15-17kHz for most adults.
  • Intermittent cutting out: usually a loose jack or a failing Bluetooth connection, not the speaker itself.

Bluetooth Headsets: Why Using the Mic Ruins the Sound

If music sounds noticeably worse the instant you join a call or start this microphone test, that's not a fault — it's how Bluetooth audio profiles work.

A Bluetooth headset streams music using A2DP, a high-bandwidth profile built for audio quality alone. The moment its microphone is needed, most headsets switch to HFP or HSP, a much lower-bandwidth profile built to carry a phone call both ways at once. Sound quality on both sides drops sharply the instant the mic turns on — that trade-off is built into the Bluetooth standard, not a defect in your headset.

  • Use a wired connection instead when audio quality matters and you also need the microphone.
  • Some newer earbuds support Bluetooth LE Audio, which can carry better-quality two-way audio — check whether your headset and device both support it.
  • If you only need to listen (no mic), the headset stays on the high-quality A2DP profile the whole time.

Fixing It: Per-OS and Per-Browser Steps

Windows

Settings → System → Sound → Input, check the input volume and "microphone boost" level, and confirm no other app has exclusive control of the device (Settings → Sound → More sound settings → Recording → device Properties → Advanced, uncheck "Allow applications to take exclusive control"). "Listen to this device" under the same Properties dialog lets you hear your own mic live, useful for isolating whether an issue is the mic or your headphones.

macOS

System Settings → Sound → Input, select the correct device and check the input level responds when you speak. If a specific app has no sound, check System Settings → Privacy & Security → Microphone and confirm your browser is allowed.

Android and iOS

Check your browser has microphone permission in the system app-permissions settings, and check no other app is holding the microphone in the background.

"Another app is using your microphone"

Extremely common with Teams, Discord, Zoom, or any app that keeps a background process running after you close its window — check your system tray or open-app list and fully quit it, not just close the window.

Resetting a site's permission

If you accidentally denied microphone access, click the padlock or site-info icon in your address bar, find Microphone in the permissions list, and change it to Allow, then reload the page.

Safe Listening: Why This Test Starts Quiet

Your ear isn't equally sensitive across the audible range — it's most sensitive between roughly 2 and 5kHz. A tone or sweep played at a constant volume level doesn't sound like constant loudness; that band sounds noticeably louder than the low and high ends of the sweep. This page compensates for that automatically, but the safest thing you can do is turn your system volume down before starting, especially on headphones.

A commonly cited safe-listening guideline is roughly 85 decibels averaged over 8 hours before hearing risk becomes a real concern — the level control on this page defaults to a conservative setting well under that for exactly this reason.

Frequently asked questions

Is my voice uploaded anywhere?

No. Your microphone stream is analyzed entirely in your browser using the Web Audio API. Nothing is sent to any server, and the short recording used for the playback loop is discarded when you leave the page.

Why does the browser ask for permission?

Browsers require an explicit permission prompt before any website can access a microphone or camera, as a privacy and security protection. You can revoke that permission at any time from your browser's site settings.

Why does my microphone work here but not in Zoom or Teams?

Most often another app already has exclusive access to the device, or that specific app doesn't have OS-level microphone permission even though your browser does. Fully quit other calling apps and check each app's own microphone permission separately.

Why does my Bluetooth headset sound bad when the microphone is on?

Bluetooth switches from the high-quality A2DP audio profile to a lower-bandwidth call profile (HFP/HSP) the moment a microphone is needed — that trade-off is part of the Bluetooth standard, not a fault in your headset. A wired connection avoids it entirely.

How do I test left and right speakers separately?

Use the Play left and Play right buttons, and after each one, answer which side you actually heard the tone from. Comparing what was played against what you heard is what produces the stereo-ok, swapped, or dead-channel result.

What is clipping and how do I fix it?

Clipping is what happens when a signal is pushed past 0 dBFS — the loudest peaks get chopped flat, which is permanent, audible distortion. Lower your microphone's input gain (often called "mic boost") until peaks stay comfortably under 0 dBFS.

Can I hear myself live while testing?

This test doesn't offer that on purpose — routing your live microphone straight to your speakers risks a feedback loop (a loud screeching sound) the moment volume is turned up, which is uncomfortable and can stress your speakers or your ears. Use the record-and-play-back option instead; it's a safe way to hear how your mic actually sounds.

Why can't I pick my output device in Safari or Firefox?

Choosing a specific speaker or headphone output from a webpage (the setSinkId API) isn't supported in Safari or Firefox today — only Chrome and Edge support it. In unsupported browsers, sound always plays through your system's current default output.

How loud is too loud?

A commonly cited guideline is roughly 85 decibels averaged over 8 hours of exposure before hearing risk becomes a real concern. This test's default volume level is deliberately conservative and well under that, and the level control lets you go quieter still.

Why can't I hear the very low or very high end of the sweep?

That can be completely normal. Human hearing typically tops out well below 20kHz, more so with age, and small speakers often can't reproduce the lowest frequencies at all — check with headphones if you want to isolate whether it's your ears or your speakers.

Your microphone stream is analyzed only in memory, in your own browser; any short recording used for the playback loop is decoded in memory and discarded when you leave this page. Nothing is uploaded, stored, or logged anywhere.