Where Are NINJA GAIDEN: Ragebound Save Files Located?
Ragebound stores saves and settings in LocalLow under The Game Kitchen, in per-store folders that keep Steam and GOG progress apart.
Last updated
The Game Kitchen put Ragebound's data under %USERPROFILE%\AppData\LocalLow\The Game Kitchen\NINJA GAIDEN Ragebound, which is standard for Unity and slightly awkward for anyone used to Documents. Inside, systems.bin holds options and bookkeeping, and the Savegames folder holds checkpoints and completion data.
Two copies can share the parent folder without sharing progress: the Steam build writes into SteamUser_<number>, the GOG build into GOGUser_<number>, each named with the account number. Steam Cloud and Xbox Cloud both pick the folder up, which makes moving PCs easy and running two machines at once slightly annoying.
Where NINJA GAIDEN: Ragebound stores this, by platform
%USERPROFILE%\AppData\LocalLow\The Game Kitchen\NINJA GAIDEN Ragebound
SteamUser_<number> and GOGUser_<number> keep the store copies separate inside this tree. The Savegames folder and the .bin files are the full picture; back the whole folder up rather than single files.
~/.local/share/Steam/steamapps/compatdata/2542120/pfx/drive_c/users/steamuser/AppData/LocalLow/The Game Kitchen/NINJA GAIDEN Ragebound
The Windows build through Proton on Linux and Steam Deck, inside the prefix for app ID 2542120. The game is a pixel-art action platformer, so it is a comfortable Deck title when you want it portable.
Frequently asked questions
Where is the save file for the Steam version of Ragebound?
In %USERPROFILE%\AppData\LocalLow\The Game Kitchen\NINJA GAIDEN Ragebound, under SteamUser_<your account number>. The Savegames folder and the .bin files next to it are the complete picture.
Can I move a Ragebound save from GOG to Steam?
Yes, the data is portable. Close both copies, copy the contents of GOGUser_<number> into SteamUser_<your Steam number>, and let the Steam copy sync to the cloud before launching the GOG version again.
Why are there two systems.bin files?
One sits at the root and covers the shared install; the copy inside the per-store folder travels with the cloud save. When restoring a backup, take the whole folder rather than picking files, or options and progress can disagree.
Notice an outdated path? Let us know.