Keyboard Ghosting Test & NKRO Checker

How to use this keyboard ghosting test

1. Click anywhere on this page so it has keyboard focus.
2. Hold down two keys at once, then add a third, then a fourth: try a real combo you'd use in a game, like W + A + Shift, or just walk your fingers across the keyboard.
3. Watch the grid above: every key you're currently holding lights up purple. If one of your fingers is pressing a key that never lights up while the others are held, that's ghosting.
4. Keep an eye on Peak simultaneous: that's the largest number of keys this keyboard has registered at once during this session.

What causes ghosting?

Most keyboards scan their keys in a grid, a matrix of rows and columns, rather than wiring every single key to its own dedicated circuit, which would be far more expensive to manufacture. When certain combinations of keys are held together, the matrix can create an electrical ambiguity: the controller can't tell which of a few possible keys is actually being pressed, so it either drops one of them (ghosting) or, in some cases, reports a key nobody is touching (a "phantom" key). Keyboards designed to avoid this add diodes to every switch (full NKRO) or are wired specifically so that the most common combinations, like WASD plus a modifier, never collide.

How keyboard matrix scanning actually works

Inside most keyboards, every key sits at the intersection of one row wire and one column wire. The controller scans through the rows one at a time, applying a small voltage, and checks which columns report that voltage coming back. If exactly one key on a given row is pressed, the intersection is unambiguous. The problem starts when three or more keys are held down in a pattern that forms a rectangle across two rows and two columns: current can flow through paths the controller didn't expect, and the scan can no longer tell for certain whether a fourth key at the remaining corner of that rectangle is genuinely pressed. That false positive is a phantom key, and the ambiguity is exactly why the controller sometimes chooses to drop a key instead.

Why diode placement solves the ambiguity

A diode is a small component that only lets current flow in one direction. When a keyboard manufacturer places one diode behind every single switch, current from a pressed key can no longer leak backward into a different row or column, which is exactly the leakage that causes the rectangle problem described above. With a diode at every switch, the matrix can report any combination of keys with no ambiguity at all, which is what full N-key rollover requires. Diodes add cost and manufacturing complexity, which is why cheaper membrane keyboards often skip them entirely, or only wire diodes into the small cluster of keys the manufacturer expects gamers to press together.

Anti-ghosting vs. full N-key rollover (NKRO): what's the difference

"Anti-ghosting" and "NKRO" both describe fixes for the same matrix problem, but they solve it to different degrees. Anti-ghosting typically means the manufacturer has verified that a specific, limited set of key combinations, almost always WASD plus common modifiers like Shift, Ctrl, and Space, will never ghost against each other. It doesn't promise anything about combinations outside that set. Full NKRO means every key on the board can be held down simultaneously with every other key and still register correctly, because diodes isolate every switch from every other one.

In practice, this means a keyboard can be legitimately marketed as "anti-ghosting" and still ghost if you press an unusual combination the manufacturer didn't design around, such as holding several number keys plus letter keys at once for a fighting-game input. A keyboard ghost test that only checks WASD and a couple of modifiers won't catch that. Running this keyboard ghosting test across the full board, not just your usual movement keys, is the only way to see where a partial anti-ghosting solution stops covering you.

For a deeper walkthrough of testing methodology and what counts as a reliable result, see our guide to testing keyboard ghosting, and for the full technical background on rollover specs, our beginner's guide to NKRO and anti-ghosting.

Which key combinations matter most for your game

Not every player stresses the same part of a keyboard's matrix. The combinations worth testing depend heavily on the genre you actually play, so it's worth running this keyboard ghosting test with your specific game's bindings in mind rather than only checking WASD in isolation.

FPS games: movement clusters and modifiers

Shooters lean hardest on the movement cluster: W, A, S, D held in various combinations alongside Shift (sprint), Ctrl (crouch), and Space (jump). A common failure case is holding two diagonal movement keys plus Shift plus Space for a jump-strafe, which stacks four keys from different rows and columns at once. If your keyboard drops one of those under load, movement can feel like it randomly stutters mid-fight.

MOBA and RTS games: ability rows plus modifiers

MOBA and RTS players often hold a movement or camera key while rapidly tapping ability keys across the QWER row, sometimes with Ctrl or Alt held for a modified cast. Because these games map several abilities to adjacent keys, it's worth testing combinations like Q, W, E, R together, and separately with a movement key held underneath, to make sure the ability row doesn't ghost when it matters most, in a team fight.

Fighting games: motion inputs and multi-button presses

Fighting games frequently require directional inputs combined with two or three attack buttons pressed within the same frame, for command grabs or simultaneous button presses. These combinations often span the number row and letter row together on a keyboard, which is a different part of the matrix than the WASD cluster most anti-ghosting keyboards are designed around. This is exactly the kind of combination a narrow anti-ghosting solution can miss.

Rhythm games: lane clusters under sustained load

Rhythm games map multiple simultaneous "lanes" to adjacent keys, and high-difficulty charts can require four, six, or more keys held or tapped in rapid overlapping succession. Because the keys involved are usually close together on the board (for example, a run of keys in a single row), they're more likely to share rows or columns in the matrix, which is precisely the condition that causes ghosting. Players in this genre typically need a keyboard closer to full NKRO than a movement-key anti-ghosting design provides.

Reading your keyboard ghosting test results

There's no universal "pass" number, since it depends entirely on what you need the keyboard for. Someone who only ever types won't notice 2-key rollover; a gamer relying on simultaneous WASD + Shift + an ability key needs at least that many to register reliably. If you find a specific real-world combo that drops a key, that's the actionable result: check whether your keyboard's marketing mentions anti-ghosting for that specific combination, or whether it's simply a budget membrane board without dedicated diodes.

Using this test when shopping for a new keyboard

If you're trying to decide whether to buy a specific keyboard, run this keyboard ghosting test on it in-store or during a return window, using the exact combination you rely on in your main game. A result that matters more than any marketing claim on the box is whether your own real combo lights up cleanly. If a keyboard is advertised as "anti-ghosting" but drops a key in your specific fighting-game or rhythm-game combo, that product simply wasn't designed around your use case, even though the claim on the packaging is technically accurate for the combos it was designed for.

It also helps to retest after firmware updates or when switching between wired and wireless modes on the same keyboard, since some boards behave differently depending on connection mode or onboard profile. Because ghosting is a hardware property, a clean result on one connection mode is a reasonable predictor for the others, but it's not a guarantee, so a quick recheck costs nothing.

What this keyboard ghosting test can and can't tell you

This page can only report what the browser's keyboard events actually deliver. When you hold a key and it lights up in the grid above, the browser received a keydown event for it; when it doesn't light up, no such event arrived. That's a reliable, honest signal, but it has one real limitation worth understanding before you draw conclusions about your hardware.

A dropped key could mean the keyboard's internal matrix never detected the press at all, which is true hardware ghosting. It could also mean the matrix detected it correctly, but the operating system, driver, or browser itself discarded or coalesced the event somewhere between the keyboard and this page. From JavaScript running in a browser tab, those two situations are indistinguishable. This keyboard ghosting test is a strong diagnostic starting point, and a consistent, repeatable drop on the same combination across multiple attempts is a meaningful signal, but it is not a substitute for a hardware-level analyzer if you need to certify a device.