Steam Deck button and keyboard mapping
Map Deck controls per game through Steam Input. Open Controller Settings, set the layout, then assign the buttons you need.
Three input layers, not one
Most Deck mapping confusion comes from not knowing which layer is in charge:
- The game or emulator reads whatever device it is given and maps it internally.
- Steam Input intercepts the physical controls and presents a virtual pad or keyboard commands.
- SteamOS handles system-level shortcuts — the keyboard, brightness, and the QAM.
A button that “does nothing” is usually being consumed by the wrong layer. Emulators in particular often want the raw pad, which is why disabling Steam Input fixes so many mapping complaints.
Map per game, in Gaming Mode
- Launch the game or emulator and press the QAM button (three dots).
- Open Controller Settings, then Edit Layout.
- Work through the tabs: Buttons, Triggers, Trackpads, Grips. The back grips are separate buttons, not duplicates of the shoulders.
- For emulators, bind the trackpad as a mouse and the right trackpad click as a left click — that covers most launcher UIs and touch menus.
- Save the layout under a name. Community layouts are a good base but assume the game, not an emulator.
Bring up the keyboard reliably
The on-screen keyboard appears with Steam + X, and that works inside most emulators. If it does not, the emulator is capturing input exclusively — switch to Desktop Mode to type, or enable Steam Input for that title so the shortcut is routed.
When the emulator ignores input entirely
Check whether the pad works in the emulator’s own input settings screen. If it lists a device and responds, the game’s internal bindings are the problem. If it lists nothing, Steam Input is intercepting the pad — disable it for that title in Properties → Controller, then relaunch.
On a Deck, restarting from Gaming Mode after changing controller settings is worth doing. Some emulators read controller state only at boot and will keep the old layout until the process restarts.