Where Does Bazzite Store Game Saves?
Bazzite follows standard Linux paths: Steam libraries, compatdata prefixes, and a shared MicroSD library.
Last updated
Bazzite stores game data exactly where Fedora and Steam put it, since it is an Atomic Fedora image with Steam preinstalled. Native saves live in your home folder per game, while Windows games live inside Proton prefixes under compatdata.
The Bazzite specific bits are conveniences: automatic trimming keeps compatdata small, shader caches stay lean, and one MicroSD library can serve several Bazzite installs. Proton logs for troubleshooting land in home named by app id when you set PROTON_LOG=1.
Deck edition quirks matter on handhelds. Single user only, so secondary accounts hit prefix ownership errors, fixed with a separate library folder plus symlinks for shared data.
Where Bazzite stores this, by platform
~/.local/share/Steam/steamapps/compatdata/<appid>/ (Proton saves)
Per game prefixes holding Windows save paths. Native Linux saves follow each game's own home folder convention. Proton logs appear as ~/steam-<appid>.log with PROTON_LOG=1. MicroSD libraries share across installs.
Frequently asked questions
Where are my Steam Deck style saves on Bazzite?
Inside each game's compatdata prefix under ~/.local/share/Steam/steamapps, mirroring the Windows paths the game expects. Native games save in home folders like on any Linux distro. Back up the prefix or the game's folder before reinstalling.
Why won't games launch for a second user on Bazzite Deck?
Prefix files belong to the first user. Create a separate Steam library folder for the second account and symlink the shared parts like common game data. Console logs in ~/.local/share/Steam/logs name the offending prefix.
Notice an outdated path? Let us know.