Keyboard Polling Rate Test | Check Your Keyboard’s Hz Free (2026)

Keyboard polling rate is the number of times per second your keyboard sends input data to your computer, measured in Hz. A 1000Hz keyboard reports 1,000 times per second at a 1ms interval, while a 125Hz keyboard reports every 8ms. Use the polling rate tester above to measure your own keyboard’s real Hz in seconds.

Updated: 16 -07 -2026

Keyboard Polling Rate Test

Measure your keyboard polling rate, input latency, and response stability online. Works with 125Hz to 8000Hz gaming keyboards.

Live Test

● Stopped
STABILITY 0%
3
Live Detection
0Hz

Click Start and wait for the countdown.

On touch devices, this test only works with a physical (e.g. Bluetooth) keyboard — on-screen keyboards don’t reliably fire the events this tool needs.

Average Rate0 Hz
Peak Rate0 Hz
Low 5%0 Hz
Jitter0.00 ms
Stability0%
Avg Interval0.00 ms

How to Run the Keyboard Polling Rate Test

  1. Click Start Timed Test — the tool begins a short countdown, then switches into Live Detection mode.
  2. Press or hold any key steadily. The large Hz counter updates in real time as your keystrokes are captured.
  3. Let the timer run to completion for the most reliable result — stopping early gives the test less data to average.
  4. Hit Stop anytime to end early, or let it finish automatically.
  5. Your results appear in the stats row below the test area. Click Reset to run it again.
  6. Use Share to send your result, or Download CSV to export the raw data — handy if you’re comparing multiple keyboards side by side.

Works with any keyboard from 125Hz office boards up to 8000Hz high-end gaming keyboards.

What Is Keyboard Polling Rate?

Keyboard polling rate is the frequency at which a keyboard’s firmware transmits its input state to the PC over the connection (USB or wireless), expressed in Hertz (Hz).

The relationship is simple math: polling interval (ms) = 1000 ÷ polling rate (Hz).

  • 125Hz → reports every 8ms (standard for most office keyboards)
  • 500Hz → reports every 2ms
  • 1000Hz → reports every 1ms (the current competitive-gaming standard)
  • 4000–8000Hz → reports every 0.25ms–0.125ms (found on newer high-end gaming boards)

A higher polling rate means the computer receives your keystroke sooner after you press it, which shortens the input chain before the action appears on screen or in-game.

Polling Rate vs. Scan Rate vs. Response Time vs. Report Rate

These four terms get used interchangeably online, but they describe different links in the same chain — and mixing them up is where most confusion (and most SEO content gaps) comes from.

TermWhat It Actually Measures
Polling RateHow often the keyboard sends data to the PC (Hz)
Scan RateHow often the keyboard’s internal matrix checks which keys are pressed
Response Time / Input LagThe total delay from physical keypress to on-screen action (debounce + scan + polling + system rendering)
Report RateMarketing/software term used by brands like Razer and Logitech that means the same thing as polling rate

So if a keyboard’s software calls it “report rate,” that’s not a separate spec from polling rate — it’s the same measurement under a different label.

Keyboard Polling Rate Comparison Chart

Polling Rate (Hz)Delay Between ReportsBest Suited For
125 Hz8 msOffice work, everyday typing, non-gaming use
250 Hz4 msCasual gaming, general text input
500 Hz2 msModerate/competitive gaming, fast text processing
1000 Hz1 msCompetitive FPS, fighting games, professional input
4000 Hz0.25 msHigh-refresh-rate gaming setups (360Hz+ monitors)
8000 Hz0.125 msMarginal gains are mostly a spec-sheet number

Practical takeaway: the jump from 125Hz to 1000Hz is noticeable. The jump from 1000Hz to 8000Hz is, for almost every player, not, which is why most professional esports players still run standard 1000Hz.

Why Polling Rate Matters

  • Gaming (FPS, fighting, rhythm games): every millisecond of hardware delay stacks on top of your natural human reaction time (typically 150–250ms). Removing input lag from the hardware chain is one less variable working against you.
  • High-speed typing and programming: faster reporting reduces the chance of dropped or delayed keystrokes during rapid input. Typists pushing 100+ WPM on typing speed tests are especially likely to notice missed or doubled characters on a low-polling-rate keyboard during fast bursts.
  • Precision control (music production, live performance, professional software control): consistent, high-frequency reporting keeps timing-sensitive commands accurate.
  • Turn-based or slower-paced games and general browsing: polling rate has effectively zero perceptible impact; a stock 125Hz keyboard performs identically here.

