Persona 5 Royal is another title where the storefront determines the storage model. Steam keeps user-scoped files under the SEGA P5R directory, while the Microsoft Store/Xbox app build relies on WGS. A useful backup must therefore capture the correct container for the copy you actually play. SaveEditor.com does not present the existence of third-party conversion workflows as proof that every platform save is directly compatible; the Game Hub separates location facts from conversion claims.
Choose the correct backup boundary
For Persona 5 Royal, the researched PC save location is Windows: Steam: %APPDATA%SEGAP5RSteam<user-id>savedata
Microsoft Store: %LOCALAPPDATA%PackagesSEGAofAmericaInc.F0cb6b3aer_s751p9cej88mtSystemAppDatawgs<user-id> | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/1687950/pfx/. The known save file or folder pattern is Steam savedata directory records; Microsoft Store WGS container records. Copy the complete Steam savedata directory or the complete Microsoft Store WGS data for the active profile. Keep the original untouched before any cross-platform conversion experiment. Copying the complete documented save boundary is safer than selecting one visually obvious file, because companion metadata, indexes, backups, or multiple slots can be required together.
Make an offline copy before changing anything
Close the game first, wait for the active launcher to finish writing, then copy the save data to a separate folder that the game and sync client do not watch. Label the copy with the game, storefront, profile, and date. Documented launcher context: Steam, Microsoft Store / Xbox app. The Steam and Microsoft Store versions use different storage systems. Account/profile IDs are part of the path and should be preserved when documenting or restoring a backup.
Account for cloud saves
Steam Cloud and Xbox Cloud are documented for the corresponding storefronts. Before restoring an older backup, decide which copy should win. If the game or launcher starts while an older manual copy is in place, synchronization can replace it before you confirm that it works. Keep the untouched backup outside the live save path until the restored progress has been opened and saved normally.
Restore without changing format assumptions
Steam exposes a normal account-scoped savedata directory. The Microsoft Store build uses WGS. Decrypted PlayStation 4 saves have separate conversion considerations and are not treated as byte-compatible with the PC storefront containers. Compatibility note: Do not assume Steam, Microsoft Store, or decrypted PlayStation saves can be interchanged by filename. Conversion is a separate operation from backup. Restore into the matching storefront/profile context whenever possible. Do not rename a save extension, move a folder into a different container type, or assume a console/mobile copy is equivalent unless a tested migration path specifically says so.
Recovery fallback
If the game starts without expected system/save data, verify the storefront, active user ID, and cloud state before overwriting anything. Proton users should also use a current compatibility layer when diagnosing old save-creation issues. If the restored copy fails, put the untouched original back first. Then compare location, account/profile, cloud state, and the full directory structure before trying a different backup. The objective is reversible recovery, not repeated destructive experiments on the only copy.
Verification context: Storefront-specific PC paths, cloud support, and the documented note about decrypted PS4 conversion were reviewed against current PCGamingWiki coverage.