Skip to content

Gamepad API Tester

Inspect what the Gamepad API actually returns for the selected device.

Start testing Read guide
Gamepad API Tester

Gamepad API workspace

Useful for developers validating browser support and report shapes.

Inspect raw Gamepad API snapshots for development

The Gamepad API Tester is aimed at developers and power users who want to see ids, mapping strings, button arrays, axes, and timestamps as the browser reports them. It complements player-facing views on Controller Tester by emphasizing the underlying objects rather than stylized dualsense or Xbox chrome.

Honest limits remain central: no direct XInput, no guaranteed GamepadHapticActuator, no WebHID DualSense NVS writes from this page. Pose and touch surfaces may be undefined. Treat missing optional fields as specification gaps across browsers, not necessarily broken controllers.

Developer walkthrough

  • Log mapping values: standard versus empty strings.
  • Compare button length across pads to catch adapters.
  • Watch axis noise at rest before blaming game code.
  • Cross-check with Gamepad Debugger for live watchers.

Mapping disagreements belong on Gamepad Mapping Tester. Player detection failures still start at Controller Detection.

FAQ: can I automate hardware QA with only this page?

It helps gather evidence, but CI-grade controller farms need native hooks. Browsers throttle background tabs and differ by OS builds.