A keyboard that skips letters, repeats characters, or ignores one stubborn key is hard to diagnose by typing random words into a blank document. A keyboard checker gives you a cleaner answer by showing which key presses your browser or system actually detects. Start with the fast online tests, then move to built-in tools and hardware checks when the same key keeps failing.
1. Start With a Basic Keyboard Checker
Use this first when one key feels dead, sticky, or inconsistent.
- 1.Open keyboardchecker.com in a desktop browser.
- 2.Click the test page so it has focus.
- 3.Press each physical key on your keyboard.
- 4.Watch the matching on-screen key turn green when the page detects it.
It is the quickest way to see whether your desktop browser receives the key press at all. This works on Windows, macOS, ChromeOS, Linux, and other desktop systems with a modern browser. Do not judge Fn keys, media keys, or operating-system shortcuts from this test alone, because browser pages do not capture every hardware-level key.
2. Confirm the Result in Another Tester
- 1.Open OnlineMicTest Keyboard Test.
- 2.Press the exact keys that failed or felt inconsistent in the first checker.
- 3.Watch the virtual keyboard and confirm whether each key lights up.
One failed test is useful. Two matching tests give you a much clearer read before you blame the keyboard.
The visual keyboard uses a U.S. English layout, but the test still reports key events from other layouts. If the same key fails here too, treat it as a real input problem and keep going.
3. Check Ghosting With Microsoft’s Demo
For gaming, shortcuts, and fast typing, test rollover and ghosting separately.
- 1.Open Microsoft Keyboard Ghosting Interactive Demonstration.
- 2.Select Click to Start Demo.
- 3.Type on the physical keyboard and watch the on-screen keyboard show recognized keys.
- 4.Hold A, S, D, and W, then press other keys to check multi-key behavior.
A single-key checker does not prove that your keyboard handles several keys at once. Microsoft’s demo is built for ghosting and rollover checks. It does not work in Internet Explorer, and it is not the right tool for testing every special key.
4. Use the Keyboard Maker’s Web Tool
Programmable keyboards deserve a different test. If your keyboard supports VIA, QMK, Keychron Launcher, or Lemokey Launcher, use the matching tool instead of a generic checker.
- For VIA-compatible keyboards: connect the keyboard by USB, open VIA, open the KEY TESTER tab and select Test Matrix, and press keys to verify the matrix and key output.
- For supported Keychron keyboards: connect the keyboard by cable or 2.4 GHz receiver, open Keychron Launcher, select Connect, choose the matching device, open Key Test, and press each key.
- For QMK-enabled Lemokey keyboards: connect the keyboard with the cable, open Lemokey Launcher, select connect +, choose the corresponding model, open Key Test, select Test Matrix, and press each key.
These tools require supported keyboards and WebHID-capable desktop browsers such as Chrome or Edge. They are not for ordinary laptop keyboards unless that keyboard is a supported programmable device.
5. Run ChromeOS Diagnostics on a Chromebook
- 1.Select the time at the bottom right.
- 2.Open Settings.
- 3.Select About ChromeOS.
- 4.Open Diagnostics.
- 5.In the Keyboard section, select Test.
- 6.Stay in the Diagnostics window while pressing keys.
Chromebooks have their own keyboard test in Diagnostics. Use it on ChromeOS version 90 and up.
There is a faster route too: press the Launcher key or select the Launcher button, type Diagnostics in the search bar, open Diagnostics, then use the Keyboard test.
If the keyboard problem follows one Chromebook account, restart the Chromebook and browse as a guest. When the keys work in Guest mode, remove the problem account from the Chromebook and add it again.
6. Compare Input on Mac and Windows
Built-in viewers are not full hardware diagnostics, but they are useful when you want to compare physical key presses with what the operating system shows on screen.
On Mac: click the Input menu in the menu bar, then choose Show Keyboard Viewer. If the menu is missing, open Apple menu, select System Settings, open Keyboard, choose Text Input, select Edit, then turn on Show Input menu in menu bar.
- On Windows: open Start, select Settings, choose Accessibility, open Keyboard, then turn on On-Screen Keyboard. With it open, select Options and turn on Turn on numeric keypad when you need to check number-pad behavior.
- At the Windows sign-in screen: select the Accessibility button in the lower-right corner, then select On-Screen Keyboard.
7. Isolate Settings, Ports, and Drivers
When the same key fails across more than one tester, stop retesting the page and isolate the device.
- On Mac: open Apple menu, select System Settings, open Accessibility, choose Keyboard, and turn off Slow Keys. Then open Accessibility, choose Pointer Control, and turn off Mouse Keys. You can also press Option-Command-F5 and deselect Mouse Keys.
- On Windows with an external keyboard: connect the keyboard to another PC. For USB keyboards, try a different USB port and bypass USB hubs. If the keyboard still does not work on the other PC and the correct driver is installed, Microsoft says you might need to replace it.
- For USB wireless keyboards: unplug the USB wireless receiver, wait about 10 seconds, then plug it back in. If the device has a Reset button, press it to disconnect and reconnect.
- For Windows driver updates: type check for updates in the taskbar search box, select Check for updates, then select Check for updates under Windows Update. To use Device Manager instead, type device manager, open Device Manager, find the keyboard or device category, double-click the device, open the Driver tab, and select Update Driver.
- For a Windows driver reinstall: right-click Start, open Device Manager, expand Keyboards or Human Interface Devices, right-click the device, select Uninstall device, confirm with Uninstall, then restart from Start, Shut down or sign out, Restart.
8. Check Surface Keyboards Separately
Surface Pro keyboards have their own quick checks before you move to replacement.
- For Surface Pro Keyboard or Type Cover: press Caps and Fn a few times and check whether the LEDs turn on and off. For a deeper check, boot into Surface UEFI and press the up arrow and down arrow keys to change the selection in the left-side menu.
- For Surface Pro Flex Keyboard: disconnect the Surface from power, remove the Surface Pro Flex Keyboard, inspect it for debris, damage, or obstructions, open Start, select Power, choose Shut down, hold the power button for 20 seconds until the Surface logo reappears, reattach the keyboard, and test the keys again.
9. Avoid Outdated Keyboard Test Advice
Skip old Windows instructions that send you to Settings, System, Troubleshoot, Other troubleshooters, and a Keyboard troubleshooter. Microsoft’s current documentation redirects some legacy troubleshooters to Get Help and lists the Keyboard troubleshooter for removal as part of MSDT deprecation.
Use Windows Update, Device Manager, On-Screen Keyboard, Microsoft’s current help surfaces, or a supported tester instead.
Also skip old web keyboard checkers built around keypress or onkeypress; current web guidance uses keydown and keyup for press and release behavior.
Frequently Asked Questions
Can an online keyboard checker test every key on my keyboard?
No. Webpages do not guarantee access to browser shortcuts, operating-system shortcuts, Fn behavior, or media keys.
Why does my keyboard work while typing but fail during games?
Typing usually tests one key at a time. Use Microsoft’s anti-ghosting demo to check whether your keyboard recognizes multi-key combinations such as WASD plus another key.
Is there an official online keyboard checker from Apple, Microsoft, or Google?
The verified research found no general-purpose official online keyboard checker from Apple, Microsoft, or Google beyond Microsoft’s anti-ghosting demo and ChromeOS Diagnostics.
What does it mean when the same key fails in two keyboard checkers?
Move to hardware isolation. Test the keyboard on another PC, try another USB port, bypass hubs, reconnect the wireless receiver, and update or reinstall the Windows device driver.
