Press every key and watch it light up on a full-size, tenkeyless, 75%, ISO, or Mac laptop layout. See the key, code, and keyCode each press sends, which keys have not registered yet, which ones type twice, and how many keys your board reads at once.
Keys fill while held and keep a tick once released. They are matched by physical position, so the drawing lines up whatever language your keyboard types.
Keys work normally on this page until you start. Press Start capture or click the keyboard, then press every key once.
Leave out Ctrl+W, Cmd+W, Cmd+Q, and Alt+F4: they close the tab or the browser, and no web page can stop them.
The drawing is visual only. Each press is announced, and the lists below name every key that has registered, every key still untested, and every key flagged for chatter. Press Escape twice within one second to pause.
Full-size ANSI: 104 keys: function row, navigation cluster, and numpad, with the wide US Enter. Dashed keys are drawn for orientation only: Fn and Touch ID work inside the keyboard and never send anything a web page can read. Brightness, volume, and media keys usually stop at the operating system too.
0 / 104 keys · scroll sideways for the whole board
Start capture and press any key. Everything the browser reports about it lands here.
Totals for the selected layout. Switching layout re-sorts the presses you have already made.
Hold several keys together, such as the ones you use at once in a game, to measure rollover and spot ghosting.
A key is flagged when it reports a fresh press less than 50 ms after it was released, which is quicker than a finger can lift and press again.
No chatter so far. A key that types twice from one press is listed here with the gap that gave it away. To check a suspect key, tap it slowly about twenty times.
Keys this keyboard sent that the selected layout does not draw: media keys, an ISO or Japanese key, or a numpad on a smaller layout.
Nothing extra so far. Volume or media keys that reach the browser, the ISO key beside left Shift on an ANSI drawing, or numpad keys on a tenkeyless drawing appear here.
Newest first. key is what the press typed with your current layout and modifiers, code is the physical key, and keyCode is the deprecated number older scripts still read.
Start capture and press a key. Each press appears here with its key, code, keyCode, location, and how long it was held.
Fn and Touch ID work inside the keyboard, and most brightness, volume, and media keys stop at the operating system or a vendor driver. They are drawn dashed or not at all, and a key that stays dark for that reason is not broken.
Ctrl+W and Cmd+W close the tab, Cmd+Q and Alt+F4 quit the browser, and Alt+Tab, Cmd+Tab, and Ctrl+Alt+Delete belong to the operating system. No page can intercept them, so leave them out of the test. Press the Windows key once: it registers, then the Start menu opens and capture pauses, so click the keyboard to carry on.
A keyboard in USB boot mode reports at most six keys plus modifiers, and many laptops and Bluetooth keyboards report fewer. A low count here can come from the link as well as the switch matrix.
Keys sit where they are on a US board, with UK legends on the two extra ISO keys. On a French, German, or Nordic keyboard the printed letters differ, but every key still lights in its physical place.
This is not a keylogger.The page listens for key events only while capture is on, keeps them in this tab's memory to draw the keyboard and the log, and forgets them when you reset or leave. Nothing is uploaded, written to storage, or sent to analytics, and a report leaves the page only if you copy or download it yourself. Escape is tested like any other key: one press is recorded, and a second press within 1 second pauses capture. The log keeps the last 60 events, and a press counts as chatter under 50 ms after its own release.
Once every key checks out, measure how fast and accurately you type on it, with timing for the transitions that slow you down.
The same kind of check for your mouse: clicks per second, the interval between clicks, and how steady your clicking stays.
Write a real paragraph after a cleaning or a switch swap, and see whether any letter still doubles or drops in everyday typing.
When you press a key, the keyboard sends a scan code, the operating system translates it, and the browser hands the page a KeyboardEvent carrying two names for it: code, the physical position, and key, what that position types right now. This tester listens for those events while capture is on and matches them by code, so the drawing is right for any language and the results do not depend on your layout settings. A key that never produces an event (Fn, a media key the system keeps, a shortcut the operating system takes) cannot be tested by any web page, and the page says so rather than counting it as a failure. Everything happens inside the tab: no key press is uploaded, stored, or kept after you close it.
Full-size, tenkeyless, 75%, ISO, or Mac laptop, with Windows or Mac legends. Keys are matched by physical position, so the drawing lines up with your board even when the letters printed on it are not American.
Press Start capture or click the keyboard. Each key fills while it is held and keeps a tick once released, and the list of keys not pressed yet shrinks as you go. Press Escape twice within a second, or use Pause, to stop.
Hold the keys you use together to measure rollover and catch ghosting, tap any suspect key slowly to look for chatter, and copy or download a plain-text report of everything that registered.
Each key is identified by KeyboardEvent.code, the position of the switch, rather than by the character it types. An AZERTY, QWERTZ, Dvorak, or ISO keyboard lights the right key in the drawing, and the log still shows what your layout typed.
Full-size ANSI, tenkeyless, 75%, full-size ISO with the tall Enter and the extra key beside left Shift, and a MacBook-style laptop board. Switch to Mac legends to see Command and Option where Windows and Alt would be.
Every key you have not pressed yet is named and grouped by area, which is far quicker than scanning a drawing for the one key that stayed dark. A laptop check is finished when the list is empty.
A key that reports a fresh press within 50 ms of its own release turns amber with an exclamation mark, and is listed with how often it happened and the shortest gap seen: the usual sign of a dirty or worn switch.
The held-now count and the record for most keys down at once show how many simultaneous presses actually reach the computer, and the record names the keys that set it.
key, code, the deprecated keyCode, location (left, right, or numpad), how long the key was held, auto-repeats, and the gap since its last release, for the last 60 events. Copy or download it as plain text.
Choose the layout that matches your keyboard, then press Start capture or click the drawing and press every key once. Each key fills while it is held and keeps a tick after you let go, and the list of keys not pressed yet should shrink to nothing on a healthy keyboard. To check combinations, hold several keys at once and watch the held count. When you are finished, press Escape twice within a second or use the Pause button, and copy the report if you need a record.
Some keys never reach a web page. Fn is handled inside the keyboard and changes what other keys send rather than sending anything itself. Brightness, volume, media, and launcher keys are usually taken by the operating system or a vendor driver first. Shortcuts the system reserves, such as Alt+Tab, Cmd+Tab, Cmd+Space, and Ctrl+Alt+Delete, pull focus away before the page sees them, which is why capture pauses when the window loses focus. The Windows key is different: press it once and it registers, then the Start menu opens and capture pauses, so click the keyboard to carry on. If an ordinary letter, number, or arrow stays dark, though, the problem is that key and not the browser.
Rollover is how many keys a keyboard can report at the same moment. Ghosting is what happens past that limit: a key you pressed goes missing, or one you did not press appears, because of how the switch matrix is wired. Many membrane keyboards manage only two or three keys in some combinations. 6KRO means six keys plus modifiers, the ceiling of the USB boot protocol, and NKRO means every key independently. To test, hold the exact combination you use, such as W, A, Shift, and Space, and check that every key in it is lit at once. The Max rollover tile keeps the highest count this page has seen. The connection matters as well as the board: many laptops and Bluetooth keyboards report fewer keys than the hardware could.
Chatter is a switch registering two presses when you pressed once, so letters come out doubled. This page flags any fresh press that arrives less than 50 milliseconds after the same key was released, which is quicker than a finger can lift and press again, and shows the shortest gap it measured. To confirm, tap the suspect key slowly about twenty times and watch whether the flag count rises. Fixes, roughly in order: turn the keyboard over and blow out debris with compressed air; pull the keycap and clean around the switch; raise the debounce time in the keyboard's software or firmware if it offers one; on a hot-swap board, replace the switch; on a soldered board, have the switch desoldered and replaced. Chatter on a new keyboard is a warranty claim.
Start by finding out exactly which keys fail: choose the 75% or Mac laptop layout and press everything. If no key responds at all, the cause is usually software. On Windows, make sure Filter Keys is off (holding right Shift for eight seconds turns it on, and it ignores brief presses), reinstall the keyboard driver from Device Manager, and plug in an external keyboard to see whether the fault follows the laptop. A key that stays lit after you let go is stuck or dirty. A whole row or block that never registers usually points to the ribbon cable or the keyboard assembly, which is a repair rather than a setting.
They are three answers to which key was pressed. key is what the press produces with the current layout and modifiers, so the same switch gives a, A, or q depending on Shift and on whether the system types QWERTY or AZERTY. code names the physical position: KeyA is the key where A sits on a US keyboard, whatever it types on yours. keyCode is an older number that browsers still send, but it is deprecated and inconsistent between browsers and layouts, so new code should not rely on it. Games, shortcuts, and keyboard testers want code; text input wants key.
Yes. Keys are matched by physical position, so every layout lights the right key in the drawing, even though the drawing shows US legends and your printed letters may differ. Pick the ISO layout if your Enter key is tall and there is an extra key between left Shift and Z; that extra key reports as IntlBackslash. The log shows what your layout actually types, so the A key on an AZERTY board reports code KeyQ and key a. On Windows, AltGr also reports a Left Ctrl press, so Left Ctrl can light up without being touched; press it on its own and check the log.
Press each switch slowly, then quickly, and watch three things. Every key should register once per press with no chatter flag. The held time in the log should match how long you held the key, so a switch that reports a few milliseconds when you held it for a second is releasing early. And it should keep registering while other keys are down, which the held count and the rollover record show. Repeat after cleaning or replacing a switch to confirm the fix.
No. A keylogger records keystrokes and stores or sends them somewhere. This page does neither: it listens for key events only while capture is on, keeps them in this tab's memory to draw the keyboard and the log, and forgets them when you reset or close the tab. Nothing is uploaded, nothing is written to browser storage, and no key press is sent to analytics. A report leaves the page only if you copy or download it yourself. Even so, there is never a reason to type a password into a keyboard tester.
Switch to Mac legends (chosen for you on a Mac) to see Command and Option where Windows and Alt would be; the codes underneath are the same, MetaLeft and AltLeft. On a MacBook the top row sends brightness and media actions by default, which macOS keeps for itself, so hold Fn while pressing them to send F1 to F12, or turn on the setting that uses them as standard function keys. Fn and Touch ID never reach the browser. Caps Lock on a Mac usually reports a press when it turns on and a release when it turns off, so it stays lit while caps lock is on. And macOS drops the release of any key pressed while Command is held, so this page lets go of those keys when the next key goes down or Command comes up, instead of leaving them stuck and counting them as held together.
Explore the growing collection for calculations, documents, writing, and everyday work.