Connect And Wake
Plug in USB, pair Bluetooth or insert a 2.4G receiver, then press a button so the browser lists the gamepad.
Controller Polling Rate Test
Move a stick for 8 to 10 seconds to estimate browser-visible gamepad Hz, input interval, jitter, sample count and stability. Use the same browser and PC to compare USB, Bluetooth and 2.4G controller modes.
controller polling rate testgamepad Hz checkerjitterUSB vs Bluetooth
Quick Steps
Run the sample the same way every time before judging whether one connection mode is actually faster.
Move Continuously
Rotate a stick or press buttons for 8 to 10 seconds so the page receives enough visible input changes.
Repeat The Same Way
Run at least two passes per mode and change only one variable, such as cable, USB port, adapter or browser.
Result Metrics
Use the full metric set. A high peak with poor stability is less useful than a steady average with low jitter.
Average Hz
The main comparison number. It averages the visible update frequency collected during the current rolling sample.
Peak Hz
The fastest burst observed. Treat it as a ceiling, not as proof that the controller is stable at that speed.
Interval
The average time between visible updates. For example, 250 Hz is about 4 ms and 1000 Hz is about 1 ms.
Jitter
The spread in update intervals. Lower jitter means the browser sees more consistent timing.
Samples
The number of visible updates in the rolling sample. Very low sample counts are not enough to judge a setup.
Stability
A consistency score derived from variation around the average Hz. It helps catch unstable adapters or noisy wireless paths.
Accuracy & Methodology
This page measures the update layer the browser can see. It is designed for setup comparison, not hardware certification.
Browser Measurement Layer
The tester reads navigator.getGamepads() and uses exposed timestamps or input-change timing to estimate visible update frequency.
Sample Size And Confidence
Move for 8 to 10 seconds and look for a stable sample count. Repeat the pass if the graph has only a few points or obvious gaps.
API Limits
The Gamepad API is not a USB protocol analyzer. Some browsers do not expose reliable hardware timestamps, and high-Hz devices may appear lower in JavaScript than in native tools.
What Is Controller Polling Rate?
Polling rate is how often a controller or receiver can report input updates to the host device.
Hz Means Reports Per Second
125 Hz means roughly 125 update opportunities per second. 1000 Hz means roughly 1000 per second when the full path supports it.
Interval Is The Same Idea In Milliseconds
Divide 1000 by the Hz value to get the theoretical report interval: 125 Hz is 8 ms, 250 Hz is 4 ms, and 1000 Hz is 1 ms.
It Is Not Total Input Lag
Full latency also includes stick mechanics, firmware, wireless transmission, the game engine, frame pacing, display scanout and response time.
How To Test Correctly
A clean polling test controls the environment before it compares numbers.
Use A Foreground Tab
Keep this page focused and avoid running a game, capture tool or heavy download during the sample.
Move Instead Of Waiting
Many gamepads reduce reports when idle. Continuous stick movement gives the browser more changes to observe.
Compare Like With Like
Use the same browser, monitor mode and power profile when comparing USB, Bluetooth, 2.4G or different USB ports.
Guide: Polling Rate Result Bands
Use this table to turn the Hz reading into a practical setup judgment. The interval is the theoretical spacing between reports before game and display latency.
| Result band | Interval | How to read it |
|---|---|---|
| Under 125 Hz | Over 8 ms | Low for modern PC play. Check Bluetooth mode, browser support, battery saver and whether input is moving. |
| 125 Hz | 8.0 ms | Common baseline for standard controllers and Bluetooth HID paths. Often acceptable for casual play. |
| 250 Hz | 4.0 ms | A solid console-class result and a normal cap for many licensed wireless controller paths. |
| 500 Hz | 2.0 ms | Strong PC result when USB or a 2.4G receiver exposes stable updates to the browser. |
| 1000 Hz | 1.0 ms | High-performance PC target. Use stability and jitter to confirm the result is actually steady. |
| 2000 Hz+ | 0.5 ms or less | Premium controller territory. A browser may report lower than native software or hardware analyzers. |
Interval is calculated as 1000 / Hz. It describes report spacing only, not total button-to-photon latency.
Settings / Fix / Change
If the result is lower than expected, change the connection path before blaming the controller.
Try USB First
Use a data-capable cable and a motherboard USB port as the baseline. Front-panel hubs and low-quality cables can reduce stability.
Move Wireless Receivers
Place 2.4G dongles away from metal cases, USB 3.0 noise and other wireless devices. A short extension cable often helps.
Check Vendor Software
Some controllers require Razer Synapse, GameSir Nexus, 8BitDo Ultimate Software or similar tools to enable 500 Hz, 1000 Hz or higher PC modes.
Troubleshooting
Most abnormal readings come from idle input, browser visibility limits, wireless variability or power management.
Reading Stuck Near Display Refresh
If the result clusters around 60, 120 or 144 Hz, the browser path may be frame-scheduled. Repeat in another Chromium browser and compare USB mode.
No Controller Detected
Press a button after connecting, close apps that capture the controller, and use a browser with Gamepad API support.
Spikes Or Dropouts
Disable laptop battery saver, close overlays, avoid crowded Bluetooth environments and repeat with a wired connection.
Community Benchmarks / Reference Ranges
These rows are source-linked reference values from real controller models. They are not yet live user submissions, and your browser-visible result may be lower than native or hardware-level tests.
| Controller / setup | Published or measured rate | Notes |
|---|---|---|
| Xbox Wireless Controller | 125 Hz published baseline | Useful baseline for first-party Xbox pads. If your browser result is much lower while moving a stick, compare USB and wireless modes.Windows Central |
| Razer Raiju V3 Pro | 250 Hz PS5 wireless; 2000 Hz PC wired | Razer lists separate PlayStation and PC polling paths, which is why the same controller can show very different rates by platform.Razer FAQ |
| Razer Wolverine V3 Pro 8K PC | 8000 Hz spec; about 7500 Hz measured | Razer lists 8000 Hz wired and wireless on PC. One reviewer measured about 7500 Hz, with motherboard USB closer to the target than front case USB.Razer specWindows Central test |
| GameSir G7 SE | 250 / 500 / 1000 Hz PC settings | Reported as a wired PC controller with selectable higher polling modes. Console behavior can be lower than PC mode.Windows CentralWIRED review |
| Turtle Beach Stealth Pivot | 125 Hz wireless; 165 Hz wired | A real example where a premium controller can feel good on console but still show low PC polling figures.Windows Central review |
Reference values are source-linked and should be treated as sanity ranges, not guarantees for every firmware, USB port, driver, browser or operating system.
Controller Polling Rate Test FAQ
Short answers for using this browser-based controller tool and interpreting the result.
Is this controller polling rate test accurate?
It is accurate for browser-visible updates, not for raw USB electrical polling. Use it to compare setups on the same computer and browser, not as a lab certificate.
Why should I rotate a stick during the test?
Many controllers are event-driven and report less often when nothing changes. Continuous stick movement keeps input changing so the browser can observe update frequency.
Is 125 Hz Bluetooth normal?
Yes. Many Bluetooth HID paths show around 125 Hz or variable readings in browsers. USB or a quality 2.4G receiver often reports higher and more stable values.
Why does my 1000 Hz or 8000 Hz controller show a lower browser result?
The page measures browser-visible Gamepad API updates, not the raw USB bus. High-Hz controllers can appear lower when the browser, driver, operating system, USB hub or power profile does not expose every hardware report to JavaScript.
Are the benchmark rows live community submissions?
Not yet. The table uses source-linked reference values from real controller models and reviews. Treat them as sanity ranges until a verified submission system is added.
Can a web page measure real input lag?
A web page can estimate update interval and browser-visible stability. It cannot measure the full chain from button press to game engine response to display output.
Do I need 1000 Hz for games?
Not always. A stable 250 Hz reading can already feel responsive for many games. Competitive shooters and fighting games may benefit from higher and more consistent update rates.