Every Windows game you launch through Steam on Linux runs inside its own private imitation of a Windows PC, and that imitation is called a prefix. It is a real folder on your drive, filled with a fake C drive, registry files, and the configuration each game expects to find. Most players never open it, yet it decides where saves live, which DLLs load, and why deleting a folder can fix one broken game while costing another its progress.
This article explains the prefix as a concept: its anatomy, its lifecycle, and the rules for handling it safely. It is deliberately not a tweaking tutorial. The folder’s batch-5 companion guide to Protontricks covers the tool that edits prefixes verb by verb; here the goal is to understand what that tool is editing, so the edits — and the occasional full reset — stop being guesswork.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
A Proton prefix is the self-contained fake Windows environment Steam builds for each game, stored in the steamapps/compatdata folder under the game’s app ID. It holds a drive_c folder, registry files, and per-game DLL settings. Proton creates it on first launch, updates it when the Proton version changes, and deleting it forces a clean rebuild — at the cost of anything stored only inside it.
What a Proton prefix actually is
Wine, the compatibility layer Proton is built on, has always worked this way: instead of emulating a whole Windows machine, it gives each application a directory that pretends to be one. That directory is the WINEPREFIX. Inside it, Wine maintains the folder structure Windows software expects, translates the registry into files it controls, and records which Windows libraries should be replaced, overridden, or loaded in a particular order.
Proton’s contribution is automation and isolation at Steam scale. Classic Wine setups often shared one prefix among many programs, so a tweak for one game could break another. Steam instead creates one prefix per game, keyed to the game’s app ID, and manages its creation and maintenance invisibly. Install two hundred games and you have two hundred small, independent Windows environments, each disposable without touching the others. That isolation is the single most important idea in this article: nearly every safe-handling rule follows from it.
Anatomy: what lives inside the folder
Open a game’s compatdata folder and the layout is consistent. The top level carries the app ID’s folder name, a small timestamp file Proton uses to judge whether the prefix is current, and the pfx directory, which is the prefix itself. Everything Windows-facing sits inside pfx.
The largest piece is drive_c, the fake C drive. It contains the familiar skeleton — Program Files, Program Files (x86), ProgramData, windows, and a users folder with a steamuser account inside it. Games that install redistributables write them here. More importantly, games that follow Windows conventions store settings and saves under the steamuser profile: Documents, My Games, Saved Games, and AppData paths all resolve into this folder. That is why the prefix is not purely disposable configuration; for games without cloud saves, it can be the only home your progress has.
Beside drive_c sit the registry files: system.reg for machine-wide settings, user.reg for the current user’s settings, and userdef.reg for default-user values. Wine keeps the registry as plain files rather than a live database, and every change a game or installer makes to the Windows registry lands in one of these. A corrupted registry is one of the classic reasons a prefix misbehaves. A dosdevices folder holds the drive-letter links, mapping c: to drive_c and z: to the root of your Linux filesystem, which is how games can browse out to a second drive. Finally, configuration Proton records for the game — DLL overrides and similar choices — is stored with the prefix, so tweaks belong to the environment they were made in.
The lifecycle: creation, updates, and version changes
A prefix is born on a game’s first launch. Proton copies and links a prepared template, called the default prefix, from its own files, then runs Wine’s boot process to initialise the registry and system folders for that specific game. This is the pause players see before a freshly installed title starts, and it happens again any time the prefix has to be rebuilt from scratch.
The prefix then has a quiet middle life. Games write saves and settings into it, installers add components, and tools such as Protontricks apply verbs — a missing runtime here, a font there — that persist between sessions. Nothing about this is shared with neighbouring games.
The interesting moment is a Proton version change. When you switch a game to another Proton release, or Valve updates the default build, Proton compares the prefix’s recorded timestamp against the new build. If the prefix is older, an update pass runs: Wine refreshes the system files and registry entries it manages, while the game’s own files in drive_c are normally left in place. This is why most version switches are painless — and why they occasionally are not. A prefix carrying overrides written for an older Proton can confuse a newer one, and a half-finished update after a crash can leave the environment inconsistent.
Why deleting a prefix both fixes and breaks games
Deleting the compatdata folder is the community’s standard last resort, and the anatomy explains both sides of it. On the next launch, Proton builds a brand-new prefix from the template: clean registry, clean system folders, no accumulated overrides, no half-applied changes. Any fault that lived in those layers — a broken DLL registration, a bad override, a registry entry a game wrote once and chokes on forever — is gone. For launch failures and mysterious regressions after a tweak, that is a genuine cure.
The breakage is equally predictable. Everything stored only inside the old prefix is deleted with it. Saves under the steamuser profile vanish for games that save there and do not use Steam Cloud. Settings, keybinds, and graphics choices stored in the profile go too, as do components a game installed into its own environment. Games whose saves live in Steam’s separate userdata area, or that sync through Steam Cloud, typically survive a reset untouched, which is why experiences differ so wildly between titles. The rule is not “never delete”; it is “know what this particular game keeps inside before you do.”
Safe-handling rules
A few habits make prefixes boring, which is what you want. First, back up before surgery: copying a game’s compatdata folder somewhere safe turns every experiment into a reversible one, and the folder can be restored wholesale if a fix makes things worse. Second, change one thing at a time inside a prefix — an override, a verb, a Proton version — so a regression has an obvious cause. Third, let update passes finish; interrupting a first launch after a Proton switch is how half-updated prefixes happen. Fourth, remember that reinstalling the game itself does not necessarily rebuild the prefix, because game files and compatdata are separate; players sometimes reinstall twice and troubleshoot the same untouched environment.
Storage that keeps a library of prefixes painless
Prefixes multiply quietly: a large library can mean hundreds of environments plus shader caches, and they reward fast, roomy storage.
Samsung 990 PRO 2TB NVMe SSD
A high-end Gen4 drive suited to being the main library disk, where hundreds of prefixes, game installs, and caches share one volume.
- Interface: PCIe 4.0 NVMe M.2 2280
- Capacity: 2TB
- Maker-rated sequential read: up to 7,450 MB/s
WD Black SN850X 2TB NVMe SSD
Western Digital’s gaming line, a like-for-like alternative for a primary library drive.
- Interface: PCIe 4.0 NVMe M.2 2280
- Capacity: 2TB
- Maker-rated sequential read: up to 7,300 MB/s
Crucial P3 Plus 4TB NVMe SSD
The capacity-first option: a single 4TB volume removes the temptation to scatter a library across filesystems that prefixes dislike.
- Interface: PCIe 4.0 NVMe M.2 2280
- Capacity: 4TB
- Maker-rated sequential read: up to 5,000 MB/s
Samsung T9 Portable SSD 2TB
The backup half of the system: fast enough over USB that copying compatdata folders before an experiment takes minutes, not an evening.
- Interface: USB 3.2 Gen 2×2
- Capacity: 2TB
- Maker-rated sequential read: up to 2,000 MB/s
Crucial MX500 1TB SATA SSD
A budget-tier home for a secondary library or an archive of prefix backups, where raw speed matters less than having the copy exist.
- Interface: SATA 2.5-inch
- Capacity: 1TB
- Maker-rated sequential read: up to 560 MB/s
How to choose: reset or repair, by symptom
Work through the symptom rather than reaching for the delete key. If a game stopped launching right after you applied a tweak, repair first: undo that single change, because the prefix was healthy minutes earlier. If a game broke after a Proton version switch, try switching back or letting a fresh update pass complete before assuming corruption. If saves are your fear, check where the game stores them — Steam Cloud status and a peek inside the steamuser profile tell you whether a reset is safe. Reserve the full prefix deletion for corruption you cannot localise: random launch failures, registry-level errors, or an environment patched so many times its state is unknown. And whatever you choose, copy the folder first; a backup converts every option on this list from a gamble into a procedure.
Who should skip this
Skip the internals entirely if your games simply work — the prefix model is designed to be invisible, and most players will never need to open compatdata. Also skip manual prefix surgery if a game’s community already documents a known-good Proton version and steps; following the documented route beats understanding the machinery. Finally, if your library lives on a Steam Deck you never tinker with, Valve’s defaults are the supportable path, and this knowledge is insurance rather than a to-do list.
FAQ
Where exactly is my game’s prefix?
Inside the Steam library that holds the game, under steamapps/compatdata, in a folder named with the game’s app ID; the prefix itself is the pfx folder within. Games added as non-Steam shortcuts get generated IDs and prefixes in the same place.
Does deleting a prefix delete my save files?
Only the saves stored inside it. Games saving under the in-prefix steamuser profile and lacking Steam Cloud lose them; games using Steam Cloud or Steam’s userdata area generally do not. Check the individual game first, and back the folder up regardless.
Why does a game rebuild everything after I change Proton versions?
Because the new Proton build finds the prefix’s timestamp older than its own template and runs an update pass, refreshing the system files and registry it manages. Your game files and profile data are normally preserved through that pass.
Can two games share one prefix?
Under Steam, no — Proton deliberately isolates each game in its own environment, and that isolation is a feature. Shared prefixes belong to manual Wine setups, where one game’s fix can become another game’s bug.
Final verdict
The Proton prefix is a small, honest design: one folder pretending to be one Windows PC, per game, so no game’s environment can poison another’s. Understand what lives inside — especially the saves hiding in the steamuser profile — and the folklore resolves into simple rules: back it up, change one thing at a time, and delete it only when you know what it holds.











