Steam Input vs Native Controller Support: When to Use Which

You plug a DualSense into your PC, launch a Steam game, and it just works — buttons show PlayStation icons, the touchpad opens the menu, the haptics fire. Magic. Then you launch a non-Steam game and the same controller is invisible. Welcome to the world of Steam Input.

What Steam Input Actually Does

Windows has two main controller standards: Xinput (Xbox-style, universally supported) and DirectInput (older, generic, supports more buttons but less standardised). Most modern games speak Xinput; PlayStation and Switch controllers don't natively output it.

Steam Input solves this by sitting between your controller and the game. It reads the raw HID data, then exposes a virtual Xbox controller to the game. The game thinks an Xbox 360 pad is plugged in. You're really using a DualSense, Switch Pro, or whatever.

When to Enable Steam Input

• PlayStation controllers (DualSense, DualShock 4): Yes, always.
• Switch Pro Controller: Yes — it's the only way to get full button mapping in most PC games.
• Generic / off-brand pads: Yes — covers compatibility gaps.
• Steam Controller: Yes (it was designed for it).
• Xbox 360 / Xbox One / Series controllers: Optional. Native Xinput already works perfectly; only enable for advanced features like custom button mapping or gyro on a Series controller.

How to Configure It (Once)

In Steam: Steam → Settings → Controller. Enable the boxes for your controller types: PlayStation, Xbox Extended, Nintendo, Generic. Restart Steam.

For per-game tweaks, in Big Picture mode: hover the game, click the gear, click Controller Options. You can swap input style, remap any button, set up gyro aiming, and enable rumble emulation.

The "Doubled Inputs" Trap

The most common Steam Input bug: every button press registers twice. Example: pressing A makes your character jump twice, or selects then de-selects a menu item.

Cause: the game reads the controller natively and sees the Steam Input virtual Xbox controller. Two controllers, one set of fingers.

Fix: right-click the game in your Library → Properties → Controller → set to "Disable Steam Input". The game will read the native pad only. (For PlayStation pads in older games that lack native PS support, instead disable native PS support in Steam settings and rely solely on Steam Input.)

Wrong Button Glyphs

The game shows Xbox glyphs even though you're holding a DualSense — or vice versa. This is just a glyph preference and rarely a real bug. In Steam: Settings → Controller → set "Force show glyphs for" to your preferred style. Some modern games (e.g. Helldivers 2, Cyberpunk 2077) read DualSense glyphs natively when Steam Input is disabled.

Using Non-Steam Games with Steam Input

This is the killer feature most people don't know about. In Steam, click Add a Game → Add a Non-Steam Game. Pick the .exe of any game (Game Pass, Epic, GOG, emulators). Launch it from Steam. Steam Input now works in that game just as if it were a Steam title.

This is how you get DualSense haptics in Forza Horizon (Game Pass), or full controller support in older PC ports that ignore your pad.

For Non-Steam Workflows: DS4Windows

If you don't want to route everything through Steam, install DS4Windows (free, open source). It runs in the background and turns any PlayStation controller into a virtual Xbox controller, system-wide. The same idea as Steam Input but always-on, even outside Steam. There's also BetterJoy for Switch controllers.

Verifying What the Game Sees

Plug in your controller and open the KeyTest controller tester. The controller ID line tells you exactly what the browser (and by extension, games) sees. If it says "Xbox 360 Controller" while you're holding a DualSense, Steam Input is doing its job.

Frequently Asked Questions