GAMEPAD CHECK

SETUP · VALUES · LIMITS

How to Test a Controller Online

Use this guide to connect a controller, make it visible to the browser, and interpret the raw evidence without overstating what a browser test can prove.

USB or Bluetooth

Connection setup

  1. 01

    Connect

    Plug in a known data-capable USB cable or pair the controller in your operating system's Bluetooth settings.

  2. 02

    Expose

    Open the tester, keep the tab active, and press a physical button so the browser can expose the controller.

  3. 03

    Verify

    Confirm the expected device appears before moving sticks, pressing buttons, or starting a timed trial.

Support follows exposed APIs

Browser capability guide

Chrome and Edge reference

Current desktop Chrome and Edge are the practical reference for broad Gamepad API coverage, but exposed mappings and output support still depend on the device and platform.

Firefox, Safari, and mobile browsers

Use only the capabilities they expose. Availability is not identical across browsers, operating systems, controller models, permissions, or connection modes.

Interpret, do not guess

Read raw values

Axes

The Gamepad API reports every axis as a normalized value from -1 to 1. A standard mapping defines the meaning of each axis and button index; it does not guarantee that center is exactly 0 or that physical travel reaches -1 or 1. With a non-standard mapping, confirm each control by its raw index.

Buttons

A button value is normalized from 0 to 1, and pressed is a boolean state. Touched is a browser-observed state; it does not prove a physical touch sensor because an implementation may derive it from pressed or value.

Make observations repeatable

How to run a useful test

  1. 01Start from a released, centered controller and note the browser, operating system, and USB or Bluetooth connection mode.
  2. 02Move one control at a time before testing combinations, ranges, or a guided timing window.
  3. 03Repeat the same motion and compare raw evidence instead of treating a single sample as a pass or fail verdict.

What the numbers mean

Measurement limitations

Every result is browser-observed, not a hardware certification. Browser scheduling can change sampled intervals, so this site cannot certify physical polling rate or true end-to-end latency. Use an external physical reference when those measurements matter.

If no input appears

Troubleshooting

  • Keep the tab active, press a physical button, and confirm the correct controller is selected.
  • Verify USB or Bluetooth connection in the operating system, then try another cable, port, or connection mode.
  • Close games, controller mappers, or other tabs that might hold device access.
  • Compare a current Chrome or Edge release if another browser exposes fewer capabilities.

Continue with a focused view

Related controller tools