NKRO vs 6-Key Rollover Explained

Press enough keys at once and every keyboard has a limit. Where that limit sits — and what happens when you hit it — is what key rollover describes. “6-key rollover” (6KRO) and “N-key rollover” (NKRO) are the two terms you’ll see on spec sheets, and the difference matters if you game, type very fast, or use key-chord-heavy software.

Here’s what the terms actually mean, why the number 6 keeps showing up, how rollover differs from ghosting (they’re constantly confused), and how to test what your keyboard really does.

What Key Rollover Means

Key rollover is the number of simultaneous keypresses a keyboard can correctly detect and report. “Correctly” is the key word: every key held down registers, no held key gets dropped, and no phantom key appears.

• 2KRO: any two keys work together; a third may be ignored depending on the combination. Common on cheap membrane keyboards.
• 6KRO: any six keys (plus modifiers like Shift, Ctrl, Alt, which are counted separately) register simultaneously. The classic USB keyboard standard.
• NKRO: N keys — every key on the board can be held at once and all of them register.

Note the “any” in those definitions. A 2KRO board isn’t limited to two keys in all cases — many combinations of 3+ keys work fine, but some specific combinations fail. That’s why rollover problems feel random until you understand the mechanism.

Rollover vs Ghosting: Not the Same Problem

These two get merged in casual use, but they’re distinct failure modes:

• Rollover limitation (key blocking/jamming): you press a key and it doesn’t register because the keyboard already hit its simultaneous-key limit or can’t resolve that combination. Keys go missing.
• Ghosting: you press some keys and an extra key you never pressed registers. Keys appear from nowhere.

Both come from the same root cause. Most keyboards wire their switches in a matrix of rows and columns rather than giving each key its own dedicated line. When you press certain three-key combinations that form three corners of a rectangle in the matrix, current can flow through a path that makes the fourth corner look pressed too — that’s the ghost. Manufacturers prevent false inputs by blocking: the controller detects an ambiguous combination and deliberately ignores the third key. So on cheap boards, anti-ghosting is implemented as key blocking — the ghost is suppressed, but your real keypress is dropped.

Better keyboards solve it properly with a diode per switch, which stops current from back-flowing through the matrix. With diodes, every key reads independently, no combination is ambiguous, and true NKRO becomes possible. This is standard on quality mechanical keyboards and essentially all custom/enthusiast boards.

So when a spec sheet says “anti-ghosting,” ask: anti-ghosting by blocking (limited rollover) or by diodes (real rollover)? Marketing rarely says — testing does.

Why 6 Keys? The USB Story

The number 6 isn’t about switches at all. It comes from the USB HID (Human Interface Device) boot protocol — the simple keyboard report format defined so that BIOS/UEFI firmware and other minimal environments can read a keyboard without a full driver. That standard report has room for exactly six regular keycodes plus a bitmap for eight modifiers. Hence 6KRO: six keys plus Shift/Ctrl/Alt/Win combinations.

Full NKRO over USB is completely possible — the keyboard just uses a different report format (typically a bitmap with one bit per key) instead of the six-slot array. The catch is compatibility: some BIOS screens, recovery environments, KVM switches, and consoles only understand the boot protocol. That’s why many NKRO keyboards ship with a toggle (often a keyboard shortcut or a software setting) to fall back to 6KRO mode, and why a keyboard that types fine in Windows can act strangely in the BIOS until you flip that switch.

Historical footnote: PS/2 keyboards, which sent interrupt-driven scancodes rather than polled reports, supported NKRO naturally — one of the few things the old connector did better by default.

Does Rollover Actually Matter for You?

Honest answer by use case:

• Typing, even fast typing: 6KRO is effectively never a limitation. Even at very high typing speeds you overlap two or three keys at most, and modifiers don’t count against the six.
• Gaming: this is where it matters. Movement (up to 2 keys) + sprint + crouch + ability + push-to-talk can pass six keys held, and on 2KRO boards even simple combos like W+Shift+Space can hit a blocked combination. If a jump or reload occasionally “doesn’t register” during intense moments, rollover blocking is a prime suspect.
• Local multiplayer on one keyboard: two players on one board hits rollover limits constantly. This is the strongest NKRO use case there is.
• Music software, stenography, accessibility chording: applications that treat the keyboard as a chord instrument benefit directly from NKRO.

If you never hold more than a few keys, a well-implemented 6KRO board will never bother you. The problem child is not 6KRO — it’s 2KRO with blocking, sold under a vague “anti-ghosting” label.

Test Your Keyboard Right Now

Specs describe intent; a test shows reality. Open the keyboard tester — it highlights every key the OS reports as held, in real time — and run these checks:

1. The gamer combo: hold W+A+S+D together, then add Space, then Shift, then Ctrl. All should light and stay lit.
2. The rectangle probe: hold Q+W, then add A and S. On matrix-limited boards, clusters of physically adjacent keys are where blocking or ghosting shows up first.
3. The count test: starting from one end, hold down keys one at a time — A, S, D, F, G, H, J… — and watch when new keys stop registering. Stops at 6? You’re in 6KRO mode. Keeps going as far as your hands can reach? NKRO.
4. Ghost hunt: while holding three keys, watch the tester for any key lighting up that you’re not touching. A phantom key appearing is true ghosting — rare on modern boards, but it happens on old or very cheap ones.
5. Both hands, palms if needed: for a proper NKRO check, press 10–15 keys at once. Every single one should show as held.

Two testing caveats. First, run the test with the keyboard in its normal mode; if your board has an NKRO toggle, test both modes so you know what each does. Second, wireless keyboards can behave differently over Bluetooth versus their USB dongle — Bluetooth’s HID implementation on some boards limits rollover even when the same keyboard does NKRO wired. Test the connection you actually use.

While you’re in the tester, it’s also worth pressing each key individually once — simultaneous-press problems and per-key faults like chatter are different issues, and the same tool catches both. If you find keys double-registering on single presses, that’s chatter, not rollover, and it has its own fixes.

Buying and Configuring Advice

1. Reading spec sheets: “N-key rollover (USB)” is the clear claim. “Anti-ghosting” alone, or “anti-ghosting for 19/26 keys,” means a partial matrix improvement — the marked gaming cluster (WASD region) has extra rollover headroom, the rest of the board doesn’t. Fine for most gaming, but know what you’re getting.
2. If your NKRO board acts weird in BIOS or on a console, find its 6KRO/boot-protocol toggle in the manual and switch modes for that environment.
3. If your current board blocks combos you actually use, first check for a “gaming mode” that changes the report format. If it’s a hardware matrix limitation, no setting fixes it — the workaround is rebinding your game so the colliding keys move to non-blocking combinations, which the tester will help you map out.
4. Custom firmware users: QMK/ZMK boards typically support NKRO with a config flag or keycode toggle if it isn’t already on.

Rollover is one of those specs that’s invisible until the exact moment it costs you a jump input. Five minutes with the keyboard tester tells you exactly where your board’s limits are — and if you’re auditing your setup anyway, give your other input device the same treatment with the mouse tester and check simultaneous button presses there too. Fighting-game players using both devices at once have found silent input caps in stranger places.