Why is my controller not detected?
Some browsers wait for a controller button press before showing it. Check the connection and try again with this tab open.

Check a connected controller's buttons and stick movement. The page shows the inputs your browser receives without changing controller settings.
Connect a controller, then press a button on it.
B0, B1, and other button numbers are the browser's labels. The number beside each button shows its value; the tile fills when the browser marks it as pressed.
An axis is one direction of stick movement. Its value usually runs from -1 to 1, with zero at the centre. Button order can differ when the mapping is non-standard.
If no controller appears, keep the tab open and press a button on the controller. Then check the connection and browser support.
A small value at rest does not by itself prove stick drift. Compare repeat runs and the controls in a game, where small movements may be filtered out.
Some browsers wait for a controller button press before showing it. Check the connection and try again with this tab open.
They are positions reported by the browser, not printed button names. Non-standard mappings can use a different order.
Not necessarily. Compare repeated readings at rest with the behaviour in a game. The page does not apply a dead zone to hide small movements.
No. It only reads the inputs reported by the browser. It does not change calibration, firmware, or vibration settings.
Last reviewed: