Guides › Hardware tests

Some key combinations don't register? Testing keyboard ghosting and rollover

You hold W and Shift to sprint, press Space to jump, and nothing happens. Or you type quickly and a letter goes missing. Before you blame the game or yourself, check whether the keyboard can actually report that combination of keys. This guide explains the two limits involved, ghosting and rollover, and shows how to test them with our keyboard tester.

Short answer: the browser is not the bottleneck. In our test, Chromium delivered all 26 keys we held down at the same time. If a combination fails, the keyboard is dropping it. Hold the combination in the tester and see which keys light up; the "max held" counter tells you your keyboard's real limit for that combination.

What we measured

We opened our keyboard tester in Chromium 153 and used browser automation to press and hold 26 keys one after another without releasing any: 20 letters, four digits, left Shift and Space. The tester showed 26 keys held and a maximum of 26. When we released them, the count returned to 0 and all 26 keys were marked as tested.

Automation injects key presses into the browser directly, skipping the physical keyboard. That is exactly the point of the test: it shows that the browser and the page pass on every key they receive. Any limit you see with a real keyboard happens before the browser, inside the keyboard or its connection.

Ghosting: when the keyboard invents or hides a key

Inside most keyboards the keys sit on a grid of wires, rows and columns, and the keyboard's controller finds a pressed key by checking where a row and column are connected. Cheap designs have no diode at each key. When three keys forming three corners of a rectangle on the grid are pressed, current can flow round the rectangle and make the fourth corner look pressed too. That phantom key is a "ghost".

To avoid sending phantom keys, controllers on these keyboards simply refuse to report the combination, so the third or fourth key appears dead. Which combinations fail depends entirely on how that keyboard's grid is wired, which is why the same game works on one keyboard and not another. Manufacturers usually wire the common gaming cluster (W, A, S, D with Shift, Ctrl and Space) to avoid conflicts, and the failures show up elsewhere.

Counting the pattern on one real keyboard's wiring

To see how often the rectangle pattern can arise, we took the wiring grid of the 101-key IBM Model M, a buckling-spring keyboard whose key contacts sit on a membrane sheet, as it is defined in the open-source QMK firmware project (linked in the references at the end of this page). The Model M's 101 keys sit on a grid of 8 rows and 16 columns, and its membrane has no diode at each key. We checked every possible set of three keys, 166,650 in all, for the three-corners pattern described above.

Sets of three keysCountShare
All possible sets166,650100%
Three corners of a rectangle on the grid7,0144.21%
…where the fourth corner is another key5,9203.55%
…where the fourth corner is an unused position1,0940.66%

Only the 5,920 sets in the third row can be mistaken for a fourth key. In the last row there is no key at the fourth corner, so the three keys can still be read correctly, although some firmware blocks these sets anyway.

This is a count of the sets that form the pattern on this wiring, not a test of a keyboard on a desk: what a particular controller does with such a set (drop the last key, or report a key you did not press) depends on its firmware. Other keyboards are wired differently, so your failing combinations will be different ones; the proportions give a sense of scale.

Both files are .csv and open in any spreadsheet; each starts with a header row. The key positions come from the QMK Firmware project (GPL-2.0).

Rollover: how many keys can be reported at once

"Key rollover" is the number of simultaneously held keys a keyboard can report correctly. The terms you will see:

TermMeaning
2KROOnly two keys are guaranteed; a third may be dropped. Common on basic membrane keyboards.
6KROSix ordinary keys plus the modifier keys (Ctrl, Shift, Alt, Windows/Command). This is the limit of the standard USB "boot keyboard" report, which has six slots for keys plus a set of bits for modifiers.
NKRO (n-key rollover)Every key can be held at once. Requires a diode per key and a report format larger than the boot report.

Most people never need more than 6KRO. Where NKRO matters is rhythm games, stenography and some fast-paced games, or two people sharing one keyboard.

A five-minute test routine

  1. Open the keyboard tester and press every key once. Keys that never light up are faulty or blocked by the operating system (see below).
  2. Hold the exact combination that fails for you in practice, for example W + A + Shift + Space. Watch which keys light up together and read the "held" counter.
  3. For the rollover limit, hold letters one by one without releasing: A, S, D, F, then J, K, L. When the counter stops rising, you have reached the keyboard's limit for that group.
  4. Repeat with keys from the other side of the keyboard. Ghosting is combination-specific, so a pass in one area says nothing about another.
  5. Press and release a suspect key 20 times slowly. If it sometimes fails, or registers twice, the switch is worn or dirty rather than a ghosting problem.

Keys a web page cannot see

KeyWhy it may not show up
FnHandled inside the keyboard to change what other keys send; it never reaches the computer as a key.
Print ScreenOn Windows the system takes it for screenshots, and browsers often receive only the key release.
Windows / Command key combinationsMany are captured by the operating system before the browser, for example Win + D.
Ctrl + W, Ctrl + T, Ctrl + NReserved by browsers for closing and opening tabs and windows, so pages cannot intercept them.
Media keys, brightness keysUsually handled by the operating system or keyboard software.

So a key that is dead in our tester is not necessarily broken. Check it in a plain text editor before concluding the hardware is at fault.

If a key fails

Common questions

Does a USB or Bluetooth connection limit rollover?

The standard boot report used by many keyboards caps at six ordinary keys plus modifiers. NKRO keyboards use a different report format. Bluetooth keyboards vary by model.

Why does the tester show a key I'm not pressing?

Either the keyboard is ghosting, or a key is stuck. Release everything; if the key stays lit, it is physically stuck or the switch is shorted.

Does the tester record what I type?

No. It runs entirely in your browser and only highlights keys on the on-screen layout; it does not record or transmit what you type. Ads and visit statistics on this page are described in our privacy policy.

References

  1. USB-IF: Device Class Definition for HID 1.11 (boot keyboard report, Appendix B)
  2. W3C: UI Events KeyboardEvent code Values
  3. MDN: KeyboardEvent.code
  4. MDN: KeyboardEvent.repeat
  5. QMK Firmware: IBM Model M 101/102 matrix definition (keyboard.json)

Written and checked by Ria Kim for GlowHalo; figures without a source link come from the steps shown on this page. Companion tool: Keyboard Tester. Spotted an error? Write to help@glowhalo.org. Windows, Chromium and Bluetooth are trademarks of their owners; GlowHalo is not affiliated with them.

More guides

Hardware testsWhy a website says your 1080p screen is 1536 pixels wide: resolution, viewport and pixel ratioWe ran our screen resolution tool under seven emulated device profiles. Why a phone with 1179 physical pixels reports 393, and which number matters for what.Read guide →Hardware testsHow much of your reaction time score is actually your screen?A bot that reacts instantly still scored 0 to 17 ms on a 60 Hz display in our test. What that means for your result, and how to compare scores fairly.Read guide →