Controller Not Connecting to Steam
A controller Windows recognizes but Steam ignores almost always means Steam Input — Steam's built-in controller layer — is disabled, misconfigured, or fighting a game's own controller support. The button test confirms Windows sees the controller; if it does, the fix is in Steam's controller settings, not the driver or the pairing.
Diagnose before you fix
Confirm the symptom and measure its severity first. The test result tells you whether to clean, recalibrate, or replace — different severities call for different fixes.
Button Test
Before touching Steam, prove Windows itself sees the controller. The button test reads directly from the browser's controller interface — the same layer Steam sits on top of. If buttons register here, the controller is paired and working at the OS level, and any Steam-specific failure is Steam's configuration, not the connection. If nothing registers, treat it as a generic pairing problem first.
Run the button test- Steam client (latest version)
- A USB data cable (to rule out Bluetooth as a factor)
Step by step
Work through these in order. After the last step, run the diagnostic again to confirm the fix held.
- 01
Confirm Windows sees the controller first
Run the button test. If buttons light up as you press them, Windows and the browser are receiving inputs correctly, and the failure is inside Steam — skip to the Steam Input steps. If the button test shows nothing, Steam isn't the problem and you have a generic pairing issue: pair the controller to Windows first before troubleshooting Steam at all.
- 02
Enable Steam Input for your controller type
Open Steam → Settings → Controller. Steam ships with per-brand toggles: PlayStation Support, Xbox Support, Switch Pro Support, and Generic. If your controller's brand isn't enabled here, Steam will ignore it even if Windows sees it. Turn on the toggle for your controller. Some brands (particularly DualSense on PC) also need 'Enable Steam Input' set to on rather than the default 'auto' for consistent behavior in every game.
- 03
Check the per-game controller profile
Steam Input works globally AND per-game — a working global config can be overridden by a per-game profile that disables the controller or maps it strangely. In your Library, right-click the game → Properties → Controller. Set 'Override for [game]' to 'Enable Steam Input' if the game's controller support is flaky, or 'Disable Steam Input' if the game has native support and Steam is fighting it. Wrong choice here is the single most common cause of 'my controller works in one game but not another.'
- 04
Restart Steam after every controller change
Steam's controller detection runs at startup — plug and unplug events during a session don't always re-scan the pipeline properly. After changing any controller setting, or after re-pairing the controller, fully quit Steam (right-click tray icon → Exit, not just close the window) and reopen it. Many 'still not working' cases resolve here without any deeper fix.
- 05
Retest wired if Bluetooth is unstable
Bluetooth adds a layer where Steam and Windows can disagree about controller state — one sees it, the other doesn't. Connect a USB data cable and restart Steam. If wired works and Bluetooth doesn't, the fix is either Steam's Bluetooth support for that controller or Windows Bluetooth pairing — but at least you've localized the fault to the wireless path rather than Steam or the controller.
- 06
Reset Steam Input configuration if all else fails
Corrupted per-game profiles can persist across reinstalls. In Steam → Settings → Controller, choose 'Reset Configuration' for the affected controller — this wipes custom mappings back to defaults. Also try Big Picture Mode's controller test (Settings → Controller → Test Device Inputs), which shows what Steam is actually receiving. If Big Picture sees the controller correctly but games don't, the per-game profile is the culprit.
Where to go next
Persistent symptoms usually mean hardware wear that cleaning and recalibration can't reach. These resources cover repair, replacement, and warranty paths.
Other tests for the same controller
A symptom rarely arrives alone. Worn sticks often coincide with deadzone creep and reduced circularity — run the related diagnostics while the controller is already in your hands.
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
Because Steam has its own controller layer, Steam Input, that sits on top of Windows and can be independently disabled. If Steam Input isn't enabled for your controller's brand (PlayStation, Xbox, Switch Pro), Steam will ignore a controller Windows can see perfectly. The button test confirms Windows sees the controller; if it does, the fix is in Steam's controller settings.
Per-game controller profiles. Steam Input can be globally enabled but disabled for a specific game — or vice versa. Right-click the game in your Library → Properties → Controller and check the Steam Input override setting for that title. Wrong override choice here is the most common reason a controller behaves differently across games.
Depends on the game. For games with strong native controller support (most AAA titles), disable Steam Input — it can interfere. For games with weak or broken controller support (indie titles, keyboard-only games), enable Steam Input to have Steam translate your controller inputs into keystrokes or a mapped profile. The per-game override lets you pick per title.
Mostly yes on wired, more limited on Bluetooth. Steam Input has native DualSense support with rumble and touchpad; adaptive triggers and haptics work in select games (God of War, Metro Exodus). Some players still prefer DS4Windows to have the DualSense present as an Xbox pad universally — pick whichever gives you more consistent results in the games you play.
Xbox controllers should Just Work in Steam via XInput, so if Steam isn't seeing yours, the usual causes are: Xbox Support toggle disabled in Steam's controller settings, a Windows driver issue preventing XInput enumeration, or Steam Input's 'auto' mode misidentifying the controller. Verify with the button test first — if the button test doesn't see the controller either, treat it as a generic Windows pairing problem.
Not usually, but Big Picture's controller settings are more comprehensive than the standard desktop client's, and its 'Test Device Inputs' screen is the fastest way to see exactly what Steam is receiving from your controller. If desktop Steam is behaving oddly with a controller, launching Big Picture briefly to configure and test can resolve issues that don't surface in the smaller desktop UI.
Yes, absolutely. Both intercept controller input and try to translate it, so running both against the same DualSense produces double inputs, phantom presses, or complete non-detection. Pick one: use Steam Input alone (simpler for Steam games), or use DS4Windows alone with Steam Input disabled for the DualSense (better for non-Steam launchers). Running both is guaranteed conflict.
Still seeing the issue?
Re-run the diagnostic to confirm whether the fix held or whether escalation is needed.
Run the test again