From ArchWiki
(Redirected from Launch option)

Steam is a popular game distribution platform by Valve.

Note: Steam for Linux only supports Ubuntu LTS.[1] Thus, do not turn to Valve for support for issues with Steam on Arch Linux.


Enable the multilib repository and install the steam (recommended) or alternatively the steam-native-runtime package for running Steam with native system libraries. See /Troubleshooting#Steam runtime.

Note: If you are installing for the first time, you may be prompted for the 32-bit Vulkan driver package. By default pacman alphabetically chooses lib32-amdvlk, which can introduce issues like being unable to use Vulkan at all when you install it by accident for different GPU vendor or launch games on AMD GPUs if not installed alongside amdvlk. See Vulkan#Installation to choose the proper driver for your GPU.

In order to run Steam on Arch Linux:


Install steamcmdAUR for the command-line version of Steam.

Directory structure

The default Steam install location is ~/.local/share/Steam. If Steam cannot find it, it will prompt you to reinstall it or select the new location. This article uses the ~/.steam/root symlink to refer to the install location.

Library folders

Every Steam application has a unique AppID, which you can find by either looking at its Steam Store page path or visiting SteamDB.

Steam installs games into a directory under LIBRARY/steamapps/common/. LIBRARY normally is ~/.steam/root but you can also have multiple library folders (Steam > Settings > Downloads > Steam Library Folders).

In order for Steam to recognize a game it needs to have an appmanifest_AppId.acf file in LIBRARY/steamapps/. The appmanifest file uses the KeyValues format and its installdir property determines the game directory name.

Note: In order to add additional drives to a Steam installation made through flathub, the user must first give the Steam Client authorization to access the mount-point of the additional drive manually through a tool such as flatsealAUR.


