Polling Rate Test - Free Online Controller Hz & Input Frequency Checker

For competitive gaming, 1000 Hz via USB is the gold standard — it delivers a 1ms polling interval and the lowest possible input delay from the controller itself. For general gaming, 250 Hz (4ms) is excellent and most players cannot perceive the difference between 250 Hz and 1000 Hz in practice. 125 Hz (8ms) is acceptable for casual play but noticeably laggy for competitive scenarios. If our test shows you are at 60 Hz or lower, your browser or OS is throttling the connection — check your power settings, use Chrome on Windows, and test via USB.

This is expected. Browser-based polling rate tests measure the browser-received frequency rather than the raw hardware output. Two factors reduce the reading: first, the browser's own Gamepad API polling cycle (typically 60 Hz in most browsers) can act as a ceiling; second, OS driver processing adds a small delay between hardware report and browser delivery. The result you see typically runs 10–20% lower than the hardware spec. This is normal and does not indicate a problem with your controller. For readings above 500 Hz, a native desktop application will give more accurate measurements.

The Gamepad API only generates new timestamp events when the controller's state changes. If the stick is stationary and no buttons are pressed, the controller sends no new data packets — there is nothing to measure. By moving the analog stick continuously, you generate a constant stream of unique state updates, each with a new timestamp. The time delta between these timestamps is what we use to calculate polling rate. Moving in smooth circles gives the most consistent stream of updates and the most accurate Hz reading. Rapid jerky movements or stopping mid-test will introduce gaps that distort the measurement.

No — the impact of polling rate varies significantly by game type. In competitive FPS, fighting games, and rhythm games, where precise timing and fast reaction are critical, the difference between 125 Hz (8ms) and 1000 Hz (1ms) is meaningful and can influence performance. In RPGs, turn-based games, adventure games, and slower-paced titles, a 7ms difference is effectively imperceptible. Some older game engines actually do not poll input faster than 60 Hz themselves, making any controller polling above 60 Hz redundant in that specific title — though the improvement is still real at the OS and driver layer.

Jitter is the variation in timing between consecutive data packets. A controller with 1000 Hz polling and zero jitter would deliver exactly one packet every 1.000 ms. In practice, jitter means that some packets arrive after 0.8ms and others after 1.3ms — even if the average is 1.0ms. High jitter makes inputs feel inconsistent and "stuttery" even if the average polling rate looks good. Low jitter means your inputs arrive in a predictable, smooth rhythm. USB connections produce much lower jitter than Bluetooth. Background processes and CPU load increase jitter. Our tool displays jitter as the standard deviation of interval times in milliseconds.

The PS5 DualSense already achieves excellent polling rates — approximately 1000 Hz via USB-C and ~250 Hz via Bluetooth. The USB connection is already at the upper limit of standard HID polling. You can use the hidusbf driver override tool on Windows to attempt to push beyond 1000 Hz, but this provides diminishing returns and requires careful setup. More impactful improvements are: ensuring you use USB-C rather than Bluetooth, updating DualSense firmware to the latest version via Sony's PC updater, and disabling USB power saving in Windows Device Manager. These typically restore or confirm full polling rate without any risk.

For wired USB controllers, higher polling rate has a negligible effect on power consumption — the controller is powered by the USB cable and the radio transmission overhead is not a factor. For wireless Bluetooth controllers, higher polling rates do increase radio transmission frequency, which modestly reduces battery life. This is one reason why many wireless controllers default to 125–250 Hz rather than the maximum they could achieve — it is a deliberate trade-off between responsiveness and battery longevity. If you are testing wirelessly and want maximum accuracy, we recommend switching to USB for both the polling test and competitive play.

No — these are completely different metrics. Controller polling rate (Hz) is how often the gamepad sends its state to the computer — it governs input latency. Display refresh rate (Hz) is how often your monitor or TV updates its image — it governs how smoothly you see motion on screen. A high-refresh-rate display (144 Hz) paired with a low-polling controller (125 Hz) will show smooth visuals but will have laggy inputs. For the best gaming experience, optimise both: high controller polling rate (via USB) and high display refresh rate together minimise all forms of perceptible latency. Our tool measures controller polling rate only.

Bluetooth has a fundamental bandwidth and latency overhead that USB does not. Bluetooth packets are packetised, encoded, transmitted over the 2.4 GHz radio spectrum, received, decoded, and then delivered to the OS. This entire process takes time and limits how frequently new controller state data can be delivered. Standard Bluetooth HID operates at around 7.5ms intervals (approximately 125–133 Hz). Even advanced Bluetooth implementations in the PS5 DualSense improve this to around 250 Hz but cannot match USB. Additionally, wireless interference from nearby devices (Wi-Fi routers, other Bluetooth devices, microwave ovens) increases jitter further. If you need consistent low-latency input, a USB connection is always recommended.

Partially. A healthy controller should deliver a consistent, smooth polling rate with low jitter when tested via USB. If our test shows extremely high jitter (large swings between minimum and maximum Hz), erratic readings, or a rate significantly below the expected value for your controller and connection type — this can indicate a hardware or firmware issue. A damaged USB port on the controller, a faulty cable, corrupted firmware, or a failing internal clock can all affect polling consistency. However, many polling rate variations are caused by the OS, browser, or USB hub rather than the controller hardware itself — rule out software causes first before concluding a hardware fault.

No. This polling rate test runs entirely within your browser using the W3C Gamepad API. All timestamp reading, interval calculation, Hz derivation, jitter analysis, and chart rendering happen locally in your browser tab. No controller data, polling rate results, stick position values, or any other information is transmitted to our servers at any point. You can confirm this by opening your browser's developer tools Network tab during the test — you will see no outbound requests to our servers while the tool is running.

Scan rate (also called sampling rate) refers to how often the controller's internal microcontroller checks its own sensors — buttons, analog sticks, and triggers. Polling rate refers to how often the controller transmits that data to the host computer. These are two distinct steps in the input chain. A controller might scan its inputs at 8000 Hz internally (like some Razer keyboards) but only report via USB at 1000 Hz. For browser-based testing, only the polling rate (what the computer receives) is measurable. The scan rate is a hardware specification you can find in manufacturer documentation.