Troubleshooting
If Chrome does not detect your controller, reconnect it and confirm the browser is up to date. Try a direct USB connection first and avoid hubs, then re-test to see axis and button values. If another site detects it but this page does not, reload the tab and close controller remappers.
Pro tip
Test wired first to rule out Bluetooth latency or pairing issues, then compare results.
Common symptoms
- Chrome not detecting controller
- Gamepad API issues
- Inputs not updating
Chrome gamepad test gives you a quick baseline so you can see what the controller is actually sending. A controller works in one browser but not another, so you want to confirm Gamepad API detection in Chrome. In Chrome, the key is whether the Gamepad API is exposing the device cleanly.
This page is about browser detection: whether the Gamepad API sees the controller and whether values update smoothly. Once that looks stable, you can treat game issues as settings, not detection.
Small drift does not automatically mean the controller is dying. Many games apply their own deadzone, and some browsers smooth axis values. What matters is whether the center value keeps moving with hands off, and whether the movement is big enough to change aim or movement. Keep the chrome gamepad test run short and repeatable.
Quick checks that usually reveal the issue: - Try the d-pad and shoulder buttons, some controllers expose them differently. - Let go of the stick and watch if it settles near center or keeps drifting. - Press every face button once and twice to catch missed taps. - Move each stick in a slow circle and watch for flat spots or jumps.
If the results look different between wired and Bluetooth, that comparison is useful. Run chrome gamepad test once wired, then again over Bluetooth, and note whether the same button or axis is the one acting up. If everything looks fine here but feels wrong only inside one game, the next place to look is usually deadzone, sensitivity, or in-game remapping.
For more input diagnostics, open the broader input tests hub, or use the generic checker at gamepad test online to compare against this specific page. Your last step is simple, if the behavior is repeatable in this page and across devices, it is likely the controller, if it only happens in one title, it is likely settings.
Once you have a baseline, you can come back and re-run chrome gamepad test after each change.