Gear test

Keyboard test

Press every key and watch a real full-size, TKL or laptop layout light up. BenchRush shows event.key, event.code and keyCode for each press, how long it was held, how many keys are down at once, and flags possible chatter — one press that fires twice.

Live key map

0 / 0keys tested0held right now0possible chatter
Press any key to see its details.

Press keys anywhere on this page. Space and Arrow keys stay inside the test instead of scrolling.

Tab is captured as a test key. To move focus with the keyboard, press Esc then Tab.

How to test every key in two minutes

  1. Pick your layout — Full-size (with numpad), TKL (no numpad) or Laptop / 60%. The counter only tracks keys your keyboard actually has.
  2. Sweep row by row, left to right, including both Shift, Ctrl and Alt keys. Each key turns green once the browser receives it.
  3. Look for gaps: a key that stays dark is not reaching the browser. Press it a few times with different force before concluding it is dead.
  4. Watch the chatter counter: a red-outlined key fired again less than 25 ms after it was released — the classic sign of a worn or dirty switch that types double letters.

Reading the key details

event.keyThe character or action produced, which depends on your keyboard language (a German board types “z” where US types “y”).
event.codeThe physical key position, independent of language. This is what the map uses, so layouts like AZERTY or QWERTZ still light up the correct key.
keyCodeThe legacy numeric code many older scripts and games still use. Handy when you need a keycode for configuration files.
locationTells left from right modifiers and numpad from the main row.
heldHow long the key stayed down. Very short holds on keys you pressed firmly can point to a switch that releases too early.

Keys a browser cannot always see

The Fn key is handled inside the keyboard and never reaches the browser. Print Screen on Windows often only reports a release. The Windows / Command key, F11, F12 and some media keys can be captured by the operating system or browser first. A dark key in this group is not proof of a fault — test it in another app before replacing anything.

Use the result as a baseline, not a diagnosis

BenchRush measures browser-visible input. If a result looks wrong, repeat the run, check focus and settings, compare another browser/device where practical, and use manufacturer diagnostics for hardware conclusions.

Keyboard rollover → · View PlayerScore →

Interpret the result

A missing key needs a single-key check first

Separate focus, reserved shortcuts, repeat behavior, connection and a device-level fault before moving on to rollover combinations.

Read the guide →

Questions people ask

What does this keyboard test actually prove?

It proves that a key event reached this browser tab. It cannot inspect the physical switch, cable or keyboard firmware directly.

Can I test a laptop keyboard?

Yes. Any keyboard that sends normal browser key events can be checked, including built-in laptop keyboards and external USB or Bluetooth keyboards.

Why does a system key not appear?

Some operating-system, function-layer and media keys are intercepted before the browser can see them. Missing those keys here does not automatically mean the keyboard is faulty.

Privacy by default

Your personal bests, XP and streak are stored locally in this browser. The current tool does not require an account or upload your individual run to a global leaderboard.