Keyboard Ghosting and N-Key Rollover Explained
Press W, A, and the space bar together in a game and jump while running diagonally — on some keyboards it works, on others the jump silently never happens. That missing keystroke is the everyday face of two related concepts: ghosting and rollover. Both come down to how keyboards are wired internally, and once you understand the wiring, the behaviour stops being mysterious and becomes something you can actually test for.
The matrix under every keyboard
A keyboard doesn't have a dedicated wire running from each key to the controller — that would need over a hundred separate connections. Instead, keys are arranged in a grid, or matrix, of rows and columns. Each key sits at the intersection of one row and one column, and the controller figures out which key you pressed by scanning the grid: energizing each column in turn and checking which rows respond. This is elegant and cheap, and for ordinary typing — where you press one key at a time, or a couple in quick succession — it works flawlessly.
The trouble starts when you hold several keys down at once, because the matrix can become ambiguous about what's really being pressed.
What ghosting actually is
Imagine three keys held down that happen to form three corners of a rectangle in the matrix grid — sharing rows and columns in just the wrong way. When the controller scans, the electrical path can complete through those three keys as if a fourth key, at the empty corner, were also pressed. That phantom keystroke is a ghost: a key you never touched registering as pressed. True ghosting — a genuinely false extra keypress — would be chaos, so essentially every modern keyboard prevents it. But it prevents it using a technique that creates the second problem.
Blocking: the fix that causes the missed keys
To stop ghosts, keyboards use blocking (sometimes called jamming): when a combination of keys would produce an ambiguous ghost reading, the controller refuses to register the additional key rather than risk inventing a phantom one. So instead of a wrong key appearing, a real key you pressed is simply ignored. This is why your jump didn't happen — the keyboard blocked the space bar because registering it alongside W and A would have been ambiguous in the matrix. What people loosely call "ghosting" in a gaming context is almost always blocking: not a phantom key, but a swallowed one.
The likelihood of blocking depends entirely on which keys share rows and columns. Cheaper keyboards lay out the matrix without much thought to which key groups gamers press together, so common combinations like movement keys plus a modifier plus the space bar can collide. This is why the same three-key combo works on one board and fails on another.
Where rollover comes in
Rollover describes how many keys a keyboard can register simultaneously without dropping any. You'll see it written a few ways:
- 2KRO — two-key rollover, the bare minimum. The keyboard guarantees any two keys plus, usually, modifier keys. Fine for typing, limiting for gaming.
- 6KRO — six-key rollover, the common standard for USB keyboards. It reliably registers six regular keys at once (plus modifiers like Shift and Ctrl), which covers almost anything a person can physically press with ten fingers in normal use.
- NKRO — N-key rollover, meaning every key is independent and any number can be pressed at once with none blocked. This is the gold standard for gaming and fast typing, achieved by wiring the matrix so no combination is ambiguous, often by adding a diode at each key.
The historical reason 6KRO is so common is a quirk of the standard USB keyboard protocol, which reports keys in a fixed-size slot list that holds six regular keys plus modifiers. True NKRO keyboards work around this, but the six-key figure is enough that most users never hit the ceiling outside of intense gaming.
Testing your own keyboard
You don't have to guess where your keyboard's limits are — you can measure them. Open the keyboard tester and hold down a growing handful of keys at once while watching the "held now" counter. Start with a realistic gaming cluster: a movement key, an adjacent one, a modifier, and the space bar. If the counter stops climbing before you've added the keys you're actually holding, you've found a blocking limit — the keyboard won't register beyond that many simultaneous presses in that particular combination. Try different key groups, because blocking depends on the specific matrix layout: some trios collide while others don't.
The same tool is useful for the more mundane faults, too. Because pressed keys stay highlighted, you can press every key in turn and immediately see any that never light up (a dead key), and you can watch for a key that lights on its own or refuses to turn off (a stuck key). A key's physical code and legacy keyCode are shown as you press, which helps when a key seems to type the wrong character and you suspect a layout remap rather than a hardware fault.
Do you need NKRO?
For writing, email, and everyday work, even humble 2KRO is genuinely fine — you can't type faster than the keyboard can follow. For fast-paced games where you routinely hold three or four keys and tap a fifth, 6KRO covers the vast majority of situations, and full NKRO is a nice guarantee rather than a strict necessity. The practical move is to test the combinations you actually use: if they all register, your keyboard is good enough, whatever its spec sheet claims. If a combo you rely on gets blocked, that's the moment NKRO becomes worth paying for.