Speaker Test

Left, right, single tones and a full sweep — the quickest way to hear a swapped channel or a buzzing driver.

Checked in a browser on 2026-11-19 · how these tools are tested · runs on your device

Channels and frequencies

A left tone that sounds like it comes from the right means the channels are swapped somewhere: the cable, the adapter, or a balance setting. The page pans the tone hard to one side to make that obvious.

Single tones at 500 Hz, 1 kHz and 4 kHz cover the range where small speakers are strongest and weakest. A sweep from 120 Hz to 12 kHz is the quickest way to hear a rattle, a buzz or a cone that has given up.

    Volume and safety

    The tone is generated at a fixed level well below full scale, but headphones still make it loud. Take them off before running the sweep, and turn the system volume down first.

    Nothing is recorded and the audio stream never leaves the tab: the oscillator exists for the length of the tone and is then discarded.

      Stereo, mono and the middle

      A tone played to the centre should sound like it comes from directly in front of you. If it leans to one side, the balance setting or the seating is off, and the channel test confirms which.

        How Speaker Test works

        Play a tone on the left, the right or both, check individual frequencies, and run a sweep to hear rattles or a dead cone. The method behind Speaker Test is the single-purpose logic inside wave51.js, and this page shows the result with its assumptions in the open.

        • Open Speaker Test and provide speaker test — the page accepts it in the field it shows.
        • For Speaker Test, browser APIs and, where stated, one public endpoint do the work.
        • The Speaker Test output appears on the page and can be copied or downloaded in the format it offers; nothing is kept afterwards.

        A worked example for Speaker Test

        A typical run of Speaker Test starts with speaker test and ends with the result shown above; the page reports what it did in plain words so the output can be checked against a known-good case before it matters.

        Repeat the check on a second network: a result that changes with the network is a routing fact, not a fault in your device. That check applies directly to Speaker Test with speaker test.

          When to use Speaker Test — and when not to

          Reasonable uses: Diagnosing a connection; Checking DNS or registration data; Testing hardware in the browser. Speaker Test is deliberately narrow: it does one job and states its assumptions instead of hiding them.

          Diagnostic apps and terminal tools go deeper but need installs or shell access. For a quick lookup or a device test, a page is the lower-friction path. The honest ceiling for Speaker Test: for Speaker Test, results reflect your network and device.

          • Best case for Speaker Test: Diagnosing a connection
          • Also fine with Speaker Test: Checking DNS or registration data
          • Not what Speaker Test is for: for Speaker Test, results reflect your network and device.

          Reading the Speaker Test result

          The output of Speaker Test is a function of the inputs alone — no hidden state and no server.

            Accuracy and limits of Speaker Test

            The method is the single-purpose logic inside wave51.js. Speaker Test prints results at the precision its inputs justify, and the limits below are the honest ones:

            • Speaker Test: For Speaker Test, results reflect your network and device.
            • For Speaker Test, pages that call an endpoint say so and call it only on your click.

            Privacy and speed on the Speaker Test page

            The Speaker Test page is a static file plus wave51.js; there is no upload endpoint behind it, so your input cannot be stored or logged. Closing the tab discards the work.

            Speed follows the build: Speaker Test loads one stylesheet and one script, with no framework, no web font and no tracker. That is why the tool responds as you type instead of waiting on a round trip.

              What you get from Speaker Test

              The output of Speaker Test appears on this page and can be copied or downloaded in the format the page offers. Nothing is queued, nothing is emailed, and there is no usage counter — the web work finishes the moment the numbers are in.

              Because Speaker Test is built from wave51.js rather than a server call, the practical ceiling is your device: memory for large inputs, and CPU for anything that loops over pixels or pages. On a normal laptop that ceiling sits far above everyday use; on an old phone it arrives sooner, and the page tells you when a job is too big instead of failing silently.

                Questions

                What does Speaker Test do?

                Play a tone on the left, the right or both, check individual frequencies, and run a sweep to hear rattles or a dead cone. Everything runs in your browser; nothing is uploaded.

                How accurate is Speaker Test?

                The method is the single-purpose logic inside wave51.js. For Speaker Test, results reflect your network and device.

                What are the limits of Speaker Test?

                For Speaker Test, pages that call an endpoint say so and call it only on your click.

                Is anything uploaded when I use Speaker Test?

                No. Speaker Test runs entirely in the browser tab; nothing is uploaded, stored or logged.

                Can I use Speaker Test offline?

                Yes — Speaker Test keeps working offline once the page has loaded; the whole tool is a local script.

                Device tests

                Keep going

                More web tools