Skip to content
ZeroServer.tools

Keyboard Tester

Press each key and watch it light up. Find keys that are dead, stuck or typing twice. Your keystrokes stay in this tab.

Board
Shape
Keys
0 of 104 keys pressedFull size, ANSI, 104 keys

Press every key once: each lights up green as the browser receives it, and blue while it is held. Hold several keys at once to see how many your keyboard sends, and hold one for two seconds to measure its repeat. To leave the test with the keyboard, press Esc, then Tab.

Held now

0

Most at once: 0

Possible chatter

0

No key pressed again within 50 ms of its release.

Under

Key repeat

Hold one key down for two seconds to measure your repeat delay and rate.

Other keys

Keys this drawing has no place for, such as media keys or F13, are listed here.

Not pressed yet (104)
  • Esc
  • F1
  • F2
  • F3
  • F4
  • F5
  • F6
  • F7
  • F8
  • F9
  • F10
  • F11
  • F12
  • PrtSc
  • ScrLk
  • Pause
  • `
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 0
  • -
  • =
  • Backspace
  • Tab
  • Q
  • W
  • E
  • R
  • T
  • Y
  • U
  • I
  • O
  • P
  • [
  • ]
  • Caps Lock
  • A
  • S
  • D
  • F
  • G
  • H
  • J
  • K
  • L
  • ;
  • '
  • \
  • Enter
  • Left Shift
  • Z
  • X
  • C
  • V
  • B
  • N
  • M
  • ,
  • .
  • /
  • Right Shift
  • Left Ctrl
  • Left Win
  • Left Alt
  • Space
  • Right Alt
  • Right Win
  • Menu
  • Right Ctrl
  • Ins
  • Home
  • PgUp
  • Del
  • End
  • PgDn
  • Up arrow
  • Left arrow
  • Down arrow
  • Right arrow
  • Num Lock
  • Numpad /
  • Numpad *
  • Numpad -
  • Numpad 7
  • Numpad 8
  • Numpad 9
  • Numpad +
  • Numpad 4
  • Numpad 5
  • Numpad 6
  • Numpad 1
  • Numpad 2
  • Numpad 3
  • Numpad Enter
  • Numpad 0
  • Numpad .

Key log

Each key event appears here with its key, code and time since the one before.

How the keyboard tester reads your keys

Every key press reaches a web page as two events, keydown and keyup, and each carries a code naming the key's position on the board, such as KeyQ for the key right of Tab. The tester lights the key of that position, so a French AZERTY board, where that key types A, lights the right key too; in Chrome and Edge the drawing also shows your own letters. A key that never lights up sent nothing to the computer: a worn switch, a broken trace, or a key the keyboard keeps to itself, as it keeps Fn.

A key held down is sent again and again by the operating system, after a delay, as repeats the page tells apart from presses; holding one measures that delay and rate. A press that comes within 50 ms of the same key's release, or 30 or 80 ms if you choose, is marked as possible chatter: a worn switch bounces as it opens or closes, and its phantom press follows a release by a few milliseconds, sooner than a finger can press again. Nothing you type is sent anywhere: the record lives in this tab and is gone when you close it.

What this tool is used for

  • Checking a second-hand keyboard, or a laptop's, key by key before buying it or handing it back.
  • Finding which key of a mechanical keyboard types letters twice, before cleaning or swapping its switch.
  • Making sure no key was left dead after building a keyboard, changing its switches or putting its keycaps back.
  • Checking how many keys a gaming keyboard sends at once, for games that need several held together.
  • Finding a key that seems stuck: Held now lists every key the browser still counts as held down.
  • Seeing what media keys and Fn shortcuts send, such as Play/Pause or Volume up, under Other keys.

How it works in practice

A worked example

A mechanical keyboard bought a year ago now and then types "heello" for "hello". Its owner wants to know whether a switch is failing, and which, before opening it up.

Input
Board: Full size, ANSI. Possible chatter: Under 50 ms.
R, T and Y: ten presses each, held 90 ms, one every 400 ms.
E: ten presses the same way, a phantom press of 5 ms
following three of its releases by 11, 7 and 4 ms.
Output
Possible chatter: 1
E: 3× within 50 ms of its release, shortest 4 ms

Key log, newest first:
Event  key  code  After
up     e    KeyE   5 ms
down   e    KeyE   4 ms
up     e    KeyE  90 ms
down   e    KeyE 310 ms

Report: Possible chatter (pressed again within 50 ms of release): E 3x, shortest 4 ms

A press closes a switch and a release opens it, and the switch's metal contacts bounce for a moment each time; the keyboard ignores changes for a few milliseconds, its debounce, to hide that. A worn or dirty switch bounces for longer, and the keyboard reports the extra closing as a second press: in the log, E's release after 90 ms was followed by a press 4 ms later, too soon for a finger. The page measures that gap from each key's own release, so a phantom press is caught however long the key was held, and it counts per key. R, T and Y, pressed the same way, showed none, so the fault is E's switch rather than the cable, the receiver or the computer. Cleaning the switch, or replacing it on a hot-swap board, is the usual fix; some keyboards' software can lengthen the debounce instead.

The edge case that catches people

Auto-repeat is not chatter. E held down for two seconds, repeating as Windows does by default, sent 46 repeats; the browser marks each as a repeat, and the page logged them so, measured a first repeat after 500 ms and then one every 33 ms, 30.3 a second, and counted no chatter. If letters double only when a key is held a little long, lengthen the repeat delay in the system's keyboard settings rather than blaming the switch.

When not to use this tool

To see every field of the events a web app receives, such as keyCode and which, use the JS keycode tester. A key that types the wrong character, rather than none or two, points to the layout chosen in the operating system, not to a fault; in Chrome and Edge the drawing's legends follow that layout, so compare them with your keycaps. And the tester sees what a keyboard sends after its own software has remapped it: a remapped key lights up as the key it now sends.

Frequently Asked Questions

How do I find a dead key?
Pick the board that matches yours, then press each key once. A key turns green the moment the browser receives it, and Not pressed yet lists every key still unlit. A key that stays unlit after a firm press sent the computer nothing: a worn switch, dirt under it or a broken trace.
How does the tester tell chatter from a fast double tap?
By the time from a key's release to its next press. A bouncing switch adds its phantom press a few milliseconds after a release, sooner than a finger can, so a press within 50 ms of its own release is marked amber, with the shortest gap shown. 30 ms is stricter; 80 ms catches more, and more fast taps.
Why is the Fn key drawn with a dashed outline?
On most keyboards Fn is handled inside the keyboard, which uses it to change what its other keys send, so no event reaches a web page. The 75% and 60% drawings show it dashed and leave it out of the count; it lights up only if your browser does report it. Test its shortcuts instead: a media key shows under Other keys.
What does Most at once say about rollover?
It is the largest number of keys the browser saw held down together. A keyboard using the basic report every computer understands sends six keys plus the modifiers; many gaming boards send them all, and some cheap ones drop a key in certain groups of three. Hold keys down one after another to find your limit.
What do the key repeat numbers mean?
Hold a key and the system types it again after a pause, then again and again. The tester times that pause and the repeats per second from the browser's own timestamps. On Windows, the Repeat delay and Repeat rate sliders of Control Panel's Keyboard settings set both; by default, about 500 ms and about 30 a second.
Which boards and layouts can I test?
Full size, TKL, 75% and 60% boards, each in the ANSI or the ISO shape, with Windows or Mac legends. Keys are matched by where they sit, not by what they type, so AZERTY, QWERTZ and other layouts light the right keys, and Chrome and Edge draw your own letters on them.
Why can't I test Ctrl+W, Alt+F4 or Print Screen like other keys?
The browser and the system act on some shortcuts before a page can, Ctrl+W closing the tab and Alt+F4 the window, so test such keys one at a time. Full screen asks Chrome and Edge to pass more keys to the page. Print Screen counts on its release alone, as Windows keeps its press.
Is anything I type sent or saved?
No. The record lives in this tab's memory and is gone when you press Reset or close the tab. Copy report and Download report put a summary on your clipboard or in a file on your computer. Nothing is uploaded, and the page needs no network once it has loaded.

Common errors and gotchas

  • Testing while focus is elsewhere, such as in the site's search box: keys then go there, and the drawing says Paused. Click the drawing to go on testing.
  • Taking the dashed Fn key for a fault. On most keyboards Fn is handled inside the keyboard and never reaches a computer; check the keys its shortcuts send instead.
  • Pressing Ctrl+W, Ctrl+T or Alt+F4 to test those keys together: the browser or Windows acts on them first, closing the tab or the window, or opening a tab.
  • Judging a key by one amber mark after a very fast double tap, which can come within 50 ms of a release. Press it at a normal pace a dozen times: a chattering switch keeps doing it.
  • Leaving the drawing on full size for a 60% keyboard, whose 44 missing keys then stay unlit. Pick the board that matches yours.

Related Developer Utilities tools

Private & free — this tool runs entirely in your browser.

IndieKit — Ship your Next.js startup in days.affiliate