Keyboard Event Viewer: Key, Code and Modifiers
Click the area below, then press your keys. Press physical keys or hold combinations. Automatic key repeats are identified separately. Browser and operating-system shortcuts may not reach the page.
Results
—
What the keyboard event viewer lists
Click the test area and press keys. Each key down or key up shows the code, the key label, the location, and the repeat flag, so you can see what this browser actually received.
System and browser shortcuts may never reach the page. Code names the key position, and key is the character or label. The list is a log of events, not proof that every hardware switch works.
Common questions
Why is a shortcut missing from the log?
The browser or the system can handle it first. If no event arrives, this viewer cannot describe that keypress.
What is the difference between key and code?
Code names the position, such as KeyA. Key is the label or character, such as a. Location and the repeat flag sit beside them.
Does the repeat flag mean the switch bounced?
No. It marks automatic repeat while a key is held. It is a property of the event, not a fault finding.
How to use this tool
Click the area below, then press your keys. Press physical keys or hold combinations. Automatic key repeats are identified separately. Browser and operating-system shortcuts may not reach the page.
| Results | Method and units |
|---|---|
| Recent events | KeyboardEvent.code / key / location / repeat |
Example
Recent events: keydown / key=a / code=KeyA / location=0 / repeat=false
What this test can and cannot tell you
Results reflect events and signals available to your browser. Settings, permissions and device support can affect them; they do not certify that hardware is healthy or faulty.