Controller Works in the Tester but Not in a Game
If your controller responds in a browser tester but not in a game, start with that game's input settings. The tester confirms that input reaches the browser, not that every game supports the same device. Check gamepad support, the active controller, and any remapping software before changing drivers or buying replacement parts.
Diagnose before you fix
First check which inputs reach the browser. Use the result to choose a software or connection check; it does not prove which part needs repair.
Button Test
Press a face button, a bumper, and both sticks. If the browser shows each input, continue below. If it sees no input, use the gamepad-not-detected guide instead. A working test does not rule out faults in untested buttons or wireless dropouts.
Run the button test- The affected game and its controller settings
- One connected controller
- A note of your current mappings
Step by step
Work through these in order. After the last step, run the diagnostic again to confirm the fix held.
- 01
Only one game fails? Check that title first
Open the game's help page or settings and confirm it supports your controller or a compatible input mode. Select gamepad input if the game offers that choice. Close the game, connect the controller, then launch it again. Try actual gameplay as well as menus: some titles use different controls in each.
- 02
The wrong pad responds? Isolate the active device
Disconnect spare gamepads, wheels, and adapters for this test. Close virtual-controller apps you are not using. Restart the game with just the intended controller connected. If it now works, reconnect the other devices one at a time and check the game's player or controller assignment.
- 03
Steam sees it but the game does not? Compare one input path
In the game's Steam properties, find Controller and note the current Steam Input setting. Test the game's native support first if its help page recommends it. Then compare with Steam Input enabled if translation is needed. Relaunch the game after each change. Keep the setting that works for this title; it need not suit every game.
- 04
Two actions happen per press? Check for duplicate mappings
One physical controller can produce both native and translated input. Pause extra remapping software and test again. If you need that software for accessibility or a custom layout, keep it and check its instructions for avoiding duplicate input instead. Save your current profile before changing it.
- 05
No supported input mode? Choose a supported route
Some controllers offer separate PC and console modes. Use the mode named in the manufacturer's PC guide, then reconnect and retest. A keyboard-only game may need a keyboard mapping profile; a browser detecting the pad cannot add native controller support. For non-Steam games, use the publisher's supported setup rather than assuming Steam settings apply.
- 06
Verify the fix with the same short sequence
Repeat the button, stick, and trigger checks in the affected game. Test a second controller-enabled game if the first still fails. If only one title fails, send its support team the game version, controller model, connection type, and settings tried. If several games fail, investigate the shared input mode or remapping setup.
Where to go next
Choose the next resource based on where input stops. A persistent game-specific problem does not by itself establish a hardware fault.
Other tests for the same controller
Compare button actions and mappings before and after changing a profile. Keep the controller and connection the same.
Variants of this symptom
The same underlying issue presents differently across controllers. These device-specific guides cover the variations.
Key definitions
Plain-language definitions for the terms used on this page. Each links to the full glossary entry with thresholds, mechanism, and FAQs.
connection questions
It means the tested inputs reached that browser in that session. It does not verify every game, every connection mode, battery life, or features such as adaptive triggers. Use the specific symptom to choose your next check.
Follow the game's advice, then compare one setting at a time. Translation can help when a game does not support the pad directly. Native support can be useful when the game offers device-specific features. There is no single setting that fits every game.
The game may use Xbox-style prompts for a translated controller or for all gamepads. Test the actions before treating the icons as a connection fault. Look for a prompt-style option in the game if the labels bother you.
Calibration addresses position or range problems. It is unlikely to solve a game that ignores every button while the browser reads them. Check game support and the active input path first.
The game may receive duplicate input, or a button may repeat unexpectedly. Close an extra remapper and compare. If the button also repeats in the browser with that software closed, follow the double-input guide.
Start with the game and input settings when browser input works. Broad driver changes can disturb a working setup and make the cause harder to find. Use manufacturer or operating-system guidance if later checks point to a driver problem.
Still seeing the issue?
Re-run the diagnostic to confirm whether the fix held or whether escalation is needed.
Run the test again