Where Does GE-Proton Install Compatibility Builds?
GE-Proton installs custom compatibility builds into compatibilitytools.d on Linux, with per-game prefixes staying under compatdata instead.
Last updated
GE-Proton is a toolbox, not a save folder. Each release drops a versioned directory with its proton binary and manifest into compatibilitytools.d, and Steam lists it as a runner afterward. Game data never enters the picture.
Roots vary by install flavor while the folder name stays constant. Native, Flatpak and Snap each anchor differently, with old root-alias guides describing current spots through links. Prefixes with actual saves live separately under compatdata per game.
Where GE-Proton stores this, by platform
~/.steam/steam/compatibilitytools.d
Custom runner installs with proton binary and manifest per version folder. Create the folder, extract releases there, restart Steam. Old root-alias paths resolve to the same place.
Frequently asked questions
How do I install GE-Proton manually?
Create the compatibilitytools.d folder under the Steam root flavor you run, extract the release tarball there, and restart Steam. Native, Flatpak and Snap each use their own root with the same folder name. Each version folder carries its proton binary and tool manifest.
Are my saves inside the GE-Proton folder?
They are different trees. Compatibility builds live in compatibilitytools.d while game prefixes with saves live in steamapps compatdata per app ID. Deleting a Proton version never touches saves, which belong to the prefix.
Which compatibilitytools.d path is mine?
Use the matching root for your install flavor. Native and Deck builds share the steam-root form while Flatpak and Snap nest under their sandbox paths. Old guides quoting the root alias describe the same place through a symlink.
Notice an outdated path? Let us know.