RigCheckup

Keyboard Test

Press any key. It lights up below as you type — no clicks needed, just start typing.

Keys held now

0

Max rollover (NKRO)

0

Keys tested

0/73

Recent keys

Waiting for input…

Collect all your test results on one sheet: PC Checkup Report

What this test checks

Every key you press is detected through your browser's physical key events, so it works with any keyboard in any language layout. A key that never lights up is not registering — usually a stuck switch, a broken solder joint, or debris under the keycap.

The rollover counter shows how many keys your keyboard can register at the same time (N-key rollover). Hold down several letter keys at once: gaming keyboards typically handle 6 or more, while basic office keyboards may miss keys beyond 2–3 — that's called ghosting.

How this test works

When you press a key, the operating system hands your browser a keydown event, and when you release it, a keyup event. Our keyboard test reads one field from those events: the code value, which identifies the physical key position rather than the character it produced. That is why the same key always lights the same spot on the virtual keyboard whether you are typing in English, Korean or a Dvorak layout, and whether you are on Windows, macOS or Linux. Holding a key down makes the OS repeat the keydown event; the test ignores those repeats, so a long press does not inflate the rollover count or the input history.

While the page is open it suppresses the browser's own reactions to keys that would otherwise interfere: Tab no longer jumps between elements, Space does not scroll the page and the F-keys do not open browser features. Refresh (F5, Ctrl+R or Cmd+R) and the developer tools shortcut (F12) are deliberately left alone so you always have a way out. If you switch to another window or the tab is hidden, the browser never receives the matching keyup events, so the test clears its held-keys list at that moment to avoid phantom pressed keys.

Some keys never reach a browser at all. Fn is a modifier handled by the keyboard's own controller and does not send a signal to the PC; many media, lighting and macro keys behave the same way. Combinations the operating system reserves for itself, such as a lone Windows key opening the Start menu, Ctrl+Alt+Delete, or Cmd+Tab on a Mac, are consumed before the browser sees them. When those keys stay unlit it reflects how keyboards and operating systems are built, not a fault.

Everything happens inside the page. The key codes are kept in memory only long enough to draw the display, and nothing is sent to our servers or stored anywhere. Pressing Reset or closing the tab discards the record.

How to read the results

The virtual keyboard uses two highlight states: a key you have pressed at least once stays marked as tested, and a key you are holding right now is shown in a stronger colour. Walk through every key one by one; if all of them change colour, the keyboard is registering correctly. A key that never changes is not getting its signal through to the PC. Remember that the on-screen layout is an 87-key ANSI arrangement, so a numeric keypad, the extra key on ISO boards and keys your laptop lacks are simply outside its scope.

The keys-held-now list shows what the browser currently believes is pressed. If you have let go of everything and a key remains there, its release was never reported: either the switch is physically stuck part-way, or focus left the window at the wrong moment. Pressing and releasing that key once more normally clears it. Max rollover is the highest number of keys held simultaneously during the session. A ceiling of 2 or 3 is typical of inexpensive membrane boards, exactly 6 means the standard USB six-key mode, and anything higher confirms that N-key rollover is active. Ten fingers rarely exceed 10, so the usual trick for checking high counts is to press a whole row with the flat of your palm.

Keys tested counts how many distinct keys have registered, against the total on the virtual layout; treat it as a progress bar for a full sweep. Recent keys lists the last ten inputs with the newest first, and it is the readout that matters for chatter. Press one key slowly, once, and release it. If the same key appears twice in a row, the switch contacts bounced and produced a second keydown after the keyup. Because auto-repeat is filtered out, simply holding the key will not create a duplicate, so any double entry from a single press is a genuine fault.

When to use it: common situations

Unboxing a new keyboard. Within the return window, press every key once and confirm the whole layout lights up, then check that the rollover reading matches what was advertised, whether that is 6KRO or NKRO. It takes ten minutes and catches problems that would otherwise turn into a paid repair after the deadline.

A key that works only sometimes after a spill. Dried sugary residue on the contacts causes intermittent registration rather than total failure. Press the suspect key twenty or thirty times in a row while watching the virtual keyboard and the recent-input list, and count any presses that produce nothing. Even one miss means the switch needs cleaning or replacement.

