Steam Not Detecting Your Controller? Fixes for Windows, Mac and Linux

When Steam doesn't detect a controller, first work out whether the computer sees it at all. If the operating system doesn't, no Steam setting will help. If it does, the fix is almost always in Steam's Controller settings: the configuration support box for your type of pad is off, another remapper is holding the controller, the game wasn't started from Steam, or, on Linux, the udev rules that let Steam open the device are missing.

Start by checking what your computer reports, before Steam is involved:

If our tester shows the buttons and sticks moving, your system is fine and the rest of this page applies. If it shows nothing after you've pressed a button, fix the connection first; the controller not detected guide covers Windows Bluetooth, cables and drivers. Browsers only list a gamepad after a button press, so press one before you decide it's missing.

Where Steam lists the controllers it can see

In the desktop client, open Steam › Settings › Controller. Valve's guide for players says every connected controller that the configurator recognises shows up on this screen. That makes it the quickest test in this whole article: if your pad is listed there, Steam has found it and the trouble is further along, in a game. If it isn't, Steam can't open the device, and the sections below explain why.

Plug the controller in, or make sure it's paired and awake, before you open that screen. A controller that's asleep, or a Bluetooth pad that has dropped its connection, simply isn't there to list.

Turn on support for your type of controller

The same screen has a set of configuration support boxes, one per controller family. Valve's player guide says to tick the box that matches your controller if you use a PlayStation 4, Xbox One, Xbox 360 or generic pad. With a box off, Steam may show the device and still leave it alone in games.

Controller	Box to tick in Steam	What else to know
Xbox One, Series X or S, Xbox 360	Xbox configuration support	Games already understand Xbox pads; Steam's layer is optional
PlayStation 4, DualSense, DualSense Edge	PlayStation configuration support	Without it, games that only read Xbox input won't see the pad
Switch Pro, Joy-Con	Switch Pro configuration support	Steam added the Switch Pro in 2018
Switch 2 Pro Controller	Same, on a recent client	Wired support on Windows arrived in a Steam beta in November 2025
8BitDo, PowerA, HORI and similar	Xbox or generic box, depending on the mode the pad is in	Many have a switch for X-input or D-input; pick X-input for the simplest result
Unknown or older pads	Generic gamepad configuration support	Steam may ask you to map the buttons once

If a controller is brand new, it may simply be newer than your Steam client. Support for new pads arrives in client updates, and a beta client sometimes gets it months earlier. A pad Steam doesn't know at all can still work as a generic gamepad once that box is on.

Steam sees it, but the game doesn't

On Windows, Steam Input works from inside the game rather than from the device. Valve's developer notes describe the Steam overlay hooking the usual controller interfaces a game uses, XInput, DirectInput, RawInput and Windows.Gaming.Input, and handing the game an emulated Xbox controller in their place. The game sees an Xbox pad no matter what you're actually holding.

That explains three common failures:

• The game was started outside Steam. A game launched from its own shortcut or another launcher doesn't get the overlay, so it never receives the emulated pad. Use Add a Game in your Steam library to list it there, then always launch it from the library.
• The overlay is off for that game. Same result: no overlay, no Steam Input. Turn the in-game overlay back on in Steam's settings or the game's properties.
• Inputs arrive twice, or the wrong button fires. The game is reading the real controller and Steam's emulated one at the same time. Valve's own example: under emulation a PlayStation touchpad click and the Options button can both turn into Start, because an Xbox pad has fewer buttons to map them to. Turn off the game's own PlayStation support, or turn off Steam Input for that title, so only one path remains.

On macOS and Linux there's no overlay hook; Valve says the emulated controller comes from a driver instead. The advice about launching from Steam still applies, because Steam only switches its layer on for games it starts.

Another program grabbed the controller first

Steam has to be the first thing reading a controller to translate it. If DS4Windows, DSX, a vendor app or an old driver is already turning your pad into a virtual Xbox controller, Steam sees that virtual pad, not your real one, and its PlayStation or Switch options have nothing to act on. Valve's player guide warns about exactly this with remappers.

Pick one tool. If you use Steam for everything, quit the others and make sure they don't start with Windows. If you need DS4Windows for games outside Steam, untick the matching configuration support box in Steam so the two don't fight over the same device.

Linux: missing udev rules

On Linux, a program can only open a controller if the system gives it access to the device node, and that's the job of udev rules. Valve keeps the rules in a public repository called steam-devices, described as the list of devices Steam and SteamVR need read and write access to, so that distributions can build their own rules from it.

Reading the rules file shows how wide that list is. It grants user access to Valve's own hardware, Sony's DualShock 3, DualShock 4, DualSense and DualSense Edge, Nintendo's Switch Pro, Joy-Con and Switch 2 controllers, and pads from 8BitDo, PowerA, Razer, HORI, Flydigi, Thrustmaster, Mad Catz and others, along with the virtual input device Steam uses to create its emulated controller. If those rules aren't installed, Steam can run perfectly and still find no controllers, or find one over USB but not over Bluetooth.

Most distributions ship them in a package named something like steam-devices, and a Steam installed from the distribution's own repository usually pulls it in. A Steam installed as a Flatpak or Snap runs in a sandbox and can't add rules to the host system, so the rules have to be installed on the host separately. After installing them, unplug and replug the controller, or log out and back in, so the new permissions apply.

Bluetooth controllers that keep disappearing

A controller that shows up in Steam and then vanishes mid-game is usually a connection problem rather than a Steam one. Check the battery, move closer, and reduce the number of other Bluetooth devices on the same adapter. If it only happens in Steam, look for a second program that wakes up and grabs the pad, such as a vendor app checking for firmware updates.

A short checklist

1. Our tester sees the controller after a button press.
2. It's listed under Steam › Settings › Controller.
3. The configuration support box for its type is on.
4. No other remapper is running, or Steam's box for that type is off.
5. The game is started from your Steam library with the overlay on.
6. On Linux, the steam-devices udev rules are installed on the host.

If every step checks out and the stick still wanders on its own, the controller is detected fine and the problem is stick drift, which Steam's deadzone settings can hide but not cure.