When a gamepad tester stays empty, the problem is usually connection order, exclusive apps, or limited browser support, not a dead site. Start on Controller Detection so you can see whether navigator.getGamepads() lists anything at all. Then open the Controller Tester once a device name appears. The Gamepad API only exposes controllers the operating system already accepts, and many pads stay idle until you press a button after connecting.
Fast checklist
- Connect the pad, then press any face button to wake browser detection.
- Prefer USB if Bluetooth pairing is incomplete or flaky.
- Close games, Discord overlays, and exclusive capture tools that may lock the device.
- Retry in an up-to-date Chromium, Firefox, or Safari desktop build.
- On phones and tablets, Gamepad API support is often limited or missing.
USB versus Bluetooth
USB is the most reliable path for first detection and for rumble experiments on Vibration. Bluetooth must finish pairing in the OS Bluetooth panel before the browser can list the device. Incomplete pairing looks identical to a missing controller in a gamepad tester. On Windows, confirm the pad appears under Bluetooth or USB devices, then return to the browser and press a button again. The PC Controller Tester is a convenient place to retest after you fix the OS side.
Browser and platform limits
If Device Manager or system settings see the pad but the browser does not, the limitation is usually the browser stack. Mobile Safari and many Android browsers offer weak or inconsistent gamepad support. Private modes, outdated builds, and strict site permissions can also block events. Stick tools such as Stick Drift and Deadzone cannot run until detection succeeds, so solve presence first.
What to try next
Swap cables and ports, forget and re-pair Bluetooth, and test a second browser. If the pad works in one browser only, keep using that browser for diagnostics while you investigate extensions or policies on the other. Read Controller on PC for Windows quirks, Gamepad API Explained for honest API limits, and the general Troubleshooting tree when multiple symptoms stack. Extra notes live on the blog.
Remember: a blank detection page means the Gamepad API never received a live pad snapshot. Fix OS visibility, wake the controller with a button press, remove exclusive locks, and retest. Once the device lists, continue with button, stick drift, and deadzone checks so you separate connection failures from hardware wear.