Test Your Audio Devices Instantly

Before you start

The audio tools run entirely in your browser. For the most reliable readings:

• Close calls, recording apps, and music players that may be holding the microphone or speakers.
• Plug headphones in directly when possible. Bluetooth introduces extra latency and noise that can confuse a quick test.
• Set system and browser volume to a comfortable mid-range — not muted, not at maximum.

If your browser asks for microphone permission, allow it just for this tab. You can revoke the permission at any time from your browser's site settings. For step-by-step help, see our microphone permissions guide.

Microphone test

Open the microphone tool, allow access, and speak normally. Two things should happen: the waveform should react to your voice, and the level meter should rise into the green range without flattening at 0 dB. Flat or absent activity usually points to the wrong input being selected at the operating-system level, an exclusive lock by another app, or a broken cable.

If you see input but it sounds wrong on calls, the issue is more often noise suppression or sample-rate mismatches than the device itself. Our microphone troubleshooting guide walks through the most common fixes by browser and OS.

Speaker and headphone test

Use the channel buttons to confirm left and right are wired correctly, then run the frequency sweep to spot dips, rattles, or one driver cutting out. A healthy pair of headphones reproduces the sweep smoothly from low rumble to bright treble; speakers in a normal room will roll off at the extremes — that is expected.

For deeper background, including why a wired connection produces a more reliable test than Bluetooth, the audio chain is described in audio latency explained.

Record & playback

Recording yourself for a few seconds and playing it back is the fastest end-to-end check. If the recording sounds quiet, dull, or echoey, the chain — not the individual tools — is the problem. Try moving closer to the microphone, switching off any "enhancements" in your OS sound settings, and re-running the test.

Latency test

Latency is the gap between sound entering one part of the chain and leaving another. Browser-reported latency under about 20 ms feels effectively instant; values above 50 ms start to be noticeable on video calls and become a problem for live monitoring. The number you see is the floor — the operating system, drivers, and any wireless link add more on top.

For why latency matters in calls, gaming, and recording, read audio latency explained.

Sound level meter

The dB meter is a relative measure of how loud your environment is at the microphone. It is great for comparing two rooms or noticing a noisy fan; it is not a calibrated SPL meter. As a rough reference, a quiet bedroom typically reads in the 30s, normal conversation around 60, and a vacuum cleaner near 70. Anything sustained above the high 80s is worth taking seriously for hearing health.

Reference levels and safe-listening guidance live on the decibel levels guide.

Hearing range test

Use headphones at a moderate volume. Start with the lower frequencies, where everyone should hear something, then climb. Most adults stop hearing somewhere between 14 kHz and 17 kHz — that is normal age-related change, not damage. Children and teens often reach the full 20 kHz cap of the test.

The test is a screen, not a diagnosis. To understand what the result does and does not tell you, see how to read your hearing range result.