GEARCHECK LAB
Controller Lab // Detection Diagnostics

CONTROLLER CONNECTION TEST

Check whether your browser can see a controller at all, inspect the reported gamepad identity and mapping, and verify that button or stick movement produces fresh input. This is the fastest first check when a controller works in one app but not another.

Live diagnostic

Connection and input detection

WAITING FOR GAMEPAD
Connect the controller and press any button.Many browsers require a user interaction on the gamepad before exposing it to a page. If nothing appears, try USB first, then reload this page and press a face button.
DETECTED DEVICE
GAMEPAD IDNo controller detected
MAPPING—
BUTTONS / AXES0 / 0
GAMEPAD INDEX—
LIVE INPUT HEALTH
BUTTONS ACTIVE0
AXIS ACTIVITY0.0%
TIMESTAMP0
FRESH UPDATES0
NO CONTROLLER INPUT OBSERVED
Waiting for connection…

What this connection test checks

  • Whether the browser exposes a connected Gamepad API device.
  • The device-reported ID, mapping type and gamepad index.
  • How many buttons and axes the browser sees.
  • Whether button presses or stick movement change the live input state.
  • Whether the gamepad timestamp updates during activity.

If your controller is not detected

  1. Press a face button after the page loads.
  2. Try a wired USB connection if you are using Bluetooth.
  3. Confirm the controller works in the operating system or console.
  4. Reload the page after reconnecting the controller.
  5. Try a current Chromium- or Firefox-based browser.
  6. Close software that may be exclusively capturing or remapping the device.

Detected but no input changes?

If the device identity appears but buttons and axes never change, compare another browser or connection method. A driver/remapping layer, firmware state, browser limitation or non-standard mapping can interfere even when the device itself is physically connected.

A successful connection only proves that the browser can see the gamepad. Use the dedicated button, trigger and stick tools to test the quality of individual inputs.

USB vs Bluetooth

The Gamepad API generally does not provide a reliable transport label that tells this page whether the controller is connected over USB or Bluetooth. GearCheck Lab therefore does not guess the connection type.

To compare transport behavior, run the same diagnostic once over USB and once over Bluetooth and note the difference yourself.

Controller connection test FAQ

Why do I have to press a button before the browser sees the controller?

Browsers often gate gamepad exposure until the user interacts with the controller. This is normal and also helps limit silent device fingerprinting.

Why does the gamepad ID look technical?

The ID string comes from the browser/driver layer and can include vendor, product or platform information. It is not standardized into a clean marketing name.

Does GearCheck Lab install a driver?

No. The test only uses browser APIs already available on your device.