Resonance: A Plague Tale Legacy Cloud Saves and Cross-Progression

Resonance: A Plague Tale Legacy is a single-player cinematic action game with a save system that splits cleanly by storefront. There is no cross-platform progression in the sense that A Plague Tale fans have asked for — a Steam save does not appear on PlayStation Plus, an Epic save does not appear on Steam, and a Microsoft Store save only crosses over to Xbox consoles through the Xbox Play Anywhere program. Sony does not participate in Play Anywhere. This page documents exactly which saves go where, where the save files live on Windows, and what to back up before you reformat. The crossplay page covers the multiplayer question; this page covers save transfer only.

The save data PCGamingWiki confirms is limited to a small set of files: profile data (settings, keybinds, accessibility), save slot data (chapter progress, inventory, collectibles), and a separate configuration file (ENGINESETTINGS) for advanced tweaks. Steam Cloud handles profile data and save slots on the Steam build. Microsoft Store’s Xbox Cloud handles them on the Xbox / Microsoft Store build. Epic Games Store syncs through Epic Cloud. PlayStation Plus syncs through PS Plus Cloud Storage. Each system is a separate pipe; nothing transfers automatically between pipes.

Save matrix by storefront

The matrix below documents what travels and what does not. “Yes” means the save transfers automatically when you sign in on the second platform; “No” means you start fresh with no transfer; “Manual” means you have to copy a file by hand.

From → To	Steam	Epic	Microsoft Store	Xbox console	PlayStation 5
Steam	Yes (Steam Cloud)	No	No	No	No
Epic Games Store	No	Yes (Epic Cloud)	No	No	No
Microsoft Store	No	No	Yes (Xbox Cloud)	Yes (Play Anywhere)	No
Xbox console	No	No	Yes (Play Anywhere)	Yes (Xbox Cloud)	No
PlayStation 5	No	No	No	No	Yes (PS Plus)

Play Anywhere is the only cross-storefront path that works at launch, and it only works between the Microsoft Store and Xbox consoles. Sony does not participate in Play Anywhere, so a PlayStation save cannot be picked up on Xbox and vice versa.

Resonance: A Plague Tale Legacy 4K gameplay walkthrough (save reference)

Where the save files live on Windows

PCGamingWiki documents the Windows save location. Steam and Microsoft Store builds use the same path. Epic Games Store uses a parallel Epic\Resonance A Plague Tale Legacy subfolder under %APPDATA%.

%APPDATA%\Resonance A Plague Tale Legacy\
├── ENGINESETTINGS        # configuration file (advanced tweaks)
├── SaveGames\            # campaign save slots
│   ├── slot_0.sav
│   ├── slot_1.sav
│   └── slot_2.sav
├── Profiles\             # player profile, settings, keybinds
└── Logs\                 # crash dumps (ignore for backups)

Back up the entire %APPDATA%\Resonance A Plague Tale Legacy folder before any of these:

• Reformatting the OS drive
• Switching from Steam to Microsoft Store or vice versa on the same Windows account
• Manually transferring the save between two Windows machines
• Troubleshooting a corrupted save

Steam Cloud automatically syncs save files when you close the game and have Steam Cloud enabled for Resonance. The Steam Cloud icon in the Steam library page shows the per-file sync status. The Steam Cloud guide explains the sync model.

Manual transfer between two Windows machines

If you want to copy your save from machine A to machine B without going through Steam Cloud, you can. Both machines need to be on the same Steam account.

1. On machine A: close the game. Copy %APPDATA%\Resonance A Plague Tale Legacy to a USB drive or external folder.
2. On machine B: close Steam entirely.
3. Paste the folder into the same %APPDATA% path on machine B.
4. Disable Steam Cloud sync for Resonance (right-click Resonance in Steam → Properties → General → uncheck “Keep game saves in the cloud for Resonance”).
5. Launch the game on machine B and verify the chapter progress.
6. Re-enable Steam Cloud sync if you want ongoing backup.

