Start by separating hardware from software.
A browser cannot read a controller until the operating system recognizes it as a gamepad. The fastest diagnosis starts outside the webpage: confirm power, data connection, pairing, and system-level detection before changing browser settings.
Most browsers also require a button press after the page opens before revealing a gamepad. This privacy behavior means a connected controller can appear absent until you actively use it.
Work through the checks in order and change one variable at a time. That makes it easier to distinguish a cable, wireless, driver, browser, or controller-mode problem.
Work through the likely causes.
- 01
Press a face button while the tester tab is active, then wait a moment for the device list to update.
- 02
For USB, use a known data-capable cable and another direct computer port; some cables provide power only.
- 03
For Bluetooth, remove the old pairing, restart pairing mode, and reconnect through operating-system settings.
- 04
Confirm the controller appears in Windows game-controller settings, macOS system information, or the platform's supported input panel.
- 05
Close games, Steam Input, emulators, remappers, and virtual-controller tools that may take exclusive control or hide the physical device.
- 06
Try a current Chromium-based browser or Firefox, reconnect the controller, reload the page, and press a button again.
Check what the browser can see.
Open the full tester to inspect buttons, sticks, triggers, mapping, range, and neutral noise.
Repeat before you conclude.
A repeatable issue across connections, browsers, and native games is stronger evidence of a controller fault than a one-time browser reading. If the problem appears only in one game, review that game’s controller support, deadzone, remapping, and launcher settings.
What to keep in mind
Avoid downloading unknown driver packages from unofficial sites.
How the browser readings are defined
Our live tools use the standardized browser Gamepad interface and explain its limits in our methodology. Device mappings and proprietary features can still differ by operating system, browser, connection, firmware, and controller mode.
Questions about this issue
Why does the controller charge but not connect?
A charge-only or damaged cable can deliver power without data. Test a cable known to transfer files or controller input.
Why must I press a button first?
Browsers commonly wait for user interaction before exposing a gamepad to a webpage. It helps prevent passive device discovery.
What if the operating system cannot see it?
The website cannot fix that layer. Check the cable, receiver, batteries, pairing, input-mode switch, drivers, firmware instructions, or manufacturer support.