Microphone & Speaker Test

Press Start Recording, say a few words, then play the recording back — hearing yourself confirms both your mic and your speakers or headphones work. For more control (live monitoring, a device picker, a dedicated speaker test), switch to the Advanced Test tab.

Yes, it's safe here specifically: this runs entirely in your browser using your device's own microphone permission (the same one every site has to ask for), and nothing is ever uploaded, recorded to a server, or stored. You can revoke microphone access for this site anytime in your browser settings.

Switch to Advanced Test and use "Listen Live" — it routes your microphone straight to your speakers or headphones as you speak, instead of recording first. Use headphones while doing this; without them, the mic can pick up its own output and cause a feedback screech.

In Advanced Test, use the Left/Both/Right buttons above the tone presets — each plays sound through only that channel, so you can immediately tell if one side is silent or if left and right are swapped.

That's a Windows and Chrome quirk, not extra microphones — Windows assigns "Default Device" and "Default Communications Device" roles to whichever physical mic is currently set for general use vs. calling apps, and Chrome shows a separate entry for each role. Your actual physical microphone count is usually much smaller than the list makes it look.

No — this tests stereo Left/Right only. A browser can address the left and right channels directly, but has no way to target a specific surround-sound channel (center, rear) on a home-theater or 5.1/7.1 system.

Run through this tool a couple of minutes beforehand — record and play back your voice to confirm both directions work, then check Advanced Test's device picker to make sure the mic your call app will actually use is the one you tested.

Yes — it uses standard browser microphone and audio APIs supported by mobile Chrome and Safari, so recording, playback, and the speaker test all work on a phone the same way they do on desktop.

Not selectively — mobile browsers don't expose a way to choose between a phone's earpiece speaker and its main loudspeaker from a web page, so the test tone plays through whichever one your phone's OS currently routes browser audio to.

An audio-engineering guideline for placing multiple microphones near each other: keep each mic at least 3 times farther from any other mic than it is from its own sound source, to avoid phase cancellation. It's unrelated to what this tool checks — it's about mic placement, not whether a mic works.

A common guideline to avoid pushing speaker or headphone volume above about 80-85% of maximum, since many speakers distort or run hotter near full volume. It's general advice, not something this tool measures or enforces.

Start by testing it here: if it never registers any sound at all (no waveform, no level movement) even after granting permission, that points to a hardware or driver problem. If it works here but not in another app, the issue is more likely that app's own input device selection or your OS's permission settings for it, not the microphone itself.

Play a test tone here first: if you hear it, the speaker itself works and the problem is specific to whatever app or setting wasn't sending it audio. If you hear nothing even at a high volume preset, check your OS's output device selection and physical volume/mute controls before assuming the speaker itself has failed.

Sustained high volume, physical impact, and moisture are the most common causes of driver damage. Some damage (a torn surround, a loose connection) can be professionally repaired; a genuinely blown driver usually can't be. This tool can only tell you a speaker isn't producing sound, not diagnose the specific physical cause.

A browser-based tool like this one needs no install and works on any device — good for a quick check. Your OS's own built-in sound settings (Windows Sound Control Panel, macOS Sound preferences) are worth checking too, since they can show hardware-level status this tool can't see. A dedicated recording app makes more sense if you need serious audio-quality analysis, not just a working/not-working check.

The sweep plays a continuous tone rising from 20Hz to 20kHz — the full range of human hearing — over about 8 seconds, so you can hear whether your speakers or headphones reproduce both the deep bass and high treble ends, or go quiet partway through. The Bass preset (100Hz) is a quicker, one-click version of the low end specifically.

Those apps typically play a low-frequency tone (commonly around 165Hz) to vibrate water out of a speaker grille — our tone generator can play a similar low frequency, but this tool isn't built or verified specifically for that purpose, so treat it as incidental rather than a guaranteed fix.

No — tones play live through the Web Audio API and aren't saved as a file. If you need a portable test-tone file, that's a different kind of tool than this one.

Yes — in Advanced Test, once you grant microphone access you'll see the device name, sample rate, whether it's mono or stereo, and whether echo cancellation, noise suppression, and automatic gain control are active for that device.

Yes — Advanced Test shows a device picker whenever more than one microphone is detected, so you can pick the exact one you want to test instead of whatever your browser defaults to.