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.
Known Persona 5 Royal save-file structure
The researched filename or folder pattern is Steam savedata directory records; Microsoft Store WGS container records. File-extension context: No single extension is sufficient to identify every relevant save record. The documented format notes are: 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.
Why an extension is not enough
A save filename can identify a likely container, but it does not prove the internal schema, game version, checksum rules, encryption state, or editability. Do not assume Steam, Microsoft Store, or decrypted PlayStation saves can be interchanged by filename. Conversion is a separate operation from backup. SaveEditor therefore separates file identification from Tool compatibility and only labels a game-specific Tool Verified when its exact profile/version evidence passes the runtime gate.
Where the format is stored
PC save locations: 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/. Storefront 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. This matters because two releases can use different containers or companion files even when the visible slot name is similar.
Back up before inspecting or editing
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. A read-only viewer is lower risk than a writer, but the live save should still be copied first. Cloud context also matters: Steam Cloud and Xbox Cloud are documented for the corresponding storefronts. Keep the original bytes available so any experiment can be reversed without relying on a cloud service or automatic backup.
What this reference does not claim
This page does not infer an undocumented checksum algorithm, encryption key, compression layer, or cross-store conversion from the file extension. Troubleshooting evidence: 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. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.
Verification context: Storefront-specific PC paths, cloud support, and the documented note about decrypted PS4 conversion were reviewed against current PCGamingWiki coverage.