Keyboard Test

A visual key map that lights up as you type, so a dead key or a stuck modifier is obvious in seconds.

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

What a key test can prove

A key that never lights up is not reaching the browser: either the switch is dead, the keyboard is in a mode where that key is remapped, or the operating system is intercepting it. Seeing which keys report and which do not narrows that down quickly.

The page listens to keydown and reads the physical code, not the character, so it works the same on an AZERTY layout and a QWERTY one — KeyQ is the same physical key on both.

    Ghosting and rollover

    Press several keys at once: cheap keyboards stop reporting after a few, a limitation of the matrix wiring rather than the browser. A keyboard that drops the fourth key is a keyboard that will drop it in a game too.

    Modifiers are shown separately so you can tell a stuck Shift from a broken letter. Nothing is logged and no keystroke leaves the page.

      N-key rollover in practice

      Gaming keyboards advertise full rollover; office keyboards rarely have it. Holding several letters at once shows which one gives up first, which is the number that matters in a game.

        How Keyboard Test works

        Press keys and see them light up on a full layout, with the key code and location. Find a key that is not registering. The method behind Keyboard Test is the single-purpose logic inside wave51.js, and this page shows the result with its assumptions in the open.

        • Open Keyboard Test and provide keyboard test — the page accepts it in the field it shows.
        • For Keyboard Test, browser APIs and, where stated, one public endpoint do the work.
        • The Keyboard 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 Keyboard Test

        A typical run of Keyboard Test starts with keyboard 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 Keyboard Test with keyboard test.

          When to use Keyboard Test — and when not to

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

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

          Reading the Keyboard Test result

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

            Accuracy and limits of Keyboard Test

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

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

            Privacy and speed on the Keyboard Test page

            The Keyboard 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: Keyboard 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 Keyboard Test

              The output of Keyboard 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 Keyboard 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 Keyboard Test do?

                Press keys and see them light up on a full layout, with the key code and location. Find a key that is not registering. Everything runs in your browser; nothing is uploaded.

                How accurate is Keyboard Test?

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

                What are the limits of Keyboard Test?

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

                Is anything uploaded when I use Keyboard Test?

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

                Can I use Keyboard Test offline?

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

                Device tests

                Keep going

                More web tools