Gamepad

Polling Rate Check

Measure how many times per second your gamepad reports its state. See your live polling rate in Hz and check how stable it is.

Not Connected
Plug in your controller, press any button, then click Connect Controller. Move the sticks or press buttons continuously during the test — controllers stop sending packets when idle to save power.
Polling Rate
Waiting…
0 HZ
Range labels: Low ≤125 Mid 250–500 High 1000+
Move the sticks! Continuous input forces full-rate packets. Idle = lower readings.
Avg Rate
0Hz
Peak Rate
0Hz
Interval
0.00ms
Jitter
0.00ms

Stability Visualizer

Last 100 samples — flat line = stable
125 500 1000+

Performance Reference

Bluetooth standard ~125 Hz · 8 ms latency
Bluetooth (DualSense) ~250 Hz · 4 ms latency
Pro wireless ~500 Hz · 2 ms latency
USB / 2.4 GHz ~1000 Hz · 1 ms latency
Disclaimer

This tool measures the rate at which your browser receives controller state updates, which is typically capped by Chrome's V-Sync or animation-frame loop (often around 60 Hz / 16.7 ms). Real hardware polling rates may be much higher — actual 1000 Hz USB controllers often appear as 60–250 Hz here. Use the readings for relative comparison (wired vs Bluetooth, controller A vs B) rather than absolute hardware spec verification. Browser scheduling, OS power-saving, and laptop battery mode can all affect results.

What a Controller Polling Rate Test Measures

Polling rate is how many times per second your controller reports its current state to your computer or console. It's measured in hertz (Hz): a 250 Hz controller sends an update 250 times a second, once every 4 milliseconds; a 1000 Hz controller updates 1000 times a second, once every millisecond. This test counts those updates in real time and shows you the effective polling rate your controller is actually achieving right now — not the number on the box, but the real one your system sees.

The measurement runs in your browser through the Gamepad API. There's no install and nothing leaves your device. Move a stick continuously or hold a button and the tester samples how frequently fresh data arrives, converting the interval between updates into a live Hz figure plus a stability reading.

Polling Rate, in Plain Numbers

The relationship between Hz and milliseconds is the whole story. A higher polling rate means a shorter gap between updates, which means the game hears about your input sooner. Here's what the common rates translate to:

125Hz
8 ms
Older / budget controllers. Fine for casual and single-player.
250Hz
4 ms
The default for most console controllers over USB. Solid baseline.
500Hz
2 ms
Common on PC gaming controllers. Noticeably crisper than 250.
1000Hz
1 ms
High-end / pro pads. The point of diminishing returns for most players.

Each doubling of polling rate halves the worst-case input delay contributed by polling. Going from 125 Hz to 250 Hz removes up to 4 ms; 250 to 500 removes up to 2 ms; 500 to 1000 removes up to 1 ms. The gains are real but shrink each step — which is why the jump from 125 to 250 is widely felt, while 500 to 1000 is debated.

Why Your Real Polling Rate Differs From the Spec

Almost every controller polls lower than its advertised maximum in normal use, for reasons that have nothing to do with the controller being faulty. Understanding why stops you from chasing a problem that isn't there.

Connection type caps the rate

Bluetooth almost always polls lower and less consistently than USB. A controller capable of 1000 Hz wired might only manage a jittery 125–250 Hz over Bluetooth, because the radio protocol schedules updates in fixed windows. If your measured rate is low, the very first thing to check is whether you're wired or wireless.

The OS and browser add scheduling limits

The browser's Gamepad API is itself polled by the page, typically tied to your display's refresh rate via the animation frame loop. On a 60 Hz monitor, the browser may only read the controller ~60 times a second even if the controller is sending data far faster. This is a measurement ceiling of the web platform, not a fault in your controller — native games can poll faster than a browser can.

Power saving throttles wireless controllers

To save battery, many wireless controllers reduce their polling rate when idle and ramp up only when they detect active input. If you start the test and see a low number that climbs as you move the sticks, that's power management working as designed, not a defect.

