Keyboard repeat rate test results describe automatic repetition delivered to this page. Use one ordinary key, keep it held and record both rate and spread. A missing repeat sequence is an incomplete observation, not proof that the keyboard has no report rate.
Part of the Keyboard test. Run the full keyboard test first for a complete device check.
The expected sample is absent Two runs disagree The result does not explain the original symptom
Keyboard polling rate test
This keyboard repeat rate test measures intervals between automatic repeat events received by the browser. The historical keyboard polling rate test URL remains, but its value is not the keyboard's USB report frequency.
Also known as: keyboard polling rate test, keyboard polling rate tester, keyboard repeat rate test, keyboard repeat test, keyboard hz test, key repeat speed test. Free, online, and no download required.
No permission neededNothing uploaded
Hold one ordinary key to collect repeat intervals.
01
What the keyboard polling rate test checks
| Check | How it is measured | Fails when |
|---|---|---|
| Repeat events | Repeated keydown timestamps are kept for one event.code. | The browser does not deliver repeat events. |
| Interval rate | The median repeat interval is converted to events per second. | Too few stable intervals arrive. |
| Spread | Median absolute deviation describes scheduling variation. | The range remains too broad for a useful estimate. |
How to run the keyboard polling rate test
- Prepare the device and close any application that could reserve the same input or media stream.
- Start the keyboard polling rate test, follow the live prompt and complete every named control or direction.
- Finish the run, record the verdict and repeat once before changing one setting or connection.
If something failed
Hold the same ordinary key with the same system repeat setting, keyboard connection and foreground browser. Reset before changing one setting. Record rate and uncertainty together. Do not combine manual taps, several keys or an initial hold delay with the repeat intervals used for the estimate.
The keyboard polling rate test cannot read the physical device's report stream. Repeat delay, operating-system repeat scheduling and browser delivery affect these intervals. They must not be presented as USB polling, matrix scan frequency or end-to-end latency.
02
How to read the result
Can a browser measure keyboard polling rate?
This page measures repetition. The keyboard polling rate tester watches repeated keydown events for one code and converts their interval to events per second. It does not open USB reports, read scan firmware or verify a rate advertised on a device specification.
Are you holding a key or tapping repeatedly? Only automatic events marked repeat=true contribute to this comparison. A sequence of manual taps answers a timing or speed question instead. Keep the key held while collecting the repeat sample, then release it before finishing.
A keyboard hz test can show a stable delivered interval while the device has a different report setting. These values refer to different stages. Use the label keyboard repeat test when describing this result so another person does not mistake it for a hardware calibration.
How to check your keyboard's real polling rate
The browser cannot provide that hardware check here. Use a documented method appropriate to the device interface if real reports are the question. The keyboard guide keeps held-key repetition, missing positions and simultaneous combinations as separate tasks.
Does the observed value change after a system repeat setting changes? Record the configured value and a fresh sample with the same key. That comparison concerns delivered repetition. It does not establish that the device's own polling frequency changed at the same time.
The key repeat speed test excludes the initial wait from the intervals between subsequent repeat events. Keep the delay before repetition separate from the repeating interval. A long initial hold followed by stable repetition is not evidence that the physical keyboard reports only after that initial delay.
Common keyboard polling rates
Rate-to-interval arithmetic is a reference, not a measurement. A nominal 125 Hz interval is 8 ms, 250 Hz is 4 ms, 500 Hz is 2 ms and 1000 Hz is 1 ms. This page cannot verify that those device reports reached the operating system.
Do not compare those nominal hardware intervals directly with this repeat result. The operating system can generate automatic key repetition on its own schedule, and browser delivery adds another observation point. A keyboard repeat rate test therefore needs a different interpretation from a device report-rate test.
When comparing runs, keep one code held steadily and the tab visible. Pauses, release events and switching keys change the sample. Record the setup and uncertainty rather than choosing the largest displayed integer as proof that one keyboard is faster.
How the keyboard polling rate test works
The implementation compares timestamps of repeat=true keydown events for the same code. The interval sample starts between repeat events rather than including the initial held-key delay. The shared timing probe reports a median frequency and uncertainty from accepted intervals. Read mouse polling rate explained for a different event-delivery comparison.
Use the keyboard polling rate test in a visible foreground tab and keep the device, connection and duration unchanged. Repeat the same action enough times to separate one missed browser event from a persistent pattern. Record the displayed value before changing one setting, then run the same sequence again.
During Keyboard polling rate test, the live readouts update from bounded counters and recent samples. Complete every requested direction, key, channel or phase before finishing. Reset between devices so events from an earlier run cannot alter the next verdict, and keep the tab focused whenever timing or event frequency is part of the result.
What the result can establish
Keyboard repeat rate test results describe automatic repetition delivered to this page. Use one ordinary key, keep it held and record both rate and spread. A missing repeat sequence is an incomplete observation, not proof that the keyboard has no report rate.
Use the keyboard polling rate test in a visible foreground tab and keep the device, connection and duration unchanged. Repeat the same action enough times to separate one missed browser event from a persistent pattern. Record the displayed value before changing one setting, then run the same sequence again.
Read pass as confirmation of the collected sample, warn as a repeatable concern that needs comparison, fail as a missing or abnormal signal with a direct next action, and inconclusive as too little valid input. The number in the detail explains which threshold or count produced the status for Keyboard polling rate test.
Measurement limits
The keyboard polling rate test cannot read the physical device's report stream. Repeat delay, operating-system repeat scheduling and browser delivery affect these intervals. They must not be presented as USB polling, matrix scan frequency or end-to-end latency.
The Keyboard polling rate test reads only signals that the operating system and browser expose to this page. It cannot inspect physical wear, firmware queues, electrical contacts, analogue circuitry or another application's private processing. A clean run confirms the observed sample, while an intermittent fault may require a longer repeat under the same conditions.
Browser scheduling, power saving, wireless transport, display timing and background work can alter the values shown by Keyboard polling rate test. Compare results only when those conditions match. Do not treat a small difference as a hardware change unless it repeats across several controlled runs.
03
Keyboard polling rate test questions
Is this keyboard hz test the same as a device report rate?
No. This keyboard hz test counts delivered automatic repeat intervals, while device report rate concerns reports from the hardware interface. The operating system can schedule held-key repetition independently. Keep both labels and sources explicit when comparing values; a stable browser number is not a certification of the hardware specification.
Why does my keyboard polling rate test match my OS setting?
The page samples automatic repeat events after operating-system processing, so a system repeat setting can affect the interval it receives. Compare a fresh run with one setting changed and the same key held. That observation does not establish that the USB device's configured polling rate also changed.
Which key should I hold for the key repeat speed test?
Use one ordinary letter key, hold it steadily and wait for repeat events to accumulate. Release before finishing or starting another key. Avoid system shortcuts and input fields. The initial delay before repetition begins is separate from the intervals measured between later repeat events.
What is a good keyboard polling rate?
This page cannot recommend a universal device polling rate from repeat timing. The observed value describes automatic events delivered to the browser. A hardware requirement depends on the application and documented device measurement, so keep this result separate from specifications or a purchase recommendation.
Does keyboard polling rate matter for gaming?
A device report setting can be one part of an input route, but this page does not measure its effect in a game. It measures held-key repetition. Use application-specific evidence and a suitable hardware method before claiming that a displayed repeat number improves gaming response.
How do I check my keyboard's real polling rate?
Use a documented device-interface measurement rather than this held-key repeat counter. The browser does not inspect USB packets or the keyboard firmware. Keep the current page for automatic repetition comparisons and record which measurement point produced a number before comparing it with a vendor report-rate setting.
How should I repeat the keyboard polling rate test fairly?
Hold the same ordinary key with the same system repeat setting, keyboard connection and foreground browser. Reset before changing one setting. Record rate and uncertainty together. Do not combine manual taps, several keys or an initial hold delay with the repeat intervals used for the estimate.
What can the keyboard polling rate test not prove?
It cannot prove physical polling, scan frequency, switch latency or a gaming benefit. It sees the repeated-event stream after operating-system processing. This keyboard polling rate test keeps its old URL but answers the repeat-timing task; use the keyboard guide for other input symptoms.