How to use this test
- Connect through USB or Bluetooth using your operating system. Open this page over HTTPS and start reading.
- Press a controller button while this page is active. Select the controller if more than one appears.
- Press every button and move both sticks through their travel. Check individual B0, B1 and later button values.
- Pause and save the button and axis observations. Use the separate stick drift test for a timed hands-off baseline.
Read the observations
Buttons are shown by API index because labels differ across controller families. A standard mapping gives a common interpretation, while a non-standard mapping needs its own reference. Button values commonly range from 0 to 1, including analog triggers when exposed as buttons. Axes are commonly in the range −1 to 1. The two circles assume axes 0/1 and 2/3; controllers with another arrangement should be read from the raw axes in the report.
What this test cannot tell you
A browser may not expose a controller until you interact with it. Drivers, remapping software and firmware can change the values before this page sees them. This tool does not flash firmware, calibrate the device, measure end-to-end latency or certify circularity. Use the dedicated stick drift test for a timed resting sample.
Need a closer comparison? Controller not detected in the browser.
Questions about the test
Why is no controller detected?
Press a controller button with the page visible. Check the OS connection, close remapping tools temporarily and compare USB with Bluetooth.
Are Xbox, PlayStation and Nintendo controllers supported?
They can work when the operating system and browser expose them through the Gamepad API. Compatibility and mapping vary; no model is guaranteed.
Technical references
Method version 2.0 · Page updated 2026-10-20