Keyboard Keys Test: How to Check Every Key Online

To test every key on your keyboard, open the online keyboard tester, keep the tab focused, then press and release each physical key one at a time. Work row by row before checking modifiers, function keys, arrows, the number pad and the combinations you actually use. A highlighted key confirms that its event reached the browser; a missing highlight is a reason to investigate, not proof that the switch is broken.

How to run a keyboard keys test online

1. Save open work. Function keys and system shortcuts can refresh a page, close a tab, change volume or move focus away from the tester.
2. Use your normal connection. If the keyboard supports USB, Bluetooth and a wireless receiver, begin with the mode in which the problem occurs.
3. Choose the closest layout. Select Windows/PC or macOS in the keyboard test. A compact or regional keyboard may not match every drawn position.
4. Press every key row by row. Start with Escape and the function row, continue through numbers and letters, then check navigation keys, arrows and the numpad.
5. Release every key fully. The active pressed state should clear after release while the tested state remains marked.
6. Check both sides. Test left and right Shift, Ctrl, Alt/Option and Windows/Command separately.
7. Try real combinations. Hold the keys used for a game, shortcut or application and compare them with the currently held list.
8. Confirm suspicious results elsewhere. Retest a missing, repeating or stuck key in a plain text editor or another suitable application.

Use a physical keyboard for this check. Clicking an on-screen key with a mouse or tapping a phone display can preview an interface, but it does not test the keyboard switch beneath your finger.

What your online keyboard test result means

A web tester listens for keydown and keyup events delivered by the browser. The event inspector can show two values that answer different questions:

• code identifies a reported physical key position, such as KeyQ or Numpad1.
• key describes the interpreted value, which can change with Shift, the active language or the operating-system layout.

That distinction matters on QWERTY, AZERTY, Dvorak and other layouts. A physical position can report the expected code while producing a different key. That usually points toward a layout, modifier or remapping check rather than a dead switch.

Complete checklist for testing every keyboard key

Typing a familiar sentence is not a complete keyboard key test. It can miss punctuation, the second modifier keys, navigation controls, the function row and the numeric keypad. Use this checklist for fuller coverage.

Letters, numbers and punctuation

Start at the top left and move across each row. Test the number row and its shifted symbols, every letter, brackets, slash, backslash, comma, period, apostrophe and any regional keys on your board. Include Backspace, Enter or Return, Tab, Caps Lock and the spacebar.

Press large keys such as Space and Enter normally rather than striking them harder. If a key works only from one edge or needs unusual force, record that behavior separately even if it eventually registers.

Modifier and essential control keys

Test left and right Shift, Ctrl, Alt, Option, Command or Windows keys as separate physical positions. First press each modifier by itself, then pair it with a harmless letter. Avoid combinations that lock the computer, close the browser or switch applications.

Check Escape, Backspace, Delete and both Enter keys if your keyboard has a dedicated numpad Enter. The Menu or Application key on some Windows keyboards also deserves its own test.

Arrow, editing and navigation keys

Check all four arrow keys, then Insert, Delete, Home, End, Page Up and Page Down where present. Compact keyboards may place these actions on a secondary layer. Test the printed primary key first, then test the action produced while holding Fn.

For movement combinations, verify each arrow individually before opening the arrow keys test. A key that works alone can still disappear from a particular diagonal or multi-key chord.

Function keys from F1 to F12

Open the function key test, save your work and press F1 through F12 one at a time. Repeat the row with Fn held if your keyboard uses media or brightness controls as the default action.

Record both the browser result and the visible system action. If volume changes without a browser highlight, the keyboard may have worked while firmware or the operating system handled the command first. If the whole row changes behavior, check Fn Lock and model-specific keyboard settings before judging every switch as faulty.

Numpad and Num Lock

The number row and numeric keypad use different physical codes, so a working Digit1 does not prove that Numpad1 works. In the online numpad test, check digits 0–9, decimal or separator, add, subtract, multiply, divide, Numpad Enter and Num Lock where present.

