Choose Start, then press a button on your controller. Browsers may expose a connected controller only after a button press. Readings stay in this browser; no vibration is requested.

Reading has not started.

Controller

Deadzone (display only) 0.10

Buttons and triggers

Axes

Release centered sticks before measuring. This heuristic checks for stable axis offsets above your deadzone; it is not a hardware diagnosis. Some device-specific axes, including triggers, do not rest at zero.

No resting sample yet.

A QUICK WALKTHROUGH

How to use this tool

Choose Start, then press a controller button so the browser can expose it.
Select a controller and try its buttons, triggers and sticks.
Adjust the display deadzone; release centered sticks and measure their resting offsets for two seconds.

Live buttons, triggers and axes

Buttons show their pressed state and analog value. Standard-mapped buttons 6 and 7 are labeled as left and right triggers. Other mappings keep the browser’s numbered inputs; layout and support vary by browser and device.

Resting drift is a heuristic

A two-second sample checks for stable average axis offsets beyond the selected deadzone. Movement above 0.08 across the sample requests another measurement. Release centered sticks first: some device-specific axes and triggers rest away from zero, so this is not a hardware diagnosis or calibration.

Explicit, local reading

The Gamepad API is read only after Start. Browsers may expose connected pads only after a controller button press. Reading pauses while the page is hidden and stops when the selected device disconnects, when you stop, or when you leave. Nothing is uploaded and no vibration is requested.

GOOD TO KNOW

Common questions

Why is my connected controller missing?

Choose Start and press a button on the controller. If it remains missing, check the controller connection and browser support for the Gamepad API over HTTPS. This page cannot force the browser to expose a device.