Steam Input Setup: 13 Steps, 40 Min [2026]

Steam Input is the layer inside the Steam client that decides what your controller actually sends to a game. It remaps buttons, runs gyro, translates a PlayStation pad into an Xbox one and stores a separate layout for every title in your library. It ships with Steam, so it carries no separate price or subscription. This Steam Input setup guide walks through 13 steps and takes roughly 40 minutes if you test as you go.

The feature is still moving. Valve’s October 9 Steam Client Beta note changed how Steam Frame controllers behave in VR games that lack native VR input, and the stable client update on October 13, 2026 added a redesigned configurator view for Steam Input API games, a multi-binding editor, compatibility labels on layouts, inverted button chords and a controller-reordering dialog. If you last touched your layouts a year ago, several screens look different now. Hardware moved too, since Valve released a new Steam Controller in 2026. Our look at how the Steam Controller stacks up against Xbox and DualSense pads covers the hardware side, so this guide stays on software.

By the end you will have Steam Input switched on for the right controller types, a personal layout for one game, a chord that opens a second set of bindings, gyro tuned to your taste, a Community Layout applied and tweaked, a non-Steam game wired in, and a scripted backup of every layout you own. The final project bundles three layouts into a household-ready setup. Every UI path below comes from the Steam client as documented in October 2026, and where a detail rests on a single report, the text says so.

·

Google · Preferred Sources

Don't miss new tech stories on Google

Add Tech Insider once in the Google app and our stories appear in your news suggestions.

Add Now

What Steam Input Is and What Changed in October 2026

Steam Input sits between your physical controller and the game. Instead of the game reading raw hardware, Steam reads the pad first, applies your layout, then hands the game a virtual device that looks like a standard Xbox controller (or a keyboard and mouse, or whatever the layout asks for). That one design choice explains most of what people see: Xbox button prompts on a PlayStation pad, remaps that work in games with no remap menu, and gyro in titles that never heard of motion controls.

Steam Input is not a separately versioned product. It lives in the Steam client, so your version is your Steam client build. The stable build you want is the October 13, 2026 update or newer. According to the Steam client notes, that update brought a configurator view that shows actions and bindings directly for games using the Steam Input API, plus compatibility info on layouts and a dialog for reordering controllers. A beta build dated October 26 reportedly added GameInput v4 support, which matters mostly to developers and to anyone chasing a niche detection bug.

Two things did not change. Per-game layouts, button remapping and Community Layouts all still work, and the Community Layouts path stayed the same in guides updated as recently as October 27. Also, the original pad is not abandoned. Valve’s October 13 notes still carry a pairing fix for the 2015 Steam Controller, which Steam now labels Steam Controller (2015) on its store page, while the newer hardware is simply called Steam Controller in official notes. Community posts sometimes say Steam Controller 2, but that is community wording rather than a Valve product name.

Why bother when other tools exist? Tools like DS4Windows or reWASD do overlapping work, but they run as separate programs, cost money in some cases and fight with Steam when both are active. Steam Input costs nothing, follows your account through cloud sync, and also runs on Linux and handheld hardware where those Windows tools do not. For a household that mixes Xbox, PlayStation and Switch pads, it is the one place to manage everything.

One caution before you start. A single user reported that the October 13 update replaced custom layouts, desktop layouts and guide-button chord layouts with game defaults. That is one report, not a confirmed Valve-wide bug. Still, it is the reason Step 13 of this guide is a backup, and the reason I suggest you read it before you spend an hour crafting bindings.

Prerequisites and Versions

You need very little. No extra downloads, no accounts beyond Steam, no admin rights for the core steps. The table below lists what to have ready and what to check, using the state of things on October 28, 2026.

Requirement	What to have	How to check
Steam client	Stable build from the October 13, 2026 update or newer	Steam menu, then Check for Steam Client Updates
Operating system	Windows 10 or 11, a current desktop Linux, Bazzite 44 or SteamOS	Windows: Win+R, then winver. Linux: cat /etc/os-release
Controller	Any Xbox, PlayStation, Switch Pro or generic pad, or a Steam Controller	Connect it before opening Steam settings
Connection	USB cable for the first test, Bluetooth or dongle afterwards	Pair in the OS first, then confirm Steam sees it
Steam account	Logged in with cloud sync on, so layouts follow you	Settings, then Cloud, then Enable Steam Cloud
Test game	One game you already own and know well	Pick something with a keyboard-only menu to expose edge cases
Optional tools	PowerShell 5.1 or newer on Windows, Bash on Linux, for the backup scripts	PowerShell: $PSVersionTable.PSVersion

