Project P.I.T.T. Save File Location
Configuration-derived Windows, macOS and Linux save paths, Steam Cloud patterns, folder backup and cautious restore steps without promising save repair.
The current Steam cloud-save configuration points to a Godot user-data folder named Project P.I.T.T: under Roaming AppData on Windows, Application Support on macOS, and the XDG data directory on native Linux. These are configuration-derived paths, not a repair tool; back up the whole folder before attempting a restore.
Windows, macOS and Linux save folders
CONFIGURATION VERIFIED · NOT AN IN-GAME TEST. SteamDB exposes the Steam app's cloud configuration; Steamworks and Godot documentation explain its operating-system roots. The paths below are derived from those fields, not checked against three local game installations.
The configured folder ends in Project P.I.T.T, without an extra trailing period. If it does not exist, confirm the operating-system account and that the game has created a save. Do not create an empty replacement and assume it is your current save.
| System | Path | Root / override |
|---|---|---|
| Windows | %APPDATA%\Godot\app_userdata\Project P.I.T.T | WinAppDataRoaming |
| macOS | ~/Library/Application Support/Godot/app_userdata/Project P.I.T.T | MacAppSupport override |
| Linux (native) | $XDG_DATA_HOME/godot/app_userdata/Project P.I.T.T | LinuxXdgDataHome override; default ~/.local/share |
Sources: Steam app cloud-save configuration, mirrored by SteamDB ↗ · Steamworks — Auto-Cloud roots and overrides ↗ · Godot documentation — user data paths ↗
Opening the folder and Linux caveats
Windows: paste the Windows path into File Explorer's address bar. macOS: use Finder → Go → Go to Folder and paste the macOS path. Native Linux: if XDG_DATA_HOME is unset, use ~/.local/share/godot/app_userdata/Project P.I.T.T; if it is customized, use that data directory instead.
These Linux rules describe the native build. A forced Windows build under Proton can use a compatibility-prefix location; no exact Proton path was verified here. Do not confuse the Steam installation directory with the user-data directory.
Sources: Steam app cloud-save configuration, mirrored by SteamDB ↗ · Godot documentation — user data paths ↗
Steam Cloud save patterns
The exposed configuration matches the following six patterns. The wildcard entries describe file patterns, not a promise that every installation has exactly one save file. Configuration files can matter for your settings and controls, so a whole-folder backup is easier to audit than selecting one guessed filename.
- *.save
- *.save.bak
- profile.cfg
- settings.cfg
- keybindings.cfg
- locale.cfg
Sources: Steam app cloud-save configuration, mirrored by SteamDB ↗
Back up before experimenting
General safe procedure: exit the game, allow Steam Cloud to finish syncing, then copy the entire Project P.I.T.T folder to a separate dated backup outside the synchronized folder. Include .save, .save.bak and configuration files that exist. Keep the original folder unchanged.
Name the backup with the date and observed game build. Confirm the copy contains files before doing cleanup, testing a secret-route theory or trying a restore. A cloud copy is not a substitute for an independent backup if an unwanted change has already synchronized.
Cautious restore, not corruption repair
First make a second backup of the current state, even if it appears broken. Quit the game and Steam before copying back a known backup so neither is writing the same files. Restore only files you can identify as belonging to this game and keep both snapshots available.
When Steam reconnects, it may present a cloud conflict. Compare the known backup, timestamps and the progress you intend to keep; do not blindly choose the newest entry or overwrite the only surviving copy. If the conflict is unclear, cancel and preserve both copies.
A restore can return a known prior state; it cannot be promised to repair corruption or make an incompatible save work. If the restored save still fails, keep the backups and report the build, operating system and reproducible symptoms.
Primary source: Steam app cloud-save configuration, mirrored by SteamDB ↗. Scope: full game.
A source-check date is not an in-game test date. Historical fixes and community observations retain their stated scope.