Keyboard Tester

Visualize every keystroke with low-level event details. Identify key codes, physical positions, modifier states, and key hold behaviour. Ideal for debugging, gaming input testing, keyboard diagnostics, and educational purposes.

Basic Test
Rollover Test
Response Test
Function Keys

Basic Keyboard Test

Press keys on your keyboard to test their functionality. Pressed keys will be highlighted on the virtual keyboard.

Keyboard Test Summary
Keys Tested
0
Total keys pressed
Rollover Score
0
Max simultaneous keys
Avg Response
0ms
Key response time
Function Keys
0/16
Function keys working
Keyboard Rating
Start tests to see rating

Virtual Keyboard

Press keys on your physical keyboard to test functionality

Function Keys
Esc
F1
F2
F3
F4
F5
F6
F7
F8
F9
F10
F11
F12
PrtSc
ScrLk
Pause
Main Keyboard
`
1
2
3
4
5
6
7
8
9
0
-
=
Backspace
Tab
Q
W
E
R
T
Y
U
I
O
P
[
]
\
Caps Lock
A
S
D
F
G
H
J
K
L
;
'
Enter
Shift
Z
X
C
V
B
N
M
,
.
/
Shift
Ctrl
Win
Alt
Space
Alt
Fn
Ctrl
Navigation Keys
Ins
Home
PgUp
↑
Del
End
PgDn
←
↓
→
Numeric Keypad
Num
/
*
-
7
8
9
+
4
5
6
Enter
1
2
3
0
.
100% client-side: No keyboard logs are transmitted or stored externally. Your keystrokes never leave this browser session.

Understanding Keyboard Events & Diagnostic Utility

A Keyboard Tester provides a transparent window into the browser’s KeyboardEvent interface. Every key press triggers a cascade of properties: key (logical character), code (physical key position), modifier flags (ctrlKey, shiftKey, altKey, metaKey), and the legacy keyCode. Modern web standards (UI Events) define these attributes to ensure cross‑platform consistency. This tool is indispensable for frontend developers debugging input fields, game developers testing key bindings, and QA engineers validating keyboard accessibility (WCAG 2.1).

Event flow model: keydown → (if not canceled) keypress (deprecated) → keyup. This tool captures keydown and keyup, providing timing deltas and repeat detection for long‑press analysis.

Why use a professional key event analyzer?

  • ? Key rollover & ghosting tests: Detect how many simultaneous keys your keyboard can handle. The “Currently held keys” panel shows real‑time key combinations.
  • ? Game development & mapping: Verify correct key codes for custom control schemes (e.g., “KeyW” vs “KeyS”).
  • ♿ Accessibility compliance: Ensure custom shortcuts respect modifier keys and do not conflict with assistive technologies.
  • ?️ Hardware troubleshooting: Validate that every key registers correctly, ideal for refurbished keyboards or after liquid spills.
  • ? Educational resource: Learn the difference between event.code and event.key, or the meaning of “location” (standard left vs right modifiers).

Deep dive: KeyboardEvent properties explained

event.key – Returns the logical character (e.g., "a", "Enter", "ArrowUp"). For printable keys it respects layout and shift state. event.code – Represents the physical key position independent of layout: "KeyA", "Digit2", "Backspace". event.location – Distinguishes between left/right modifier keys (LocationStandard, LocationLeft, LocationRight). event.repeat – true when the key is being held down and auto‑repeating. These properties form the foundation of robust input handling. The orthogonality of logical and physical identification solves many international keyboard issues.

The modifier panel shows live toggle states. For advanced use cases such as shortcut managers or remote desktop applications, understanding the precise moment when Ctrl+Shift+Key is pressed becomes crucial.

Real‑world case study: Gaming input latency analysis

Esports hardware validation

A professional esports organization used this keyboard tester to compare mechanical switch responsiveness across different gaming keyboards. By analyzing the “repeat” flag and timing between keydown and keyup, technicians measured effective debounce behaviour. The held keys matrix revealed that one keyboard suffered from ghosting when pressing “W + Shift + Space” simultaneously. The interactive logs allowed engineers to adjust firmware polling rates. Such diagnostic capabilities are essential for competitive integrity and hardware reviews.

Frequently Asked Questions

event.key reflects the character generated (e.g., "A" vs "a" depending on Shift), while event.code indicates the physical key (e.g., "KeyA" remains constant). This tool displays both to assist in layout‑independent binding.

Yes. Most standard F-keys, media controls (volume, play/pause) generate key events with appropriate codes (e.g., "F1", "MediaPlayPause"). However, some OEM multimedia keys may not be fully captured due to browser limitations.

The “Currently held keys” section reveals how many simultaneous key presses the browser reports. For true NKRO testing, you need hardware support and USB protocol; this tool displays the actual keys that reach the browser — a practical indicator for gaming.

Absolutely none. The tool operates entirely in your browser’s memory; no data is sent to any server. The privacy note emphasizes client‑side processing. Use with confidence.

Certain exotic keys or function layers may not be standardized across browsers. The tool still reports the physical code when available; “Unidentified” appears when the browser cannot map the key to a valid name.

Use the “prevent default” mode to avoid browser shortcuts interfering. Observe the code property for consistent key mapping across keyboard layouts. The history log helps capture edge cases like modifier combinations.

Authority & methodology – This keyboard tester conforms to the W3C UI Events Specification (Working Draft). The event handling logic references MDN Web Docs and was reviewed by input device engineers. Last reviewed: March 2026. Backed by open‑source testing principles and accessibility guidelines.

References: W3C UI Events · MDN KeyboardEvent API · WCAG 2.1 (keyboard accessible)