Controller won't reconnect after changing game settings?

You changed a game’s control settings, and now the controller seems disconnected or the game ignores its buttons. A changed button layout can cause confusing input, but it does not necessarily mean the controller has lost its connection.

Check the controller outside the game first. The Gamepad Test can show whether buttons, sticks, triggers, and vibration are responding in your browser. That gives you a useful way to separate a connection issue from a game setting.

Test the controller again

1. Open the Gamepad Test in a browser on the device you play on.
2. Turn on the controller or connect it by USB. Click the test page, then press a controller button so the browser can detect activity.
3. Move each stick, press several buttons, and squeeze both triggers. Check whether the test responds to the inputs you make.
4. If the controller does not appear or respond, unplug and reconnect the USB cable, or disconnect and reconnect the controller in Bluetooth settings. Press a button again on the test page.
5. If it works in the test, return to the game and check its controller and button-mapping settings. Test one setting change at a time.

The browser test checks controller input independently of a game’s control layout. It cannot tell you whether a particular game supports your controller or whether its own profile is configured correctly.

What the result means

The test responds, but the game does not

The browser is receiving controller input, so the controller is connected to the device. The likely problem is the game’s input settings, a disabled controller option, or a profile that does not match the controller. Check the game’s controls menu and restore the default layout if you are unsure which setting changed.

The test responds, but the buttons act differently than expected

The controller is communicating, but the game or operating system may be translating its inputs. A remapped layout can make a working button seem broken. Look for custom bindings, alternate control schemes, or a setting that swaps axes or buttons, then compare the game’s layout with the test results.

The test does not respond after reconnecting

The problem is below the game’s control settings. The controller may be asleep, unpaired, out of battery, connected to another device, or using a bad cable or port. Try the fixes below before changing more game settings.

How to fix it

1. Wake the controller and check its battery. Press its main button, then wait a few seconds. If it is wireless, charge it or replace its batteries before testing again.
2. Close and reopen the game. Some games only detect a controller when they start. Fully quit the game, reconnect the controller, then reopen the game and check its controls menu.
3. Check the game’s controller settings. Make sure controller input is enabled and that the selected layout or profile matches the controller. If you changed several options, use the game’s default controls as a temporary comparison.
4. Reconnect the controller at the device level. On Windows 11, open Settings › Bluetooth & devices › Devices, remove the controller if it is listed but not working, then pair it again. On macOS, open System Settings › Bluetooth, disconnect the controller and reconnect it. On an iPhone or iPad, use Settings › Bluetooth. On Android, open Settings › Connected devices and reconnect or pair it there. Menu names can vary slightly by device.
5. Try a different cable or USB port. Some cables charge a controller but do not carry data. Use a cable that supports data, connect directly to the computer rather than through a hub, and retest.
6. Restart the device. A restart can clear a stuck controller connection. Reconnect the controller after the device starts, then test it before reopening the game.

If the controller works in the browser test but still fails in one game, use the game’s own support or controls options. For broader checks of a controller that is connected but not accepted by games, see Gamepad connected but not working in games.

When to suspect the controller or connection

Test the controller with another cable, USB port, or compatible device. If it fails to connect or the same buttons remain unresponsive in the browser test on multiple devices, the problem is less likely to be the game settings. A worn cable, damaged port, weak battery, or internal controller fault may be responsible.

If wireless reconnection fails but USB works, focus on Bluetooth pairing and battery first. If both wired and wireless connections fail on more than one device, check the controller’s warranty or arrange a repair. A browser test can show that input is missing, but it cannot identify a damaged component inside the controller.

Why the browser test can disagree with a game

Games can use different input systems and may remember a controller profile separately from the computer. A game can also ignore a controller that the browser detects, or interpret buttons differently after a layout change. Compare the test and the game rather than assuming one result proves the other is wrong.

When the browser test shows input, reconnecting the controller again is unlikely to fix a game-only mapping problem. Restore or review the game’s control layout first, then test the changes inside that game.