Bluetooth Controller Tester
Confirm a paired wireless pad is visible to the browser and responding.
Bluetooth connection panel
The OS must finish pairing before the browser can list the device.
Validate wireless pads after OS pairing finishes
Bluetooth Controller Tester is for pads that only appear after the operating system completes pairing. Finish Bluetooth settings first, then open this page and press a button so the browser can attach. Wireless convenience brings tradeoffs: occasional actuator gaps, radio noise on stick axes, and multipoint confusion. Compare against a wired baseline on USB Controller Tester when results look strange.
The Gamepad API never replaces your OS Bluetooth stack. If the system panel cannot see the controller, the browser cannot invent it. Distance, interference from USB3 ports, and low batteries all degrade readings without proving mechanical stick failure.
Wireless checklist
- Forget and re-pair if the device stalls half-connected.
- Test near the receiver with a charged battery.
- Confirm idle sticks on Stick Drift over Bluetooth and USB.
- Use Controller Detection when no gamepad enumerates.
Brand pages such as PS5 Controller Tester remain useful once the wireless link is stable.
FAQ: why does rumble vanish only on Bluetooth?
Many browsers expose vibration actuators more consistently over USB. Missing wireless rumble is a common API transport limit, not automatic proof of burnt motors.