Source review: October 11, 2026. Menu labels, project releases and supported configurations can change; consult the linked documentation for your installed version.
Use the desktop as a normal computer
Valve exposes Desktop Mode through the Steam power menu, with a desktop shortcut for returning to Gaming Mode. SteamOS uses KDE Plasma, so a browser, file manager and desktop applications can coexist with the gaming interface. Keep Steam running when using its keyboard and controller integration. A physical keyboard and mouse can simplify setup, but they are convenience tools rather than a requirement for every task. Learn where downloads and application data are stored before installing several launchers or copying large files.
Prefer applications with a clear update path
Valve’s desktop FAQ describes Discover and Flatpak as the supported approach for adding desktop software to the writable part of the drive. Choose an application’s genuine publisher or project documentation, review its package identity and understand how updates are delivered. A web page’s install button and a forum command can target different packages with different data locations. Keep the original installer instructions and package identifier in your notes so a later reinstall is reproducible. Avoid running a downloaded shell script merely because its filename looks familiar.
Understand why files may be invisible
Flatpak applications run with permissions that can limit access to host files, devices and network resources. An emulator that cannot open a microSD folder may therefore have a permission or path problem rather than a damaged card. Check the application’s documented file access and storage arrangement. Grant access to the particular library folder needed instead of changing permissions broadly without understanding the result. Keep configuration and save files separate from game media where possible, which makes backing up and moving the installation much easier.
Treat system-level changes as another project
The default SteamOS operating-system layout is designed around image-based updates. Instructions for a generic Arch Linux workstation can have consequences that differ on a Deck. Before changing system packages or making the system writable, identify the exact reason, the expected update behavior and a restoration method. Most users can add useful software without modifying the base system. If a tool truly requires a deeper change, record every command, repository and configuration file and preserve an external backup of personal data before proceeding.
Troubleshoot the smallest reproducible case
Launch the application directly in Desktop Mode before adding a Steam shortcut. Confirm that its own file picker finds the expected content and that it can save data, then test controller input through the intended launch method. If it only fails from Gaming Mode, compare working directories, arguments, permissions and display behavior. Remove one experimental setting at a time. For bug reports, record SteamOS version, package version, launch method and the exact error. Screenshots are helpful, but a repeatable sequence and readable log give maintainers substantially better evidence.
Sources and project documentation
- Valve: desktop FAQ and Discover
- Flatpak: sandbox permissions
- Valve: developer FAQ and SteamOS system design
Continue with the related guide or return to the Steam Deck directory.