On handhelds the picture shifts a little. Steam Deck OLED is the current model on Valve’s own Steam Deck page, and SteamOS on stable still ships the Steam client that holds Steam Input, so nothing extra installs there either. On a Linux desktop using Flatpak Steam or a distro package, input permissions matter and get their own section later. Set aside a USB cable even if you plan to play wirelessly. Wired is the fastest way to rule out pairing problems when something misbehaves.

How Steam Input Layers Work Before You Touch a Setting

Most frustration with Steam Input comes from not knowing which switch wins. There are several places a controller can be configured, and they stack in a fixed order. The global per-controller-type toggles say whether Steam handles that kind of pad at all. A per-game override can force Steam Input on or off for one title. The layout holds the actual bindings. Finally, the desktop layout and guide-button chords control the pad when no game is running.

Layer	Where you find it	What it controls	Change it when
Global toggle per controller type	Steam, Settings, Controller, then Enable Steam Input for Xbox, PlayStation, Switch or Generic	Whether Steam grabs that pad at all	You want gyro on a DualSense or remapping on an Xbox pad
Per-game override	Library, right-click game, Properties, Controller	Forces Steam Input on or off for one game	A game has native support and double-reads the pad
Game layout	Library, controller icon, Edit Layout	Button, stick, trigger and gyro bindings	You want a custom scheme
Action sets and layers	Inside the layout editor	Alternate binding groups on demand	Menus and gameplay need different behavior
Desktop layout	Settings, Controller, Desktop Layout	Mouse and keyboard behavior outside games	You navigate Windows with a pad
Guide button chords	Settings, Controller, Guide Button Chords	Shortcuts that work everywhere	You want screenshot or keyboard shortcuts

The global toggle comes first because everything else depends on it. If Steam Input is off for PlayStation pads, no layout edit changes anything for a DualSense, and Steam shows the editor anyway, which fools people. The second thing to know is that games using the Steam Input API behave differently. Those titles ship their own action definitions, so Steam can show actions such as Jump or Reload instead of raw buttons. Valve documents this in its Steamworks notes on Steam Input gamepad emulation best practices, and it explains why some games offer a friendly action list while others give you a plain button grid.

If you live in the Xbox ecosystem and wonder whether Microsoft’s own tool is enough, the Xbox Accessories app remaps Xbox hardware at the device level, which follows the pad onto consoles and into games without Steam. The trade-off is scope. It only touches Xbox controllers, has no gyro and offers no per-game layouts. Steam Input is the better pick when your library lives in Steam, and the two can coexist if you keep the hardware-level remap simple.

Controller hardware also sets the ceiling for what a layout can do. The next table summarizes what each family brings to the party. Treat it as a planning aid, since individual models differ and firmware can add or remove features.

Controller family	Steam Input toggle	Gyro	Extra inputs worth mapping
Xbox pads	Xbox	No	Share button on newer models, paddles on Elite-class pads
DualShock 4 and DualSense	PlayStation	Yes	Touchpad as pointer, lightbar color
Switch Pro Controller	Switch	Yes	Capture button
Generic and third-party pads	Generic	Varies by model	Depends on the vendor’s mode switch
Steam Deck	Built in	Yes	Trackpads, back grips, touchscreen
Steam Controller (2026)	Built in	Yes	Trackpads and grip buttons

Steps 1 to 3: Update Steam, Enable Steam Input and Test the Controller

Step 1. Update the Steam client. Open Steam, click the Steam menu in the top left and choose Check for Steam Client Updates. If Steam restarts, let it. Then open Settings, Interface and look at the Client Beta Participation setting. For a stable setup, leave it on No beta chosen. Beta builds get Steam Input changes first, which is great for testing and bad for a layout you rely on tonight.

