I Built a Free Keyboard Tester in the Browser — Here's Exactly How It Works (and How to Use It)

Attiq Rahman — Sun, 04 Oct 2026 18:39:44 +0000

Disclosure: I built and run Key & Pixel, a free browser-tools site, and the keyboard tester discussed here is my own tool. Everything below is verified against the live tool — no invented benchmarks, no borrowed screenshots.

A switch that starts double-registering — one keypress, two letters — is one of the most common ways a keyboard starts dying, and it gets blamed on everything else first: the PC, the game, the connection. I didn't want to install a driver-level diagnostic for a five-second check, so I built a keyboard tester that runs entirely in the browser. This post is both a step-by-step guide to testing your own keyboard online and a breakdown of how the thing actually works, because the browser's keyboard events are weirder than they look.

Step 1: Test every key, systematically

Open the tester, click anywhere on the page so it has focus, and press keys row by row. Each key lights up while held and stays shaded after release, so you always know which keys you've covered. The counter (n / total keys tested) tells you when you're done.

First, make the on-screen drawing match your physical board — otherwise you'll "fail" keys that don't exist:

Size: Full (104/105), TKL, 75%, 65%, 60%, or Laptop (half-height function row, hatched Fn key)
Standard: ANSI (wide one-row Enter) vs ISO (UK, tall Enter)
Platform: Windows or Mac modifier placement

Step 2: Check for the three failure modes that actually matter

Most keyboard problems aren't dead keys. They're:

Chatter — one press, two events. The tester counts these as "chatter events." Anything above zero on a key you pressed deliberately means the switch is degrading.
Stuck keys — a key held longer than 3 seconds without you holding it gets flagged. That's a physically stuck switch or a driver issue.
Rollover limits — hold a handful of keys at once. The tester tracks "max held." Cheap membranes often cap at 2–6 simultaneous keys; if your game needs WASD + Shift + Space and your board drops one, this is how you find out.

Step 3: Measure auto-repeat and typing accuracy

Hold any letter key and the tester measures your system's repeat delay and rate — useful if typing feels sluggish and you suspect an OS setting rather than hardware. There's also a "type check" sentence that catches missed and doubled letters in real typing, matched by physical key position (event.code), so it works on any language layout — AZERTY and QWERTY produce the same codes.

How it works under the hood

The whole tool is built on keydown/keyup events, but three event properties do the real work:

window.addEventListener('keydown', (e) => {
  console.log({
    code: e.code,       // 'KeyA', 'ShiftLeft', 'Numpad7' — physical position
    keyCode: e.keyCode, // 65, 13 — legacy, deprecated, still everywhere
    location: e.location, // 1 = left, 2 = right, 3 = numpad
  });
});

code is position-based, which is why layout-independent matching works.
keyCode is deprecated but older games and software still read it, so the tester reports it.
location is the only way to tell left Shift from right Shift.

The tester also suppresses the browser's default reaction to Tab, Space, Backspace and the function keys (preventDefault()), so pressing them tests the key instead of scrolling the page.

The platform quirks that took the most time

Three real-world behaviours needed explicit handling:

Windows AltGr sends an invisible Left Ctrl event with the same timestamp. The tester spots the pairing and ignores the phantom, so Left Ctrl only counts when you actually press it.
macOS Caps Lock fires one event when it switches on and another when it switches off. Without correction it looks like a key held for minutes.
macOS + UK (ISO) keyboards report the § and ` keys (beside left Shift) with each other's codes in most browsers. The Mac ISO drawing accounts for it and self-corrects if a browser reports them the other way.

What a browser-based tester can't do — be honest with yourself

A web page only sees the keys the OS and browser pass along. So the Fn key, Touch ID, media keys, the power key, and browser-reserved shortcuts (Ctrl+W, Ctrl+T, Cmd+Q) will never register, even on a perfect keyboard. Fn is drawn hatched and excluded from the count. Print Screen on Windows only fires on release. If you need to test those, you need a driver-level tool, not a website.

It's also not a benchmarking lab: it reports what your browser observed, at browser timing precision. For 99% of "is this key dying?" questions, that's exactly enough.

Try it

The tester is free, needs no signup, stores nothing, and runs at keyandpixel.com/keyboard-tester. Press every key once, hold a handful together, and check the chatter counter — if it stays at zero, your board is fine and you can go back to blaming your aim.

If you find an edge case it misses, there's a "Tell us" link on the page. It goes straight to me.

DEV Community: Attiq Rahman