How to Read Your Result

Two numbers matter: the average rate and how steady it is. A controller locked at a rock-steady 250 Hz is healthier than one bouncing between 90 Hz and 260 Hz, because consistency is what your hands actually feel. Use this guide to interpret what you see:

Steady, at or near expected rateWired controller holding 250–1000 Hz with little variance. Working exactly as it should — no action needed.
Lower than expected but steadyLikely Bluetooth or a browser refresh-rate ceiling. Try a USB connection and re-test to see the controller's true capability.
Wildly fluctuatingBig swings between high and low suggest interference, a failing cable, an overloaded USB hub, or background software hijacking input. Investigate the connection.

How to Improve Your Polling Rate

If your measured rate is lower than your controller should deliver, work through these in order. The first two solve the overwhelming majority of cases.

Switch to a wired USB connection

This is the single biggest improvement available and it's free. A wired connection bypasses the radio scheduling that throttles Bluetooth, typically taking a controller from a jittery 125–250 Hz to a stable 500–1000 Hz. For any game where responsiveness matters, wired is the answer.

Test in a native app, not just the browser

Because the browser caps polling near your monitor's refresh rate, the in-browser number understates what the controller does inside an actual game. If you want to verify the hardware's true ceiling, a native polling-rate utility will show higher numbers than any web test can. The browser test is perfect for spotting problems and comparing controllers, but it isn't the controller's absolute maximum.

Use a direct motherboard USB port

USB hubs and front-panel ports routed through extension cables can add latency and reduce effective polling, especially when shared with other devices. Plug the controller straight into a rear motherboard port and re-test.

Update controller firmware and drivers

Manufacturers occasionally raise supported polling rates through firmware. On Xbox, use the Accessories app; on PlayStation, check via the console's controller settings; on PC, install the latest official driver. A firmware bump can unlock a higher rate the hardware always supported.

Close background input software

RGB suites, macro tools, and overlays hook the input pipeline and can interfere with clean polling. Quit them entirely and re-test to see whether your variance drops.

Does a Higher Polling Rate Actually Help You?

This is where honesty matters more than marketing. The benefit of polling rate depends entirely on what you play and what the rest of your setup looks like.

Where it genuinely helps

Competitive fighting games, fast FPS titles, and rhythm games reward lower input delay, and there the move from 125 Hz to 500 Hz is felt. Players doing frame-perfect inputs benefit from the tighter timing window a higher rate provides.

Where it doesn't

If you're on a 60 Hz TV with Game Mode off, your display is adding 50–80 ms of lag — optimizing the controller's 3 ms of polling delay is pointless until the display is fixed. Polling rate is one small link in a long chain, and it's rarely the weakest link. Fix your display and connection type first; chase polling rate last.

Polling rate and total latency are related but distinct — polling is the ceiling on how often the controller can report, while latency is the full end-to-end delay. To measure the complete picture, run the Latency Test. While the controller's connected, the Joystick Test checks for stick drift, the Gamepad Tester confirms every input registers, and the Battery Check shows your charge level.

Polling Rate vs Refresh Rate vs Frame Rate

These three numbers all use hertz and all affect how responsive a game feels, which is why they're constantly confused. They describe completely different things, and a bottleneck in any one of them limits the others.

Polling rate (the controller)

How often your controller reports its state, measured at the input device. 250–1000 Hz is typical. This is what the test on this page measures. It sets how quickly your button press can possibly be noticed.

Frame rate (the game)

How many images per second the game renders, measured in FPS. At 60 FPS the game only checks for and acts on input 60 times a second — once every 16.7 ms. A 1000 Hz controller feeding a 60 FPS game still only gets acted upon 60 times a second, because the game can't respond between frames.

Refresh rate (the display)

How many times per second your monitor draws a new image, measured in Hz. A 60 Hz display shows a new frame every 16.7 ms regardless of how fast the controller polls or the game renders. This is why a high-refresh monitor feels more responsive even with the same controller.