Step 2. Enable Steam Input for your controller type. Go to Settings, then Controller, then General Controller Settings. You will see switches labeled for Xbox, PlayStation, Switch and Generic controllers. Turn on the one that matches your pad. Switch on the PlayStation one if you own a DualShock 4 or DualSense and want gyro, the touchpad as a pointer or the lightbar settings. Leave the others off if you never use them, because fewer active translations means fewer surprises.

Step 3. Test raw input before changing anything. With the controller connected over USB, stay in the Controller settings and open the device test screen, which Steam lists next to your detected controller. Press every button, push both sticks to the edge, squeeze both triggers. You are looking for a baseline: does each input register, does a stick rest at center, does a trigger reach full travel? If a stick shows drift here, no layout will fix the hardware. Our guide to stick drift fixes for PS5, Xbox, Switch and Steam Deck covers calibration and deadzone tricks, and you should run those before you build bindings on top of a bad axis.

On Windows, a second sanity check takes ten seconds. Press Win+R, type joy.cpl and press Enter. With Steam running and Steam Input active, you should see a virtual gamepad listed, usually named like a generic Xbox controller. Select it and click Properties to watch the same inputs. If this virtual device appears, Steam is translating your pad correctly, and any problem later is a layout problem rather than a connection problem.

Expected result for the whole block: Steam updated, one controller type enabled, every input confirmed in the test screen. Pitfall alert for beginners: enabling every controller type at once. It feels thorough, but it can double-handle a pad that a game already supports natively. Start narrow, widen only when a game demands it.

Steps 4 to 6: Per-Game Override and Your First Remap

Step 4. Set the per-game override. Right-click your test game in the Library and choose Properties, then Controller. The Override setting offers three choices: Use default settings, Enable Steam Input, or Disable Steam Input. For a first remap, pick Enable Steam Input. Steam may also ask you to enable it when you click the controller icon on the game page. Accepting once is enough. Remember the flip side, because Disable Steam Input is the cleanest cure when a game with good native controller support behaves oddly.

Step 5. Open the layout editor. Back on the game’s Library page, click the small controller icon beside the play time, then choose Edit Layout. In Big Picture or on a Steam Deck, the same entry sits in the game’s controller settings. You will see a picture of the controller with every input listed in groups: bumpers, triggers, face buttons, D-pad, sticks and so on. Games that use the Steam Input API may open the newer action-and-binding view from the recent stable client update, which lists in-game actions rather than hardware buttons.

Step 6. Swap one button and check it. Pick a button you rarely need, say the right bumper, click it under the Bumpers group and choose a new output from the list. Assign it to the face button you press most. Thumbs tire quickly on A or Cross, and a trigger finger can take over that job. To disable a button entirely, click the gear icon beside it and remove the command. Return to the main screen and click View Layout to see the controller with every binding labeled. Steam saves changes automatically, so there is no Apply button.

Launch the game and check the remap on a menu and in play. Here is the edge case that catches almost everyone: the new binding works everywhere, including menus. Turn the right bumper into A and you will also select menu items with the bumper, which feels wrong in games where bumpers switch tabs. Steps 7 and 8 fix that. For now, confirm the swap works and note whether the game shows Xbox prompts. On a PlayStation pad with Steam Input on, many games show Xbox glyphs because they see the virtual Xbox device. That is expected, not a bug.

If the game refuses to open after you flip the override, the cause is rarely the controller. Launch problems usually come from Proton versions, overlay conflicts or missing runtimes, and our walkthrough for Steam games that refuse to start goes through them in order. Reset the override to Use default settings first so you isolate the variable.

Steps 7 to 9: Activators, Action Layers and Gyro

Step 7. Add an activator. A binding does not have to fire on a plain press. Click any button in the editor, then the gear icon, then Add Activator. Each activator type changes when the output fires. Since the October 13 client, Valve also ships a dedicated multi-binding editor for authoring button combinations, so a single physical input can trigger several outputs without hand-stacking commands.

Activator	Fires when	Good for
Regular Press	The button goes down and releases	Everyday bindings
Double Press	You tap twice quickly	Sprint toggles, map shortcuts
Long Press	You hold past a set time	Reload on tap, drop weapon on hold
Start Press	The instant the button goes down	Fast reactions, macros
Release Press	The button comes back up	Charge-and-release attacks
Chord	Another button is held at the same time	Second function on the same key

