Run a complete keyboard key test in your browser — press each key and watch it turn green, with a live score as you go.
Simply press any key on your keyboard to test it — if it works it will turn green
0Keys Pressed0Total Keys0%Tested
QWERTY on the US ANSI shape: a wide flat Enter and a full-length left Shift. Standard key positions, with no vendor-specific extras.
Ctrl+W, Ctrl+T, Ctrl+N, Alt+Tab and the Windows or Command key are reserved by the browser and the operating system. No web page receives them, so they cannot be tested here or anywhere else in a browser.
Keys shown greyed out with a dashed outline cannot be tested: your keyboard handles them internally and the browser never receives a key event for them. They are excluded from the totals, so 100% stays reachable.
At a glance
Key counts and layout facts
Detail
Value
What it tests
Whether each key reaches the browser
What it cannot test
Fn, Touch ID and vendor media keys
Layouts covered
QWERTY, QWERTZ, AZERTY
Form factors covered
Full size to 60%, laptop and Apple
Data sent anywhere
None — it runs on your device
Install required
No
Works offline
Yes, once the page has loaded
Browsers
Chrome, Firefox, Safari, Edge
A keyboard key test in numbers
What a single pass over the board actually establishes.
104
Keys on the default boardSwitch the form factor to match your own hardware.
60
Seconds for a full passWorking row by row rather than at random.
Downloads requiredThe test runs in the browser and stores nothing.
How to run a keyboard key test
Three steps, and the first one decides whether the score means anything.
1
Select your keyboard layout
Pick the platform, then the form factor matching your hardware, then the character layout. Testing a 60% board against a full-size diagram leaves 44 caps permanently blank and tells you nothing.
2
Press every key once
Work left to right along each row. Every key that reports turns green and stays green, so the white caps are the keys still to test. Press both Shift keys, both Ctrl keys and both Alt keys — each sends its own code.
3
Read the score and investigate the gaps
The counter shows tested keys against the total for your board. A cap still blank after a deliberate press is a key that sent nothing, which narrows the fault to that switch, the controller, the connection or software claiming the key.
What a key test proves and what it does not
Six things worth knowing before you read your result.
A blank cap is not always a broken key
Software can claim a key before the browser sees it. Screen-capture tools take Print Screen, and macro software takes the function row. Close those and retest.
Green means the code arrived, not that the right letter typed
If the correct cap lights but the wrong character appears, the keyboard is working and your system input language is set to a different layout.
A key test does not catch chatter on its own
Chatter is one press producing two characters. Watch for a cap that flickers rather than holding colour, then confirm in a text field.
Single presses do not test rollover
Keys that work alone can still fail in combination. Hold three or more at once to check that separately.
Fn can never be tested
Fn is handled inside the keyboard and reaches no browser. It is drawn hatched and excluded from the total, so 100% stays reachable.
One machine is not a diagnosis
A key failing here and working on a second computer points at software. A key failing on both points at hardware.
Everything about this layout
The shape, the trade-offs and what to watch for when testing it.
01
How a key test works
When you press a key, the controller inside your keyboard sends a scancode over USB or Bluetooth. Your operating system turns that into a key event and hands it to whatever application has focus. This page listens for those events and lights up the matching key.
That chain has several links, and a key test tells you whether the whole chain is intact — not which link is broken. A key that fails here could be a dead switch, a broken trace, a loose cable, a driver problem, or another program intercepting the key before the browser sees it.
What it does prove is definitive in one direction: if a key turns green, everything from the switch to the browser is working. The problem is then in whatever application was ignoring it.
02
Reading the results
Three numbers sit under the board. Keys Pressed counts the distinct keys that have reported so far. Total Keys is how many the selected layout has. Tested is the percentage between them.
The total deliberately excludes keys no browser can ever see. Fn is the main one: it is handled inside the keyboard to change what other keys send, and it never becomes a key event. Touch ID on a MacBook is the same — a sensor, not a key. Both are drawn with dashed outlines and left out of the count, so 100% stays reachable on every layout.
If a key lights up but flickers rather than staying lit, that is a different fault called chatter: the switch is bouncing and sending several presses for one push. This test will show it as green either way, so check in a text field if you suspect it.
03
What to do about a key that fails
First, rule out software. Test the same key on another device, or in another application. A key that works elsewhere is not a broken key — it is a program, a remapping tool, a stuck modifier or a language layout getting in the way.
Second, rule out mechanical obstruction. Debris under a cap and a slightly crooked keycap both produce keys that feel normal and report nothing. Compressed air across the switch clears most of it.
Third, if the key fails everywhere and cleaning does not help, the switch or the membrane beneath it has failed. On a hot-swap mechanical board that is a two-minute fix. On a laptop it usually means replacing the keyboard assembly.
04
Choosing the right layout to test against
The score only means something if the board on screen matches the board in front of you. Test a 60% keyboard against a full-size diagram and you will never pass 60%, because forty keys you do not physically have will stay dark.
Use the Form Factor dropdown to pick your board, or go to one of the dedicated layout pages, which open already set to the right one. If you are not sure what yours is called, count the keys: 104 or 105 is full size, about 87 with no number pad is tenkeyless, arrows crammed under the right Shift with no function row is 65%, and no arrows at all is 60%.
If your board is European rather than American, switch the Key Layout dropdown to QWERTZ or AZERTY as well. Those are ISO boards, with a tall Enter and one extra key.
Pick the board that matches your hardware
The total changes with the layout, so the score only means something once it matches.
Testable key count and features by layout
Layout
Testable keys
Function row
Arrow keys
Number pad
Full size (100%)
104
Yes
Dedicated
Yes
Tenkeyless (TKL)
87
Yes
Dedicated
No
75% compact
83
Yes
Integrated
No
65% compact
67
No
Integrated
No
60% mini
60
No
Fn layer
No
15.6 inch laptop
100
Yes
Integrated
Squeezed
ISO versions add one key beside a shortened left Shift, raising each count by one.
When the key test fails
Four results and what each one means.
1One key stays blank
On the test:A single cap never turns green while everything around it works.
Press the key ten times and count how many register. Zero means a hard fault, three of ten means a dirty contact.
Close screen-capture and macro tools, then retest.
Test the same key on a second computer to separate hardware from software.
Pull the keycap and inspect the switch for debris or a bent stem.
2A straight line of keys fails together
On the test:Neighbouring caps go blank in a row or a column.
Note the pattern. A line means a shared matrix trace, not several dead switches.
Reseat the internal ribbon connector on a desktop board.
Try another USB port and cable.
Expect liquid damage if the failure followed a spill, which follows the same trace pattern.
3Nothing registers at all
On the test:No key lights on any press.
Click once on the page. A browser only delivers key events to a focused document.
Check the keyboard works elsewhere, in a text editor or at the login screen.
Try a different port, cable or Bluetooth pairing.
Confirm JavaScript is enabled — the test reads key events and cannot run without it.
4The score will not reach 100%
On the test:Most keys are green but the counter stops short.
Check the layout selector matches your board. A mismatch leaves keys drawn that you do not have.
Look for the caps still white and press those specifically — Scroll Lock, Pause, Menu and the right Windows key are the usual stragglers.
Remember Fn is excluded from the total, so its hatched state never blocks 100%.
Frequently asked questions
How do I test if my keyboard keys are working?
Press each key and watch the board on this page. Any key that reaches your browser turns green and stays green. Work through the board systematically rather than at random, because the percentage only reaches 100% when nothing is missed.
Why does my Fn key not register?
No website can detect it. Fn is handled inside the keyboard's own controller to change what other keys send, so it never becomes a key event. It is drawn greyed out here and excluded from the total, which is why 100% is still reachable without it.
Does this keyboard test record what I type?
No. Everything runs in your browser on your own device. Key events are read, drawn to the screen and discarded when you close the tab. Nothing is uploaded, stored or logged.
A key works here but not in my game. Why?
Because the key is reaching your browser, the hardware is fine. The problem is in the game or in something running alongside it — a keybinding, an overlay, a macro tool, or the game itself blocking that key. It is also worth checking for ghosting, which stops certain key combinations registering together.
Can I test a laptop keyboard here?
Yes. Choose your laptop size from the Form Factor dropdown, or use the dedicated laptop keyboard tester, which opens already set to the right layout.
Test another keyboard
Every layout below opens with its own board ready to test.
