Controller not reconnecting after a browser restart?

Your controller worked in a browser game, but after restarting the browser it is missing or no longer responds. The controller may still be paired to your computer, while the new browser session has not detected it yet.

Use the Gamepad Test to check whether the browser can see the controller and register its buttons, sticks, triggers, and vibration. Then you can tell whether to reconnect the controller, adjust a setting, or investigate the browser.

Test the controller after restarting the browser

1. Connect the controller to your computer, then open the Gamepad Test. Move a stick and press a few buttons. Check that the test responds to the inputs you make.
2. Close the browser completely, not just the tab with the test. Keep the controller connected for this first check.
3. Open the same browser and profile again, return to the Gamepad Test, and interact with the page. Move a stick and press buttons to see whether inputs register.
4. If the controller does not appear to respond, press a controller button once, then reload the test page and try again. Some browsers update gamepad information only after a page interaction or a new input.
5. If it is still missing, disconnect and reconnect the controller. For Bluetooth, wake it or reconnect it through your computer's Bluetooth settings. Run the test again.

Use the same browser profile for both checks. A private window or a different profile may have different permissions, extensions, or settings, so it is not a clean comparison.

What the result means

The controller and its inputs appear after reopening the browser

The controller reconnected successfully. If a game still does not respond, check that game's controller settings and make sure it is using the controller you tested. A browser test confirms that the browser receives input, but it cannot confirm that every game supports the same controller layout.

The controller appears only after you press a button or reload the page

The controller was likely connected, but the new browser session had not refreshed its gamepad information. This can happen after a browser restart, after a controller goes to sleep, or when the test page was opened before the controller was ready. If input works after waking the controller or reloading, you usually do not need to pair it again.

The controller is listed, but some buttons or sticks do not respond

The browser sees the controller, but some inputs may not be reaching the page. Check the controller's battery, try another button or stick, and reconnect it. If the same input is missing in other games or tests too, it may be a controller issue rather than a browser restart issue.

Nothing responds after reopening the browser

This does not prove the controller is broken. The operating system may have disconnected it, it may be asleep, or the browser may not have refreshed its input state. Check the computer's Bluetooth or USB connection before concluding the controller has failed.

How to fix it

1. Wake the controller. Press a button or move a stick, then check the test page again. Some wireless controllers sleep when idle. If the battery is low, charge it before testing further.
2. Reload the test page. Reload after the controller is connected, then interact with the page and try the inputs again. If you left another game or test open, close it so you are checking one page at a time.
3. Check the operating system connection. On Windows 11, open Settings › Bluetooth & devices › Devices and check whether the controller is connected. On macOS, open System Settings › Bluetooth and check its connection there.
4. Reconnect the controller. For a Bluetooth controller, turn Bluetooth off and on, then reconnect the controller from the system settings. If it will not reconnect, remove or forget it and pair it again. On Windows 11, use Settings › Bluetooth & devices › Devices to remove it, then choose Add device. On macOS, open System Settings › Bluetooth, forget the controller, and pair it again.
5. Try a wired connection. If the controller supports USB, connect it with a data-capable cable. Try another USB port and avoid a hub for this check. If wired input works but Bluetooth does not, focus on the wireless connection or pairing.
6. Restart the computer. Do this after checking the simpler steps. A system restart can clear a connection that stayed stuck after the browser closed.
7. Check with another browser or device. If the controller works elsewhere but not in the original browser, update that browser and temporarily disable extensions that change page behavior. If the inputs fail in other places too, see how to test a controller after re-pairing Bluetooth.

When the controller may be faulty

Test the controller with a wired connection if possible, then try it on another computer or device that supports it. If it repeatedly disconnects or the same buttons fail in more than one place, the problem is less likely to be the browser restart. Check for a damaged cable, a loose USB connector, a depleted battery, or a pairing problem. If the controller is still under warranty, contact the seller or manufacturer before opening it. For an older or inexpensive controller, replacement may be more practical than repair.

Why restarting the browser can change detection

Closing a browser ends its current page session. It does not necessarily turn off the controller or remove its operating-system pairing, but the newly opened page has to detect the controller again. A controller that went to sleep during that time may need a button press or a fresh connection before the page receives input.

The Gamepad Test checks the input the browser can receive. It cannot repair Bluetooth pairing, diagnose a damaged controller circuit, or guarantee that a particular game will accept the controller. Use the operating system connection status and a second game or device to narrow down where the problem starts.