Build one useful example. Put the screenshot key on a Long Press of the Select or View button, so a tap still opens the map and a hold captures the screen. Test it twice. Timing defaults feel right to most people, but a long-press threshold that is too short triggers accidentally during intense play, so lengthen it if you see stray screenshots.

Step 8. Build an action layer for menus. This is the fix for the problem from Step 6. In the layout editor, look for the action set and layer controls near the top of the screen. Add a new layer, name it something like Quick Swap, and put your unusual bindings there rather than on the base layout. Then assign a button to turn that layer on, either while held or as a toggle. The base layout stays vanilla, so menus behave normally. The layer shifts your face buttons only when you ask. A held layer suits combat, a toggled layer suits long sessions where you want the new scheme to stay on.

Be honest about the limits. For games that do not use the Steam Input API, Steam cannot tell a menu from gameplay, so a layer is the closest you get. Games that do use the API often ship separate action sets for menus and gameplay already, and Steam switches between them without your help. That makes API games easier to customize but harder to override, since you work with their action names.

Step 9. Configure gyro and touch inputs. If your controller has motion sensors, such as a DualSense, a Switch Pro Controller, a Steam Deck or a Steam Controller, scroll the layout editor to the Gyro section. Choose how motion maps to output: as joystick camera for third-person games, as mouse for shooters, or as a stick replacement that only engages while you hold a button. Activation matters more than sensitivity. A common recipe turns gyro on only while a trigger is half pulled or while a trackpad or stick is touched, so the camera does not wander when you set the pad down. The Steam Controller line also supports grip-button activation for gyro, a feature that still appears in current Steam Input discussions.

Start with low sensitivity and raise it in small increments over several matches. Calibrate gyro while the controller lies flat and still, using the calibration option next to your detected controller in the Controller settings. For deep tuning, including flick stick and ratcheting, see our full gyro aiming walkthrough, which goes beyond the basics here. Trackpads work similarly on hardware that has them, and community layout authors began updating collections for the 2026 Steam Controller’s trackpads in August, according to a community layout guide.

Steps 10 and 11: Community Layouts, Templates and Saving Your Own

Step 10. Apply a Community Layout. You do not have to build every scheme from scratch. From the layout editor, or from the controller settings screen, click Current Button Layout and open the Community Layouts tab. Guides updated in late October describe the path as Library, controller icon, Edit Layout, Current Button Layout, Community Layouts. You will see layouts made by other players for this specific game, sorted by popularity, along with Templates, which are generic schemes that work across games. Templates such as gamepad with gyro, keyboard and mouse, or WASD-style layouts make a good starting point for titles that have no community upload yet.

Click a layout, read its description, then click Apply Layout. Test for five minutes before you decide. Read the description closely, because authors note which controller the layout targets. A layout built around the Steam Controller’s trackpads will not map cleanly onto an Xbox pad. Layouts also carry a compatibility indication in the newer client, which tells you whether your controller type matches. Treat that label as a hint rather than a guarantee.

Step 11. Save and export your own layout. After tuning, return to the layout screen and choose Export Layout, then Save a new personal binding. Give it a name that describes the use rather than the game, such as Gyro FPS or Couch Racing, so you can reuse it across titles. Personal bindings live in your account and sync through Steam Cloud. If you want to share, the same menu offers Export to Community, which publishes the layout so others can apply it. Keep a private copy anyway. Community uploads can be edited or removed by their authors, and a personal save does not vanish when someone updates theirs.

One more detail worth knowing: a September 1, 2026 client update reportedly added clearer labels for configurations shared across devices versus those unique to one device, along with an option to separate Steam Controller configurations from Steam Deck configurations. If you play the same game on a desktop and a handheld with different controllers, use that separation. A layout designed around trackpads would otherwise follow you to a pad that has none.

Step 12: Non-Steam Games, the Desktop Layout and Guide Chords

Steam Input only works while Steam runs, and it only attaches to games Steam knows about. For a game from another launcher, add it manually. In the Steam client, choose Games, then Add a Non-Steam Game to My Library, browse to the game’s executable and add it. Launch it from the Steam Library from now on. The shortcut gets its own controller configuration just like a purchased title, so everything from Steps 4 to 11 applies. If a launcher opens first and hides the real game, point the shortcut at the launcher and let the layout cover both, since Steam Input stays active for the whole session.

