Free online test

Keyboard Ghosting Test

See how many keys your browser receives at once and try common WASD and modifier combinations.

Reviewed by Last reviewed 2026-08-27Testing methodology

Private by design. Key events and typed text stay in this browser. They are not sent to our server or analytics.
Keyboard Ghosting Test workbench Ready — nothing is being saved
Current key—
Code—
Keys down0
Max simultaneous—

Click here to focus, then press keys. Escape stops capture. Browser and system shortcuts are not blocked.

WASD combination0 of 4 keys heldW + A + S + D
Modifier combination0 of 3 keys heldCtrl + Shift + Alt, left or right
Observed maximum0 keysBrowser events, not a hardware certification
EscF1F2F3F4F5F6F7F8F9F10F11F12
`123456789`MinusEqualBackspace
TabQWERTYUIOP[]\
CapsASDFGHJKL;'Enter
ShiftZXCVBNM,./Shift
ControlMetaAltSpaceAltMetaControl
Num7894561230.Ent

Quick answer

What Keyboard Ghosting Test tells you

See how many keys your browser receives at once and try common WASD and modifier combinations.

Observed here
Current simultaneous key count, Maximum observed rollover, WASD combinations.
How to interpret it
The simultaneous-key count includes only keys whose press events reached the browser and have not been released. A missing combination can reflect rollover limits or an intercepted shortcut, not necessarily a defective key.
Important limit
Results reflect events and values exposed by this browser.
Data handling
Key events and typed text stay in this browser. They are not sent to our server or analytics.

Useful next comparison: Test each key separately, then repeat the same combination in a different application or on a direct connection.

Understanding the result

What a result means

The useful result is the exact combination that remains visible, not only the highest key count. A key that disappears in one repeatable chord suggests blocking somewhere before the browser, while an extra unpressed key matches the stricter meaning of ghosting.

Confirm the pattern by repeating current simultaneous key count. Results reflect events and values exposed by this browser.

How to use this test

  1. Read the privacy and compatibility notes.
  2. Start the test and interact only inside the marked test area.
  3. Repeat the action several times and compare the live indicators.
  4. Use the troubleshooting section before deciding that hardware is faulty.

What this test checks

  • Current simultaneous key count
  • Maximum observed rollover
  • WASD combinations
  • Modifier combinations

What this test cannot check

Results reflect events and values exposed by this browser.

This test does not certify hardware or replace professional inspection.

Missing events can be caused by the keyboard matrix, connection, operating system or browser.

Device Test Bench provides browser-based diagnostic information for reference. It does not replace professional hardware inspection or repair.

Common problems and troubleshooting

Start with two-key pairs, add one key at a time and release the entire chord between trials. Repeat the same order in another application and connection mode so a reserved shortcut or lost page focus is not mistaken for a keyboard-matrix limit.

  1. Repeat the same observation. Focus the test surface and repeat “Current simultaneous key count” three times under the same conditions.
  2. Change one condition. Compare “Maximum observed rollover” after changing only the relevant port, connection, browser setting or application.
  3. Rule out focus or interception. Close overlays and reserved shortcuts, keep the page visible and confirm that the live indicator changes during the action.
  4. Keep the result within its limit. Results reflect events and values exposed by this browser.

If the same pattern remains across relevant applications and connections, give the manufacturer or a qualified technician the repeatable observations instead of a guessed fault label.

Browser compatibility

This test depends on ordinary keyboard events and cannot inspect the matrix scan or USB report itself. Browsers can lose a key-up event when focus changes, so the live list is cleared on reset and should be rechecked after returning to the tab.

BrowserReference statusEvidence basisVersionNotesChecked
ChromeSupportedExpected baselineNot recordedFeature detection is authoritative; permissions, platform and device support can change availability.2026-08-27
Microsoft EdgeSupportedExpected baselineNot recordedFeature detection is authoritative; permissions, platform and device support can change availability.2026-08-27
FirefoxPartialExpected baselineNot recordedFeature detection is authoritative; permissions, platform and device support can change availability.2026-08-27
SafariPartialExpected baselineNot recordedFeature detection is authoritative; permissions, platform and device support can change availability.2026-08-27

“Expected baseline” is an editorial capability expectation, not a completed browser test. The live feature check above is authoritative for this browser and device.

Privacy information

Key events and typed text stay in this browser. They are not sent to our server or analytics.

The public analytics allowlist does not accept pressed keys, typed text, pointer coordinates, media labels, device IDs, recordings, video frames or controller input. Test results are not written to LocalStorage.

Primary technical references

These specifications define the browser signals used by this test. They document web-platform behavior; they do not certify a particular device.

Frequently asked questions

Is this Keyboard Ghosting Test free?

Yes. The test works without an account, download or payment.

Is my test data uploaded?

Key events and typed text stay in this browser. They are not sent to our server or analytics.

Does this result prove my hardware is faulty?

No. It shows what the browser can observe. Repeat the test, compare another browser or device, and seek qualified support when the result matters.

Editorial and correction policyReport a problem with this test

Search