Where Are Sinking City Save Files Located?
Sinking City saves under AppData Local TSCGame with a turbulent delisting history across App IDs. Match paths to your build.
Last updated
Sinking City carries publishing drama in its file paths. Delistings and returns split builds across App IDs with save breaks between some eras. Current trees consolidate under one root with Cloud status varying.
Match every path to the running build before copying. Config branches beside saves under the same game root. Historical IDs stay reference-only for all but archaeologists.
Where The Sinking City stores this, by platform
%LOCALAPPDATA%\TSCGame\Saved\SaveGames
Progress files under the consolidated game root with delisting splits across eras. Confirm App ID before restoring. Cloud status varies and needs client verification.
%LOCALAPPDATA%\TSCGame\Saved\Config\WindowsNoEditor
Engine options under the same TSCGame root. Keep with SaveGames on migration. Historical builds branch separately and stay incompatible.
<SteamLibrary>/steamapps/compatdata/750130/pfx/
Steam Play prefix for App ID 750130. The TSCGame tree mirrors inside the prefix drive. Era splits apply on every platform.
Frequently asked questions
How do I back up Sinking City saves?
Copy %LOCALAPPDATA%\TSCGame\Saved\SaveGames whole with the game closed, after confirming your App ID era. Delistings split builds across IDs with incompatible saves between some versions. Cloud status varies by era and needs client checks.
Why does Sinking City have two App IDs?
They cycled through disputes, removals and returns with a one-day historical build beside the primary ID. Saves broke compatibility across some transitions. Current builds consolidated under long-term support with protections removed.
Where is the Sinking City config folder?
Open the WindowsNoEditor config tree beside SaveGames under the same TSCGame root. Engine options live there per Unreal convention. Keep config with saves on every migration.
Notice an outdated path? Let us know.