God of War 3 Remastered PC Save Location and Transfer

Saves, settings, logs and cache are not the same files

With a custom Saves folder, the import destination is <custom folder>\savedata\1\<CUSA>\, and the run log follows that selected root. Use the launcher’s actual selected path rather than moving files into the default directory while the game reads a different one.

Default locations and the custom-root rule

On a narrow screen, scroll the table horizontally to read every column.

Sources: Project README · Importing shadPS4 saves · Project README · Settings · Project README · Linux AppImage

Back up before transfer or rollback

Close the game and shadPS4 before copying data. Make a separate copy of both source and destination save roots. For a Windows package update, preserve the whole user directory rather than only one visible slot, and keep gow3.ini and launcher preferences if you need the same configuration. Store your manual backup outside a directory you plan to replace.

The launcher backs up saves before each start. The checked launcher source exposes Game → Save backups, Refresh and Restore, with a confirmation before replacing current saves and a safety copy of current saves. A separate manual backup remains useful when changing directories or evaluating another package.

Sources: Project README · What works · Project README · Importing shadPS4 saves · 2.4.1 source · Launcher settings and save restore

Import a same-title-ID shadPS4 save

1. Close both programs and preserve both roots

   Close the port and shadPS4. Keep separate original copies of both save folders before changing the destination.

2. Locate the matching source title

   Older shadPS4: user\savedata\1\CUSA01623\. Newer versions: home\<user-id>\savedata\CUSA01623\. Substitute your own matching title ID.

3. Use the port’s selected save root

   Default Windows example: C:\Games\gow3-windows\user\savedata\1\CUSA01623\. With a custom Saves root, append only savedata\1\CUSA01623\ to that root.

4. Copy individual slot folders

   Keep each slot’s name and game files. Do not add another nested CUSA01623 directory. Exclude the slot’s internal sce_sys folder from the game-save contents.

5. Keep metadata as sibling data

   Beside a slot, create <slot name>.sce_sys if needed. The source’s sce_sys\icon0.png can be copied there. Do not rename param.sfo to param.bin; their formats differ. Preserve an existing port param.bin.

6. Check Load Game before replacing originals

   Start the port and choose Load Game. A slot without port metadata can appear under its folder name; saving again in the port writes metadata and refreshes the information. Check the loaded progress before treating the copy as successful.

Source: Project README · Importing shadPS4 saves

If a slot is missing, test the directory without losing progress

The port displays at most 32 save entries. If a copied slot is missing from a long list, use a separate Saves folder containing only that slot under the correct savedata\1\<CUSA>\ hierarchy, with its sibling metadata folder. Keep the original root intact and restore the prior Saves-folder selection after testing.

For rollback, close the game, restore the original root or use the launcher’s selected backup, then reopen Load Game and check the expected progress. Disabling a cheat or changing the save path does not reverse progress already written to a slot. The cheat rollback notes explain that distinction.

RPCS3 progress is from the PS3 game and is not compatible with this import. The edition comparison explains why a matching game name is insufficient.

Sources: Project README · Importing shadPS4 saves · 2.4.1 source · Launcher settings and save restore