Next, look at the layouts that work outside games. In Settings, Controller you will find two entries that most people never open. The Desktop Layout controls how the pad behaves on your Windows or Linux desktop when no game runs, so you can scroll, click and type with a gamepad. Guide Button Chords define shortcuts that hold the Guide or Steam button plus another input. A useful chord set looks like this: Guide plus A for the on-screen keyboard, Guide plus B for Escape, Guide plus Y for a screenshot. The October 13 update added button-chord inversion to the binding tools, which helps if you prefer pressing the shortcut button first.

Windows adds one trap. Programs running as administrator, including UAC prompts, ignore input from a normal user process. According to Steam’s October 13 notes, a Lizard mode option now exists for the new Steam Controller when Steam Input is blocked by Windows security dialogs, which lets the pad fall back to basic keyboard and mouse behavior. For other controllers, the old rule holds. If a game runs elevated, run Steam elevated too, or lower the game’s privileges. The first option has security downsides, so avoid it unless you must.

Verify the desktop layout by closing every game, then moving the cursor with the right stick. If the pointer does not move, open Settings, Controller, Desktop Layout and look at whether the default template got replaced. A reported October 13 side effect on some accounts was layouts reverting to defaults, so this check doubles as a test for that issue.

Step 13: Back Up and Restore Your Layouts

Cloud sync saves layouts, but it syncs mistakes just as faithfully. One bad sync, one corrupted file or one client bug and your hours of tuning are gone on every device. A local backup costs nothing. Steam stores local controller configurations in folders inside your Steam installation, with subfolders per account and per game. Exact subfolder names can shift between client builds, so the scripts below copy the entire folder instead of guessing at paths. Valve added a recovery page in early October for local configuration files that fail to load, a sign the files do break now and then.

Here is a Windows backup script. Save it as backup-steam-input.ps1, close Steam, and run it from PowerShell.

$steam = (Get-ItemProperty "HKCU:\Software\Valve\Steam").SteamPath -replace '/', '\'
$src   = Join-Path $steam "steamapps\common\Steam Controller Configs"
$stamp = Get-Date -Format "yyyyMMdd-HHmm"
$dest  = Join-Path $env:USERPROFILE "Documents\SteamInputBackups\$stamp"

if (-not (Test-Path $src)) {
    Write-Error "No layout folder found at $src"
    exit 1
}

New-Item -ItemType Directory -Force -Path $dest | Out-Null
Copy-Item -Path "$src\*" -Destination $dest -Recurse -Force
$count = (Get-ChildItem $dest -Recurse -File).Count
Write-Output "Copied $count files to $dest"

Example output (your file count and path will differ):

Copied 14 files to C:\Users\you\Documents\SteamInputBackups\20261028-2005

On Linux, including Bazzite and SteamOS desktop mode, use a Bash version that checks the three usual Steam locations, including the Flatpak path.

#!/usr/bin/env bash
set -euo pipefail

CANDIDATES=(
  "$HOME/.local/share/Steam"
  "$HOME/.steam/steam"
  "$HOME/.var/app/com.valvesoftware.Steam/.local/share/Steam"
)

STEAM_DIR=""
for c in "${CANDIDATES[@]}"
do
  if [ -d "$c/steamapps/common/Steam Controller Configs" ]
  then
    STEAM_DIR="$c"
    break
  fi
done

[ -n "$STEAM_DIR" ] || { echo "No Steam Controller Configs folder found" 1>&2; exit 1; }

STAMP=$(date +%Y%m%d-%H%M)
DEST="$HOME/SteamInputBackups/$STAMP"
mkdir -p "$DEST"
cp -a "$STEAM_DIR/steamapps/common/Steam Controller Configs/." "$DEST/"
echo "Copied $(find "$DEST" -type f | wc -l) files to $DEST"

