Controller Polling Rate Test

01 / Signal basics

What Is Controller Polling Rate?

Controller polling rate is the count of input updates sent to the computer each second. A rate of 1000 Hz means the browser can receive a new state about every 1 millisecond. A rate of 125 Hz means the gap is near 8 milliseconds. The number helps you judge input delay, but it does not tell the whole story.

Think of a controller as a small radio that reports its state again and again. Each report can carry stick position, button state, and trigger value. A higher rate gives the game more chances to see a change. That can feel useful in a fast aim duel or a tight parry. It does not turn a slow game into a fast one. Frame time, game code, display refresh, cable quality, and wireless noise still shape the feel.

Controller Polling Rate Test Hardware Basics

Most pads send input through USB, a 2.4G receiver, or Bluetooth. The browser reads the exposed state through the MDN Gamepad API. This page measures the updates seen by that API. It does not read a secret chip clock. The result is best used as a repeatable browser check for one setup.

Connection type gives a useful first clue. USB often has a steady path. A 2.4G dongle can also stay near 1000 Hz when its link is clear. Xbox Bluetooth often sits near 125 Hz, while some PlayStation pads report a higher rate. The exact value depends on the model, firmware, OS, and browser. If you want to check buttons and axes at the same time, use the Gamepad Tester after this rate check. The Controller Polling Rate Test keeps the rate view separate from those button checks.

02 / Test conditions

Why Are My Test Results Unstable?

Unstable values often come from the test path, not a broken pad. A browser shares time with the page, the display, the OS, and other tasks. Short runs can catch a few odd gaps and make the result look worse than the long trend.

Chrome and other browsers often work near the screen refresh cycle. A page on a 60 Hz display may see updates in a pattern close to 60 frames per second. A 144 Hz screen can show a different pattern. The Gamepad API also uses a pull model in many browsers. That means the page asks for the current state instead of receiving every hardware packet as a native driver would.

Chrome vSync Limitation

When a graph seems stuck at 60, 120, or 144, move a stick in a slow loop and press a few buttons. Many pads use event-driven reports. They may stay quiet while every control rests. Movement wakes the report path and gives the page more changes to count. Keep the motion steady for several seconds. A burst of one button press is too short for a fair rate check.

Power Saving Interference

Laptops can lower USB and radio activity while on battery. A hub can add another delay. Bluetooth may also reduce work when the pad is idle. Plug in the laptop, use a direct USB port, and close other controller tools before you compare two runs. Do not compare a wired result with a wireless result and call the gap a fault.

• Run each test for at least ten seconds.
• Keep the same browser and display refresh mode.
• Move the stick in a calm, repeatable loop.
• Repeat a low result after a fresh reconnect.
• Write down the link type beside the measured value.

Look for a stable band, not one lucky peak. A short spike can raise the peak rate while the average stays low. That is normal for a shared browser clock. If the line has wide gaps every run, try a new port or cable. You can also compare the pad in the Stick Drift Test to see if its live axis reports drop out too.

04 / Read the panel

How to Read the Polling Rate Result

Read the live rate first, then use average, peak, interval, and jitter to add context. No single box can tell you if a pad feels good. The group of values shows how steady the input path is. Run the Controller Polling Rate Test twice when a result feels out of place.

Live rate uses the latest accepted gap. It can move up or down as the browser sees new reports. Average rate smooths the recent window and is often the best value for a quick comparison. Peak rate shows the fastest recent gap, so it can look high after one short burst. Estimated interval turns the live rate back into milliseconds. Lower delay means a shorter theory gap, not a full end-to-end latency score.

Jitter measures how much the gaps spread around their mean. Near-zero jitter means the recent intervals were close. A high value means the path had uneven gaps. It does not always mean the controller is bad. A busy tab, battery mode, or wireless noise can raise it. Let the test run longer before you make a call.

For a quick guide, 1000 Hz maps to 1 ms, 500 Hz to 2 ms, 250 Hz to 4 ms, and 125 Hz to 8 ms. Those are math values. A real click still travels through the switch, firmware, browser, game, frame queue, and display. Use this tool to spot a weak link, not to promise a final click-to-photon number.

If a rate looks low and stick values also jump, run the Stick Drift Test with the same cable. If the center or range needs work, the PS Controller Calibration guide can help with supported Sony hardware. Related checks make it easier to separate a rate issue from a stick issue.

05 / Risk and choice

Advanced note: Can Controllers Be "Overclocked"?

Some USB controllers can be pushed to report more often than their stock setting. The change usually comes from a driver or filter that asks the OS to poll the device at a shorter interval. It is not the same as changing the controller's sensor or switch.

Tools such as hidusbf are often named in overclock talks. They can raise a 125 Hz USB path toward 500 or 1000 Hz on some systems. Results depend on the controller, driver, port, and OS build. A change that works on one PC may fail on another. A browser test can show a new received rate, but it cannot prove that every game will use it in the same way.

⚠️ A steady 125–250 Hz result is safer than an unstable number that looks fast.

Overclock work can add link drops, odd input reports, and a small CPU load. A bad filter can make a pad vanish until the driver is removed. Firmware and board parts may also run outside the range set by the maker. That does not mean the board will fail at once. It does mean you should keep a restore plan and avoid changes on a pad you need for a match.

• Record the stock rate before any change.
• Use a restore point or the maker's driver path.
• Test buttons, sticks, and rumble after the rate change.
• Stop if the pad drops out or reports false inputs.
• Keep the stable setup for play that needs trust.

For most casual games, a stable link matters more than a big label. If a pad already gives a clean 250 Hz result, the gain from a risky tweak may be hard to feel. The safest use of this page is a before-and-after check with the same game, cable, browser, and display. Keep the setup that gives you repeatable control.