Quick answer
What Key Code Tester tells you
Inspect modern KeyboardEvent properties and copy the current event as JSON without relying on deprecated keyCode values.
- Observed here
- key and code, location and repeat, modifier flags.
- How to interpret it
- key reports the interpreted key value, code identifies the physical-key position, and location distinguishes left, right or keypad keys where reported. These are browser event properties, not scan codes from the keyboard firmware.
- Important limit
- Results reflect events and values exposed by this browser.
- Data handling
- Key events and typed text stay in this browser. They are not sent to our server or analytics.
Useful next comparison: Compare the same physical key with and without Shift and with the intended operating-system keyboard layout selected.
Understanding the result
What a result means
key describes the value produced by the current layout, while code describes a standardized physical position. location separates standard, left, right and number-pad controls; repeat becomes true only after the operating system begins held-key repetition.
Confirm the pattern by repeating key and code. Results reflect events and values exposed by this browser.
How to use this test
- Read the privacy and compatibility notes.
- Start the test and interact only inside the marked test area.
- Repeat the action several times and compare the live indicators.
- Use the troubleshooting section before deciding that hardware is faulty.
What this test checks
- key and code
- location and repeat
- modifier flags
- event type and timestamp
What this test cannot check
Results reflect events and values exposed by this browser.
This test does not certify hardware or replace professional inspection.
The deprecated keyCode field is intentionally not used for logic.
Common problems and troubleshooting
Finish any active IME composition and release all modifiers before comparing an unexpected value. If an application behaves differently from this page, inspect that application’s shortcut handling and do not fall back to deprecated numeric keyCode assumptions.
- Repeat the same observation. Focus the test surface and repeat “key and code” three times under the same conditions.
- Change one condition. Compare “location and repeat” after changing only the relevant port, connection, browser setting or application.
- Rule out focus or interception. Close overlays and reserved shortcuts, keep the page visible and confirm that the live indicator changes during the action.
- Keep the result within its limit. Results reflect events and values exposed by this browser.
If the same pattern remains across relevant applications and connections, give the manufacturer or a qualified technician the repeatable observations instead of a guessed fault label.
Browser compatibility
KeyboardEvent properties are widely available, but composition, dead keys and reserved shortcuts vary by platform. The page reports the event it receives and does not claim that every browser exposes identical text-input sequences.
| Browser | Reference status | Evidence basis | Version | Notes | Checked |
|---|---|---|---|---|---|
| Chrome | Supported | Expected baseline | Not recorded | Feature detection is authoritative; permissions, platform and device support can change availability. | 2026-08-27 |
| Microsoft Edge | Supported | Expected baseline | Not recorded | Feature detection is authoritative; permissions, platform and device support can change availability. | 2026-08-27 |
| Firefox | Partial | Expected baseline | Not recorded | Feature detection is authoritative; permissions, platform and device support can change availability. | 2026-08-27 |
| Safari | Partial | Expected baseline | Not recorded | Feature detection is authoritative; permissions, platform and device support can change availability. | 2026-08-27 |
Privacy information
Key events and typed text stay in this browser. They are not sent to our server or analytics.
The public analytics allowlist does not accept pressed keys, typed text, pointer coordinates, media labels, device IDs, recordings, video frames or controller input. Test results are not written to LocalStorage.
Primary technical references
These specifications define the browser signals used by this test. They document web-platform behavior; they do not certify a particular device.
Frequently asked questions
Is this Key Code Tester free?
Yes. The test works without an account, download or payment.
Is my test data uploaded?
Key events and typed text stay in this browser. They are not sent to our server or analytics.
Does this result prove my hardware is faulty?
No. It shows what the browser can observe. Repeat the test, compare another browser or device, and seek qualified support when the result matters.
Turn this result into a useful comparison
A working indicator or an unexpected event is only a starting point. Choose a plan to compare another application or connection and record what changed.
- Plan a Missing Keyboard Input Check — Separate page focus, layout and connection problems with a three-comparison keyboard worksheet and a clear record for support.