Gamepad Polling Test

Measure the browser observed update rate, report interval and timing stability of a USB or Bluetooth gamepad.

Local signal only
  1. 01Connect and press a button
  2. 02Move one stick in circles
  3. 03Compare rate and stability
Live timestamp trace Move the left stick in smooth circles during the whole trace
0%
Browser measurement limit

This estimates updates visible through the Gamepad API. It does not certify USB polling, controller overclocking or total input latency.

Zoom 100%
Utilities Studio

Want this utility on your website?

Customize colors and dark mode for WordPress, Notion or your own site.

Frequently Asked Questions

What does this gamepad polling rate checker measure?

It measures changes in the Gamepad timestamp exposed to the browser while you move an analog stick. The reported Hertz value is an observed browser update rate, not a direct electrical measurement of the USB polling interval.

Can a browser verify that my controller is running at 1000 Hz?

It can show whether timestamp updates are reaching the page at a high and consistent rate, but it cannot certify a 1000 Hz USB overclock. Browser scheduling, timer precision, operating system handling and the Gamepad implementation can hide or group hardware reports.

Why do I need to move the analog stick in circles?

Continuous circular movement keeps both axes changing and provides a useful stream of fresh controller states. Holding the stick still can leave too few meaningful updates for a stable comparison.

Can I compare USB and Bluetooth controller performance?

Yes, repeat the same duration and circular movement for each connection and compare observed rate, interval and jitter in the same browser. Treat the result as a relative browser based comparison rather than total input latency.

# Measure Browser Observed Gamepad Polling Rate

This checker watches the high resolution timestamp attached to the selected gamepad while an analog stick is moving. It removes extreme intervals, calculates a stable average interval and converts that interval to an observed rate with 1000 divided by milliseconds. Everything runs locally in the current page.
Reading What it describes What it does not prove
Observed rateTimestamp updates exposed to this page each secondThe electrical USB polling rate
Update intervalAverage time between browser visible timestamp changesTotal button to screen latency
JitterSpread between the 5th and 95th percentile intervalsA hardware fault by itself
ConfidenceSample quantity and consistency for this runLaboratory grade accuracy

# How to Run a Repeatable Controller Hertz Test

Close demanding background work, keep this tab visible and move the same stick in smooth circles for each run. Use the same browser, connection method and duration when comparing controller firmware, USB settings or Bluetooth behavior. A ten second window usually collects enough reports without making the test tedious.
Compare like with like
Run at least two passes after changing a cable, Bluetooth adapter, USB port or operating system setting. A single peak is less useful than a repeatable observed rate with narrow jitter.

# Why This Is Not an End to End Latency Test

The Gamepad API exposes controller state after the operating system and browser have processed it. It does not see the electrical report at the cable, the game engine input loop, rendering, display scanout or pixel response. The update interval is therefore useful for browser level diagnostics, but it must not be presented as complete input latency.

Bibliographic References