Keyboard Polling Rate Test

How to use this keyboard polling rate test

1. Click anywhere on this page so it has keyboard focus.
2. Hold down any single key (avoid Space, Tab, and the arrow keys, since those can scroll the page) and keep it held for a second or two.
3. Once your OS starts auto-repeating the key, the average, instantaneous, and peak Hz readings update live.
4. Release the key and press Reset to try a different one.

Reading the three numbers

Average Hz is your steadiest, most representative reading, smoothed over recent samples. Instantaneous Hz reflects only the gap between the two most recent repeat events, so it naturally jitters more. Peak Hz is the fastest single interval seen this session — useful for spotting your keyboard's best-case behavior.

Why this matters (and why it might not)

Polling rate determines the maximum delay between a physical key press and your computer finding out about it. The gap between common polling rates is small in absolute terms: going from 125Hz to 1000Hz only saves about 7 milliseconds in the worst case, but in reflex-heavy games, some players do notice the difference. Keep in mind that this keyboard polling rate test measures software-level key-repeat timing, a practical proxy, not a raw USB/HID polling-rate readout from your hardware. Read our full explainer, What Is Keyboard Polling Rate?, for the complete picture.

Polling rate vs. debounce time vs. input latency: what's the difference?

These three terms get used interchangeably online, but they describe different stages of what happens between a physical key press and your computer registering it. Understanding the difference explains why a higher-Hz keyboard doesn't automatically feel faster.

Polling rate

Polling rate is how often your keyboard reports its current state to your computer, measured in Hertz (Hz). A keyboard polling at 1000Hz can send up to 1,000 reports per second, roughly one every millisecond in the best case. It describes communication frequency between the keyboard's controller and the USB port or wireless receiver; it says nothing about how the keyboard detected the press at the switch level.

Debounce time

Debounce time is a short, deliberate delay a keyboard's firmware applies after detecting a press or release, to filter out the brief electrical "bounce" that happens as a mechanical switch's metal contacts settle. Without debouncing, a single press could register as several rapid, unintended keystrokes. Many mechanical keyboards use debounce delays in the low single-digit milliseconds, and open-source firmware such as QMK lets enthusiasts tune this value, though shortening it too aggressively risks reintroducing accidental double presses.

Input latency: the number that actually matters

Input latency is the full, end-to-end delay a player or typist actually experiences: the time from physically pressing a key to seeing the result on screen. It's the sum of several stages, including the switch's mechanical actuation, debounce delay, the wait for the next polling interval, USB or OS processing, the application reading the input, and the display's own refresh timing. Polling rate is only one ingredient in that chain, which is why doubling it rarely cuts total latency in half.

Does connection type change your keyboard's polling rate?

Yes, and the difference between USB, Bluetooth, and 2.4GHz wireless can be significant. Standard wired USB keyboards typically max out around 1000Hz, once per millisecond, the practical ceiling set by how the USB Human Interface Device (HID) specification handles standard polling frames. Some newer wired keyboards and dongles advertise 4000Hz or 8000Hz by working around that default with proprietary drivers.

Standard Bluetooth, especially Bluetooth Low Energy (BLE), negotiates a "connection interval" with the host device, and that interval is usually several milliseconds wide, well above the 1-millisecond gap a 1000Hz wired connection achieves. In practice, that means most Bluetooth keyboards report input less frequently than their wired counterparts, one reason competitive players tend to avoid Bluetooth for anything reflex-sensitive.

Proprietary 2.4GHz wireless, the USB dongle style used by many gaming keyboard and mouse brands, is a different technology from Bluetooth. Because it uses a dedicated, low-overhead radio protocol instead of the general-purpose Bluetooth stack, it can match or come close to wired USB polling rates. That's why gaming brands market their 2.4GHz wireless peripherals as "as fast as wired" while positioning Bluetooth as the casual, battery-friendly option. Our guide to polling rate and gaming performance covers how much this gap actually affects real matches.

Do 8000Hz gaming keyboards actually make a difference?

For most people, not in a way you'd consciously feel while typing or gaming, though it isn't purely a marketing gimmick either. Going from 1000Hz (1 millisecond between reports) to 8000Hz (0.125 milliseconds between reports) shrinks the theoretical worst-case reporting delay by less than one millisecond in absolute terms. Human reaction time to a visual stimulus is commonly measured at somewhere around 150 to 250 milliseconds, so a fraction-of-a-millisecond change in reporting frequency sits far below what a person can perceive.

Where higher polling rates help more is consistency rather than raw speed. More frequent reports mean less variance, or jitter, between one report and the next, which tends to matter more for a mouse's cursor smoothness than for a keyboard, since a key press is a binary on/off event rather than a continuously changing analog position. Going from a slow 125Hz keyboard to a 1000Hz one is a meaningful, measurable upgrade. Going from 1000Hz to 8000Hz is a much smaller, harder-to-notice one.

How to check or change your keyboard's configured polling rate

Most mainstream operating systems don't expose a native, per-keyboard polling rate setting, part of why a browser-based check like this one is useful as a practical stand-in. If your keyboard supports adjustable polling, the setting almost always lives in the manufacturer's companion software rather than in Windows or macOS itself.

Common examples include Razer Synapse, Logitech G HUB, SteelSeries GG, Corsair iCUE, and the configuration tools bundled with Hall-effect keyboards from brands like Wooting. Look for a setting labeled "Polling Rate," "Report Rate," or occasionally "USB Report Rate," typically offering presets such as 125Hz, 250Hz, 500Hz, and 1000Hz, with some newer high-end boards adding 2000Hz, 4000Hz, or 8000Hz options.

If your keyboard has no dedicated software, or you're using a basic membrane or office keyboard, it's likely fixed at a standard rate, often 125Hz, set by its firmware and can't be changed. Running this keyboard polling rate test is a reasonable way to sanity-check that a setting change actually took effect: you should see the average and peak Hz readings shift after adjusting the option and reconnecting the keyboard.

How polling rate relates to frame rate and monitor refresh rate

Polling rate, game frame rate, and monitor refresh rate are three separate clocks running at the same time, and a faster keyboard only helps when it isn't the slowest clock in that chain.

A 60Hz monitor redraws the screen roughly every 16.7 milliseconds. If your keyboard polls at 1000Hz, once every millisecond, your input is captured well before the next frame is drawn regardless, so pushing polling rate any higher brings no visible benefit on that display; the bottleneck has already shifted to the monitor.

On higher refresh-rate monitors, commonly 144Hz or 240Hz, each frame window is much shorter, about 6.9 or 4.2 milliseconds respectively, so there's more opportunity for a slow keyboard's stale input to show up in an extra rendered frame before it updates. That's the main reason competitive players pair high refresh-rate monitors with fast-polling keyboards and mice: the display's speed advantage only pays off fully if the input devices feeding it are also reporting quickly. A high in-game frame rate benefits from faster polling for the same reason, since the engine reads keyboard state closer to each new render, up to the point where polling stops being the limiting factor.