Gamepad tester

Test controller buttons, sticks, triggers, dead zones, and supported vibration with live browser feedback. Connect by USB or Bluetooth; no download required. Input is processed in this browser.

How to test your controller

Open this page in a browser that supports the Gamepad API, then connect a controller by USB or Bluetooth.
Press a controller button to wake it; some browsers only expose a pad after user interaction.
Select its controller slot, then press each button and pull both triggers. Detected buttons light up and are counted; trigger values update as you pull.
Move each stick through its range, then release both and select Check drift to sample their average offset. Repeat the sample with the controller untouched.
Use the dead-zone slider to view a different reference ring. Try vibration controls only if your browser and controller support them.

Understanding controller readings

Button not responding

The press count does not rise, or the button does not light up. Verify the controller mapping and retest in another browser.

Stick offset

The stick dot does not return near the center, or repeated idle samples show an offset. Browser readings can vary; this is not a hardware diagnosis.

Rapid repeated presses

Rapid repeated presses are noted from browser event timestamps. This cannot distinguish switch bounce from a deliberate fast press or prove a hardware fault.

Trigger values

The reported trigger value does not rise smoothly toward 1.00. Some controllers expose triggers differently or as digital buttons.

Stick range

Compare the reported range after moving the stick fully in every direction. Browser calibration, controller design, and API mapping affect the result.

Connection drops

The selected controller disconnects or disappears from the browser. Check its cable, battery, pairing, and active controller slot.

The diagram follows standard Gamepad API indices. Non-standard mappings and vendor-specific features can use different labels or may not be exposed to the browser.

Troubleshooting

Use the test as a functional browser check, not a certified hardware diagnostic.
If an input is missing, reconnect or recharge the controller, confirm its OS pairing, then test in another supported browser.
Close other software that may be exclusively using the controller and press a button again to wake it.

Frequently asked questions

Which controllers work?

Many USB and Bluetooth controllers can work, including Xbox, PlayStation, Nintendo Switch, and generic gamepads, provided your operating system and browser expose them through the Gamepad API. Button layout, vibration, and extra features vary by model.

My controller is not detected

Use a supported, up-to-date browser on HTTPS or localhost, connect or pair the controller, then press a button to wake it. Check the selected slot and close software that may capture the device.

Can I test more than one controller?

Yes. Pick Controller 1 to 4 above. A green dot means that slot is connected.

Does this measure polling rate or input lag?

No. Browser timestamp updates and animation frames are not raw controller reports. The page cannot certify polling rate, response latency, or input lag; results depend on browser scheduling, operating system, and device.

Why does vibration not work?

Vibration output is optional in the browser API and depends on browser, operating system, connection type, and controller support. A missing response does not necessarily indicate a fault.

What does the controller diagram show?

The diagram uses standard Gamepad API button indices. If the controller reports a non-standard mapping, displayed labels may not match its printed labels. Only inputs exposed to this page can be shown.

Is my data sent anywhere?

Gamepad inputs are read and processed locally in your browser. This tool does not upload the controller readings.