Min detected interval
— ms
Press any key to start
Listening — press different keys (don't hold one)
Last key —
Press any key to start. This free keyboard polling rate test measures the gap between key events in milliseconds — mash keys for 10–15 seconds and read min interval, last interval, and a live ms graph.
Min detected interval
— ms
Press any key to start
Listening — press different keys (don't hold one)
Last key —
TestMyGears measures time between keydown events while you mash the board. Min interval, last interval, an ms history graph, and an event log help you compare ports and settings — without a mouse Start button, and with an honest limit: web pages cannot read silent USB polls.
Holding one key triggers OS auto-repeat (~30–50 ms gaps). That is not HID polling. Mash or roll keys so each press is a fresh keydown.
~1 ms ≈ 1000 Hz, ~2 ms ≈ 500 Hz, ~8 ms ≈ 125 Hz. Office boards often sit near 8 ms; gaming firmware aims lower.
This estimates delivery of key events to JavaScript. Scheduling and focus add variance — use it as a relative meter.
If min interval stays high after a wired mash pass, raise report rate in QMK/VIA or the maker app, then retest.
Confirm whether a “1000 Hz” board delivers ~1 ms key gaps after enabling high polling in QMK/VIA, Synapse, or Wootility — then retest on another USB port.
Press keys in the browser pad for a quick ms read before installing vendor tools. No Start button — typing begins the run.
Run the same mash pattern on two boards. Min interval and log stability often differ even when both boxes claim 1000 Hz.
About one minute: press a key to start, mash, read min ms, then retest after any USB or firmware change.
No mouse Start button. Keep this tab focused and type — the first keydown begins listening.
Turn off sticky keys and close overlays before you mash
Roll fingers across ASDF for 10–15 seconds. Different keys beat holding Space.
Wired motherboard ports usually give cleaner min intervals than hubs
Min detected interval is your best gap so far. The graph and event log show whether delivery stays stable.
Reset, change one setting, then retest so you know what moved the number
Use a direct motherboard USB port — avoid unpowered hubs when comparing boards.
Disable extensions that inject key handlers if intervals look oddly capped.
Retest after raising polling in firmware; keep the same mash pattern.
Pair with the key chatter test if double letters appear while you mash.
It estimates how often key activity reaches your PC. This page shows that as the time between key events in milliseconds. About 1 ms between events is roughly 1000 Hz; 8 ms is roughly 125 Hz.
Interval in ms is what you actually measure between keydowns. Hz is just 1000 ÷ ms. Showing ms makes short gaps (0.1–2 ms) easier to compare than large Hz numbers that browsers often cannot reach.
Open this page and press any key to start. Mash different keys for 10–15 seconds and read min interval in ms. No mouse click is required to begin.
It is accurate enough for relative checks between boards and ports. It cannot certify USB HID firmware rate — browsers do not expose silent HID polls.
Holding one key only measures OS key-repeat. Mash across keys, use a wired port, raise polling in vendor software, and avoid USB hubs.
CPS counts how fast you tap. Polling / interval measures time between key events reaching the page. Use CPS for speed benchmarks; use this page for ms gaps.
Use this for a quick free online pass. Manufacturer software is better when you need an official USB report-rate setting for RMA or competitive configs.
Keyboard only — press keys to start. For mice, use the mouse polling rate test. Controller polling is a separate tool.