Speaker & Audio Tester

The Complete Speaker & Audio Testing Guide

How the left/right channel test works, why frequency range testing matters, why browsers require a click before playing sound, and a full audio troubleshooting FAQ.

Open Tool

How the Left/Right Channel Test Works

This tool uses the Web Audio API's StereoPannerNode to route a generated tone precisely to one channel at a time. "Test Left Channel" plays a 440Hz sine wave panned fully to -1 (100% left), "Test Right Channel" pans it fully to +1 (100% right), and "Test Both Channels" leaves it centered at 0 so it plays evenly through both sides. Because the panning is explicit and digital, there's no ambiguity about which channel is actually producing sound - if you press "Test Left Channel" and hear it from your right speaker instead, your channels are swapped somewhere in your cabling or system audio settings.

This matters more than it might seem: normal stereo music and video mix both channels together constantly, so a single dead channel can go unnoticed for a long time if the content you're listening to happens to route most of its sound to the working side. Isolating each channel completely removes that ambiguity.

Why Frequency Range Testing Matters

100Hz - Low BassTests the low end most driven by a woofer or subwoofer. A weak or muddy 100Hz tone can point to a damaged bass driver or an overly aggressive bass-cut filter.
1kHz - Mid RangeThe reference midpoint of human hearing, where most speech and instrument fundamentals live. This is usually the most reliable-sounding tone on any working speaker.
10kHz - High TrebleTests the top end typically produced by a tweeter. A missing or harsh 10kHz tone often signals a blown tweeter or age-related hearing roll-off.
Comparing All ThreeA speaker in good working order should play all three tones clearly at a similar perceived loudness (adjusted for how human hearing naturally weighs frequencies) - a big gap between them is worth investigating.

Browser Autoplay Policy: Why Sound Needs a Click

Modern browsers enforce an autoplay policy that blocks any page from starting audio output before the user has interacted with it in some way. This exists so that no tab can suddenly start playing sound the moment it loads - a protection against intrusive ads and unwanted noise, not a bug or a limitation of this tool specifically.

In practice, a browser's AudioContext is created in a "suspended" state and can only be resumed from inside a genuine user-gesture event handler, such as a click listener. Every test on this page is built around that requirement: each button press both resumes the audio context (if needed) and starts the tone in the very same click handler, so the very first click on any test always works without a separate "enable audio" step.

Frequently Asked Questions

Why does this tool use a sine wave instead of music or noise for testing?

A sine wave contains just one single frequency with no harmonics or overtones layered on top, unlike music or white noise, which mix many frequencies together at once. That purity makes it easy to isolate exactly what a speaker does with one specific frequency - distortion, rattling, or a weak response is unambiguous on a plain tone in a way it wouldn't be on a busy musical mix.

What does panning actually do to an audio signal?

Panning controls how a signal's volume is split between the left and right output channels without changing the tone itself. A StereoPannerNode set fully to one side sends the full signal to that channel and silences the other, a center pan splits it evenly, and values in between blend the two - which is exactly how this tool isolates each channel for testing.

Why does 1kHz usually sound louder than 100Hz or 10kHz at the same volume?

Human hearing isn't equally sensitive across all frequencies - it's most sensitive in the low-to-mid kilohertz range, where speech naturally sits, and noticeably less sensitive at deep bass and very high treble frequencies. Two tones can carry identical electrical power and still sound like very different volumes to your ears simply because of that natural hearing curve, not because your speaker is doing anything wrong.

Why does the left/right test matter if I can already hear sound?

Hearing sound overall doesn't confirm both channels work independently — a cable fault, a bad connector, or a software setting can silently drop one channel while the other still plays, and stereo content can mask this by mixing both channels together. Isolating each side is the only reliable way to catch it.

Why test specific frequencies like 100Hz, 1kHz, and 10kHz?

These three points sample the low (bass), middle, and high (treble) ends of the audible range. A speaker that plays 1kHz clearly but sounds weak or absent at 100Hz or 10kHz may have a damaged driver, a blown tweeter, or a setting (like an EQ or a bass/treble filter) cutting that range.

Will this work with Bluetooth speakers and headphones?

Yes. As long as your operating system has already routed audio output to the Bluetooth device (the way it would for music or a video call), this tool's tones play through it exactly like any other sound — no special setup or pairing steps are needed here.

Open Tool