If you leave Steam Cloud enabled and the cloud version is newer than your local copy, Steam overwrites your local copy. Disable Steam Cloud before you paste to avoid losing progress.

Manual transfer between Steam and Microsoft Store on the same Windows account

This is the only cross-storefront transfer that works at the file level. Steam and Microsoft Store use the same %APPDATA%\Resonance A Plague Tale Legacy folder, so a copy paste can move save data between the two builds on the same machine.

1. On the Steam build: launch the game, save your slot, close the game.
2. Confirm the file exists at %APPDATA%\Resonance A Plague Tale Legacy\SaveGames\slot_0.sav.
3. Close Steam. Close the Microsoft Store version. Open File Explorer and copy the folder to a backup location.
4. Launch the Microsoft Store build. Sign in with the same Xbox account you want the save attached to.
5. Save a new slot (it overwrites nothing). Close the game.
6. Compare file timestamps. If the Steam copy is older than the Microsoft Store copy, you have lost progress by launching the second build. Restore from the backup.

If both stores are linked to the same Xbox Live account, the Microsoft Store build’s save will travel to your Xbox console via Play Anywhere automatically. The Steam save will not.

Microsoft Store to Xbox (Play Anywhere)

If you bought the Microsoft Store version of Resonance and you sign in to the same Xbox account on an Xbox Series X or Xbox Series S console, the save transfers automatically when the console version downloads. The Xbox Cloud handles the transfer. This is the only cross-device transfer that works without a manual file copy.

The Microsoft Store version of the game is the same price as Steam ($49.99). If you want to play on both PC and Xbox without buying the game twice, the Microsoft Store path is the one to take. If you already own the Steam version, the Steam Cloud stays on Steam.

What Cloud Saves do not do

Cloud saves do not transfer DLC unlocks. If you bought the Heritage Pack on Steam, the Microsoft Store and Xbox versions of the game will not see it. You have to buy the DLC separately on each storefront. The Heritage Pack is sold at the same price on every storefront.

Cloud saves do not transfer achievements or trophies. The 36 Steam achievements and 37 PS5 trophies (plus the PS5 platinum) are per-storefront counters. A Steam save that pops Like a Warrior does not push the achievement to the Xbox list.

Cloud saves do not transfer save files across different Xbox accounts. If you and a family member share an Xbox console, the cloud saves are tied to whichever Xbox Live account launched the game. Profile settings are per-account too.

What this looks like for the campaign

The campaign is short (11.5 hours main, 16.5 hours 100% per HowLongToBeat). Most players finish in a single sitting or two. The Trophy / Achievement list does not require multiple playthroughs, and the Like a Warrior math fits a single run. Cloud saves matter most for:

• A player who starts on PS5 and wants to finish on PC.
• A player who buys the game on Microsoft Store to get Play Anywhere access to Xbox.
• A player who reinstalls Windows and wants to recover progress without re-doing collectibles.
• A player who uses a Steam Deck and a desktop and wants the same save on both.

For all of these, the performance page covers the Steam Deck side, and the crossplay page covers the multiplayer question (which Cloud Saves does not).

What we will not pretend to know

There is no published API for save file inspection. There is no in-game “copy my save to USB” option. There is no official tool for converting saves between storefronts. The transfer methods above rely on Windows file paths and the documented Steam Cloud / Xbox Cloud / PS Plus behavior. If a future patch adds an in-game export, this page will be updated to match.

How this page connects to the rest of the wiki

• Crossplay — confirms there is no multiplayer at all, even though Cloud Saves partially bridges devices.
• Performance — Steam Deck and Game Pass PC notes, both of which interact with cloud saves.
• Best PC Settings — the ENGINESETTINGS file referenced in the backup path above.
• Launch Arguments — additional command-line flags that interact with cloud sync.
• Trophies — confirms cloud saves do not transfer achievements.
• Official Links — the storefront URLs for each build.