With Num Lock off, keypad digits may perform navigation. If they move the pointer instead, review the operating system's Mouse Keys setting. Some laptops use an embedded numpad that is enabled through a model-specific Fn combination.

Press, release and automatic repeat

Hold a letter briefly. Normal operating-system repeat begins after a delay and should stop when you let go. A web page can lose the release event if you switch tabs or a system shortcut takes focus, so refocus and repeat before calling the key stuck.

For suspected keyboard chatter, use slow, separate taps with a full release between them. Rapid deliberate typing and normal held-key repeat are not the same as multiple discrete activations from one tap.

How to test keyboard keys on different devices

The core method stays the same, but layouts and reserved controls vary by device.

Windows 10 and Windows 11 keyboard test

Use the Windows keyboard test to check both Ctrl and Shift keys, Alt, Windows, Print Screen, arrows, navigation keys and the number pad. The Windows key opens Start, Print Screen may open a capture interface, and some shortcuts can be handled before the page sees them.

If one key does not register, compare it in Notepad or another plain text field. For an external keyboard, check its power and cable, reconnect it directly where practical, then compare another USB port or computer before changing drivers.

Laptop keyboard test online

A laptop keyboard test should cover the primary label on every key and the secondary action printed on compact layouts. Test the normal top-row action, then repeat with Fn. If letters produce numbers, check the embedded numpad or Num Lock mode.

When a built-in key fails, compare an external keyboard. If the external board works, that narrows the issue to the built-in input path, but a browser cannot distinguish a damaged mechanism, internal cable, controller or model-specific setting. Do not pry off a laptop keycap unless the manufacturer provides instructions for that exact model.

Mac and MacBook keyboard test

Use the Mac keyboard test for a MacBook, Magic Keyboard or third-party Mac layout. Check Command, Option, Control and Shift on both sides where present. Option can change the interpreted character, while Command is commonly reported as the Meta modifier in browser events.

Fn or Globe may be handled without a useful standalone browser event. Test the action produced by the combination rather than requiring Fn itself to highlight. Touch ID and the power button are not ordinary browser keyboard inputs.

Chromebook keyboard test

The Chromebook keyboard test covers ordinary keys, Launcher or Search and browser-visible top-row controls. ChromeOS may handle brightness, volume, navigation and other actions before a website receives them. If the screen brightness changes but the key does not highlight, record the successful system action as well as the missing browser event.

For a second comparison, supported ChromeOS devices also include Diagnostics for the internal keyboard. Availability and the displayed tests can depend on the ChromeOS version and device.

Mechanical, gaming and wireless keyboards

For a mechanical keyboard, test a suspect switch with slow taps and compare nearby switches using the mechanical keyboard test. Debris, switch chatter, a hot-swap socket, remapping and firmware settings can look similar in one browser session.

For gaming, use the gaming keyboard test to check WASD, Shift, Ctrl and Space both alone and in the exact combinations used in a game. If input drops only in the game, also check its bindings and input mode.

For Bluetooth or receiver-based keyboards, begin with a full charge or known-good batteries. Record the connection mode, distance and receiver placement, then compare a supported wired mode without changing several variables at once.

How to check if one keyboard key is working

If you only need to test one unresponsive keyboard key, use a controlled comparison:

1. Reset the tester and press the suspect key slowly five to ten times.
2. Confirm whether both press and release events appear consistently.
3. Compare a nearby key using the same rhythm and pressure.
4. Try the suspect key in another application and browser.
5. For an external keyboard, compare another connection or computer.

A failure that follows the same physical keyboard across applications and computers is stronger hardware evidence than one missing web event. An intermittent key that works only with extra pressure also deserves attention even if it does not fail every attempt. Continue with the keyboard keys not working guide for a symptom-based decision path.

How to test multiple keys, ghosting and rollover

