Blog

Controller buttons not responding? How to check

Test each controller button in your browser, then find out whether the problem is the game, the connection, the button mapping, or the controller itself.

Brandon ColeGames 5 min read

You press a button in a game and nothing happens, even though the controller seems connected. The problem could be the button, the wireless connection, or the game's input settings. Testing the controller outside the game helps narrow it down.

The Gamepad Test shows whether button presses, sticks, and triggers are reaching your browser. Test the controller first, then use the results to choose the right fix.

Test the controller buttons

  1. Open the Gamepad Test. Connect the controller by USB or Bluetooth if it is not already connected.
  2. Press a button on the controller to wake it and let the browser detect it. Keep the test page in the foreground while you check the inputs.
  3. Press each button once, then press the sticks and triggers. Look for a corresponding change in the test. Test the buttons that fail in your game more than once.
  4. If you have more than one controller connected, disconnect the others and repeat the test. This helps you tell which device is sending each input.
  5. Return to the game and try the same buttons. Compare what happens in the game with what you saw in the test.

Some browsers do not show a controller until you press a button after opening the page. If the test does not detect it, click the page, press a controller button, and wait a moment before deciding that the controller is not recognized.

What the result means

Every button responds in the test

The controller is sending button inputs to the browser. If the same buttons fail only in one game, check that game's controller settings, input mode, and button assignments. The game may be listening to a different controller or using a custom layout.

One button or a group of buttons does not respond

If other inputs register but one button does not, the button may be stuck, worn, or assigned differently than you expect. If several buttons in a cluster fail together, check whether the controller has a profile or remapping mode enabled. Test the same buttons in another game or on another device before concluding that the hardware is broken.

The controller is not detected

The browser is not receiving controller data. The controller may be asleep, disconnected, paired to another device, or unsupported by its current connection mode. Try a wired connection if available, then reconnect it and press a button again.

The test responds, but the game does not

This points to the game rather than a dead button. The game may have controller support turned off, a different input device selected, or a binding that was changed. Some games also ignore controller inputs while a menu, text field, or another window has focus.

How to fix it

  1. Reconnect the controller. Turn it off and on, or unplug its cable and reconnect it. For a wireless controller, disconnect it from other nearby devices that may be using it, then pair it again.
  2. Check the connection in your device settings. On Windows 11, open Settings › Bluetooth & devices › Devices and check whether the controller is listed as connected. You can also press Windows + R, enter joy.cpl, and press Enter. Select the controller, choose Properties, and check its inputs on the Test tab. On macOS, open System Settings › Bluetooth and check the controller's connection. On iPhone or iPad, look under Settings › Bluetooth. On Android, look under Settings › Connected devices.
  3. Test one controller at a time. Disconnect other controllers, steering wheels, or input devices, then reload the test page and press a button. This can reveal whether the game or browser is picking up a different device.
  4. Check the game's input settings. Open the game's controller or controls menu and confirm that controller input is enabled. Restore the default button layout if you are unsure what was changed, then test again.
  5. Close other games and remapping apps. Another program can change the controller layout or interfere with how an input reaches a game. Close those programs, reconnect the controller, and try the game again.
  6. Charge the controller and try a cable. A low battery can make a wireless controller disconnect or behave inconsistently. If possible, charge it fully and test it with a known-good USB cable.
  7. Restart the device and check for updates. Restart the computer, console, or phone. If the same problem remains, check the controller maker's support instructions for a firmware update or a reset procedure for your model.

When it's the hardware

A button is more likely to be physically damaged if it fails in the browser test and in multiple games, even after you reconnect the controller and try it on another device. A button that only works when pressed hard, feels stuck, or responds intermittently may have a worn switch or debris underneath it.

For a controller under warranty, contact the seller or manufacturer before opening it. Otherwise, compare the repair cost with the price of a replacement. Avoid pouring liquid cleaner into the button gap, since it can damage the electronics.

Why the browser test helps

A game can change button assignments or ignore controller input, which makes a working button look broken. A browser test checks whether the controller is sending the input before the game interprets it. It cannot prove that every game supports your controller, but it can help separate a controller problem from a game-specific setup issue.