Where Are Sins of a Solar Empire 2 Save Files Located?
Sins 2 versions saves by build number under AppData Local sins2, with settings JSON and replays beside them. Patches orphan old trees.
Last updated
Sins 2 files saves under build numbers, so patches orphan yesterday's folder by design. Each versioned child splits single and multiplayer saves with recordings in a separate tree. Settings JSON lives apart with bindings and mod flags.
That versioning explains most lost-save reports. Cloud mirrors the same fragile tree rather than healing it. Back up per build and confirm versions match before assuming anything transferred.
Where Sins of a Solar Empire 2 stores this, by platform
%LOCALAPPDATA%\sins2\saved_games
Versioned save folders per build with single and multiplayer branches inside. Patches orphan older trees, breaking both local and Cloud continuity. Copy the matching build child.
%LOCALAPPDATA%\sins2\settings\settings.json
Settings JSON with bindings and mod flags plus versions file beside it. Recordings branch separately for replays. Keep with the matching save build.
<SteamLibrary>/steamapps/compatdata/1575940/pfx/
Steam Play prefix for App ID 1575940. The sins2 tree mirrors inside the prefix drive. Build-version fragility applies identically on Deck and Linux.
Frequently asked questions
My Sins 2 saves vanished after a patch. Why?
Copy %LOCALAPPDATA%\sins2\saved_games with the build-numbered child matching your version plus the settings folder. Patches strand older build trees, which explains saves vanishing after updates. Cloud historically shares the same fragility.
Where is the Sins 2 settings file?
Edit settings.json with input bindings and mod flags beside it in the settings folder. Single and multiplayer saves branch per mode under each build number. Recordings keep their own tree for replays.
Do Steam and Epic share Sins 2 saves?
Through versioned folders that both stores share, with multiplayer across them supported. Cloud sync bugs trace to the same build-mismatch root. Manual copies need matching builds on both ends.
Notice an outdated path? Let us know.