About this keyboard tester
Test keyboard input by viewing keydown and keyup events in a focused test area. Each event reports the physical key code, interpreted key value and whether the key is pressed or released.
Physical codes such as KeyA describe the key position, while values such as a depend on layout and modifier state. The last twenty events appear in order. Start test focuses the dedicated area, and Stop test stops recording new events.
The browser may intercept operating-system shortcuts, media keys and security-sensitive combinations before the page receives them. This checks received events rather than electrical keyboard health. Tab can move focus away, and the tester does not record keys typed into other applications.
Using Keyboard Tester starts with the Start button. Pressing and releasing the A key records KeyA with pressed true followed by KeyA with pressed false. Select Start keyboard test to update the result below the controls. Read the output together with the keyboard tester limitations described here before using it in a document, project or decision. Change one input at a time when comparing alternatives so that you can identify which change affected the result.
Which controls should I check first?
The Keyboard Tester form labels its controls as Result. Use those labels to keep the source and settings separate. A sample argument that selects a mode is not additional source text. Choose the setting matching your intended operation before copying a result, and change it explicitly when comparing another mode. The labels describe what this form accepts; the worked examples below demonstrate only the stated supplied values.
Worked helper values
These values come from the reproducible calculation examples supplied with this tool. Each row identifies the complete supplied arguments and the returned value. A visible ↵ denotes a line break and ⇥ denotes a tab in text examples. Settings appear alongside source data so that a different mode is not mistaken for an identical input. These are helper calculations, not observations of a live device, fetched target, image decoder, browser preview or downloaded file. Use the stated method above to relate the returned fields to the actual operation.
| Supplied values | Calculated return value |
|---|---|
| KeyA; a; true | {"code": "KeyA", "key": "a", "pressed": true} |
| KeyA; a; false | {"code": "KeyA", "key": "a", "pressed": false} |
Which part of the device am I observing?
A browser device test observes only the stream or events that the browser exposes. It does not inventory every setting in the operating system, measure analog calibration, or confirm another application's access. Select the intended input in the browser or system settings before comparing results. A camera's decoded frame dimensions describe the stream, while a microphone's amplitude describes a digital signal. A keyboard event combines a physical position code with a layout-dependent character value. Keep those layers distinct so that an unexpected reading leads to the relevant setting rather than a guessed hardware fault.
How should I handle permission and focus?
Camera and microphone access depends on browser permission and an environment where those APIs are available. A denied request means the page did not obtain the requested stream; it is different from obtaining a silent microphone or a dark camera image. Keyboard input requires focus in the test area. If events stop appearing, restore focus and check whether the browser or operating system intercepted the key combination. Do not broaden the test to unrelated hardware. Start with an ordinary key or a short spoken sample so that the expected observation is easy to identify.
What should a useful small test look like?
Choose a simple stimulus and observe one result at a time. Press and release a letter key, speak at a steady volume, or point the camera at a well-lit static scene. Then change one setting and compare. A keyboard's release state should be distinct from its pressed state. A microphone can show background noise even when nobody speaks. A camera can report dimensions while displaying a poor image because exposure and focus are separate matters. Note the selected source and the environment beside your observation instead of treating a single number as a complete device diagnosis.
Why are helper examples insufficient for a live test?
The calculation examples show how sample arrays, dimensions or key-event values become displayed fields. They do not request a real device stream, grant permission, test the operating system driver or exercise browser rendering. A live device check requires an observed event or stream in that browser. A computed pixel count, for instance, establishes width multiplied by height but cannot prove that a webcam delivered those dimensions. Keep the arithmetic example useful for understanding the output while keeping the actual hardware observation separate in any troubleshooting report.
How do I use keyboard tester?
Pressing and releasing the A key records KeyA with pressed true followed by KeyA with pressed false.
What does keyboard tester support?
Physical codes such as KeyA describe the key position, while values such as a depend on layout and modifier state. The last twenty events appear in order. Start test focuses the dedicated area, and Stop test stops recording new events.
What are the limits of keyboard tester?
The browser may intercept operating-system shortcuts, media keys and security-sensitive combinations before the page receives them. This checks received events rather than electrical keyboard health. Tab can move focus away, and the tester does not record keys typed into other applications.