Your files stay on your device

# Test your gamepad

Press buttons and move the sticks to check a game controller.

Press any button on the controller to wake it: browsers only expose a gamepad after its first input. Some wireless controllers also need their mode switched (Xbox/Nintendo/Android) before the mapping lands.

- Press any button on the controller to wake it: browsers only expose a gamepad after its first input. Some wireless controllers also need their mode switched (Xbox/Nintendo/Android) before the mapping lands.
- The Gamepad API has no events for button changes; the page polls while the controller is connected, and stops the moment it disconnects.
- mapping: 'standard' means the browser promises the spec layout, so labels are real names. 'nonstandard' means raw indices only; labels would be guesses, so there are none.
- This tool exists for hub completeness: it shows what the browser sees, for debugging a controller setup. It makes no claims about latency, polling rate quality, or gaming performance.
- The vibration actuator is only reported present; the test pulse plays solely when you press the button, and unsupported pads honestly read 'no actuator'.
no controllerPaste, drop, or type to begin. Everything stays on this device.

## More device tests

- [Keyboard test](/device/keyboard)
- [Webcam test](/device/webcam)
[All device tests](/device)

---

Canonical HTML: https://nutter.tools/device/gamepad/
Markdown version: https://nutter.tools/device/gamepad/index.md
Plain-text version: https://nutter.tools/device/gamepad/index.txt
Agent index: https://nutter.tools/llms.txt