To restore, exit Steam completely, then copy the backup folder’s contents back over the live folder. On Linux that is a one-liner with rsync, shown below. On Windows, run Copy-Item in the opposite direction. Start Steam afterwards and open the game’s controller settings to confirm the layout loaded. If you also keep layouts in the cloud, expect Steam to compare the two and possibly ask which version to keep. Choose the newer one only if you know which is newer.

rsync -a "$HOME/SteamInputBackups/20261028-2005/" \
  "$HOME/.local/share/Steam/steamapps/common/Steam Controller Configs/"

Steam Input on Linux, Bazzite, Steam Deck and Steam Machine

The same layouts work on Linux, but two things differ: device permissions and how Steam is installed. Steam Input creates a virtual gamepad through the kernel’s uinput interface, which means your user needs write access to /dev/uinput and Steam needs udev rules for its supported hardware. Bazzite and SteamOS ship both. On a regular distro with the native package, the steam-devices or similar package provides the rules. On Flatpak Steam, host udev rules still apply, so install them on the host rather than inside the sandbox.

Check your setup with a few commands. They only read information, so they are safe to run.

ls -l /dev/uinput
ls /usr/lib/udev/rules.d/ /etc/udev/rules.d/ 2>/dev/null | grep -i -E 'steam|uinput'
ls -l /dev/input/by-id/

Example output on a healthy system (names and groups will differ):

crw-rw---- 1 root input 10, 223 Oct 28 19:02 /dev/uinput
60-steam-input.rules
usb-Sony_Interactive_Entertainment_DualSense_Wireless_Controller-event-joystick -> ../event21

The first command should show a device your user or group can write to. The second should list at least one Steam-related rules file. The third lists your physical controllers by name, which helps when a pad connects but Steam cannot see it. For raw event debugging, install evtest and run it with sudo to watch button presses at the kernel level. If the kernel sees a press but Steam does not, the problem sits in permissions or pairing. If neither sees it, the problem is hardware or Bluetooth.

One Linux detail from the October 7 beta note: Steam Input fixed a controller-reordering problem on Linux and a Bluetooth Low Energy issue where a controller could stay stuck in BLE mode when it could not find its host. If you saw those symptoms in September, update before you troubleshoot further. A second Linux habit saves time. Games running through Proton sometimes read the physical pad directly when SDL sees both the real device and the virtual one. A per-game launch option can hide the physical DualSense so only the Steam virtual pad is visible.

SDL_GAMECONTROLLER_IGNORE_DEVICES=0x054c/0x0ce6 %command%

Paste that into the game’s Launch Options field under Properties, General. The value pairs a vendor ID with a product ID. The example matches a DualSense, so substitute your pad’s IDs from lsusb if you use another model. Handhelds and living-room boxes follow the same logic. A Steam Deck uses its built-in controls through Steam Input by default, and our Steam Machine setup guide shows how the same layouts carry over to a console-style box with Proton and co-op play. Valve’s Steam Frame headset also uses controller layouts. The Steam Frame entry on the Valve Developer Community wiki lists its hardware, and the Steam Frame setup walkthrough covers first-time configuration. Per the October 9 beta note, Frame controllers now default to gamepad input in VR games that lack native VR input, which you can override per game.

Common Pitfalls That Waste an Evening

These mistakes show up again and again in forum threads, and every one is avoidable once you know the pattern.

• Turning on every controller type at once. It looks tidy, but it hands Steam pads that games already read natively. Enable one type, test, then add more only if needed.
• Editing the default layout instead of a personal copy. Changes to a shared template can follow you into unrelated games. Save a personal binding first, then edit that.
• Remapping menus by accident. A swapped button applies everywhere. Use an action layer, as in Step 8, when the base game should stay normal.
• Running two remappers at the same time. Steam Input plus DS4Windows or a vendor tool produces double presses and phantom inputs. Pick one translator per controller.
• Playing on the beta client and forgetting. Beta builds ship fixes and new bugs together. One user already reported layouts resetting after the stable October 13 update, so imagine the risk on beta. Stay on stable for daily play.
• Assuming a trackpad layout works on a plain gamepad. Layouts built for trackpads depend on hardware the Xbox pad lacks. Check the author’s notes before applying.
• Skipping the backup. Cloud sync copies corruption as readily as good data. Step 13 takes two minutes and saves hours.
• Blaming the layout for hardware faults. A drifting stick looks like a binding bug. Run the raw test from Step 3 first.

