Mac Keyboard Test
A keyboard test for Mac: press Start, then press every key on your MacBook or Magic Keyboard. The Mac layout (Command, Option, no numpad) is drawn by default, keys light up by physical position, and the page watches for keys that type twice or stay down. macOS has quirks that fool simpler keyboard testers; this page accounts for them. Nothing you type leaves this page.
1. Test
Press each key once. Green means your browser received it. Striped keys (like Fn) never reach a browser, so they are not counted. When you are done, press I've pressed every key so anything missing is reported.
While the test runs, keys do nothing else on this page. Stop with the button, or hold Escape for two seconds.
Advanced
Last events, as your browser delivered them (shown live, never saved):
| type | key | code | location | repeat | modifiers | time (ms) |
|---|
2. Result
Is it the keyboard or the computer?
Save the JSON here, run the test again with the keyboard on another computer or USB port, then load the first file. If the same problem shows up on both, it follows the keyboard.
In this browser
About the Mac Keyboard Test
How to use it
- Open this page in Safari, Chrome or Firefox on your Mac and press Start test.
- Press every key once. Press the function keys with and without Fn if you want to see both their F-key and media behaviour.
- Press I've pressed every key so any key that never arrived is listed.
- If a key types twice, open the Chatter check tab and press it 30 times.
What this page focuses on
- Starts on the Mac layout: Command and Option in their Mac positions, no numpad, the function row as on a MacBook.
- macOS does not report a key being let go while Command is held. Other testers show that as a stuck key; this page ignores it and does not report a fault.
- Fn and Touch ID are handled inside the Mac and never reach a web page, so they are marked as not testable instead of missing.
- Double typing (chatter), common on some MacBook keyboards, is checked on every key, with a guided 30-press check for a single key.
Reading your result
- A key stays lit while Command is held: That is macOS, not the keyboard. Let go of Command and the page clears it.
- Brightness or volume keys missing: macOS usually handles these before a browser sees them. Hold Fn while pressing them to send F1 to F12 instead, which a page can receive.
- Double typing on a MacBook: A chatter verdict on the same key across several runs points to the switch. Apple has run keyboard service programs for some models; the saved result is useful evidence.
Why doesn't Fn light up?
Fn is read by the keyboard and macOS before any app or browser sees it. No web page can test it. To check Fn, see whether Fn plus a function key changes brightness or volume.
A key looks stuck while I hold Command. Is it broken?
Probably not. macOS does not tell browsers when other keys are released while Command is down. Release Command and the page clears them.
Some keys type the wrong character. Is that the keyboard?
Usually it is the input source setting in macOS (for example British instead of U.S.). The page tells you when the characters match a different layout rather than a hardware fault.
What a browser cannot test
Fn is handled inside the keyboard and never reaches any web page. Brightness, volume and media keys are often taken by your system first. Browser and system shortcuts (Ctrl+W, Alt+Tab, the Windows key) are kept by the browser or system, except in Full keyboard mode in Chrome and Edge. Ctrl+Alt+Delete cannot be tested anywhere. No web page can measure keyboard latency, scan rate or polling rate, or certify a rollover (NKRO) rating, and this one never claims to.
Privacy
The test runs entirely in your browser. Nothing you press is uploaded, and nothing is saved after you close or refresh the page. Saved files are created on your device and only go where you send them.