— · keyCode —Keyboard test
Click the keyboard below and press any key to light it up
Needs a physical keyboardOn-screen keyboards on phones and tablets send different events from physical ones, and many keys never appear at all, so they cannot test physical keys. Use a desktop or an external keyboard.
The test area listens only while it holds focus, and it keeps Tab, Space and the arrow keys so you can test those too; press Esc to leave it. Switching tabs or navigating away releases every held key.
key is the character this press produced, so it moves with the layout, Shift and your input method. code is where the key sits on the keyboard and does not change with the layout. Showing both is what separates "wrong key" from "different layout".
This drawing shows physical positions (US ANSI 104), not the legends printed on your keyboard: the top-left letter on AZERTY still reports KeyQ. What you actually typed is the key value below.
Hold several keys at once: check for ghosting and blocked keys
Hold down the keys you use together (W, A, Shift and Space, say) and check that each one lights up; the count is what this browser received at once, not a certification of n-key rollover (NKRO) or of your keyboard.
You have not held two or more keys at once yet.
The operating system, the connection (USB or Bluetooth) and the browser can all lower how many keys get through together. If one key drops out when you press a certain group, or a key you did not press lights up, that points to key blocking or ghosting; try the same keys on another computer to compare. Groups that include Command (Mac) or the Windows key are left out of this count: while Command is down, a Mac does not tell the browser that other keys were released.
Chord watch
Press the chord you want to check once (say Ctrl+Shift+K), let go, then press "Set as target". Every press after that shows whether those keys reach the browser together.
No chord chosen yet.
Gap between presses
Recent browser events
No events yet
Some keys never reach the page: Fn, system shortcuts (Alt+Tab, Cmd+Tab) and browser-reserved combinations (Ctrl+W, Ctrl+T) are taken by the operating system or the browser first. A missing event is not a broken key.
When a key sends nothing, compare in another browser or on another computer before blaming the hardware.
Browser keyboard events · no permissions needed
What the keyboard test shows
Press any key and see what the browser actually receives. The character (key) and the physical position (code) are shown separately, and you can watch whether a chord arrives together.
Keyboard test FAQ
Why does the Fn key do nothing?
Fn is usually handled inside the keyboard and never sent to the computer, so a web page cannot see it. That is normal. Fn plus another key sends the result, such as volume or brightness; some of those show up under keys not on the map, and some are taken by the system first.
What are ghosting and key blocking?
Key blocking (masking) is when one key of a group pressed together never gets sent. Ghosting is when pressing a group produces an extra key you did not press. Many keyboards only do this with particular combinations, so test the keys you actually use together: hold them down in the test area and look for one that stays dark or one that lights up without being pressed.
Can this tell me whether my keyboard has n-key rollover (NKRO)?
Not as a certification. A web page only sees the keys the browser receives, and the operating system and the USB or Bluetooth connection also limit how many keys arrive together, so the number here only says what reached this browser on this computer. Check the maker for the specification; to know whether your usual combination works, pressing those keys is the most direct test.
How do I test a laptop keyboard?
Choose Laptop under keyboard size. The map drops the number pad and the Insert, Home and Page Up block; laptops often need Fn to send those keys, and when they arrive they light up in their usual place or appear under keys not on the map. On a Mac, switch the key names to Mac.
Does an input method (IME) affect the test?
It affects key: while an input method is composing, the browser often receives Process as the key and 229 as the keyCode instead of the character you pressed. code is not affected, so the map still lights the right position. Switch to a plain English input before checking key values.
What is keyCode, and why is it different from code?
keyCode is an older numeric code. Current web standards recommend key and code instead, but older programs, games and tutorials still use keyCode, so it is listed for comparison. The same key can report a different keyCode across browsers and layouts, and it is always 229 while an input method is composing.
More device tests
- Mouse test
Buttons, double clicks, scroll wheel and clicks per second, all in one workspace.
Start testing → - Sound test
Left and right channels, test tones and a frequency sweep.
Start testing → - Mic test
A live level meter, a clip you can play back, mic switching and fixes for blocked permissions.
Start testing → - Webcam test
A live preview with the real resolution and frame rate, camera switching and mirroring.
Start testing → - Touch screen test
How many fingers your screen registers at once, where each one is, and which squares never got a touch.
Start testing →