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 keys | Count | Share |
|---|---|---|
| All possible sets | 166,650 | 100% |
| Three corners of a rectangle on the grid | 7,014 | 4.21% |
| …where the fourth corner is another key | 5,920 | 3.55% |
| …where the fourth corner is an unused position | 1,094 | 0.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.
- Most combinations are fine, but letters fare worse. Across the whole keyboard about 1 set in 28 can be mistaken for a fourth key. Among sets of three letters it is about 1 in 9 (287 of 2,600).
- On this wiring the movement keys are not an exception. Q, W and E are on one row of the grid and A, S and D on another, with Q and A, W and S, and E and D sharing columns. So W + A + S points at Q, and W + S + D points at E. W + A + D and A + S + D do not form the pattern. This keyboard was not wired around the gaming cluster in the way the previous section describes.
- Shift, Ctrl and Space with the movement keys are clear. No set of three keys taken from W, A, S, D, Left Shift, Left Ctrl and Space that includes one of those three forms a rectangle on this grid.
- The arrow keys are affected too. Left + Right + Up points at the 0 key of the number pad. Up + Down + Left also forms the pattern, but its fourth corner is an unused position, so no extra key can appear.
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).
- The wiring grid: one row per key with its grid row and column, 101 keys.
- All 7,014 sets of three keys that form the pattern: the three keys and the key at the fourth corner (blank where that position is unused).
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:
| Term | Meaning |
|---|---|
| 2KRO | Only two keys are guaranteed; a third may be dropped. Common on basic membrane keyboards. |
| 6KRO | Six 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
- Open the keyboard tester and press every key once. Keys that never light up are faulty or blocked by the operating system (see below).
- 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.
- 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.
- Repeat with keys from the other side of the keyboard. Ghosting is combination-specific, so a pass in one area says nothing about another.
- 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
| Key | Why it may not show up |
|---|---|
| Fn | Handled inside the keyboard to change what other keys send; it never reaches the computer as a key. |
| Print Screen | On Windows the system takes it for screenshots, and browsers often receive only the key release. |
| Windows / Command key combinations | Many are captured by the operating system before the browser, for example Win + D. |
| Ctrl + W, Ctrl + T, Ctrl + N | Reserved by browsers for closing and opening tabs and windows, so pages cannot intercept them. |
| Media keys, brightness keys | Usually 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
- Dead in every program: on a mechanical keyboard, try compressed air or a replacement switch; on a laptop or membrane keyboard, the key or the keyboard needs repair.
- Registers twice from one press ("chattering"): a worn mechanical switch. Some keyboard software has a debounce setting that helps temporarily.
- Fails only in certain combinations: ghosting or rollover. Rebind the action to a key that works with the others, or look for a keyboard advertised as NKRO or "anti-ghosting" for the keys you need.
- Wireless keyboard misses keys: move the receiver closer, away from USB 3 ports and metal, and replace the batteries before suspecting the keys.
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
- USB-IF: Device Class Definition for HID 1.11 (boot keyboard report, Appendix B)
- W3C: UI Events KeyboardEvent code Values
- MDN: KeyboardEvent.code
- MDN: KeyboardEvent.repeat
- 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.