A comprehensive visual keyboard tester built for hardware troubleshooting, quality assurance, and developer debugging.
Every key on a full-size ANSI keyboard is rendered on screen. Keys flash green when pressed and stay highlighted in blue once tested, giving you instant visual feedback. You can see at a glance which keys you've verified and which remain untested.
See the full technical details of every key press: the physical event.code, the logical event.key, the legacy keyCode, and the key location (left, right, numpad, or standard). Essential for developers debugging keyboard events.
Press multiple keys simultaneously and the tester tracks the maximum number of keys registered at once. This reveals whether your keyboard supports N-key rollover (NKRO) or if it suffers from ghosting — where pressing certain key combinations prevents other keys from registering.
A scrollable log records every key-down event with its code, key name, and keyCode value. Color-coded entries distinguish presses from releases. Review up to 50 recent events to spot patterns like double-firing keys, missed presses, or erratic input behavior.
A real-time progress bar shows how many keys you've tested out of the total keyboard. Aim for 100% to verify every key works. The counter updates instantly as you press each new key, so you always know exactly how many remain untested.
Renders a complete ANSI keyboard including function keys, navigation cluster, arrow keys, and numpad. If your keyboard lacks a numpad (TKL or 60% boards), toggle it off to simplify the display. The layout includes tall keys for Numpad +, Numpad Enter, and wide keys for Space and Shift.
From gamers to IT departments, a keyboard tester is an essential diagnostic tool for anyone who relies on keyboard input.
Test anti-ghosting and N-key rollover (NKRO) before competitive matches. Verify that key combinations like WASD + Shift + Space all register simultaneously. Detect stuck keys that could cost you a game.
Quickly verify all keys work before deploying hardware. Document key failures for RMA claims with exact key codes and event data. Test batches of keyboards during procurement to ensure quality before rollout.
Debug keyboard event handling in web apps. Verify event.code vs event.key values, check location data for left/right modifiers, and confirm legacy keyCode mappings across different browsers and operating systems.
Buying a used keyboard? Open this tester in any browser and press every key to verify nothing is broken before you pay. The 100% progress bar confirms all keys are functional. No install required — just visit and test.
The tester listens for browser keydown and keyup events on the window. When you press a key, the event's code property identifies the physical key, which lights up the matching key in the on-screen layout. Keys turn green while held and stay blue after release to indicate they've been tested.
Some keys are intercepted by the operating system or browser before they reach the web page. Common examples include the Windows/Super key, certain function keys (F1 for help, F11 for fullscreen), Print Screen, and media keys. This is an OS-level limitation, not a fault in your keyboard. If a key works in other applications but not here, it's being captured by the system.
Ghosting occurs when pressing multiple keys simultaneously causes some keys to not register or extra phantom keys to appear. Anti-ghosting technology prevents this. N-key rollover (NKRO) means every key can be registered simultaneously regardless of how many others are held. The tester tracks the maximum number of simultaneous key presses detected, letting you verify your keyboard's rollover capability.
event.code represents the physical key position on the keyboard regardless of layout (e.g., "KeyA" is always the key in the A position on QWERTY, even on Dvorak or AZERTY). event.key represents the character or function the key produces, which changes with keyboard layout and modifier keys. The tester shows both so you can see the full picture.
Yes. The visual layout shown is ANSI (US), but the tester uses event.code which maps to physical key positions. A key on a German QWERTZ or French AZERTY keyboard will still light up in the correct physical position. The key info panel shows the actual character produced by your layout in the event.key field.
Absolutely. Use the numpad toggle to hide the number pad section if your keyboard doesn't have one. For 60% keyboards that also lack function keys, navigation keys, and arrows, those sections will simply remain unhighlighted — just focus on testing the keys your keyboard actually has. The progress counter will show tested keys vs the full set, but reaching 100% isn't required.
This tracks the highest number of keys the browser registered as pressed at the same time during your session. If you press 6 keys at once and all 6 register, the counter shows 6. This is a practical measure of your keyboard's rollover capability. Most membrane keyboards top out around 3–6 keys; mechanical keyboards with NKRO can handle 10+ simultaneously.
Reset clears all state: the tested keys, press history, last key info, simultaneous key counter, and progress bar all return to zero. Use it when switching keyboards or when you want to start a fresh test from scratch. Your keyboard itself is not affected — Reset only clears the on-screen data.
Completely. The tester runs entirely in your browser with zero server communication. No keystrokes are transmitted, logged, or stored anywhere outside your browser tab. When you close the tab, all data is gone. There are no accounts, no tracking, and no limits on usage.
A keyboard is the primary input device for nearly every computer interaction, yet most people never think about testing their keyboard until something goes wrong. A broken key, an intermittent contact, or a ghosting problem can range from mildly annoying to genuinely debilitating, especially for professionals who type thousands of words a day or gamers where split-second input matters. An online keyboard tester provides a fast, zero-install way to diagnose these problems using nothing but a browser.
Every keyboard, whether membrane, mechanical, or scissor-switch, works by completing an electrical circuit when a key is pressed. In a membrane keyboard, two flexible sheets with conductive traces are separated by a spacer. Pressing a key pushes the top sheet into contact with the bottom, closing the circuit at that position. Mechanical keyboards use individual switches — each key has its own spring-loaded mechanism with metal contact leaves. When pressed past the actuation point, the leaves touch and the circuit closes.
The keyboard's controller chip scans a matrix of rows and columns at high speed, detecting which intersections have closed circuits. It then translates these positions into scan codes and sends them to the computer via USB, Bluetooth, or other connection protocols. The operating system receives these scan codes and translates them into key events, which applications can then process. When you press the "A" key, this entire chain — from physical switch to circuit matrix to scan code to USB packet to OS event to browser event — happens in just a few milliseconds.
Key ghosting is one of the most common yet misunderstood keyboard issues. It occurs because of how keyboard matrices work. When you press multiple keys that share rows and columns in the matrix, the controller may be unable to determine which specific keys are pressed. In the worst case, a phantom key is registered that you never pressed, or a real key press is lost entirely.
Anti-ghosting designs add diodes to the key matrix, allowing the controller to unambiguously identify each pressed key regardless of what else is held. N-key rollover (NKRO) takes this further, guaranteeing that any number of simultaneously pressed keys will all register correctly. Budget keyboards typically offer 2-key rollover (2KRO), meaning only two keys are guaranteed to register at once. Gaming and professional keyboards often offer 6KRO or full NKRO. Our tester's simultaneous key counter lets you verify your keyboard's actual rollover capability rather than trusting marketing claims.
The most common issue is a dead key — one that produces no response when pressed. This can result from a broken switch, a damaged trace on the PCB, debris under the keycap, or a faulty solder joint. A keyboard tester makes this immediately obvious: the key simply never lights up, no matter how hard or how many times you press it. If the key works intermittently — sometimes registering and sometimes not — this usually points to a loose contact or oxidized switch terminals.
Double-firing (also called key chattering) is another frequent problem, especially with older mechanical switches. A single key press produces two or more characters. In the tester, you'll see multiple rapid-fire entries in the history log from a single physical press. Stuck keys are the opposite problem: a key that registers as held down even after you release it. The tester shows this clearly — the key stays green instead of reverting to blue.
Modern browsers provide three different properties for identifying a key press, and understanding the distinction is essential for developers. The event.code property represents the physical key on the keyboard, independent of the current keyboard layout. Pressing the key in the "A" position always produces KeyA, whether you're using QWERTY, Dvorak, AZERTY, or any other layout.
The event.key property returns the character that the key produces in the current layout and modifier state. Pressing Shift + A gives an event.key of "A" (uppercase), while the same key without Shift gives "a" (lowercase). The legacy keyCode property is a numeric value from an older standard that's still widely used in existing codebases despite being deprecated. Our tester displays all three so you can see the complete picture for any key on any layout.
Online keyboard testers are ideal for several scenarios: testing a new or used keyboard before committing to it, diagnosing intermittent issues reported by users, verifying anti-ghosting claims for gaming keyboards, debugging keyboard event handling in web applications, and documenting keyboard failures for warranty or RMA claims. Because the tester runs in a browser with no installation required, it's especially useful in environments where you cannot install software — such as public computers, locked-down corporate machines, or someone else's device. Simply open the page, start pressing keys, and get immediate results.
A keyboard tester by definition captures every key you press, which makes privacy a critical concern. Our tool processes all keyboard events locally in your browser with absolutely zero server communication. No keystrokes are transmitted over the network, stored in cookies, or recorded in any analytics system. The event listeners are attached only while the page is open and are removed when you navigate away. This is not a keylogger — it's a diagnostic tool that exists entirely within your browser tab and disappears the moment you close it.