Running on your device · 0 bytes uploaded

Test your gamepad

Press a button on the controller and watch every input the browser sees — buttons with real names when the mapping is standard, live axes, and a vibration pulse you explicitly fire.

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 controllerNothing in yet

Paste, drop, or type to begin. Everything stays on this device.

browsers expose a gamepad only after its first button press — no prompt exists to force it

Next door in Device

- Keyboard test (/device/keyboard)
- Webcam test (/device/webcam)
All device tools (/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