Output
Buttons; normalized axes; supported haptics
UserBenchmark / All Tools / Gamepad Tester
Performance
Gamepad Tester
Inspect controller buttons, stick axes, drift and supported vibration.
Free to useNo downloadNo sign-up
Gamepad Tester · At a glance
Quick answer: Inspect controller buttons, stick axes, drift and supported vibration. Axis values are normalized browser readings.
Gamepad Tester
The test loads when you open it. Device access is requested only after you choose to start.
Detailed guide
How to use this tool
- Connect the controller and press a button to expose it to the browser.
- Inspect buttons and sticks at rest and through their full travel.
Input
Connected controller and physical interaction
Browser requirement
Gamepad API; device-dependent haptics
Processing
Runs on your device; no tool-result upload
How it works and what the result means
Axes are normalized browser values. A stick resting away from zero can indicate drift, but deadzones and controller mapping influence the readings.
Reading the result
Axis values are normalized browser readings. Center offsets are useful drift clues but mapping and deadzones influence interpretation.
What to check next
Try another USB connection or browser if absent. Haptics appear only when the reported device supports them.
Vibration is requested only when you press its button and the controller reports a supported actuator. Some browsers or controllers do not expose haptics.
Frequently asked questions
Does a nonzero center value prove unusable drift?
No. Compare its size, consistency and behavior in the game deadzone you use. This page reports values rather than prescribing a universal pass threshold.
How do I start the Gamepad Tester?
Connect a controller and press a button to make it visible to the browser. Watch button pressure and stick axis values.
Does this tool require a download or an account?
No. Open the interactive tool above in a modern browser. The instructions and explanations are available even with JavaScript disabled; running a test needs JavaScript.
Why can two attempts give different results?
Power settings, background tasks, browser scheduling, operating-system input processing and device settings affect measurements. Compare repeated attempts with identical settings rather than the single highest score.