A final pattern deserves its own warning. Many people install a Community Layout, find one thing they dislike and then rebuild the whole scheme by hand. Edit the layout in place instead. Steam keeps your changes as a modified copy, so you can still revert to the original later through the layout browser. That route keeps what the author got right and fixes only the part you disagree with.

Troubleshooting: 10 Fixes for Steam Input Problems

Work through these in order. Each starts with the symptom and ends with the quickest fix.

1. The controller does not appear in Steam at all. Connect it by USB, check Settings, Controller for the matching Steam Input toggle and restart Steam. On Linux, run the permission checks from the previous section.
2. A PlayStation pad shows Xbox prompts in games. That is normal behavior when Steam presents a virtual Xbox device. For native PlayStation glyphs, set the game’s override to Disable Steam Input, but you lose Steam remapping and gyro for that title.
3. Buttons fire twice or phantom inputs appear. Two programs translate the same pad. Quit DS4Windows or any vendor remapper, or disable Steam Input for the game in Properties, Controller.
4. The controller works in Steam but not in a non-Steam game. Launch the game from the Steam Library after adding it as a non-Steam game. Steam Input needs Steam running and needs to know the game exists.
5. Your layout reverted to defaults after an update. One user reported this after the October 13 client update. Reapply your saved personal binding or restore the Step 13 backup, then check that cloud sync did not push an old copy back.
6. The configurator screen is blank or the gyro settings render wrongly. Restart Steam first, which a report from early October says clears a display bug. If the screen stays blank, a recovery page for unloadable local config files was added in a client update that month, so follow its prompt.
7. Menus misbehave after a remap. Move the unusual bindings to an action layer and switch it on only in gameplay, as in Step 8.
8. Player order is wrong in local co-op. Use the controller-reordering dialog added for Steam Input API games in the October 13 update. Note that reordering briefly disconnects the pads, so do it before the match starts.
9. Windows ignores the pad in admin windows. Elevated programs reject input from a non-elevated Steam. Run the game without elevation, or use the Lizard mode fallback on the new Steam Controller.
10. A Steam Controller will not pair or keeps dropping. Update its firmware through Steam. According to the October 13 notes, firmware added a second Bluetooth Low Energy pairing slot, configurable rumble intensity and fixes for repeated disconnects and puck pairing. Re-pair after the update rather than before.

If none of those match, collect evidence before you ask for help. Note your Steam client build, controller model, connection type, whether the problem shows in the device test screen and whether it survives a restart. Posts that include those details get useful answers. Posts that say it doesn’t work usually get none.

Complete Working Project: A Three-Layout Household Setup

Now put it together. The goal is a repeatable setup for a home where one person plays shooters with gyro, another races, and both sometimes drive the desktop from the couch. You will build three named layouts, one chord set and one backup, then verify the whole thing with a checklist. Budget about 25 minutes.

Layout one: Gyro FPS. Pick a shooter you own. Apply a gyro template from the Templates tab. Set gyro to act as mouse or joystick camera, activate it while the left trigger is half pulled, and lower sensitivity until aiming feels slow, then raise it by small steps. Add a Long Press on View or Select for screenshots. Export it as Gyro FPS under Personal Bindings.

Layout two: Couch Racing. Choose a racing game. Keep the left stick for steering and map throttle and brake to the triggers. Move the handbrake and camera to the bumpers. Add a Double Press on Y for reset. Because racing menus usually pair with plain face buttons, skip action layers here. Export it as Couch Racing.

Layout three: Desktop Couch. Open Settings, Controller, Desktop Layout. Make the right stick the mouse, the right trigger the left click and the left trigger the right click. Under Guide Button Chords, set Guide plus A to open the on-screen keyboard, Guide plus B to send Escape, and Guide plus Y to take a screenshot. This layout stays out of games, so it never clashes with the two above.

Backup and verification. Run the Step 13 script for your OS. Then work through this checklist:

• Steam Input is enabled only for the controller types in this household.
• Gyro FPS appears under Personal Bindings and applies to a second shooter in two clicks.
• Couch Racing steers, brakes and resets correctly in one race.
• The desktop pointer moves with the right stick with no game running.
• The Guide plus A chord opens the on-screen keyboard.
• A backup folder with a timestamp exists and holds at least one file.
• After restarting Steam, every layout above is still present.

