Guide · Input
Key Rollover and Ghosting, Explained
When you hold a strafe, a sprint, and a jump at once and one of them silently fails, the cause is almost never a broken switch — it's arithmetic in the keyboard's wiring. This guide explains what rollover measures, why ghosting exists, what 6KRO and NKRO actually promise, and how to test your own keyboard in about a minute.
Rollover is a number, and you can read yours directly. Hold key combinations and watch the Held and Max rollover counters respond live — everything runs in your browser and nothing you press leaves your device.
What rollover actually measures
Rollover is the number of keys a keyboard can register simultaneously and report correctly. The naming convention is n-key rollover: a 2KRO board guarantees any two keys at once, a 6KRO board guarantees six, and NKRO — n-key rollover in the literal sense — means every key on the board can be held at the same time and each one still registers.
Every keyboard has some limit, and the limit is a property of two separate things: how the keys are wired inside the keyboard, and how the keyboard reports presses to the computer. Both matter, and they fail in different ways — which is why the same board can behave differently on different combinations. To understand either, you have to look at the wiring first.
How a keyboard matrix works
A full-size keyboard has over a hundred keys. Giving each one a dedicated wire to the controller would be expensive and bulky, so nearly every keyboard instead wires its keys into a grid: a set of row lines crossing a set of column lines, with one key switch sitting at each intersection. Pressing a key closes its switch and electrically bridges one row to one column.
The controller finds pressed keys by scanning: it energizes one row at a time and reads which columns carry current, then moves to the next row, sweeping the whole grid many times per second. If row 3 is energized and column 7 reads active, the key at that intersection is down. With one key held, this is unambiguous. The trouble starts when several keys are held at once, because current doesn't care about the controller's intentions — it flows through every closed switch it can reach.
Why ghosting happens — and why you rarely see a ghost
Picture three held keys whose intersections form three corners of a rectangle in the grid: two keys sharing a row, one of them also sharing a column with the third. When the controller energizes a row, current sneaks through the three closed switches in series and comes back up a line it was never meant to reach — making the fourth corner of the rectangle read as pressed. Electrically, that phantom press is indistinguishable from a real one. The keyboard cannot tell three real keys plus one ghost apart from four real keys. That phantom fourth key is ghosting in the original sense.
Because a phantom keystroke is worse than a missing one — imagine a stray character appearing in a password field — firmware on matrix-limited keyboards almost universally chooses the safer failure: it blocks. When a third keypress would complete an ambiguous rectangle, the controller simply refuses to register it. This is why the symptom you actually experience is a key that goes dead in certain combinations, not letters appearing on their own. The name "ghosting" survives in everyday use, but what modern keyboards actually do is blocking; the ghost is the problem the blocking prevents.
The clean fix is a diode wired in series with every switch. Diodes pass current in one direction only, so the sneak path back through the three-switch chain is cut off and every intersection reads independently. Per-key diodes are what make true NKRO electrically possible; without them, some three-key combination on the board will always be ambiguous.
6KRO, NKRO, and why modifiers don't count
The other half of the limit is the report format. The classic USB boot-protocol keyboard report — the simple format every PC understands, including the BIOS before an operating system loads — has room for exactly six simultaneous key slots plus one byte of eight modifier bits: left and right Ctrl, Shift, Alt, and the OS key each get their own bit. That is where 6KRO comes from: six keys is not a wiring limit but a message-size limit. And because modifiers live in their own bitfield, they never count against the six. Ctrl+Shift+Alt plus four letters is still within a 6KRO board's guarantee.
NKRO keyboards need both halves solved: per-key diodes so the matrix can actually distinguish every combination, and a different report format — typically a bitmap with one bit per key — so the message to the computer has room to say it all. One board-specific caveat: the Fn key on laptops and compact keyboards is handled entirely inside the keyboard and never reaches the operating system, so no software tester can see it.
The honest framing: for typing, 6KRO is nearly always enough. Even fast typists overlap two or three keys during normal rollover between strokes. Rollover limits matter when you deliberately chord — holding movement keys, a modifier, and action keys together in games, playing rhythm titles, or leaning on multi-key shortcuts. If that describes your use, the difference is real; if not, it mostly isn't.
How to test yours
Open the keyboard tester and hold combinations down. The Held readout shows how many keys the computer currently sees pressed, and Max rollover records the highest count reached in the session. Start with the clusters that matter to you: W+A+S+D plus Shift plus Space is the canonical gaming chord, and it exercises keys that sit close together in most matrices, which is exactly where diode-less layouts run out of unambiguous combinations.
Read the result the way an instrument would. If Held stops climbing at six while more fingers go down, you are watching the boot-protocol report limit — six slots, filled. If a specific combination refuses to register no matter how hard or how often you press it, while each key works fine on its own, that is the matrix, not a broken switch: the controller is blocking a press that would complete an ambiguous rectangle. No cleaning, driver update, or replacement switch changes it, because it is the wiring layout doing precisely what it was designed to do. A key that intermittently fails alone, by contrast, is a switch problem — a different diagnosis covered in the keyboard chatter guide.
Test the combinations you actually use rather than chasing the biggest number. A board that blocks some exotic ten-key spread but handles every chord you play is, for you, a keyboard without a rollover problem. The measurement, not the spec sheet, is the answer.