Test your keyboard key by key
Every press lights up. Dead keys expose themselves. Nothing is logged, ever.
Press any key — it lights up below. Keys you've tested stay marked.
Keys outside this layout (function row, numpad, media keys) still register in the readout above even without a picture. Nothing you type is stored or sent — it's DOM events and paint, that's all.
The five-minute verdict on a suspect keyboard
Spilled coffee, a key that "sometimes" works, a second-hand mechanical board you want to trust — the test is the same: walk every key and watch the board. Tested keys stay marked so you can be systematic instead of hopeful. A keyboard tester is also the one place typing something should make you think about privacy — here your keystrokes are paint on a page and nothing else, which is the QuietPix deal on every tool.
More device tests
Frequently asked questions
How do I test if my keyboard keys work?
Just start typing on this page — every press lights its key on the board and stays marked as tested. Walk the rows key by key; any key that never lights up is your culprit.
A key registers here but not in my game or app. Why?
Then the hardware is fine and the app is the problem — check its keybindings and whether another program is capturing the shortcut. This test reads the same events every app receives.
What is key ghosting and can I test it?
Ghosting is when certain key combinations physically can’t register together. Hold several keys at once — every one that lights up simultaneously is registering. Gaming keyboards advertise "N-key rollover" for exactly this.
My key needs a hard press or double-types. Is it dying?
Classic symptoms: debris under the cap (compressed air fixes many), or a worn switch. On mechanical keyboards a single switch can be replaced; on membrane boards a stubborn key usually means the board is aging.
Is anything I type recorded?
No. Key events paint pixels on this page and are immediately forgotten — nothing is stored, logged or transmitted. There is no server involved at all.