Modifier Key Test: Free Online Keyboard Tester

How to Run a Modifier Key Test on Your Keyboard

You need a physical keyboard on a computer and about a minute. A touch screen sends different key events, so skip phones and tablets; a typing test on a virtual keyboard proves nothing about hardware. Repeat the function key test a few times for a more reliable reading.

1. Click the test area so the page can receive keyboard events from your browser.
2. Press the Shift key, then Control, Alt and the Windows or Command key, one at a time.
3. Watch each pressed key turn green on the on-screen layout.
4. Release it, confirm the key states clear, then hit Reset to start a new session.

Verify Modifier Keys on the Left and Right

Most modifier keys come in pairs. A good keyboard checker reports a duplicate modifier separately, so press the left Shift, then the right one, and check that both light up. Repeat for Ctrl, Alt and Meta so all the modifiers are covered. Simpler testers merge both sides into one key, which hides a dead twin. Finish with a modifier combination such as Ctrl+Shift+Alt, because a combination shows whether the keys register together.

Which Modifier Keys the Keyboard Checker Detects

The test covers Shift, Ctrl, Alt and Meta, plus AltGr on international layouts. Arrow keys, Space, Enter, Backspace, Home, End, Insert, Delete and the numpad also light up, so one pass checks the whole board. A quick pass through the keyboard rollover test shows whether the problem is your keyboard or your settings.

Caps Lock, Function Keys and the Numpad

• Shift, Ctrl and Alt change what another key does and sit on both sides of the keyboard.
• Meta is the logo key on a PC and the Command key on a Mac.
• Caps Lock toggles a state, so it reports a press rather than a held key.
• The Fn key is handled by firmware and often never reaches the page.

Read Your Key Test Results

The session summary counts tested keys and lists the keys currently pressed. Each keyboard event carries the key, so the tool can detect which one fired. The last event panel shows the key, its code, its location (left, right or standard) and whether the press is a repeat. Each press creates a keydown and a keyup, and both key events should arrive in that order. The code follows KeyboardEvent.code, so it names the physical key, not the character; hovering over a key reveals it.

Developers read the same data in an event handler, using a bitwise AND on the modifier flags to learn whether a key is pressed. The tester does that for you, so each modifier shows as lit or unlit through visual indicators.

A Dead Right Shift Key Found with an Online Keyboard Test

I rescued an 87-key tenkeyless board after a coffee spill, and the right Shift feels mushy. Before it goes back on my desk I want a measurable verdict from the tester, so I check every modifier first.

I click the test surface and press Left Shift, Left Ctrl, Left Alt, then the right-hand set. Left Shift reports location 1, right Ctrl and right Alt report location 2, and the summary climbs to 86 of 87 tested keys (98.9%). The one grey key on the layout is right Shift: pressing it produces no event at all. As a cross-check I type Shift+A in a text editor with each side; the left key gives a capital A and the right key gives a lowercase a.

Then I rerun the check after each repair, ten presses per attempt:

• As found: 0 of 10 presses register.
• After cleaning the contacts with isopropyl alcohol: 6 of 10.
• After swapping in a spare switch: 10 of 10.

My judgement is that 6 of 10 is still a fail. A modifier is held during every shortcut, so one dropped press in ten is enough to turn Ctrl+S into a plain s, and the number to watch is the per-key hit rate, not the headline tested count. Only 10 of 10 returns the board to service.

One edge case misleads people. On a layout with AltGr, the right Alt press lights Left Ctrl and Right Alt together on Windows, because the system sends both. That is expected behaviour, not a stuck Ctrl, so I confirm it by pressing left Ctrl alone first. The Fn key stays invisible either way; if a fault involves Fn, the browser cannot settle it, and I would check the vendor utility instead. The W3C UI Events specification defines location 2 as the right-hand key, which is why the right Shift result is trustworthy.

Troubleshoot a Stuck Key with the Online Keyboard Test

Press the suspect Shift, Ctrl, Alt or Meta several times. A stuck key stays lit after release, while an unresponsive or faulty one never lights up. Sticky or dead keys are common on a laptop or an older membrane board, and a worn switch on a mechanical keyboard behaves the same way. Software settings can mimic the fault, so a result that stays clean here points away from hardware.

Check Ghosting and Key Chatter

Press multiple keys at once, such as Ctrl and Shift together, and see whether each stays lit. A missing key is ghosting, which matters for gaming. Key chatter is one press producing two key registrations; watch the pressed keys and the repeat flag, and plan a repair if it persists.

Browser Limitations of a Free Keyboard Test

Some operating system shortcuts and media keys never reach the page, and a few Command shortcuts are caught first. Print Screen and Escape may be captured first, and Tab only moves focus. Chrome, Safari, Firefox and Edge on Windows, Mac and Linux behave alike, though a different browser sometimes catches a key another one misses. The labels follow physical position, so an ANSI or ISO layout both work.

Your Key Presses Stay Local

Privacy is simple here: the page processes input locally and does not upload anything you type, and a mouse click only sets focus. Read the detected keys, reset when done, and use the modifier key test again after any repair.

Comments and feedback