What Affects Real-World Keyboard Latency Beyond Polling Rate

Polling rate is only one link in the latency chain. A keyboard can advertise 1000Hz and still feel laggy if these other factors aren’t optimized:

Debounce Time: The keyboard’s firmware waits a few milliseconds after a keypress to confirm it’s a genuine press and not a mechanical switch “bounce.” Faster debounce algorithms (common on optical and Hall Effect switches) shave real time off total latency.

Switch Type

  • Mechanical switches rely on physical contact and require a debounce delay.
  • Optical switches use a light beam, cutting debounce time significantly.
  • Hall Effect (magnetic) switches, increasingly common on 2025–2026 gaming keyboards, allow adjustable actuation points, letting users trigger a keypress earlier in the travel distance for lower perceived latency.

N-Key Rollover (NKRO) and Anti-Ghosting: These control how many simultaneous keypresses a keyboard can correctly register. They don’t change the polling rate directly, but low-quality rollover support can cause dropped inputs that feel like added latency during fast multi-key combos.

Connection Type

  • Wired (USB): lowest and most consistent latency; USB 3.0 ports have a slight edge over USB 2.0.
  • 2.4GHz wireless dongle: can match wired 1000Hz performance on gaming-grade wireless keyboards.
  • Bluetooth: capped at roughly 125Hz by the protocol itself, this is a hardware/protocol limitation, not something firmware updates can fix.

USB HID Protocol and OS-Level Polling. Every keyboard communicates with a PC through the USB Human Interface Device (HID) class. The operating system’s own interrupt handling and USB polling settings can also influence the effective rate at which the system actually processes, independent of what the keyboard is rated for.

How to Check or Change Your Keyboard’s Polling Rate

Gaming keyboards (adjustable):

  1. Open the manufacturer’s software — Razer Synapse, Logitech G HUB, Corsair iCUE, or SteelSeries GG.
  2. Locate the Polling Rate or Report Rate setting (usually under Performance or Device settings).
  3. Select your target Hz (1000Hz is the recommended default for most users).
  4. Some boards also support a hardware shortcut, such as Fn + 1 for 125Hz or Fn + 4 for 1000Hz — check your model’s manual.

Office/standard keyboards (fixed): These ship locked to a factory-set polling rate (usually 125Hz) with no software or firmware option to change it. Reaching a higher rate requires switching to a gaming-oriented keyboard.

Understanding Your Test Results

Once your test finishes, you’ll see six key stats:

  • Average Rate — the average Hz across the whole test, and the number that best represents your keyboard’s real-world polling rate.
  • Peak Rate — the single highest Hz reading captured. Good for seeing your keyboard’s ceiling, but not representative of typical performance on its own.
  • Low 5% — the average of the slowest 5% of readings during the test. This is the same “low percentile” concept used in PC gaming benchmarks (like 1% low framerates) — it shows how your keyboard performs in its worst moments, not just its best. A big gap between Average Rate and Low 5% usually points to inconsistent polling rather than a hardware limitation.
  • Jitter — how much the time between reports varies, in milliseconds. Lower jitter means steadier, more predictable input timing; higher jitter means your interval is bouncing around even if the average Hz looks fine.
  • Stability — a percentage score summarizing how consistent your polling rate was overall. Closer to 100% means your keyboard held a steady rate throughout; a lower score usually points to USB scheduling interference, background system load, or a wireless connection dropping frames.
  • Avg Interval — the average time in milliseconds between each report — is the same math from earlier in this article, just expressed as an interval instead of a frequency (interval = 1000 ÷ Hz).

You’ll also see Elapsed time and Key Presses, which show how long the test ran and how many inputs it captured — more key presses over a longer test generally mean a more statistically reliable result. The Grade at the bottom gives you a quick overall read on your keyboard’s performance without needing to interpret every stat individually.

Troubleshooting a Lower-Than-Expected Result

