- Top Pick: Samsung 990 PRO 2TB NVMe SSD
- Runner-up: WD Black SN850X 2TB NVMe SSD
- Also consider: Crucial T500 2TB NVMe SSD
Every Linux gamer eventually meets the game that breaks the pattern: the whole library launches happily on the default Proton build, but one title crashes on startup, plays its cutscenes as a black screen, or ran perfectly until an update landed. The fix is rarely a new distro or a reinstall. Steam lets you pin a specific compatibility build to a single game while everything else keeps the global default, and knowing which build to reach for turns a frustrating evening into a five-minute adjustment.
This guide is the management workflow itself: the three build families and what each is actually for, the per-game override mechanics, a decision sequence for one stubborn title, and how to roll a single game back when an update does damage. A companion article on this site compares the stable and Experimental channels head to head; here the focus stays on running several builds side by side, one per game, entirely on purpose.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
Set a global default Proton build in Steam’s Compatibility settings, then override it per game from that game’s Properties menu whenever one title misbehaves. Read the game’s ProtonDB page to see which build recent players settled on, try Experimental or GE-Proton for stubborn cases, and pin the older build again if an update breaks a working game.
The three build families and what each is for
Official numbered Proton builds are Valve’s stable releases, and they are the default for a reason: each one is a frozen, broadly checked snapshot that most of the library runs well on. Crucially for this workflow, a new numbered release arrives as its own separate entry in the compatibility list, and older entries stay selectable indefinitely. That permanence is the raw material of per-game management.
Proton Experimental is the rolling branch where fixes land first, and it is also where Valve publishes Hotfix builds aimed at specific launch-day breakage. Experimental can repair a game weeks before the fix reaches a numbered release, but a rolling branch can also regress, which is exactly why it belongs on one game at a time rather than as your global default.
GE-Proton is the community build maintained by GloriousEggroll. It adds media codec support and game-specific patches that licensing keeps out of Valve’s official builds, and its classic symptom is the game whose video cutscenes play as a black screen or without sound under official Proton. GE builds are installed outside Steam’s own tooling, usually with ProtonUp-Qt, and then appear in the same per-game list as everything else.
How the per-game override actually works
Steam has two layers of setting. The Compatibility page in Steam’s main Settings chooses the global default for every title that has no override of its own. Each game’s Properties panel has its own Compatibility section with a checkbox that forces a specific Steam Play compatibility tool, and that per-game choice wins for that game only.
The isolation runs deeper than the menu. Every game executes inside its own prefix, a self-contained folder tree that mimics a Windows installation and is keyed to that game’s app ID. Builds and prefixes are per-title by design, so switching one game’s build never touches another game’s files. The first launch after a switch can take longer while Steam validates the prefix and rebuilds shader caches; that pause is normal and is not data loss. Saves stored inside the prefix survive a build switch, because the prefix is only removed when you delete it deliberately.
A decision workflow for one stubborn game
Start by reproducing the failure on the default build and naming it precisely: no launch at all, a crash after the logos, black cutscenes, a dead controller, missing audio. The symptom decides the remedy, so write it down before changing anything.
Next, open the game’s ProtonDB page and read the recent reports, weighting the ones from players on the same graphics brand as yours. Look for the build names that repeat. For any given problem title, the crowd usually converges on one build, and that consensus is the single most useful data point in this whole workflow.
Then match the symptom to a family. Launch-day breakage points to Experimental, or to a Hotfix build if one exists for the title. Broken video playback points to GE-Proton. A game that worked last month and broke after an update points backwards, to the previous numbered build. Change one variable at a time: the build first, and any launch options the ProtonDB reports mention only afterwards, so you always know which change did the work. Finally, play past the original failure point, not just to the main menu, before declaring the fix real.
Keeping notes per title
Per-game overrides are invisible until you go looking for them, and six months later nobody remembers which build rescued which game. Keep a plain text file or a simple spreadsheet with four columns: the game, its app ID, the build that works, and any launch options attached, plus the date you set it. Steam also provides a notes field for each game in the library, which is enough room for a build name on its own.
The payoff arrives after a reinstall, a distro hop, or a new machine, when the notes let you rebuild every override in minutes instead of re-deriving each fix from scratch. Before experimenting on a game whose saves are not cloud synced, copy its prefix folder somewhere safe; the notes tell you where your working configuration lives, and the backup makes the experiment reversible.
Rolling one game back after a bad update
Two different updates can break a game: the game itself can patch, or the Proton build underneath it can move. The per-game override treats the second kind. Open the same Compatibility panel in the game’s Properties and select the previous numbered build; because Valve leaves older builds installed and selectable, the pin takes effect on the next launch.
The rest of the library stays on the current default while the one fragile title sits on its older build, and that isolation is the entire point of managing versions per game. Leave the pin in place while you play. Revisit it after the next Proton release, or after the game’s own patch notes mention compatibility work, and try returning to the default then, ideally with the prefix backed up first.
How to choose
Match the build family to the game’s behaviour rather than to habit:
- Runs fine on the default: do nothing. An override is a fix, not an upgrade, and a working game gains nothing from a different build.
- New release broken at launch: try Experimental first, and the title’s Hotfix build when Valve publishes one.
- Cutscenes black, silent, or stuttering: reach for GE-Proton, whose extra codec support targets exactly that failure.
- Worked before, broken after an update: pin the previous numbered build and wait for the next release.
- Multiplayer title with anti-cheat: check the game’s current status first. No build choice overrides a publisher that has not enabled Linux support.
Who should skip this
Players whose entire library runs well on the default build can skip all of it; per-game management is maintenance you only need once a specific title misbehaves. Native Linux games never touch Proton, so there is nothing to pin. And games handled by other launchers, such as Heroic, Lutris, or Bottles, manage their Wine and GE builds through their own panels, so the Steam settings described here do not apply to them.
Gear that suits a multi-build library
Several installed builds, one prefix per game, and shader caches for every title all live on disk at once, so a library managed this way rewards fast, roomy storage. The picks below carry maker-stated specifications only, and the speeds quoted are the manufacturers’ published figures.
Samsung 990 PRO 2TB NVMe SSD
A flagship Gen4 drive for the main library, where prefix validation and shader cache writes are everyday events.
Specs:
– Capacity: 2 TB
– Interface: PCIe Gen4 x4, NVMe
– Form factor: M.2 2280
– Maker-stated sequential read: up to 7,450 MB/s
– Model: MZ-V9P2T0B/AM
WD Black SN850X 2TB NVMe SSD
Western Digital’s gaming line offers the same class of Gen4 speed, a straightforward alternative for a second library drive.
Specs:
– Capacity: 2 TB
– Interface: PCIe Gen4 x4, NVMe
– Form factor: M.2 2280
– Maker-stated sequential read: up to 7,300 MB/s
– Model: WDS200T2X0E
Crucial T500 2TB NVMe SSD
A DRAM-equipped Gen4 drive that suits a mixed library of large single-player titles with heavy shader caches.
Specs:
– Capacity: 2 TB
– Interface: PCIe Gen4 x4, NVMe
– Form factor: M.2 2280
– Maker-stated sequential read: up to 7,400 MB/s
– Model: CT2000T500SSD8
Samsung T9 Portable SSD 2TB
A fast external drive for carrying a library or prefix backups between a desktop and a handheld, so a working configuration travels with you.
Specs:
– Capacity: 2 TB
– Interface: USB 3.2 Gen 2×2
– Maker-stated sequential read: up to 2,000 MB/s
– Model: MU-PG2T0B/AM
8BitDo Ultimate 2 Bluetooth Controller
Once the build is right, the game still needs a pad; this one pairs over Bluetooth or a cable and brings its own charging dock.
Specs:
– Connectivity: Bluetooth and USB wired
– Joysticks: TMR
– Triggers: switchable Hall Effect and tactile modes
– Extras: back buttons, motion control, charging dock
FAQ
Does forcing a build for one game change my other games?
No. The per-game setting overrides the global default for that title only, and each game keeps its own prefix, so the rest of the library is untouched.
Will switching builds delete my save games?
A build switch keeps the game’s prefix, which is where local saves live, and cloud-synced saves are stored by Steam regardless. Only deleting the prefix removes local saves, so back it up first if a game does not use cloud saves.
Why do old Proton builds stay in the list?
Because pinning and rollback depend on them. Valve leaves previous numbered builds selectable so a game that regresses on a new release can be parked on the last build that worked.
Should every game just use GE-Proton?
No. Official builds receive Valve’s own per-game attention and are the safer default. GE-Proton earns its place as a targeted fix, most often for media playback problems, applied one title at a time.
Final verdict
Managing Proton versions per game is a small habit with an outsized payoff: one global default you rarely touch, a ProtonDB check before any change, a symptom-matched build pinned to the one game that needs it, and a short note so the fix survives a reinstall. Treat builds as per-title settings rather than system-wide upgrades, and a broken update becomes a two-minute detour instead of a lost evening.