Deciding whether chatter justifies a warranty claim. Pick your most-used keys such as Space, Enter and the vowels, press each fifty times slowly, and count duplicate entries. One or two duplicates in fifty presses is already noticeable in everyday typing, and chatter tends to worsen over time, so it is worth filing the claim while the warranty is still valid.

Checking a second-hand laptop before paying. Opening this page in front of the seller and pressing every key is the most reliable keyboard check you can do on the spot. Laptop keyboards are expensive to replace and parts are often hard to source, so a few minutes here can save a lot later.

Confirming NKRO before a tournament, and verifying a remap. Many gaming keyboards toggle between a compatibility 6KRO mode and NKRO with a shortcut, so hold the exact combination you rely on in play, such as W, A, Shift, Space and a number key, and make sure every one of them appears in the held list. After changing a layout with QMK, VIA or vendor software, or flashing new firmware, press the remapped keys and confirm the light appears where you intended; because the test shows physical key codes, it is the most direct way to see what the firmware is actually sending.

Limits of a browser test and what to check elsewhere

This test answers one question: did the keyboard's signal travel through the operating system and arrive in the browser? It cannot see Fn combinations, on-board macros or anything the keyboard resolves internally, and it does not measure physical properties such as actuation force, actuation point or how worn a switch is. Nor does it give millisecond-accurate input latency, because when the browser processes an event depends on the display refresh cycle and OS scheduling rather than on the keyboard alone.

Operating system settings can skew what you see. Filter Keys on Windows, which ignores brief keystrokes, Sticky Keys, and Slow Keys on macOS can all make a healthy keyboard look like it is dropping presses. Software remappers such as PowerToys, Karabiner-Elements and AutoHotkey rewrite key codes before they reach the browser, so the light appears on a different key. Pause those tools before testing if you want a clean reading.

When the browser shows a fault, the next step is to separate the keyboard from the computer. Try the same keyboard on another PC, or in a different USB port connected directly to the machine rather than through a hub; if the symptom follows the keyboard, the keyboard is the cause. Switch a wireless model to its cable, update its firmware through the vendor software and try a factory reset. For mechanical boards, raising the debounce time in the firmware sometimes tames mild chatter without any hardware work.

For deeper reading, our guide on keys not registering or typing twice covers the causes of chatter and the order in which to try debounce changes, contact cleaning and switch replacement. The guide on some keys not working shows how the pattern of dead keys points to a particular cause. The rollover test guide and the NKRO and ghosting explainer cover the difference between 6KRO, NKRO and ghosting, and how much rollover games actually need.

Frequently asked questions

I pressed a key and nothing lights up. Is the key broken?
First click once anywhere on this page so the browser window has focus, then try again. If one specific key still shows nothing, its signal is not reaching the computer — a failed switch or debris under the keycap is the usual cause. Note that the Fn key, some media keys and vendor-specific keys are handled inside the keyboard itself and never send a signal to the browser, so it is normal for them not to appear.
Can this test show a key that types twice from one press?
Yes. Press the suspect key slowly, one press at a time, and watch the recent input history. If a single press is logged twice in a row, the switch contacts are bouncing — a fault known as key chatter. It mostly affects well-used keys on mechanical keyboards, and our key chatter guide walks through the causes and fixes.
My simultaneous key count stops at 6. Is that a defect?
No. The standard USB keyboard protocol sends up to six regular keys plus the modifiers (Ctrl, Shift, Alt) at once, so many keyboards stop at exactly six. If your keyboard is advertised as NKRO but still stops at six, check whether it has a shortcut that switches between 6KRO and NKRO modes, and whether it is running in wireless or compatibility mode.
Does it work with laptop keyboards and Macs?
Yes. The test reads the physical position of each key rather than the character it produces, so it works regardless of language layout or operating system. On a Mac, Command appears in the Windows key position and Option in the Alt position. The on-screen layout is standard ANSI, so keys your laptop does not have will simply stay unlit.
Is anything I type sent to a server?
No. Everything is processed inside your browser, and the keys you press are never stored or transmitted. The history disappears when you close the page or press reset. Even so, it is a good habit not to type passwords or other sensitive text while testing.

Related guides