Connect a controller and press a button to begin.
Left stick
Right stick
Release the sticks and watch the values. Small offsets are not a universal fault threshold; dead zones and mapping vary by controller and app.
Inspect controller buttons and axis values exposed through the browser’s Gamepad API. Standard-mapped controllers show familiar button names; other mappings use numbered buttons. Vibration is available only when the browser and controller expose it.
How to use this tool
Connect a controller, keep this page visible and press a button to activate detection. Test each button and move the sticks slowly. Release the sticks to inspect resting values. Try vibration if its button is enabled.
What this test can and cannot show
Mappings, axes and vibration support vary. The first two axis pairs are drawn as sticks; specialized controllers may use them differently. An offset is not a universal drift diagnosis. This tool shows browser input and does not calibrate or repair a controller.
Updated October 1, 2026. Browser and device support varies.
Questions and troubleshooting
Why is my connected gamepad not detected?
Keep this page focused, press a controller button and confirm the USB or Bluetooth connection. Try a browser that exposes the Gamepad API. Detection depends on what the browser and operating system provide; this page cannot install a driver.
Does a non-zero resting stick value prove drift?
No. Watch the value after releasing and recentering the stick, then compare how your game uses its dead zone. Mapping and tolerances vary. The displayed axes are browser input values, not a universal pass/fail threshold or a calibration.
How this tool was checked
Automated Chromium checks on October 1, 2026 used a simulated controller to check mapping, buttons, axes, vibration requests and disconnect cleanup. Real controller accuracy and physical vibration were not verified.
Technical references: MDN: Gamepad API