See the event behind a key press. Compare physical codes, typed values, modifier states and input-method composition in one focused debugging view.
Focus the input, press a key or use an IME. See the events this browser actually receives.
Paused. Focus the input to resume. · 0 events observed · latest 200 retained
Tab leaves the input; Escape pauses. System shortcuts, Fn/Globe and Touch ID may never reach a web page. key follows the input layout; code identifies the physical position. location 1/2/3 means left/right/numpad. keyCode is deprecated and shown for legacy debugging. Logs stay on this page. Avoid entering passwords.
Focus the capture area and press the same key with and without Shift or Option. The key value reflects the current layout and modifiers; code describes a physical key position. A different printed character is not automatically a broken key. Use the event log to compare the values.
Press and release one key, then try a modifier with a letter. Compare keydown and keyup entries, location, repeat and modifier flags. Browser-reserved or macOS shortcuts may interrupt the sequence. A missing keyup after a focus change is not enough to diagnose a stuck switch.
With a Chinese input method active, compose a short sample in the input area and commit it. Composition events and isComposing help explain why a keyboard event and final text are different. Event order and values vary by browser and input method; use the final committed text as a separate observation.
Clear the log before a small reproduction case, choose the relevant event type and inspect the resulting sequence. Copy or download a local report when you need to compare sessions. Logs can contain typed characters or composition text: use samples and review the report before sharing.
Read the original documentation behind the browser properties and Mac settings.
About the test, your keyboard, and that one key that won’t light up.
More answersThe main tester answers which keys reach the browser and shows a physical map. The inspector focuses on event properties and sequences for layout, modifier and input-method debugging, rather than key-completion scores.
No. KeyboardEvent.code describes a key position; KeyboardEvent.key depends on the layout and modifier state. Remapping, unusual devices and browser support can also affect delivered values.
No. The inspector only records input directed to its focused input area; it cannot monitor other applications or override all system shortcuts. Do not enter passwords or private information here: copied JSON and downloaded JSON or CSV can contain raw key values, typed text and input-method composition text.
From missed keys to double taps. Find the right Mac keyboard test for the job.
Meet every key. Check your MacBook or Magic Keyboard, one press at a time.
Hold one key. Check the delay before repeat and its steady rhythm.
Find your flow. Measure your typing speed and accuracy.
Hold a few keys together. See which combinations make it through.
Tested in your browser. No accounts, no keystroke uploads, no fuss.