The practical takeaway: these stack. Your felt responsiveness is limited by the slowest link. A 1000 Hz controller is wasted on a 60 FPS game on a 60 Hz monitor — the controller is reporting 16 times for every single frame the game and display can use. Balance the three rather than maxing one.

Platform Notes

PlayStation (DualSense & DualShock 4)

Over USB, the DualSense reports at a steady rate well-suited to console play. Over Bluetooth it drops and becomes less consistent. PS5 games are built around the controller's wired and wireless behaviour, so for normal console use you don't need to tune anything — but for PC play, plug in via USB-C to get the controller's best polling.

Xbox (Series & One controllers)

Xbox controllers over the proprietary Xbox Wireless protocol poll more consistently than generic Bluetooth, which is part of why the official Xbox Wireless Adapter is recommended over a generic Bluetooth dongle on PC. Wired USB remains the most consistent. Keep controller firmware current via the Accessories app.

PC controllers

This is where polling rate matters most and where you have the most control. Many PC-oriented and pro controllers expose polling-rate options in their software and support 1000 Hz over USB. If you're buying specifically for low input delay, a wired controller with a configurable 1000 Hz rate gives you the headroom — just remember the rest of your chain has to keep up for it to matter.

Frequently Asked Questions

What is a good controller polling rate?
250 Hz (4 ms) is a solid baseline that most console controllers hit over USB and is fine for the vast majority of games. 500 Hz (2 ms) is noticeably crisper and common on PC gaming controllers. 1000 Hz (1 ms) is the high end found on pro pads, though the difference between 500 and 1000 Hz is subtle for most players. Below 125 Hz starts to feel sluggish in fast-paced games.
Why is my controller polling rate so low in this test?
Two common reasons. First, if you're on Bluetooth, the wireless protocol schedules updates in fixed windows and caps the rate — switch to USB to see the true number. Second, browser-based tests are limited by your monitor's refresh rate because the Gamepad API is read on the animation frame loop, so a 60 Hz display caps the browser reading near 60 Hz even when the controller sends data faster. Native games can poll faster than any browser test.
How do I test my controller polling rate?
Connect your controller via USB or Bluetooth, press a button to activate it, then continuously move a stick or hold an input while the tester samples how often fresh data arrives. The tool converts the interval between updates into a live Hz figure. For the most accurate reading of your controller's real capability, use a wired USB connection.
Does a higher polling rate reduce input lag?
Yes, but by a small and shrinking amount. Going from 125 Hz to 250 Hz removes up to 4 ms of worst-case polling delay; 250 to 500 removes up to 2 ms; 500 to 1000 removes up to 1 ms. Polling is only one component of total input lag, though — your connection type, OS, game engine, and display all add far more. Fix those bigger contributors before chasing polling rate.
Is 1000 Hz polling worth it for a controller?
For most players, no — the difference between 500 Hz and 1000 Hz is hard to feel and easily swamped by display lag or a wireless connection. It genuinely helps in competitive fighting games, fast FPS, and rhythm titles where frame-perfect timing matters. If you play those competitively on a low-lag display with a wired connection, 1000 Hz is a real if modest edge. Otherwise it's marketing.
Why does my polling rate fluctuate?
Some fluctuation is normal, especially on wireless. Large swings usually point to a specific cause: radio interference from Wi-Fi or other 2.4 GHz devices on Bluetooth, a failing or charge-only USB cable, an overloaded USB hub, or background software (RGB suites, macro tools, overlays) hooking the input pipeline. Switch to a direct wired connection and close background apps to isolate the cause.
Can I change my controller's polling rate?
Sometimes. A few PC-focused and pro controllers expose a polling-rate setting in their companion software. Most console controllers run at a fixed rate that you can't change directly, but you can reach their maximum supported rate by using USB instead of Bluetooth and keeping firmware up to date. The biggest lever for most people isn't a setting — it's switching from wireless to wired.
Related Tools

You Might Also Like

Guides & Articles

Helpful Guides

In-depth articles on testing, fixing, and optimizing your gaming gear.