Gamepad Test
Inspect connected gamepad buttons, axes, triggers and analog dead-zone behavior.
How to use this test
Connect the controller, press any button to expose it to the browser, then move sticks and press each button while watching the mapped labels and dead-zone readout.
How the measurement works
The tester polls navigator.getGamepads at a throttled display rate, labels standard-mapped buttons, tracks analog axes and records peak trigger/button pressure.
How to interpret results
Centered sticks should sit close to zero after the dead zone is applied. Large idle offsets or flickering buttons can indicate drift, calibration issues or a worn switch.
Troubleshooting tips
Reconnect the controller, press a button after page load, try USB instead of Bluetooth and confirm the browser supports the Gamepad API.
Related tests
You can also browse every utility from the complete tool index.
Common gamepad questions
How do I test a controller for stick drift?
Connect the controller, release the sticks completely and watch the raw axis position and dead-zone visualizer. A persistent offset that returns when untouched can indicate drift or calibration issues.
Read full answer →Why is my controller not detected by the browser?
Some browsers expose a controller only after you press a button. Reconnect it, try USB instead of Bluetooth, press a button after page load and confirm that the browser supports the Gamepad API.
Read full answer →How can I test controller triggers and buttons?
Press each button and trigger while watching the live mapped values. Standard-mapped controllers get familiar labels, while non-standard controllers may show raw button numbers because their layout is not guaranteed.
Read full answer →Why is my controller not detected until I press a button?
Many browsers expose a gamepad to the page only after user interaction for privacy and security reasons. Press a controller button after opening the page.
Read full answer →