Controller Works in Steam but Not in Game?

This one has a very specific and maddening shape. Your controller navigates the Steam library perfectly. Big Picture responds to every input. Steam's own settings screens show it connected and working. Then you launch a game and it does absolutely nothing.

The good news is that this narrow symptom rules a lot out. If the controller drives Steam's interface, your hardware, drivers, cable, and connection are all fine. The problem sits entirely in the handoff between Steam and the game, and that's a configuration issue with a manageable list of causes.

Here are the eight fixes, in the order most likely to work.

Why this happens at all

Steam has its own input layer, Steam Input, which sits between your controller and games. When it's active, Steam intercepts your physical controller and presents the game with a virtual controller instead, translating inputs according to a layout.

Steam's own interface doesn't depend on that translation; it reads controllers directly. So a controller can drive Steam flawlessly while the translation into the game fails, is disabled, or produces something the game doesn't recognise. That gap is exactly where this problem lives.

Because Steam's interface working proves nothing about the game handoff, don't take it as evidence your setup is fine. It only proves the hardware is.

Fix 1: Toggle Steam Input for that specific game

Start here, because it resolves the majority of cases.

In your Steam library, right-click the game, choose Properties, then Controller. You'll see an override setting, usually defaulting to global behaviour. Change it explicitly: set it to "Enable Steam Input," relaunch the game, and test. If that doesn't work, set it to "Disable Steam Input," relaunch, and test again.

Try both. Which one works depends on the game, and the logic runs like this. Games with their own native controller support often work best with Steam Input disabled, so they read the controller directly without a translation layer confusing matters. Games with no built-in controller support, or older titles, need Steam Input enabled so Steam can present something they understand.

Crucially, relaunch between changes. Many games only scan for controllers at startup, so changing the setting while the game is running does nothing and makes it look like the fix failed.

Fix 2: Check the game's controller layout

Steam Input works from a layout, and if that layout is wrong or empty, the game receives nothing useful even though everything appears connected.

From the game's library page, open the controller settings and inspect the current layout. If it's set to something inappropriate, a keyboard-and-mouse layout, a template for a different genre, or a partially edited custom layout, inputs may go nowhere.

The reliable fix is to reset to a recommended layout. Steam offers official and community layouts for many games, and switching to the official or most popular community configuration usually restores normal behaviour immediately. If you've previously experimented with custom bindings, this is very often the culprit.

Fix 3: Confirm the Steam overlay is enabled

An underappreciated dependency. Steam Input relies on the Steam overlay being able to hook into the game, and if the overlay is disabled, either globally or for that specific title, Steam Input can lose its ability to inject input.

Check Steam's global setting under Settings > In Game, and check the per-game setting under the game's Properties. If the overlay is off, enable it and relaunch.

This is a common cause when someone disabled the overlay months ago for performance reasons and forgot, then later wondered why controllers stopped working in games while continuing to work in Steam itself.

Fix 4: Make sure you're launching through Steam

Steam Input only applies to games launched via Steam. If you're starting the game from a desktop shortcut that points directly at the executable, or through another launcher, Steam never gets involved and Steam Input isn't in the picture at all.

The symptom fits exactly: the controller works in Steam because Steam is running, but the game receives nothing because it was never launched under Steam's supervision.

Launch from your Steam library instead. For non-Steam games, add them as a non-Steam shortcut and launch them that way, though results vary by title.

There's a related wrinkle with games that use their own secondary launcher. Some titles launch a publisher's launcher first, which then starts the game as a separate process, and Steam can lose track of it. If your game does that, Steam Input may not follow it through.

Fix 5: Kill conflicting input software

If you're running DS4Windows, a vendor configuration app, or another remapping tool alongside Steam Input, they can interfere with each other.

Steam deliberately ignores PlayStation controllers when it detects DS4Windows running, on the assumption that you're emulating an Xbox pad. That behaviour is usually helpful, but combined with certain settings it can leave a game receiving nothing.

Pick a single input path and stick to it. Either run Steam Input with the other tool closed, or run the other tool with Steam Input disabled for that game. Running both untuned is also what produces the classic double-input bug where every press registers twice. Our guide on remapping controller buttons on PC covers choosing the right tool and avoiding conflicts.

Fix 6: Check controller support type in Steam settings

Steam has per-controller-type support toggles under Settings > Controller, covering PlayStation, Xbox, Switch, and generic controllers.

If support for your controller's type is switched off, Steam won't apply Steam Input to it in games, even though the controller still navigates Steam's interface. Turn on the setting matching your controller and relaunch.

This is worth checking specifically if you recently changed controller brands, since a setup that worked with your old pad may not cover your new one.

Fix 7: Check the game's own controller settings

Not everything is Steam's fault. Plenty of games have their own controller toggle or input-mode selector buried in their options.

Look under Options, Controls, or Input for a master "enable controller" or "gamepad" switch that may be off, an input device selector where you have to explicitly choose controller over keyboard, or a controller-type setting. Some games also only switch input mode when they detect a controller press on a particular screen.

Restart the game after changing any of these, since several apply only on a fresh launch.

Fix 8: Rule out anti-cheat interference

Some anti-cheat systems are wary of virtual input devices, which is exactly what Steam Input creates. In a small number of competitive titles, that can result in controller input being blocked or ignored inside the game while everything else works normally.

If the game in question uses strict anti-cheat and the other fixes haven't helped, try disabling Steam Input for that title specifically and using the controller natively. Xbox controllers have an advantage here, since they present as standard XInput devices and need no translation.

Confirm the controller itself is fine

Worth a sanity check, particularly if you've been changing settings for a while and want to rule the hardware back out. Connect the controller and run a quick check on the joystick calibration page, confirming both sticks move through their range and rest cleanly at centre.

If the browser reads the controller correctly, the hardware and connection are definitively fine and you're chasing a software configuration problem, which keeps you focused on the right layer. If it doesn't, the problem is further upstream than Steam, and our guide on a controller connected but not working in game covers the broader detection issues.

The short version

The controller driving Steam but not games proves your hardware is fine and the problem is in the Steam-to-game handoff. Toggle Steam Input for that specific game and relaunch between changes, since which setting works depends on whether the game has native controller support. Reset the game's controller layout to an official or popular community one if you've customised it. Check the Steam overlay is enabled, since Steam Input depends on it. Make sure you're launching through Steam rather than a desktop shortcut or separate launcher. Close conflicting remapping software, verify your controller type is enabled in Steam's controller settings, and check the game's own controller toggle.