Mechanical keyboard switch tester
Press each switch after assembly, cleaning, or repair to confirm the browser sees a clean press and release.
Switch testing for mechanical keyboards.
Use this mechanical keyboard tester to check every switch after a build, repair, cleaning, or keycap swap.
The report is generated locally and can be used as a build or repair checklist.
Inspection flow
Press every key in the selected layout until the progress reaches 100%.
Hold each listed combo and confirm all keys appear together.
Tap Press a key ten times with normal pressure, then review possible chatter.
Live status
Ghosting test
Try common gaming combinations to check for possible ghosting.
Diagnostics
These are browser-based estimates. Retest a suspicious key several times before treating it as a hardware fault.
Local report
Keyboard Tester Online Report ============================= Generated at: 2026-05-15T07:32:42.423Z Selected layout: Windows TKL Browser / OS: Unknown browser on Win32 Tested keys: 0/87 Untested keys: 87 Untested key list: Esc, F1, F2, F3, F4, F5, F6, F7, F8, F9, F10, F11, F12, PrtSc, ScrLk, Pause, `, 1, 2, 3, 4, 5, 6, 7, 8, 9, 0, -, =, Backspace, Ins, Home, PgUp, Tab, Q, W, E, R, T, Y, and 47 more Max simultaneous keys detected: 0 Possible stuck keys: None Possible chatter keys: None Pass / fail checklist --------------------- All layout keys tested: CHECK No possible stuck keys: PASS No possible chatter keys: PASS Multi-key input detected: CHECK Issue summary: 87 layout keys were not tested; multi-key rollover was not meaningfully tested Notes: Browser-based estimate. Some hardware keys, Fn keys, media keys, and system shortcuts may not be detectable.
Press each switch after assembly, cleaning, or repair to confirm the browser sees a clean press and release.
Use the chatter panel to spot keys that may trigger repeated inputs under normal tapping pressure.
After hot-swap or soldered switch replacement, run a full pass and export the report before closing the build.
Choose a compact layout such as 60 percent or 75 percent when testing smaller custom keyboards.
Save a TXT or JSON report listing tested keys, missing keys, and possible switch issues.
Yes. It is useful for checking switch response, missing keys, chatter flags, and reportable build issues.
No. It tests browser-detected input events, not switch acoustics, force curves, or tactile feel.