How to use the gamepad test
- 1
Connect your controller by cable or Bluetooth.
- 2
Press a button so the browser can detect it.
- 3
Move sticks and press buttons while watching live values.
Connect a controller and inspect buttons and analog axes reported through the browser Gamepad API.
The original controller artwork responds only to current browser values.
Standard controls illuminate only when the browser reports a standard mapping. Current mapping: not reported.
Shown when the browser exposes triggers at standard button indices.
No button or axis activity yet.
Connect your controller by cable or Bluetooth.
Press a button so the browser can detect it.
Move sticks and press buttons while watching live values.
The Gamepad API exposes the controller name, button values, and analog axes supplied by the browser. Many browsers reveal a USB or Bluetooth controller only after a button is pressed while the page is active.
Mappings for sticks, triggers, and extra buttons vary by controller, driver, browser, and operating system. Untouched controls remain untested; they are never automatically labeled broken.
Press a button after connecting, then verify that the operating system recognizes it.
Mappings vary by controller, driver, browser, and operating system.
Check battery level, reduce interference, or try a wired connection.
No. Support and mappings vary, especially for specialized controllers.
No. It reports browser values but does not change calibration.
Continue through all 17 core checks in one guided session and download a private PDF report.