Gamepad Test
Press every controller button, move both sticks, and run a neutral drift check.
Press any button to connect
Gamepad & Controller Tester
Connect any USB or Bluetooth gamepad (Xbox, PlayStation, Nintendo, generic HID) to verify button presses, trigger analog values, and joystick drift.
No active gamepad detected. Ensure your controller is connected via USB or Bluetooth and press any button.
Press any button on your connected controller to activate browser detection.
Analog Joystick Axes & Drift
Stick Drift Check: When untouched, axes values should sit within ±0.05 of zero. Values permanently resting above ±0.15 indicate potentiometer wear (stick drift).
Browser Gamepad API provides standardized axis coordinates; it does not replace manufacturer firmware calibration tools.
How to Test
- •Connect your controller by USB or Bluetooth and press any button.
- •Watch each button and stick axis register in real time.
- •Run the Neutral Drift Check with the sticks untouched for 2.5 seconds.
Browser Limitations
- •Connection alone does not verify every button — press each control to observe it.
- •The drift threshold is this tool’s approximate heuristic, not a manufacturer certification.
Troubleshooting Tips
- •Controller not detected? Press a button while the page is focused to wake the browser API.
- •Some controllers need xpad/xone drivers on Linux or Steam Input to appear.
About the Gamepad Test
The Gamepad Test connects through the browser’s Gamepad API: press any button on a connected controller and the pad appears here with every button, stick axis, and trigger shown live. Move the sticks and watch their axes trace the full range, then run the neutral drift check to see how far from center each stick sits while untouched.
This is the fastest way to check a controller before a gaming session or a second-hand purchase: confirm every button fires, both sticks center cleanly, and the triggers sweep smoothly — without installing console or vendor software.
Tips for a reliable result
- Connect by USB first — it is the most reliable — and press any button once so the browser detects the pad.
- Press every button, including the D-pad, shoulder buttons, and stick clicks (L3/R3), and watch each one register.
- For the drift check, leave the sticks untouched for the full duration; even small constant offsets show up.
- Compare both sticks: a small symmetric offset is normal analog tolerance, while a large constant offset on one side points to wear.
- Keep wireless controllers close to the computer and away from other 2.4 GHz traffic during the test.
Common problems and fixes
The controller is not detected
The Gamepad API only reports a pad after a button press, and only while the page is focused: click the page, then press a button. On Linux, some pads need xpad/xone drivers or Steam Input enabled to appear.
A stick shows drift without input
A small offset inside the tool’s tolerance band is normal analog tolerance. A large constant offset is worth investigating, but it does not identify the cause on its own: worn potentiometers, a stick that was recalibrated while held off-centre, and debris around the base can all produce one. Clean around the stick base and recalibrate with the sticks resting, then retest — if a constant offset survives that, the stick module may need replacement, and the stick-drift guide on this site covers the repair path.
Buttons register but triggers do not
Triggers are analog axes on modern pads. If they never move, try a different USB port or browser — some browsers report analog triggers only when the pad’s mapping is recognized.
Inputs arrive late or stutter
Wireless interference or heavy CPU load delays event polling. Switch to USB, move the wireless dongle to a front port, and close background apps while testing.
FAQ
Does this work with any controller brand?
Xbox, PlayStation, Switch Pro, and generic PC controllers all expose the standard Gamepad API. Vendor-exclusive extras — audio passthrough, custom profiles — are outside what a browser can see.
Why do I have to press a button first?
It is a privacy rule built into the Gamepad API: a pad is not reported until you interact with it, so pages cannot silently enumerate your controllers. Press any button while this page is focused.
Can I test rumble or vibration here?
If your browser exposes the pad’s vibration actuator, the tester enables a rumble check. Support is optional in browsers today, so a missing rumble test means your browser lacks the API — not that the pad cannot vibrate.
Does the drift check certify my stick?
No. The threshold is this tool’s practical heuristic for flagging drift, not a manufacturer measurement, and a flagged offset does not identify the cause. Use it to compare before and after cleaning or recalibrating, or to document a fault.
Is any data from my controller uploaded?
No. Button and axis readings render locally and disappear when you close the tab.