Controller works in browser but not in a game

Check controller detection separately from game input support and mapping so you can troubleshoot a working browser test without guessing.

By Hardware Detective editorial team · Last updated September 21, 2026 · How we test

A controller responding in Controller Tester has a working path to that browser. If a game ignores it then the next investigation is the game’s input path. Replacing the controller at this stage skips evidence you already have.

Record what the browser can see

Press a button while the test page is active and note the controller name shown. Move each stick and try the ordinary buttons. Write down whether the entire controller responds or only some controls.

The browser receives gamepad state through a browser interface rather than through the game’s own input code. MDN’s Gamepad API guide explains that separation. A browser test therefore doesn’t certify game compatibility or every device feature.

Check the game’s stated support

Look at the game’s controller settings and official help. Some titles require an input mode to be selected while others have limited controller support. Don’t assume that a menu responds to the same inputs as gameplay.

Start with an ordinary supported action such as confirming a menu choice. If the game responds there but not during play then inspect its control bindings. If it never responds then focus on detection before tuning sensitivity.

Keep the connection consistent

Use the same wired or wireless connection that passed the browser test. A controller connected over USB may appear differently from the same device connected wirelessly. Changing the connection is a useful experiment but it creates a new configuration that needs testing.

Disconnect other controllers temporarily if the game might be using a different device. Note which controller is assigned to the player where the game exposes that choice. Reconnect additional devices after the first one works.

Inspect remapping layers one at a time

A launcher or controller utility may translate input before it reaches the game. Check whether such a feature is enabled and whether the game expects it. Consult the game or launcher’s documentation for the specific combination instead of assuming translation should always be on or always be off.

Before changing anything note the original setting. Try one change and restart the affected application if its instructions require it. Stacking multiple remappers can make two apparent devices out of one physical controller and complicate diagnosis.

Separate mapping problems from axis problems

If buttons work but movement feels wrong then inspect bindings and deadzones. A stick that rests slightly away from the center is a different problem from a controller that the game never detects.

Use the stick-drift guide for interpreting resting movement. Don’t use a browser center reading alone to choose a universal setting for every game because each title may process the input differently.

Keep a useful troubleshooting record

Record the controller model and connection method along with the game and input settings used. Include which buttons worked in the browser and which actions failed in the game. That report gives support a reproducible configuration rather than a general statement that the controller is broken.