Keyboard Ghosting Test / Key Rollover Explained / N-Key Rollover

You're sprinting diagonally, holding crouch, and you try to reload. Nothing happens. Or worse, a key you never touched fires instead. Then you let go of one key and everything works again.

That's your keyboard hitting its rollover limit, and it's one of the few gaming problems that's genuinely a hardware constraint rather than a setting you can change. Understanding what's actually happening tells you whether you need a new keyboard or just a smarter key layout.

Here's what ghosting really means, how it differs from the thing most people call ghosting, and how to test yours.

Ghosting and blocking are not the same thing

Almost everyone uses "ghosting" for both problems, but they're opposites, and knowing which you have matters.

Ghosting is when your keyboard registers a key you never pressed. A phantom input appears out of nowhere. This is the original meaning of the term, and on modern keyboards it's actually rare.

Blocking, sometimes called masking, is when your keyboard fails to register a key you did press. You press it, nothing happens, and releasing another key makes it work again.

Both come from the same underlying matrix limitation, which is why they get lumped together. But in practice, if you're a gamer in 2026, what you're almost certainly experiencing is blocking, not true ghosting. Your keys aren't inventing inputs; they're being dropped.

Why it happens: the keyboard matrix

Keyboards don't wire every key individually, because a 104-key board would need an impractical amount of wiring. Instead, they use a matrix: rows and columns of traces that intersect beneath each key. The keyboard's controller rapidly scans the rows while monitoring the columns, and a keypress closes a connection at a specific row-column intersection.

This design is efficient and cheap, and it has one flaw. When you press certain combinations of keys, the current can find an unintended path through the matrix, creating a "phantom" intersection that the controller reads as a fourth key being pressed. That's ghosting.

The fix is straightforward electrically: put a diode at each key position so current can only flow one direction, eliminating phantom paths. Quality keyboards do this. Budget keyboards frequently don't, because diodes cost money at scale.

Where diodes aren't present, manufacturers prevent ghosting by blocking instead: rather than risk a phantom key, the controller simply refuses to register additional presses. That's why cheap keyboards drop inputs rather than inventing them, and it's a deliberate design decision rather than a defect.

What rollover numbers actually mean

Rollover describes how many keys your keyboard can register simultaneously and correctly.

2KRO guarantees any two keys together. Press three and things start failing. This is typical of cheap office keyboards and many laptops, and it's a common cause of dropped inputs in games.

6KRO handles six simultaneous non-modifier keys. This is the standard, and it's genuinely sufficient for the overwhelming majority of players.

NKRO means every key is scanned independently and any number can be reported together. The "N" is an algebraic variable, not a specific number.

You'll also see figures like 12KRO, 18KRO, or 22KRO. These usually describe heavily optimised matrices or NKRO keyboards limited by their interface. Be a little wary of marketing numbers here, since some brands count modifiers in the total, so "10KRO" can simply mean 6KRO plus four modifiers, which is just the standard dressed up.

The USB 6-key limit, explained properly

There's a persistent myth that USB caps keyboards at six keys. The reality is more specific.

The USB HID boot protocol, the simple compatibility mode that works before an operating system loads its own drivers, reports six non-modifier keys plus four modifiers (Ctrl, Shift, Alt, Win). That's where the six-key figure originates, and it's why keyboards default to 6KRO: it matches the universal standard without needing anything custom.

But the full USB HID specification itself supports N-key rollover perfectly well. Modern operating systems use the standard HID report protocol, which handles larger bitmaps. Keyboards achieve NKRO over USB by using extended reports or by presenting themselves as multiple HID interfaces.

So USB doesn't prevent NKRO on a desktop. What it does mean is that your keyboard may fall back to 6KRO in BIOS or in a pre-boot environment, which is a feature rather than a fault.

Bluetooth is the real limitation. The Bluetooth HID profile doesn't support the extended reporting that NKRO relies on, so wireless keyboards over Bluetooth are effectively capped at 6KRO. Many premium keyboards support NKRO over USB and switch to 6KRO automatically when you go wireless. If you play competitively on a wireless keyboard and need full rollover, plug it in.