If each key works alone but a combination fails, open the ghosting test. Hold the first key, add the others one at a time, compare the held-key list with your fingers, then release in reverse order. Repeat the chord in another order and test combinations you actually use, such as W + Shift + Space.

These terms describe different results:

• Blocking means an intended pressed key is withheld.
• Ghosting means an unpressed key is reported.
• Rollover describes how many simultaneous keys can be reported correctly under the tested conditions.

Use the N-key rollover test to record an observed lower bound. If ten non-modifier keys appear together, the defensible result is that at least that tested group registered. One successful chord does not certify every combination or a manufacturer-wide NKRO claim.

Why some keys do not appear in a browser test

An online keyboard tester can check only events exposed to the page. The browser, operating system or keyboard firmware may handle a key first. Common examples include Fn, media controls, brightness keys, power buttons, authentication keys and reserved shortcuts.

Focus also matters. Opening Start, switching applications or triggering a screenshot tool can interrupt the test or hide a later release event. Check whether the intended system action occurred, refocus the page and compare another application before concluding that a non-highlighted key is dead.

What an online keyboard tester cannot prove

A browser test is useful for isolating and recording a symptom, but it cannot:

• Inspect a switch, membrane, socket or internal laptop cable
• Identify which physical keyboard produced an event when several are connected
• Guarantee capture of every operating-system or browser shortcut
• Reliably expose a firmware-only Fn key or authentication button
• Certify every possible ghosting or rollover combination
• Measure raw switch latency, scan rate or USB polling rate from browser timing alone
• Prove long-term reliability from one successful session

Read how Keyboardtest evaluates input for the site's counting rules, privacy notes and measurement limits.

Frequently asked questions

How do I test every key on my keyboard online?

Open the keyboard tester, keep the tab focused and press every physical key row by row. Check that each key becomes active when pressed and clears when released. Finish with modifiers, F1–F12, arrows, the numpad and the multi-key combinations you use.

Can I test keyboard keys online without downloading software?

Yes. A compatible desktop browser can show ordinary keyboard events without a download or account. Native software may still be needed for firmware settings, vendor-specific controls or hardware-level measurements that a web page cannot access.

How can I tell whether a keyboard key is dead?

Test the key several times in the browser, then compare it in another application and, if practical, on another computer. Consistent failure across those checks is stronger evidence of a fault. One missing browser highlight is not enough for a definitive diagnosis.

Why does the Fn key not show in an online keyboard test?

Many keyboards process Fn inside their firmware and send only the resulting F-key, media or brightness command. Test the action produced with Fn rather than expecting a separate event. A missing standalone Fn highlight can be normal.

Can an online keyboard test find double typing or key chatter?

It can record extra browser events that follow one deliberate tap, which is useful evidence. Normal automatic repeat while a key is held is different. Use the focused double typing test and compare another application before attributing duplicates to a switch.

Why does the tester show a different character from the keycap?

The active input language, keyboard layout, Shift or Alt/Option state, remapping software and application settings can change the interpreted key value. Compare it with code, which identifies the reported physical position.

Does this work for laptop, Mac, Windows and wireless keyboards?

Yes, for ordinary browser-visible events. Choose the closest layout and follow the device-specific checks above. Compact layers, system controls and proprietary keys may require testing their actual action or using the manufacturer's utility.

How do I test keyboard ghosting online?

Confirm each key individually, then hold the exact combination you want to test and compare the reported held keys with your fingers. Repeat in another order. A missing pressed key suggests blocking; an unintended reported key is ghosting.

Technical references

• MDN: KeyboardEvent.code explains physical-position values and layout differences.
• MDN: KeyboardEvent.key explains interpreted key values.
• MDN: KeyboardEvent.repeat documents the repeat flag for held keys.
• W3C UI Events defines browser keyboard-event behavior.
• Microsoft: Mouse and keyboard problems in Windows provides connection, power and cleaning checks.

Ready to begin? Start the free keyboard keys test, then return to this checklist to interpret anything unusual.