How to Install Steam on Linux: A Complete Setup Guide
Steam on Linux is more capable than many people expect. Valve has invested heavily in Linux gaming infrastructure — including Proton, its compatibility layer for running Windows games on Linux — and the result is a platform that works well across a wide range of distributions. That said, the installation process varies depending on which distro you're running, how it's configured, and what you want to do with Steam once it's installed.
Why Steam Works on Linux
Steam has offered a native Linux client since 2013. Over time, Valve's development of Proton (built on Wine and additional compatibility tools) dramatically expanded the library of playable games beyond those with native Linux builds. Today, thousands of titles run on Linux through Steam with little to no extra configuration.
The Linux client supports the same core features as its Windows counterpart: game downloads, cloud saves, the Steam overlay, remote play, and the Steam Workshop. What differs is how you get it running — and how smoothly it runs — depending on your setup.
What You Need Before You Start
Before installing Steam, a few things are worth checking:
- Distribution: Steam officially supports Ubuntu, Debian, Fedora, Arch Linux, and several others. Most major distros work, but package availability and update frequency vary.
- Architecture: Steam requires a 64-bit operating system. On some distros, you'll also need 32-bit libraries enabled, because Steam's runtime still depends on certain 32-bit components.
- GPU drivers: For gaming, you'll want the correct graphics drivers installed. AMD and Intel GPUs use open-source drivers that are typically included in the kernel. NVIDIA requires proprietary drivers, which need to be installed separately before Steam will perform well.
- Disk space: Steam itself is lightweight, but games vary widely. Make sure you have adequate storage before proceeding.
Installation Methods by Distribution
Ubuntu and Debian-Based Distros
On Ubuntu, Linux Mint, Pop!_OS, and similar systems, Steam is available directly from the default repositories or as a downloadable .deb package from Valve.
Via the package manager:
sudo apt update sudo apt install steam This installs the Steam installer package, which then downloads and sets up the full client on first launch. Some distros may require you to enable multiverse (Ubuntu) or non-free (Debian) repositories first, since Steam is proprietary software.
Via Valve's .deb package: Download the package from store.steampowered.com, then install it using:
sudo dpkg -i steam_latest.deb sudo apt --fix-broken install The second command resolves any missing dependencies automatically.
Fedora and RPM-Based Distros
Steam isn't in Fedora's default repositories due to licensing, but it's available through RPM Fusion, a third-party repository:
sudo dnf install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm sudo dnf install steam On openSUSE, Steam is available through the Packman repository using similar steps.
Arch Linux and Arch-Based Distros (Manjaro, EndeavourOS)
On Arch, Steam is available from the multilib repository. Enable it by uncommenting the [multilib] section in /etc/pacman.conf, then run:
sudo pacman -Syu sudo pacman -S steam Arch-based systems give you more control over which version and dependencies are installed, but they also require more attention to driver and library compatibility. 🐧
Flatpak (Distribution-Agnostic)
If your distro doesn't have a well-maintained Steam package, or you want an isolated installation, Flatpak is a reliable option:
flatpak install flathub com.valvesoftware.Steam Flatpak packages Steam in a sandboxed environment with its own runtime. The trade-off is that filesystem access works differently — you may need to configure permissions to point Steam at game libraries on external drives or non-default paths.
Setting Up Proton for Windows Games
Once Steam is installed, enabling Proton lets you run games without native Linux builds. In Steam settings, navigate to Steam Play and enable "Enable Steam Play for all other titles." You can select a specific Proton version or use the default recommended one.
Proton compatibility varies by game. The site ProtonDB (a community database) tracks which games work well, which need tweaks, and which are currently broken. It's a useful reference before you spend time troubleshooting.
| Game Type | Typical Experience |
|---|---|
| Native Linux build | Generally runs as expected |
| Proton-supported (verified) | Works with minimal configuration |
| Proton-supported (community) | May need launch options or specific Proton version |
| Anti-cheat dependent titles | Often limited or non-functional on Linux |
Common Post-Installation Issues
- Black screen on launch: Often a driver issue, especially with NVIDIA. Confirm the correct proprietary driver is active.
- Missing 32-bit libraries: Some games won't launch without them. On Ubuntu:
sudo apt install libGL1:i386. - Steam won't open after install: Try launching from the terminal to see error output. A corrupted runtime can sometimes be fixed by deleting
~/.steamand~/.local/share/Steamand reinstalling. ⚠️ - Flatpak permission errors: Use Flatseal (a Flatpak permissions manager) to grant Steam access to additional drives or directories.
The Variables That Shape Your Experience
Steam on Linux works reliably for many users, but the quality of that experience shifts based on factors specific to each setup:
- Your GPU and driver version have more impact on gaming performance than almost anything else
- Your distro's update cadence affects how current your Steam client, drivers, and Proton version are
- The specific games in your library may or may not have Linux builds, and Proton compatibility ranges from seamless to unsupported
- Your comfort level with the terminal determines how easily you can resolve dependency issues or tweak configurations
- Whether you're gaming on a desktop, laptop, or Steam Deck changes which drivers and power settings matter
A user on a freshly installed Ubuntu system with an AMD GPU and a library of indie titles will have a very different experience than someone on a minimal Arch install with NVIDIA hardware trying to run competitive multiplayer games. Both are valid setups — they just involve different steps, different troubleshooting paths, and different realistic expectations. 🎮
Understanding your own hardware, distro, and game library is ultimately what determines which installation method to use and how much configuration to expect afterward.