How to use Gamepad Tester
- Connect a controller and press a button so the browser can expose it, then select its controller index from 0 to 3.
- Set a sample duration from 1 to 60 seconds. Release the controls and select Start neutral drift sample; keep the controller untouched for a neutral measurement.
- When sampling finishes, select Read sample to review axis minimum, maximum, mean and mean absolute values. You can stop early with Stop sampling.
- Download the observed values as JSON if useful. For button or stick checks, take a separate deliberate-input sample and watch the live values; do not treat it as a neutral-drift measurement.
Example: Gamepad Tester
Read the statistics from a single neutral observation with two zero-valued axes.
Supported inputs and limits
- Requires the browser Gamepad API and a controller exposed to this page.
- Supports indexes 0 to 3, sixteen axes and sixty-four buttons.
- Samples last one to sixty seconds and stop at 3,600 observations.
- Sampling stops when hidden or disconnected.
- Browser mappings, controller firmware, dead zones and OS-reserved inputs affect observed values.
More details
The neutral sample should be taken without touching sticks or triggers.
Statistics describe received values only, rather than proving a fault, calibration quality or manufacturer specification.
Physical-controller testing is separate from synthetic API tests.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Questions about Gamepad Tester
Why is a connected controller missing?
Some browsers expose a controller only after a button press. Check permissions, controller support and the selected index.
Is a nonzero average always hardware drift?
No. Dead zones, mapping, touch input and driver behavior affect the observed values. Compare repeat samples in the same environment.
Can the tester calibrate or repair a controller?
It only reads browser-delivered state. It does not change firmware or system calibration.