Capture workbench
Focus the capture area, press any key, and review the keyboard event properties you need for shortcut handling, game controls, accessibility testing, or cross-browser debugging.
Keyboard event capture
Click or tab into the capture area if needed, then press a key or shortcut to inspect the properties that your browser reports.
Press any key to inspect it
This panel is ready to capture keydown events, including modifiers like Ctrl, Shift, Alt, and Meta.
How to Use This Keycode Tool
Focus the capture area, press the key or combination you care about, then compare the event properties before you wire up the final keyboard handling logic.
Focus the capture area
Click or tab into the capture panel so your next key press is recorded in the workbench.
Press a key or shortcut
Try a single key like Enter, or a combination like Ctrl+Shift+P to inspect the keyboard event data.
Review key, code, and location
Compare logical key values with physical codes and location details when you need more reliable shortcut behavior.
Check modifiers and copy the event data
Confirm which modifier keys were active, then copy the event snapshot into debugging notes or implementation work.
When This Tool Is Most Useful
It is most useful when you need to understand exactly what the browser reports for a pressed key before building keyboard shortcuts or debugging key handling.
Shortcut implementation
Test which key and code values your browser reports before wiring up keyboard shortcuts in editors, dashboards, or command palettes.
Game and app controls
Inspect movement keys, numpad input, or repeated keydown behavior when you need more reliable interactive controls.
Accessibility and keyboard QA
Verify Enter, Space, and modifier combinations while testing keyboard navigation and a11y behavior in interactive UI.
Cross-browser debugging
See the exact event properties reported for a key when a shortcut behaves differently across browsers or operating systems.
FAQs
What is the difference between key and code?
The key value reflects the logical character or action, while code reflects the physical key position on the keyboard.
Why still show keyCode and which?
They are legacy fields, but they still help when you are debugging older code or working with older event handling logic.
Can I test modifier combinations here?
Yes. Press a key while holding Ctrl, Shift, Alt, or Meta and the modifier state will be shown beside the main event values.
Does this capture data locally?
Yes. The key event is captured in your browser so you can inspect it directly while building or debugging keyboard behavior.