Windows Keyboard Tester
Check received key presses and releases on full or tenkeyless Windows-style diagrams. Compare Win, navigation and keypad codes or preview keycaps in a separate touch simulation.
Compare Windows Numpad and Digit Row Events
Capture paused.
Main keys
Navigation
Numeric keypad
Check Win, Menu, navigation and keypad codes on the chosen ANSI diagram. Reserved shortcuts and firmware keys may be handled before the browser receives them.
- Distinct records
- 0
- Held now
- 0
- Maximum held
- 0
- Events received
- 0
- Latest event
- Waiting for a key event
- Key
- —
- Code
—- Location
- —
- Left Shift · released
- Right Shift · released
- Left Control · released
- Right Control · released
- Left Alt · released
- Right Alt · released
- Left Win · released
- Right Win · released
- Caps Lock · unobserved
- Num Lock · unobserved
- Scroll Lock · unobserved
Windows Keyboard Tester: how to use it
- Choose Windows full ANSI or Windows tenkeyless ANSI and start the focused keyboard test.
- Press the digit-row 1 and keypad 1 separately. Check Digit1 and Numpad1, alongside their locations. Review right and left modifiers when each is available.
- Review recent events or export the report. Select Simulate a key to try keycap highlights with a mouse or touchscreen.
Limits and notes
The diagrams depict representative ANSI positions. Results come from DOM events inside the focused test area. The browser or operating system may reserve shortcuts and firmware keys. The session stays in memory until you clear it or leave, with up to 40 recent events in the report. Simulation changes the diagram only. Lock states report the last observed event. Windows can consume system chords such as Ctrl+Alt+Delete.
How your privacy works →Windows Keyboard Tester: common questions
Can I distinguish keypad 1 with Num Lock off?
Check the physical code Numpad1 and location 3 if reported. The key value can change to End when Num Lock is off.
What does a release without a captured press mean?
The browser delivered a keyup event without a matching keydown active in the session. Focus changes or OS shortcuts can cause this sequence.
Does tapping a key prove the physical switch works?
Simulate a key previews the visual state. Start the focused test and use the physical keyboard to gather browser events.