Quick answer
What Gamepad Test tells you
Visualize connected controller buttons, triggers, axes, D-pad, mapping and optional vibration through the Gamepad API.
- Observed here
- Connection and disconnection, Buttons and trigger values, Analog axes and drift plot.
- How to interpret it
- Buttons and axes show values exposed by the browser Gamepad API after interaction. Mapping and axis order depend on the controller and browser, not just the labels on its case.
- Important limit
- Results reflect events and values exposed by this browser.
- Data handling
- Controller identity and input values are displayed locally and are not transmitted or stored.
Useful next comparison: Press one button at a time, move each stick through its range and compare mapping in the application where the issue occurs.
Understanding the result
What a result means
A connected controller appears only after the browser exposes it, often after a button press. Button, trigger and axis values confirm the mapping received by the page; they do not certify force feedback, battery condition or console-only features.
Confirm the pattern by repeating connection and disconnection. Results reflect events and values exposed by this browser.
How to use this test
- Connect by USB or Bluetooth.
- Press any controller button so the browser exposes it.
- Move every stick and press each button.
- Disconnect or close the page when finished.
What this test checks
- Connection and disconnection
- Buttons and trigger values
- Analog axes and drift plot
- Mapping and optional vibration
What this test cannot check
Results reflect events and values exposed by this browser.
This test does not certify hardware or replace professional inspection.
Controller ID is shown locally but never sent.
Console-only functions may not be exposed to a browser.
Common problems and troubleshooting
Press a button after loading, reconnect USB or Bluetooth and close applications that may claim the controller. Test each mode separately and record the local button number when a non-standard mapping differs.
- Repeat the same observation. Focus the test surface and repeat “Connection and disconnection” three times under the same conditions.
- Change one condition. Compare “Buttons and trigger values” after changing only the relevant port, connection, browser setting or application.
- Rule out focus or interception. Close overlays and reserved shortcuts, keep the page visible and confirm that the live indicator changes during the action.
- Keep the result within its limit. Results reflect events and values exposed by this browser.
If the same pattern remains across relevant applications and connections, give the manufacturer or a qualified technician the repeatable observations instead of a guessed fault label.
Browser compatibility
The Gamepad API is strongest in current Chromium and Firefox desktop browsers; support and mapping vary on Safari, mobile platforms and wireless profiles. Controller identifiers remain local and are never sent with analytics.
| Browser | Reference status | Evidence basis | Version | Notes | Checked |
|---|---|---|---|---|---|
| Chrome | Supported | Expected baseline | Not recorded | Feature detection is authoritative; permissions, platform and device support can change availability. | 2026-08-27 |
| Microsoft Edge | Supported | Expected baseline | Not recorded | Feature detection is authoritative; permissions, platform and device support can change availability. | 2026-08-27 |
| Firefox | Partial | Expected baseline | Not recorded | Feature detection is authoritative; permissions, platform and device support can change availability. | 2026-08-27 |
| Safari | Partial | Expected baseline | Not recorded | Feature detection is authoritative; permissions, platform and device support can change availability. | 2026-08-27 |
Privacy information
Controller identity and input values are displayed locally and are not transmitted or stored.
The public analytics allowlist does not accept pressed keys, typed text, pointer coordinates, media labels, device IDs, recordings, video frames or controller input. Test results are not written to LocalStorage.
Primary technical references
These specifications define the browser signals used by this test. They document web-platform behavior; they do not certify a particular device.
Frequently asked questions
Is this Gamepad Test free?
Yes. The test works without an account, download or payment.
Is my test data uploaded?
Controller identity and input values are displayed locally and are not transmitted or stored.
Does this result prove my hardware is faulty?
No. It shows what the browser can observe. Repeat the test, compare another browser or device, and seek qualified support when the result matters.
Turn this result into a useful comparison
A working indicator or an unexpected event is only a starting point. Choose a plan to compare another application or connection and record what changed.
- Plan a Controller Drift and Mapping Check — Compare browser controller discovery, centered axes and game behavior before changing dead zones or assuming a damaged stick.