Gamepad Tester

Connect a controller and press something: every button and stick is drawn live, with the browser's own mapping.

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

What the browser reports

The Gamepad API exposes buttons, axes and a mapping string. A controller with a standard mapping reports the same button order as a console pad; one without a mapping reports whatever the driver sends, which is why some third-party pads look scrambled.

Sticks are drawn as dots inside a circle, and triggers usually appear as axes on the same list, so a trigger that never reaches full value shows up as a dot that cannot reach the edge.

    Why nothing appears at first

    Browsers hide controllers until a button is pressed, a privacy measure against fingerprinting. Press any button and the pad appears; the page then reads it every frame until the tab closes.

    Calibration drift — a stick that rests slightly off centre — is visible as a dot that will not sit in the middle. That is usually a dead zone setting in the game, not a broken stick.

      Multiple controllers

      The first connected pad is the one shown. Disconnecting it reveals the next, which is a quick way to check which of two pads has a sticking button.

        How Gamepad Tester works

        See every button press, both sticks and the axes of a connected controller, with the mapping the browser reports. The method behind Gamepad Tester is the single-purpose logic inside wave51.js, and this page shows the result with its assumptions in the open.

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

        A worked example for Gamepad Tester

        A typical run of Gamepad Tester starts with gamepad tester 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 Gamepad Tester with gamepad tester.

          When to use Gamepad Tester — and when not to

          Reasonable uses: Diagnosing a connection; Checking DNS or registration data; Testing hardware in the browser. Gamepad Tester 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 Gamepad Tester: for Gamepad Tester, results reflect your network and device.

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

          Reading the Gamepad Tester result

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

            Accuracy and limits of Gamepad Tester

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

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

            Privacy and speed on the Gamepad Tester page

            The Gamepad Tester 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: Gamepad Tester 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 Gamepad Tester

              The output of Gamepad Tester 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 Gamepad Tester 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 Gamepad Tester do?

                See every button press, both sticks and the axes of a connected controller, with the mapping the browser reports. Everything runs in your browser; nothing is uploaded.

                How accurate is Gamepad Tester?

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

                What are the limits of Gamepad Tester?

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

                Is anything uploaded when I use Gamepad Tester?

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

                Can I use Gamepad Tester offline?

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

                Device tests

                Keep going

                More web tools