Where Are Expedition 33 Save Files Located?
Where Expedition 33 keeps EXPEDITION saves and its Backup folder on PC, and how rollbacks actually work.
Last updated
Expedition 33 keeps saves in a Sandfall folder under AppData\Local, inside Saved\SaveGames and then a numbered account folder. Two files matter: EXPEDITION_0.sav (your run) and SavesContainer.sav (the index around it). Both must travel together for a restore to load.
The Backup subfolder beside them holds timestamped copies and is the real safety net: several disappearance reports end with a renamed backup file recovering the run. Treat Steam Cloud with suspicion here instead of trust, since an empty launch can push a blank save over a good one.
Where Clair Obscur: Expedition 33 stores this, by platform
%LOCALAPPDATA%\Sandfall\Saved\SaveGames\[AccountID]
The numbered folder is your account ID. Back up the whole numbered folder (live files plus Backup) with the game closed. Game Pass builds save in a KeplerInteractive package folder instead, with hashed filenames.
~/.steam/steam/steamapps/compatdata/1903340/pfx/drive_c/users/steamuser/AppData/Local/Sandfall/Saved/SaveGames
Proton path for app ID 1903340. The Steam root varies, so search under compatdata/1903340 for the Sandfall folder. Linux cloud conflicts follow the same empty overwrite pattern, so disable sync while repairing.
Frequently asked questions
My Expedition 33 save vanished. Can the Backup folder rescue it?
Copy a timestamped EXPEDITION_0 backup over the live EXPEDITION_0.sav, keeping SavesContainer.sav alongside it. Start a new game first so the Continue button exists, then swap the files with the game closed and load through Continue.
Why did Steam Cloud overwrite my good save with an empty one?
That overwrite is the known failure mode: launching a fresh session uploads an empty container to the cloud, destroying the good copy. Disable cloud sync before troubleshooting a missing save, and only re enable it after the local files load correctly.
Notice an outdated path? Let us know.