Where Does ProtonUp-Qt Install Compatibility Tools?
ProtonUp-Qt installs compatibility tools into Steam compatibilitytools.d folders, with its own config beside the install.
Last updated
ProtonUp-Qt manages files in two places. Compatibility tools (GE-Proton, custom Wine builds) go into a Steam compatibilitytools.d directory, whose exact parent depends on how Steam was installed: .local/share/Steam, .steam/steam, or Flatpak paths. Its own settings live with the app install, under the Flatpak config tree for Flatpak users.
Location drift is the whole support history of this app. Valve moved the canonical compat dir more than once, and symlinked .steam trees confuse detection. Check the launcher dropdown first whenever installs vanish: the tool and Steam simply disagree about which Steam is real.
Where ProtonUp-Qt stores this, by platform
~/.local/share/Steam/compatibilitytools.d
Current canonical target. Older installs used .steam/root variants that may still shadow it. Each tool version is one subfolder here.
~/.var/app/net.davidotek.pupgui2/config/pupgui
Flatpak app settings including custom install dirs. Native installs keep config next to the binary instead.
Frequently asked questions
Steam does not see my ProtonUp-Qt installed versions. Why?
Open the launcher dropdown and confirm it lists the right Steam root. Symlinked .steam paths and leftover empty Steam trees are the usual reason tools land unseen.
Can I install to a custom directory?
Yes through the custom install directory dialog. Point it at the right compatibilitytools.d and restart the app before installing anything.
ProtonUp-Qt crashes looking for config.vdf. What fixes it?
Delete the stale empty Steam tree or copy the VDF files in. ProtonUp-Qt validates installs by config.vdf and libraryfolders.vdf, not by folder existence.
Notice an outdated path? Let us know.