If all seven pass, the setup is done. Schedule the backup script to run weekly. On Windows, Task Scheduler can run backup-steam-input.ps1 every Sunday evening. On Linux, a systemd user timer or a cron entry does the same job. Both cost nothing and turn a nasty surprise into a five-minute restore.

Advanced Tips for Power Users

Once the basics feel natural, a few techniques separate a good setup from a great one. Start with mode shifts. A mode shift swaps how a single stick or trackpad behaves while a button is held. Hold the left bumper and the right stick turns from camera control into a radial menu or a scroll wheel. It gives you a whole second input surface without adding hardware. Pair it with a Soft Press on triggers, where a light pull does one thing and a full pull does another. Racing and stealth games benefit from this the most.

Next, use per-device layouts deliberately. The September client behavior lets you keep one configuration for a Steam Controller and a different one for a Steam Deck. Handheld players who also dock the Deck can have trackpad bindings on the handheld and plain gamepad bindings on a TV pad without exporting anything by hand. Name the variants clearly, because Steam shows a long list quickly. One naming rule that works: device, then use, then game family, like Deck Gyro Shooters.

For people who swap controllers often, build a standard template and copy it. Make one personal binding with your preferred deadzones, trigger thresholds and a chord set. Duplicate it for each new game and change only the unique inputs. You keep muscle memory consistent, which beats reinventing the scheme in every title. Use the controller-reordering dialog when guests join, and run your pad test again whenever you plug in a different brand, since sensors and triggers vary a lot.

Developers have extra hooks. Games can opt into the Steam Input API and ship action sets, which is the reason some titles show a clean action list. Valve’s Steamworks documentation describes the emulation behavior and best practices, and the October 26 beta reportedly added GameInput v4 support for games that read pads through Microsoft’s newer API. You do not need that unless you test games, but it explains odd detection differences between builds. For more guides in this area, browse our gaming section, and for a running list of Steam Frame updates, Output Lag’s Steam Frame page keeps one.

Last, treat your layouts like code. Keep the backup folder in a synced directory or a private git repository, commit before big experiments and write a short note about what changed. When a client update misbehaves, a diff of two backups shows exactly which game lost its layout. That habit costs a minute per session and pays off the first time a patch shuffles your bindings.

Frequently Asked Questions

Is Steam Input free?

Yes. Steam Input is part of the Steam client and has no separate price, plan or subscription. Controller hardware costs money, but the software layer does not.

Does Steam Input work with PlayStation and Xbox controllers?

Yes. Valve’s own guidance describes it as working with the Steam Controller and other controllers, including Xbox, PlayStation, Switch and generic pads. You enable it per controller type in Settings, Controller.

Why does my PlayStation controller show Xbox buttons?

Steam Input presents a virtual Xbox-style device to the game, so the game draws Xbox icons. You can disable Steam Input for that game to regain native prompts, though that removes remapping and gyro for the title.

How do I use Steam Input with non-Steam games?

Add the game with Games, then Add a Non-Steam Game to My Library, and launch it from your Steam Library. Steam must be running, and the game needs its own entry so you can edit its layout.

Where do Community Layouts live in the current client?

Guides updated in late October 2026 describe the path as Library, controller icon, Edit Layout, Current Button Layout, then the Community Layouts tab. Templates sit in the same area for generic schemes.

Can I use gyro on any controller?

Only on hardware with motion sensors. A DualSense, a Switch Pro Controller, a Steam Deck and Steam Controllers qualify, while a standard Xbox pad does not. Steam Input handles the mapping, but it cannot invent sensors.

Did the October 2026 update break custom layouts?

One user reported that the October 13 client update replaced custom, desktop and chord layouts with defaults. That is a single community report and not a confirmed Valve-wide issue, so back up your layouts and check them after any client update.

Do I need the new Steam Controller to follow this guide?

No. Every step works with an ordinary Xbox, PlayStation or Switch pad. The new Steam Controller adds trackpad and grip options, and Valve still ships fixes for the 2015 Steam Controller, so older hardware stays supported too.