Keyboard Test Check every key, ghosting and chatter

Press each key to see what your browser receives, then try combinations or check for repeated presses.

Which keys register?

Ready

Connect a physical keyboard (USB or Bluetooth) to test it.

Click or tap this area, then press keys. Press Esc to leave the test.

Keys tested: 0 of 104Held: 0Maximum held: 0

Untested Tested ✓ Held ↓

No key events yet.

The counter covers the selected view. Hidden or extra keys still appear in the log. Mac changes modifier labels and their positions; keyboard models vary.

Simultaneous keys

Hold A S D F J K L ; together. Check that every key lights up and Held matches the keys you are pressing. Release them, then try another combination.

Maximum held is the most this page has seen in this session, across all views. It is not a hardware rollover rating.

Possible key chatter

Default: 30 ms. Changes apply to future presses. This is a screening setting, not a pass/fail standard. Automatic key repeats are excluded.

No rapid re-presses flagged.

    Recent key events

    Latest 20 events, newest first. Held ms is the interval between browser events, not hardware latency. An unmatched release shows “—”.

    Key / codeEventHeld msRepeat
    No events yet.
    Some keys may not register. Fn is usually handled by the keyboard itself. Win/Cmd shortcuts, Alt+Tab, Ctrl+Alt+Delete, media keys and Print Screen on some systems may be intercepted before they reach this page. A missing event does not by itself mean a broken key. This page cannot measure true polling rate or hardware latency.
    The keyboard test runs entirely in your browser. Key inputs are not uploaded or saved, and reloading clears them.

    How to test your keyboard

    Start with individual keys

    Choose the view closest to your keyboard and focus the test area. Work along each row. A held key has a solid fill and a down arrow; after release it keeps a check mark. Test both Shift, Ctrl and Alt keys, then the separate numpad. Reset clears the session.

    On a phone or tablet, connect a physical keyboard first. Tapping the diagram only focuses it; it does not count as a hardware key press.

    Read the key and its position

    The diagram follows the physical code, while the label and event log show the received key. A different language layout or Shift can change the label without moving the key. Left and right modifiers are tracked separately. See the W3C keyboard code reference for how positions are named.

    While the area is focused, the tester asks the browser to block plain Tab, Space, arrows and function keys where allowed. Esc leaves the area so Tab can navigate again. OS shortcuts may still take effect.

    Keyboard not working? Check these first

    Nothing appears

    Focus the test area again. Check the connection, power and selected Bluetooth device. For USB, try a direct port. Try typing in another application to see whether the problem is limited to this browser.

    Only some keys fail

    Check your operating system's keyboard language, Num Lock and accessibility settings. Close remapping software temporarily if you use it. Test a suspect key alone and in combinations. Compare with another keyboard or device before deciding the keyboard needs repair.

    What is keyboard ghosting?

    Unexpected or missing inputs

    Ghosting means a combination produces a key you did not press. People also use the term for missing keys when several are held. Rollover describes how many simultaneous keys a keyboard can report. Here, compare the lit keys with your fingers to look for a mismatch.

    Try more than one combination

    Start with the suggested home-row keys, then try combinations you use in games or work. One successful combination does not prove every combination will work. The browser can only show events it receives, so system shortcuts and missed releases can affect the result. Changing focus clears held keys to avoid leaving them stuck on screen.

    What is key chatter?

    A rapid release and re-press

    Key chatter is an unintended extra press. Press a suspect key slowly and watch its count. This detector flags a new press of the same position when it arrives less than the chosen threshold after a release. The count is a clue to investigate, not a diagnosis: deliberate fast presses can also be flagged.

    Repeating while held is different

    A held key can generate automatic repeat events. These are shown in the log but do not add chatter counts or increase the number held. The W3C keyboard event specification describes key, location and repeat information. Timing here reflects browser events, including any delays before delivery.

    Keyboard test FAQ

    How do I test keyboard input?

    Focus the test area and press a physical key. Its received label, code and down/up events appear in the log. Release it to see the held time. A code outside the selected diagram is still logged.

    Why is my keyboard not typing?

    Check that the intended field or test area has focus, then check power and the connection. Try another application. If only this page misses a key, it may be reserved by the browser or operating system rather than faulty.

    Why is my keyboard typing wrong letters?

    Check the active language layout, modifier keys and remapping settings. The event's key is the interpreted value; its code identifies a physical position. Those can differ on layouts other than US QWERTY. This tester does not change your system layout.

    Why is my keyboard lagging?

    Try a wired connection if available, check wireless power and test in another application. A busy browser or system may delay input. This page cannot separate those delays from keyboard delays or measure the time from physical contact to an event.

    What is keyboard polling rate?

    Polling rate describes how often the host checks a keyboard for reports. Keyboard events are delivered after device and operating-system processing; they are not a record of every hardware poll. Counting these events cannot reveal true polling rate, so this tool does not display a rate.

    How do I test a keyboard in BIOS?

    Follow your computer manufacturer's instructions to enter BIOS or UEFI setup at startup. Try navigating its menus without changing settings, then exit without saving. This can check basic input outside the operating system, but it is not a test of every key. This web page cannot run there.

    Why do Fn, Command or Print Screen stay untested?

    Fn often changes what the keyboard sends without producing its own event. The operating system or browser may intercept Command/Windows shortcuts and Print Screen. Some keyboards do not have every key in the diagram. You do not need to reach the full count to establish that your available keys register.