How to test your keyboard

Testing takes under a minute and tells you exactly where your limits are.

Open a browser keyboard test, then hold down keys one at a time and watch which register. Start with your actual gaming cluster: hold W, A, S, D, then add Shift, Ctrl, Space, and your common ability keys one by one.

Two things to watch for. If keys stop lighting up as you add more, that's blocking, and you've found your rollover ceiling. If a key lights up that you never touched, that's genuine ghosting, and it means your keyboard lacks proper diode isolation.

Test the combinations you actually use rather than a random selection, because rollover limits are specific to matrix routes rather than uniform across the board. A keyboard might handle six keys fine in one corner and fail at four in another.

Also test the same combinations on a different keyboard if you have one, which confirms whether the limit is your hardware or something in the game.

What you can and can't fix

Here's the honest part. You cannot fix hardware-level ghosting or blocking in software. No driver, firmware update, or registry tweak changes physical diode placement. If your keyboard's matrix can't isolate certain keys, that's a manufacturing decision baked into the circuit board.

But there are three things worth trying.

Check for an NKRO toggle. Some gaming keyboards ship in 6KRO mode for maximum compatibility and offer a firmware hotkey or software switch to enable NKRO. Consult your keyboard's documentation, because a fair number of people own NKRO keyboards running in 6KRO without realising.

Switch from Bluetooth to wired. If your keyboard supports both, this alone can take you from 6KRO to full NKRO.

Remap around the problem. This is the genuinely useful workaround. Ghosting and blocking affect keys sharing matrix rows or columns, so moving one conflicting action to a key in a different part of the board escapes the problem zone. If W+A+D+Shift fails, rebinding one of those actions to a function key or numpad key often resolves it entirely. It costs nothing and works on any keyboard.

Do you actually need NKRO?

Worth being realistic, because this is heavily marketed.

For typing and most gaming, 6KRO is genuinely enough. You rarely press more than six non-modifier keys simultaneously with two hands, and modifiers are counted separately anyway. Plenty of competitive players use 6KRO boards without issue.

NKRO earns its place when you're layering multiple modifiers with several action keys, playing rhythm games with dense simultaneous inputs, using complex hotbar setups in MMOs or strategy games, or sharing a keyboard for local multiplayer, which is the scenario where rollover limits bite hardest.

The more important specification for most people is simply that the keyboard doesn't ghost and doesn't block within the range they actually use. A well-designed 6KRO keyboard beats a poorly-implemented NKRO one, and note that "anti-ghosting" is a marketing term with no fixed standard behind it, so it can mean anything from full diode isolation to a handful of protected key clusters.

When keys fail for other reasons

Rollover isn't the only reason a key stops working, and it's worth distinguishing.

If a single key fails consistently regardless of what else you're pressing, that's a dead or dirty switch, not a rollover problem. If a key registers twice from one press, that's switch chatter, the keyboard equivalent of a mouse double-clicking, caused by worn contacts bouncing beyond the debounce window. Our guide on fixing a double-clicking mouse covers that mechanism in detail, and it applies to keyboards too.

Testing your mouse at the same time is worth doing if your whole setup is a few years old, since peripherals bought together tend to wear on similar timelines. And if a keyboard is failing in several ways at once, our peripheral failure guide covers judging repair against replacement.

The short version

Ghosting means your keyboard reports a key you didn't press; blocking means it drops a key you did. Both stem from the matrix design that keyboards use to avoid wiring every key individually, and diodes at each key position are what prevent them. The USB six-key figure comes from the HID boot protocol, not from USB itself, so NKRO over USB works fine on a desktop, though Bluetooth genuinely caps you at 6KRO. Test by holding your real gaming key cluster and adding keys until something drops. You can't fix a matrix limitation in software, but you can check for an NKRO toggle, switch to wired, or simply remap conflicting actions to keys elsewhere on the board.