About Audio Testing
Audio problems span both hardware and human perception in a way few other categories do - a microphone that isn't being picked up is a device issue, but not being able to hear a high frequency clearly is sometimes just normal, healthy hearing behaving exactly as expected. This category covers both sides honestly: real device checks using your browser's actual audio input and output APIs, and genuine perception-based tests that measure what you can hear rather than pretending a browser can certify your hearing medically.
Why Audio Issues Are Easy to Miss Until It Matters
A muted microphone, a dead speaker channel, or unusually high audio latency often go unnoticed during casual use, because your brain fills in gaps and adapts to small inconsistencies without you realizing it. The moment stakes rise - a job interview over video call, a livestream going out to an audience, a recording session that can't be redone - these same issues become genuinely costly. Testing beforehand, rather than discovering a problem live, is the entire reason this category exists.
What Each Tool in This Category Actually Checks
The Microphone Tester gives you a live spectrum view of your actual mic input so you can confirm it's picking up sound and see roughly how it responds across frequencies, while the Speaker Tester and Headphone Tester isolate left and right channels individually to catch a dead or weak channel that stereo content alone can mask. The Audio Device Detector lists every microphone and speaker your browser can actually see, useful when you're not sure which device is currently active. For more technical checks, the Audio Latency Test reports real system-reported output latency alongside a genuine click-to-hear round-trip measurement, and the Frequency Generator plays an exact, mathematically generated tone anywhere from 20Hz to 20kHz for testing speaker range or simply hearing what a specific frequency sounds like. The Hearing Range Test and Sound Level Meter turn attention back to you and your room - mapping which frequencies you can actually hear, and giving a live relative sense of input loudness from your microphone.
Common Situations Where This Category Helps
Streamers and remote workers lean on the microphone, speaker, and latency tools before any call or broadcast, catching a muted input or unusually high delay before it becomes visible to an audience. Anyone buying secondhand headphones or speakers can quickly confirm both channels genuinely work rather than trusting a seller's description. Musicians and audio engineers use the frequency generator to test speaker range and cabinet response at specific frequencies, while anyone simply curious about age-related hearing change can run the hearing range test out of genuine curiosity rather than any diagnostic necessity.
Interpreting What You Find
A microphone that shows no input activity at all, even when you speak directly into it, usually points to either an OS-level mute, an incorrect default device selection, or a genuine hardware fault - check the simpler causes first before assuming the worst. A dead speaker channel confirmed by the channel-isolation test is a real, provable finding worth acting on immediately, especially if you're within a return or warranty window. Not being able to hear very high frequencies on the hearing range test, especially above roughly 15–17kHz, is extremely common and expected with age - it's not something the frequency generator or your speakers are doing wrong.
Getting the Most Reliable Results
Test in a quiet room whenever possible, since background noise can affect both microphone level readings and how clearly you can judge speaker output. For the hearing range test specifically, use headphones rather than external speakers, since room acoustics and speaker frequency response can otherwise mask frequencies your ears would actually pick up. When testing latency, close other applications that might be using audio simultaneously, since competing audio processes can add extra, misleading delay that has nothing to do with your actual hardware's real latency.
Building a Simple Pre-Session Routine
For anyone who regularly streams, records, or takes video calls, running two or three of these tools into a quick habit - a mic check, a speaker channel check, maybe a latency check if you're doing anything timing-sensitive - takes under a minute and catches the specific failures that are otherwise embarrassing to discover live. Since none of these tools require installation or an account, there's no real friction to making this a standard part of setting up before something important, the same way you'd glance in a mirror before walking out the door.