Gamepad Test Online: Controller, Stick Drift & Trigger Check
Click Controller tester Use this browser-based gamepad tester to check controller detection, button mapping, thumbsticks, trigger travel, drift-watch offset, raw input, and optional vibration support.
Browser gamepad tester
Live controller buttons, sticks, triggers, and vibration
Connect one or more controllers, press any button to wake the active pad, and watch live input, drift-watch offset, circularity, trigger values, and optional vibration support.
No controller detected yet
Connect a controller by USB or Bluetooth, keep this tab active, and press a button, trigger, or stick to help the browser expose it.
Why run a gamepad test online
A gamepad test online is useful when you need a quick answer to practical controller problems: is the pad detected, do the buttons map correctly, do the triggers report smoothly, do the sticks return near center, and does the browser expose vibration at all. It works as a first-pass diagnostic for many Xbox, PlayStation, Nintendo, and generic controllers that the browser can see through the Gamepad API.
How the test works
This page reads live browser gamepad input and shows face buttons, D-pad, bumpers, triggers, stick presses, raw button values, raw axis values, and the current mapping type. It also tracks a simple drift-watch center offset, keeps a stick trace for circular sweeps, and can trigger short haptic tests when the browser exposes vibration support. Because it is based on browser input, it reflects what web apps and browser games can actually see on your current setup.
How to interpret results
If the controller is detected, the expected buttons light up, trigger values move smoothly, and the sticks settle close to center after release, the controller is probably behaving well at the browser level. A moderate or high center offset can suggest stick drift, weak spring return, or a stick that does not rest close to zero. If labels look wrong, the controller may still be fine, but the browser may be exposing a non-standard mapping. If vibration is unavailable, that usually means the browser or current connection path does not expose haptics rather than proving the controller cannot rumble elsewhere.
- Use the controller switcher if more than one pad is connected.
- Press a button after connecting because some browsers only expose live state after user input.
- Compare USB and Bluetooth results if mapping, vibration, or detection behaves differently.
- Use the raw data section when friendly labels look wrong or a mapping seems non-standard.
- Treat drift-watch offset as a practical warning signal, not a formal calibration result.
This tool reports browser-level controller input only. It does not calibrate sticks, repair dead zones, flash firmware, guarantee console compatibility, or provide lab-grade latency or polling-rate measurement. It is best used as a fast browser-side controller diagnostic before deeper hardware testing.