Yakuza: Like a Dragon separates PC save storage by storefront more clearly than many games: standard/Steam, GOG, and Microsoft Store each have different roots. That means a generic instruction such as “copy the Sega folder” is too broad. SaveEditor records the user-ID level and the GOG-specific suffix so a backup can be put back into the environment that created it. Microsoft Store remains a WGS container and is not described as file-compatible with the normal AppData layout.
Known Yakuza: Like a Dragon save-file structure
The researched filename or folder pattern is User-ID-specific save records inside the active storefront directory.. File-extension context: No single extension is sufficient to identify every relevant save record. The documented format notes are: Steam/standard Windows and GOG use separate Roaming AppData roots, while Microsoft Store uses WGS. The account-specific subfolder is part of the save location and should be preserved.
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. Cross-store copies are not guaranteed by identical game content. The WGS edition in particular should be treated as a separate container until a tested transfer workflow is available. 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/Windows: %APPDATA%SegaYakuzaLikeADragon<user-id> ; GOG: %APPDATA%SegaYakuzaLikeADragon_GOG<user-id> ; Microsoft Store: %LOCALAPPDATA%PackagesSEGAofAmericaInc.Yazawa_s751p9cej88mtSystemAppDatawgs<user-id>. Storefront context: Steam, GOG, Microsoft Store. GOG deliberately uses a different YakuzaLikeADragon_GOG root. Microsoft Store data is not a normal AppData file set. 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
Back up the complete storefront-specific user-ID folder. Do not flatten files from GOG and Steam into one Sega directory because each edition has its own expected root. 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, GOG Galaxy cloud, and Xbox Cloud are documented. 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 progress is missing, confirm the storefront and user ID first. Then check whether the launcher restored cloud data after the local folder was changed. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.
Verification context: Reviewed against current PCGamingWiki Yakuza: Like a Dragon save paths and cloud-sync table.