If your result comes in noticeably below your keyboard’s advertised polling rate, check these before assuming the keyboard itself is at fault:

  • USB port type and location: use a USB 2.0-or-higher port on the motherboard directly, not through a hub or a front-panel extension.
  • Keyboard drivers: outdated or missing manufacturer drivers can silently cap the effective polling rate — reinstall or update them.
  • BIOS/USB settings: some motherboards throttle USB polling at the firmware level; check your BIOS USB configuration if the issue persists across multiple browsers.
  • Manufacturer software: some keyboards ship defaulted to a lower rate and require Razer Synapse, Logitech G HUB, Corsair iCUE, or SteelSeries GG to unlock their maximum advertised Hz.

Information Gain: Why Browser-Based Polling Rate Tests Show Lower Numbers Than the Rated Spec

This is the part most polling rate testers online don’t explain, and it matters for interpreting your own result correctly.

Browser-based tests measure time using JavaScript’s event loop and timing APIs (such as requestAnimationFrame or performance.now()), which are not perfectly synchronized with the operating system’s hardware interrupt timing. The browser, tab throttling, background processes, and rendering pipeline all introduce small amounts of overhead.

What this means practically:

  • A genuinely 1000Hz-rated keyboard may show 700–950Hz in a browser test — that’s expected, not a defect.
  • Relative comparisons are reliable: testing two keyboards back-to-back in the same browser session, on the same tab, will accurately show which one is faster, even if neither absolute number matches the box spec exactly.
  • For lab-accurate absolute numbers, dedicated desktop tools using direct hardware polling (not browser timers) are required — browser tests are best used as a quick, relative benchmarking tool.

To get the most accurate browser-test result:

  • Close other browser tabs and background apps before testing
  • Plug directly into a USB port rather than through a hub
  • Press keys at a steady, consistent rate throughout the test

Related Tools

Polling rate is one piece of your overall input performance. For a fuller picture of your setup, also check:

Frequently Asked Questions

What is a good keyboard polling rate for gaming?

1000Hz is the current standard for competitive and casual gaming alike. It delivers a 1ms report interval, which covers the practical latency needs of virtually all fast-paced games without the diminishing returns of 4000–8000Hz options.

Does polling rate affect typing speed?

Not typing speed itself, but it can affect how quickly and consistently each keystroke registers during very fast input, which reduces the chance of a keystroke feeling delayed or dropped.

Is my wireless keyboard’s polling rate lower than a wired one?

It depends on the connection method. Bluetooth keyboards are capped around 125Hz by the protocol itself, but gaming-grade wireless keyboards using a dedicated 2.4GHz USB dongle can reach the same 1000Hz as wired models.

Why does my keyboard show a lower Hz than advertised when I test it?

Because browser-based tests measure timing through JavaScript, which carries small system and rendering overhead compared to direct hardware polling. A drop from the rated spec (e.g., 1000Hz showing as 800–900Hz) is normal and doesn’t indicate a faulty keyboard.

Is a 1000Hz polling rate good for a keyboard?

Yes, it’s genuinely good — 1000Hz is the sweet spot most gamers and fast typists should aim for. It reports your keystrokes every 1ms, which is fast enough to keep hardware delay out of the equation in almost any game or typing scenario. It’s also what most professional esports players actually use, so you’re not missing out by not going higher.

Is 125Hz better than a 1000 Hz keyboard?

No, 125Hz is slower. It only reports every 8ms compared to 1000Hz’s 1ms, so there’s more delay between your keypress and it registering on your PC. For everyday typing, browsing, or office work, you’ll never notice the difference — but for gaming or fast typing, 1000Hz is the better choice every time.

Is a 4000 Hz polling rate good for a keyboard?

It’s good on paper, but most people won’t actually feel the difference. Going from 1000Hz to 4000Hz cuts your response interval from 1ms down to 0.25ms, a real number, but one that’s smaller than most human reflexes (or even most monitors) can take advantage of. It’s mainly worth it if you’re already running high-refresh-rate hardware (240Hz+ monitor) and want every possible edge.

Conclusion

This Keyboard Polling Rate Test helps you verify your keyboard’s real input performance. Test, adjust your settings, and retest to improve stability and reduce delay.

umair aalam
Owner & Creator • PollingRateTester.com | Website |  + posts

PollingRateTester.com provides browser-based testing tools for measuring mouse DPI, polling rate, latency, and other device performance metrics. All tools are tested on real hardware, including USB and Bluetooth mice and high-refresh-rate monitors, to ensure accurate and repeatable results.
The website is maintained by a technical team that regularly updates tools and guides in response to browser, sensor, or firmware changes to keep measurements consistent, precise, and transparent.

Scroll to Top