Inspect gamepad buttons and axes
Read browser-exposed gamepad state after an explicit user start, without WebHID, WebUSB or haptic commands.
Make the controller visible
Use HTTPS or localhost, choose Gamepad and start. Press a controller button or move an axis; browsers may hide a connected device until interaction. Keep the diagnostic area focused. The tool shows the browser ID label, index, mapping string, timestamp, button indices/values/pressed/touched flags and raw axes.
Understand mapping and dead zone
A standard mapping is the browser report, not proof that printed button labels match. Controls stay indexed B0/B1 and Axis 0/1. The axes 0/1 coordinate view is not a claim about a physical stick. A 0–0.5 UI dead zone sets each axis to zero inside that absolute threshold, without rescaling other values or calibrating hardware. Raw values remain visible; the central square shows per-axis filtering.
Observation rate and disconnects
Reads occur via requestAnimationFrame only while this selected area is active, visible and focused. The displayed reads/second measures UI API observation, not hardware polling. State changes and native connection/disconnection events enter the bounded history. Disconnect removes the live connected indicator. Pause/focus loss clears live controller state; resume rediscovers it.
Recover
If the API is missing, insecure, or blocked by embedding/browser policy, the tool explains the limitation and other tests remain available. Try a secure top-level page, check browser/device connection and interact again. No permissions bypass, drift certification or hardware health verdict is provided.