Gamepad Not Detected by the Browser?

Common causes

A sleeping Bluetooth controller, charge or cable failure, unsupported browser API, stale pairing, driver problems, remote sessions, and platform privacy rules can hide a controller. Some devices report a nonstandard mapping even when connected correctly.

• A sleeping Bluetooth controller
• charge or cable failure
• unsupported browser API
• stale pairing
• driver problems
• remote sessions
• and platform privacy rules can hide a controller. Some devices report a nonstandard mapping even when connected correctly.

Try these checks in order

1. Step 1. Connect or pair the controller, focus the test page.
2. Step 2. press a face button. Try a data-capable USB cable, reconnect Bluetooth, close games and controller tools.
3. Step 3. reload the page. Confirm the operating system sees the device, then compare another current browser and connection mode..

Change one thing at a time and repeat the browser test. That makes it easier to identify which permission, connection, or routing change actually restored the signal.

What the browser test can confirm

The test can list controllers exposed through the standard Gamepad API and display buttons, axes, stick centers, and observed range. It cannot install drivers, access controllers hidden by the operating system, certify calibration, or guarantee behavior in a particular game.

Limits and privacy

Controller inputs are read locally by the page and are not uploaded by the Device Check test engine.

A successful browser result means the expected event or stream reached this page during the test. It is useful evidence, but it is not a repair, calibration, warranty, or manufacturer certification.

Related guides