Keyboard test
Press your keys. See what responds. Check what needs another look.
Choose Start testing, then press your physical keys. Tab or Esc leaves the test.
Ready to test- Press & release To observe
- 5 separate taps To observe
- Hold for 2 seconds To observe
Swipe sideways to see the whole keyboard. A physical keyboard is needed to test keys.
This is a schematic reference, not an exact drawing of your keyboard. Layout or format changes clear the test.
Investigate unwanted extra presses
Tap slowly and release fully each time. Separate press/release cycles are compared; the system’s normal repeats while a key is held are counted separately.
Changing this threshold resets all observations. This is a comparison aid, not a manufacturer limit or proof of contact bounce.
The maximum counts selected keys simultaneously held in this page. Keys that work alone but are missing together need another comparison; an incomplete gesture or intercepted shortcut can produce the same observation. This cannot certify NKRO.
Keyboard reference & format
Adjust which keys are present
Optional: exclude a position absent from your keyboard. It stays separate in the report and is never marked as tested. Pressing an excluded key includes it again.
No positions excluded.
Your keyboard observations
The download contains selected positions and observations, never the text you typed.
Guided checks and timing observations
Detected 0
These positions sent a key event.
Not observed 0
These positions have not sent an event in this test. This does not prove a fault.
Excluded by you 0
Outside your chosen selection; not counted as tested.
The report describes this page’s observations only. It cannot certify every key combination, the electronics or a successful repair.
How to test your keyboard
This online keyboard tester shows the key events your browser receives. Use it to check a suspect key, work through a keyboard after cleaning, or inspect a second-hand keyboard before deciding what to investigate next.
- Choose a reference. Select US QWERTY, French AZERTY or Belgian AZERTY (Windows), then a format with or without a number pad. The compact option is one schematic arrangement; compact keyboards vary. Under “Adjust which keys are present”, exclude positions your keyboard does not have.
- Activate the test. Choose Start testing or focus the diagram. Press your physical keys one at a time, working through letters, numbers, modifiers, navigation keys and the number pad. Holding a key does not increase the number of detected positions.
- Review the observations. Choose View my report. Detected means the browser received a response. Not observed means more checking may be needed. Excluded means you removed that position from the selection.
Tab and Esc are observed if received, then leave the test. Browser and system command shortcuts remain available; a command such as F5 may reload the page and clear its observations. Switch back to Start testing after a shortcut takes you elsewhere. Clicking or tapping the drawing does not count as a keyboard test.
A repeatable check for a suspect key
Choose “Check one key step by step”, then select the physical position. Press and release once, make five separate taps, then hold for at least two seconds and release. Only received keyboard events advance the steps. Selecting a key on screen never validates it.
A held key can produce many native repeat events: that is normal system behaviour. We show those separately from new press/release cycles. For unwanted extra presses, compare the event timestamps between successive new presses after a release. The adjustable 40, 80 or 120 ms threshold is exploratory; fast intentional taps can also cross it. A close pair alone is not proof of a damaged switch.
Leaving the test while holding a key records an interruption and discards that unfinished hold. An unpaired new press or unusable timestamp is reported separately. Durations use the browser’s event timestamps, so a busy page does not turn its own handler delay into a false short interval. Browser input delivery, timestamp precision, the operating system and firmware still limit the observation.
Choose “Compare a key combination” to establish that each selected key responds alone, then try them together in different orders. Choose a preset or build a custom selection of two to six positions. The report gives the highest number of selected keys actually observed together and the completed attempts. A successful selection does not prove unlimited rollover or every possible combination. These checks stay on this page until reset or navigation; changing a target restarts its guided sequence, while its cycle aggregates remain until “Restart this key” or a full reset.
A key does not respond: what to check next
First check that the test says “Listening” and the position exists on your keyboard. Press the key alone. A missing highlight can mean an absent key, an application intercepting the input, a reserved shortcut, a different mapping or a connection problem.
Try the key in another application where it has a purpose. Check the keyboard language selected in your operating system. For an external keyboard, check its cable or wireless connection and battery, then compare another port or device if available. Keep the same key and action in each comparison.
A response in another application points toward a context or mapping difference. A repeated failure across applications and devices deserves further hardware investigation; this page cannot establish the electrical cause or guarantee that replacing a switch will fix it.
Why the letter can differ from the drawing
The drawing follows physical position codes. “Last key received” shows the value reported for that press, which can change with your language, Shift, AltGr or remapping. For example, the position named KeyQ commonly produces A on French AZERTY. That difference alone is not a faulty key.
The symbol references here are PC US, PC France and Windows Belgian French (KLID 0000080C). Mac labels change the modifier names to Control, Option and Command; they do not reproduce every Mac keyboard. French and Belgian AZERTY are different, and French Mac symbols can also differ. Choose the closest reference and use the actual received value when checking symbols.
The Belgian reference follows Microsoft Windows Belgian French (KLID 0000080C): § at Digit6, ! at Digit8, - at Equal, µ at Backslash and = at Slash. It does not reproduce Belgian Apple symbols or every Belgian variant. Automated checks verify the drawing and codes; no physical Belgian keyboard was tested for this version.
Testing the number pad and special keys
The full format separates number-pad positions from the number row. Try both Num Lock states if your keyboard supports them: the same number-pad position can send a digit or a navigation value. The displayed count uses the reported position, so Numpad1 and Digit1 remain separate when your browser exposes them separately.
Fn often acts inside the keyboard or device and may send no independent event. Media controls, power buttons, some function keys and operating-system shortcuts can also be intercepted. A key outside the selected diagram appears in the last-key readout but does not increase its coverage. If no usable physical code arrives, the tester says so instead of guessing a position.
A tablet or phone needs a connected physical keyboard for this test. An on-screen keyboard may supply text without reliable physical position codes. The optional combination mode compares selected keys alone and together. The guided key mode separates normal held-key repeats from new press/release cycles. Neither measures hardware latency nor establishes an electrical fault.
What stays on your device
Key observations stay in this page’s memory and disappear when you reload or leave. No text history is kept. The optional text or print report is created locally and contains the chosen reference, position lists, coverage, completed cycle counts, exploratory interval aggregates, guided observations and method version. No event timeline is retained. It excludes received characters, device identifiers and serial numbers.
TinyFingers uses its existing Google Analytics for site usage and broad actions such as beginning a test or viewing a report. Key values, position lists and typed text are never attached to those events. Read about TinyFingers and privacy.
Method: keyboard observations v2. How TinyFingers tests inputs. Physical position codes and received key values are documented by MDN. See also native key repeats and event timestamps.
Check another input
- Follow the guide for a key that does not respond
- Test mouse buttons, dragging and scrolling
- Investigate an unwanted double-click
- Explore TinyFingers Tools
Looking for playful keyboard exploration? Open the TinyFingers keyboard toy.