Gamepad Deadzone Test
Sample your sticks at rest to see resting noise and a suggested deadzone. It never changes system settings.
This feature isn’t available here
The Gamepad API isn’t available here.
Commonly supported by: Chrome, Edge, Firefox, Safari (desktop).
What you can do: Use a recent desktop browser.
How this test works
Gamepad tests use the Gamepad API, which the browser only reveals after you press a button on the controller. On each animation frame we poll the current snapshot of every connected pad and read its buttons, analog triggers and stick axes.
Stick values are normalized to a −1…+1 range. Drift and deadzone tests sample the sticks at rest to visualize how far they sit from center, and how much that reading wanders, rather than judging a controller from a single reading.
Vibration is only offered when the browser exposes a haptic actuator for your controller, and intensity and duration are bounded for safety. We never report a fake rumble.
How to use it
- Connect your controller by USB or Bluetooth.
- Press any button — the browser hides gamepads until they send input.
- Watch buttons, triggers and sticks respond live in the visualization.
- For drift tests, leave the sticks untouched to sample their resting position.
- For vibration, use the bounded intensity and duration controls to trigger a rumble.
What it detects
- Whether the browser sees the controller and its standard or custom mapping
- Button pressed states and analog trigger values
- Stick axis positions, resting offset (drift) and suggested deadzones
- Whether a haptic actuator is available for vibration
What it can’t detect
- A definitive ‘broken’ verdict from one short sample
- Hardware wear versus a mapping or calibration difference
- Vibration on controllers or browsers that don’t expose the haptics API
Troubleshooting
| Symptom | What to do |
|---|---|
| Controller not detected | Press any button first — browsers hide gamepads until they receive input — and confirm it’s connected and powered. |
| Wrong button mapping | Non-standard controllers may not match the standard layout; the raw indices are still shown. |
| Small stick offset at rest | A tiny resting offset is normal; only a consistent, larger off-center reading suggests real drift. |
| Vibration does nothing | Your controller or browser may not expose the haptics API; we never fake a successful rumble. |
FAQ
Why isn’t my controller detected?
Press any button first — browsers hide gamepads until they receive input. Also make sure it’s connected and powered.
Is a little stick drift normal?
A tiny resting offset is normal. Consistent, larger off-center readings may indicate real drift.
Does vibration work?
Only where the browser exposes the haptic API. We never fake a successful rumble.
Which controllers are supported?
Most standard USB and Bluetooth controllers (Xbox, PlayStation, and many others) that the browser’s Gamepad API recognizes.
Can I test multiple controllers at once?
Yes — connect several and each appears separately once you press a button on it.
Is my controller input sent anywhere?
No. Button, trigger and stick data are processed locally and never uploaded.
Related tests
Sample your sticks at rest to visualize deadzone, drift magnitude and range. One sample doesn't condemn a controller.
Connect a controller and see live button values, analog triggers, axes and mapping for one or more devices.
A live JSON view of all buttons and axes, with a local event-trace recording you can download for debugging.