Ezels.dev
REFERENCE

Browser support for gamepad testing and WebHID

Testing buttons, sticks and triggers works in every current major browser. Reading a DualSense's gyro, touchpad and battery needs WebHID, which only desktop Chrome, Edge and Opera provide.

Updated

Support at a glance

First browser version that supports each feature
BrowserGamepad API (buttons, sticks, triggers)WebHID (DualSense motion, touchpad, battery)
Chrome 2189
Edge 1289
Opera 1575
Firefox 29Not supported
Safari on macOS 10.1Not supported
Chrome on Android 25Not supported
Firefox on Android 32Not supported
Safari on iOS 10.3Not supported
Samsung Internet 1.5Not supported

Versions come from the MDN browser compatibility data, checked on 8 October 2026. They show when a feature first appeared in a browser. Whether a particular controller works also depends on the operating system, the driver and how the controller is connected.

What the Gamepad API provides

The Gamepad API is how a web page reads controllers. For each controller it reports an id, a list of buttons (each pressed or not, with an analog value for triggers) and a list of axes for the sticks. Every control in this tester except the DualSense extras comes from it. Browsers only reveal a controller to a page after you press a button or move a stick on it, and only to the page that has focus.

The API has no battery level, no gyroscope or accelerometer and no touchpad position, so it can't show them. It also includes a vibration feature, available in Chrome, Edge and Safari 16.4 and later but not Firefox, that this tester doesn't use.

What WebHID adds

WebHID lets a page talk to a USB or Bluetooth HID device directly, after the user picks the device in a browser prompt. This tester uses it, for the DualSense and DualSense Edge only, to read the raw input reports that contain the gyro, accelerometer, touchpad fingers, battery level and the mute button.

  • It needs a secure context, which means the page must be served over HTTPS (or run from localhost).
  • It is limited to desktop Chrome, Edge and Opera. Chrome on Android, Firefox and Safari do not have it.
  • The tester only reads from the controller; it sends no commands.
  • In a browser without WebHID, the Enable HID button reads "NOT SUPPORTED HERE" and everything else keeps working.

Which browser should I use?

  • For everything, including DualSense motion and touchpad: Chrome or Edge on a desktop computer.
  • For buttons, sticks and triggers only: any current Chrome, Edge, Firefox or Safari.
  • On phones and tablets: the browsers above list Gamepad API support, and the page is responsive, but the tester has not been checked with controllers paired to a phone.

Behaviour can differ between operating systems. The same controller can appear under a different name in different browsers, which is why the tester also shows a controller it does not recognise on the tab you have selected. If your controller does not appear, see the controller not detected guide.

Try it

Open the gamepad tester, or go straight to the PS5 controller tester or the Xbox controller tester.

Frequently asked questions

Does the Gamepad API work in Safari?

Yes. Safari has supported it since version 10.1 on macOS and 10.3 on iOS. Safari does not support WebHID, so DualSense motion, touchpad and battery readings are unavailable there.

Is WebHID supported in Firefox?

No. WebHID is available in Chrome, Edge and Opera on desktop. In Firefox the tester still shows buttons, sticks and triggers.

Why does the Enable HID button say "NOT SUPPORTED HERE"?

Your browser does not provide WebHID. Open the page in desktop Chrome or Edge to read DualSense motion, touchpad and battery.

Does the tester work on a phone?

The browsers on phones list Gamepad API support, and the page is responsive. We have not tested it with controllers paired to a phone, and WebHID features are not available on mobile.

Does the tester work offline?

No. There is no offline mode, so the page needs an internet connection to load.