Why the browser misses some gamepad features

Your controller works in a game, but a browser test shows only some buttons, sticks, or triggers. Or the controls appear, but vibration and other features are missing. That does not automatically mean the controller is broken.

A browser can test only the input the operating system and browser make available to web pages. Use the Gamepad Test to see what your current setup exposes, then narrow down whether the limit is the controller, its connection, or browser support.

Check what the browser can detect

1. Open the Gamepad Test on the computer or device where you want to use the controller.
2. Connect the controller by USB or Bluetooth. If it is asleep, press a control once, then return to the test page.
3. Move each stick, press the buttons and squeeze the triggers. Watch for the corresponding inputs to change in the test.
4. If vibration is available in the test, check it separately. A gamepad can send button and stick input even when the browser cannot trigger its vibration feature.
5. Reconnect the controller and reload the page if nothing appears. Keep the test tab active while you try the controls.

Test one controller at a time if you have several connected. This makes it easier to tell which device is producing the input.

What the result means

Buttons, sticks, and triggers respond, but vibration does not

The browser is receiving ordinary gamepad input. Vibration support depends on the controller, operating system, connection type, and browser. A missing vibration test does not prove the motor is faulty. If the test offers vibration but it does not work, try the controller in a game or system that supports its vibration feature. For more checks, see Controller vibration unavailable: what to check.

Some controls respond, but others are missing

The browser may be receiving a standard set of controls rather than every feature the controller has. The browser Gamepad API, the interface web pages use to read gamepad input, represents common buttons and axes. Special controls such as a touch surface, extra paddles, motion sensors, headset functions, or adaptive triggers may not be exposed as separate inputs. A controller or driver can also present its controls in a different layout.

No controller appears in the test

The browser is not currently receiving a gamepad it can read. The controller may be disconnected, asleep, paired to another device, or using a connection mode the browser does not recognize. Start with the connection and system checks below.

The test sees input, but a game does not

The controller is reaching the browser, but that does not guarantee every game supports its layout or features. A game may listen for only certain buttons, use a different control mapping, or rely on a feature that the browser does not provide. Check the game’s own controller settings before assuming the device has failed.

How to fix missing gamepad input

1. Reconnect the controller. Unplug a wired controller, wait a few seconds, and connect it directly to another USB port. For Bluetooth, disconnect and pair it again. Avoid a hub or adapter for the first test.
2. Check that the system sees it. In Windows 11, open Settings › Bluetooth & devices › Devices and check whether a Bluetooth controller is connected. On macOS, open System Settings › Bluetooth and confirm the controller is connected. A wired device may not appear in the Bluetooth list.
3. Close apps that may be using the controller. Quit games, controller configuration utilities, and remote-play apps, then reload the test. These apps can change how input is presented or keep the controller active in another mode.
4. Check the controller’s connection mode. Some models support different modes for computers, consoles, or mobile devices. Use the mode recommended for your device, and check the controller maker’s instructions if buttons map incorrectly or advanced inputs are missing.
5. Try a different connection type. If the controller is wireless, test it over USB if possible. If it is wired, try Bluetooth only if the controller supports it. Comparing connection types can reveal whether the limitation is specific to a wireless mode or adapter.
6. Update and retest the browser. Install available browser updates, close and reopen the browser, and run the test again. If features are still missing, try another current browser on the same device. Browser support and gamepad mappings can differ.
7. Restart the device. A restart can clear a stuck connection or driver state. Reconnect the controller after startup, then check it in the test before opening a game.

When the controller may be faulty

Test the same controls in another game or on another compatible device. If a particular button or trigger fails everywhere, while other controls work, the control or its connection may be damaged. If the same controller works elsewhere but one browser test omits an advanced feature, browser or operating-system support is a more likely explanation.

For a controller under warranty, document which controls fail and which connection you tested before contacting the seller or manufacturer. For an older controller with a physically unreliable button or stick, repair or replacement may be more practical than changing browser settings.

Why one controller can look different from another

Browsers receive a standardized view of gamepads, not a complete hardware inspection. The operating system and controller driver can translate the device into a common layout, and the browser reports the inputs available through its gamepad support. Extra functions may use proprietary software or may not have a browser interface at all.

That is why a browser test is useful for checking basic input, but cannot certify every feature a controller advertises. A missing feature is evidence about what this browser and connection expose, not proof that the feature is broken.