steam [ -options ] [ steam:// URL ]

For the available command-line options see the Command Line Options article on the Valve Developer Wiki.

Steam also accepts an optional Steam URL, see the Steam browser procotol.

Launch options

When you launch a Steam game, Steam executes its launch command with /bin/sh. To let you alter the launch command Steam provides launch options, which can be set for a game by right-clicking on it in your library, selecting Properties and clicking on Set Launch Options.

By default Steam simply appends your option string to the launch command. To set environment variables or pass the launch command as an argument to another command you can use the %command% substitute.


  • only arguments: -foo
  • environment variables: FOO=bar BAZ=bar %command% -baz
  • completely different command: othercommand # %command%

Tips and tricks

Start Minimized

It is possible to have Steam start minimized to the system tray, rather than taking focus. Add -silent to the list of command line arguments; see Desktop entries#Modify desktop files for doing this by default.

Small Mode

Steam supports an alternative, minimal UI with just your game list - the store, community and cover collection views are hidden. You can switch to it with View > Small Mode. To go back to the standard UI, select View > Large Mode.

Proton Steam-Play

Valve developed a compatibility tool for Steam Play based on Wine and additional components named Proton. It allows you to launch many Windows games (see compatibility list).

It is open-source and available on GitHub. Steam will install its own versions of Proton when Steam Play is enabled.

Proton needs to be enabled on Steam client: Steam > Settings > Compatibility. You can enable Steam Play for games that have and have not been whitelisted by Valve in that dialog.

Proton supports Easy Anti Cheat integration if the developer activates it, however EAC may require a particular patched version of glibc: if a game is been reported to be working but is not in your machine, try using Steam Flatpak because it comes with glibc patched.

Force Proton usage

If needed, to force enable Proton or a specific version of Proton for a game, right click on the game, click Properties > Compatibility > Force the use of a specific Steam Play compatibility tool, and select the desired version. Doing so can also be used to force games that have a Linux port to use the Windows version.

Use Proton outside of Steam

You can also install Proton from AUR with protonAUR or proton-gitAUR, but extra setup is required for them to work with Steam. See the Proton GitHub for details on how Steam recognizes Proton installs.

Steam Input

When a controller is plugged in while Steam is running, Steam's default behavior is to leave it alone and let games use it as-is. The gamepad's evdev and joystick devices are exposed by the kernel, and games may use them using APIs such as SDL2 as if Steam were not in the picture.

The Steam Input subsystem offers an abstraction layer which allows for more advanced functionality such as rebinding buttons and axes, having game-specific profiles, and doing higher-level button mappings based on in-game actions. The Steam Input Configurator (SIC) is the part of the system that implements this functionality. To enable Steam Input for a controller, go to Steam > Settings > Controller > General Controller Setting. [2] This will open a menu from the Big Picture settings, where you can enable the Configuration Support option corresponding to your controller.

Steam Input Configurator

When SIC is enabled for a controller, there are a few different controller devices:

  • The virtual Steam Controller, used by games that utilize the Steam Input API. All rebindings and Steam-specific features are functional.
  • An evdev device representing an emulated Xbox 360 controller, used by games that do not support Steam Input. Basic rebindings are in effect. [3]
  • The original controller evdev device, whose inputs are passed through the SIC. Rebindings are not in effect, but games should be defaulting to the 360 controller instead.
  • The joystick analogues of the above two devices.

The SIC's behavior is context dependent:

  • When launching a game that supports the Steam Input API, it is using the SIC in native mode. The game receives "actions" rather than raw inputs to handle.
    • This works for games running in Proton that would be using Steam Input on Windows.
    • Even though it's theoretically not needed, the emulated 360 controller is still present.
    • A game may choose to provide both support for the Steam Input, and traditional input API libraries that defer to evdev and joystick under the hood. When the game is launched with Steam and with SIC enabled for the controller, Steam Input takes higher priority.
    • A game can also choose to only support Steam Input. For example, in Among Us, a gamepad will not work unless you have the SIC running.
  • When launching a game that does not support Steam Input, it is (unknowingly) using the SIC in legacy mode. The game receives its expected low-level raw inputs from what seems to be a 360 controller, but they are actually spoofed by the SIC to emulate the desired behavior of native mode.
    • This is the case for native games that use evdev or joystick, as well as Windows games running through Proton that use DirectInput or XInput.
  • When launching a game that supports neither Steam Input nor other gamepad APIs, SIC can activate a profile that emulates gamepad support as described below.
  • When Big Picture has focus, the current Big Picture profile is in effect, configurable via Steam > Settings > Controller > Big Picture Configuration.
  • When anything else has focus, the current Desktop profile is in effect, configurable via Steam > Settings > Controller > Desktop Configuration.
  • When anything has focus, additional global bindings can be configured via Steam > Settings > Controller > Guide Button Chord Configuration.

Games are rated on how comprehensive their gamepad support is. A game can have one of three icons in the Big Picture UI: [4]

  • A full gamepad icon, indicating that the game has full controller support. This can be achieved even if the game does not use the Steam Input API; the focus is on accessibility regardless of API.
  • A half-filled gamepad icon, indicating that the game has partial gamepad support. Even if the game is using the Steam Input API, there are instances like Team Fortress 2 where certain parts are still inaccessible to warrant this rating.
  • A keyboard icon, indicating the game does not have native gamepad support.

In cases where the game does not have full gamepad support, SIC tries to fill the gaps. For example, in Bloons Tower Defense 5, a game that requires you to point and click, Steam will automatically activate the Keyboard (WASD) and Mouse profile, allowing you to use your gamepad to move and click.

Recommended Steam Input usage

To summarize what this all means for usage:

  • Enabling "Configuration Support" in the Big Picture settings is recommended for enhanced gamepad support such as rebinding to one's liking, or automated fixes like Nintendo-style button remapping or keyboard/mouse.
  • For some games, enabling this is outright required if they do not support traditional gamepad APIs.
  • By default, if you have enabled this, then the controller will not work with non-Steam games because the 360 controller takes precedence over the original controller device, but the default Desktop profile has the buttons disabled. To fix this, you can either:
    • Set your Desktop profile to the template for Gamepad. This will pass through the inputs to the 360 controller, making the default device usable for other programs.
    • Have the other game use the original device if it supports this. Note that the game will not benefit from any Steam Input rebindings.
    • Disable the whole feature for the controller so Steam does not create the 360 controller at all. Note that Steam games would then not benefit from the enhanced gamepad support.
    • Close Steam when using the other games.

Big Picture Mode without a window manager

To start Steam in Big Picture Mode from a Display manager, you can either:

  • Install steamos-compositorAUR
  • Alternatively, install steamos-compositor-plusAUR, which hides the annoying color flashing on startup of Proton games and adds a fix for games that start in the background
  • Manually add a Steam entry (but you lose the steam compositor advantages: mainly you cannot control Big Picture mode with keyboard or gamepad):

create a /usr/share/xsessions/steam-big-picture.desktop file with the following contents:

[Desktop Entry]
Name=Steam Big Picture Mode
Comment=Start Steam in Big Picture Mode
Exec=/usr/bin/steam -bigpicture

Steam skins

Note: A new Steam UI was released in June 2023. Skins not updated for this new UI will have no effect.

The Steam interface can be customized using skins. Follow this Steam guide for more information.

Some skins updated for the 2023 UI are:

Changing the Steam notification position

The default Steam notification position is bottom right.

You can change the Steam notification position by altering Notifications.PanelPosition in

  • resource/styles/steam.styles for desktop notifications, and
  • resource/styles/gameoverlay.styles for in-game notifications

Both files are overwritten by Steam on startup and steam.styles is only read on startup.

Note: Some games do not respect the setting in gameoverlay.styles e.g. XCOM: Enemy Unknown.

Use a skin

You can create a skin to change the notification position to your liking. For example to change the position to top right:

$ cd ~/.steam/root/skins
$ mkdir -p Top-Right/resource
$ cp -r ~/.steam/root/resource/styles Top-Right/resource
$ sed -i '/Notifications.PanelPosition/ s/"[A-Za-z]*"/"TopRight"/' Top-Right/resource/styles/*

Live patching

gameoverlay.styles can be overwritten while Steam is running, allowing you to have game-specific notification positions.

sed -i "/Notifications.PanelPosition/ s/\"[A-Za-z]*\"/\"$1\"/" ~/.steam/root/resource/styles/gameoverlay.styles

And the #Launch options should be something like:

~/.steam/ TopLeft && %command%

Steam Remote Play

Note: Steam In-Home Streaming has become Steam Remote Play.

Steam has built-in support for remote play.

See this Steam Community guide on how to setup a headless streaming server on Linux.

Sharing games with Windows when using Proton

If you use Proton (Steam Play) for launching your games, and still keep a Windows installation for some reason (for example, if some game has problems with anti cheat or if you want to make a comparison tests with Windows), you may want to store your games in a common partition instead of keeping two copies of game one per OS.

To add another folder for library, click on Steam > Settings > Downloads > STEAM LIBRARY FOLDERS, then on the ⊕ (Plus) button.

There are three file systems, that can be read/write by both Windows and Linux.


See for more information on how to configure that. To launch games from an NTFS drive, follow the steps from Steam/Troubleshooting#Steam Library in NTFS partition.

Using ntfs has disadvantages. It happens often that shaders cache folder becomes corrupted. Messages saying ntfs3: sdb6 ino=1921f, steamapprun_pipeline_cache Looks like your dir is corrupt. You cannot fix that from linux. You need to boot to Windows and use chkdsk for that.


This FS has disadvantage that it is case-insensitive. You will get such message: SteamLibrary has both 'SteamApps' and 'steamapps' directories. This will cause problems. Please fix manually and only keep 'steamapps' See issue #7665

Also it is problematic to create symlinks on exfat, so you cannot use the method of symlinking compatdata as in ntfs method.


This file system can be used without a problem. The only thing to remember is that Linux has not yet write support to udf 2.50+. So just create a udf formatted partition in Gparded, and it will be 2.01.

Faster shader pre-compilation

In certain circumstances shader pre-compilation may only use one core, however this can be overridden by the user, example to use 8 cores:

unShaderBackgroundProcessingThreads 8

Compatibility layers other than Proton

There are compatibility tools other than Proton/Wine.

  • Luxtorpeda — Run games using native Linux engines. || luxtorpeda-gitAUR
  • Boxtron — Run DOS games using native Linux DOSBox || boxtronAUR

You can also use protonup-qtAUR to manage them:

  1. Close Steam
  2. Install protonup-qtAUR
  3. Open protonup-qt and install desired tools
  4. Start Steam
  5. In the game properties window, select Force the use of a specific Steam Play compatibility tool and select the desired tool.

Disable HTTP2 for faster downloads

Some systems and configurations seem to have issues with HTTP2. Disabling HTTP2 will probably yield faster downloads on those configurations. You can either use the console command @nClientDownloadEnableHTTP2PlatformLinux 0 or set it in steam_dev.cfg like so:

@nClientDownloadEnableHTTP2PlatformLinux 0

Run games using discrete GPU

On hybrid graphics laptops, Steam runs games using the integrated GPU by default. See PRIME#PRIME GPU offloading to switch to the more powerful discrete GPU for specific games.


Note: Installing Steam from Flathub/Flatpak will fix many of the issues faced on the client but will require alternative, less documented forms of troubleshooting on the long run.

Steam can also be installed with Flatpak as com.valvesoftware.Steam from Flathub. The easiest way to install it for the current user is by using the Flathub repository:

$ flatpak --user remote-add --if-not-exists flathub
$ flatpak --user install flathub com.valvesoftware.Steam
$ flatpak run com.valvesoftware.Steam

The Flatpak application currently does not support themes. Also you currently cannot run games via optirun/primusrun, see Issue#869 for more details.

Steam installed via Flatpak is not able to access your home directory and overriding this will cause Steam to not run because it is not safe. However, you can freely add directories outside the home directory. If you want to add an external library, run the following command to add it:

$ flatpak override --user com.valvesoftware.Steam --filesystem=/path/to/directory

Launching Steam with Flatpak might warn you about installing the steam-devices package. This package currently does not exist but game-devices-udevAUR can be installed instead, see Gamepad#Device permissions.

Asian Font Problems with Flatpak

If you are having problem getting Asian fonts to show in game, it is because org.freedesktop.Platform does not include it. First try mounting your local font :

$ flatpak run --filesystem=~/.local/share/fonts --filesystem=~/.config/fontconfig com.valvesoftware.Steam

If that does not work, consider this hack: make the fonts available by directly copying the font files into org.freedesktop.Platform's directories, e.g.



See Steam/Troubleshooting.

See also