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.
Where Yakuza: Like a Dragon stores PC saves
The researched save-location boundary is Windows: Steam/Windows: %APPDATA%SegaYakuzaLikeADragon<user-id> ; GOG: %APPDATA%SegaYakuzaLikeADragon_GOG<user-id> ; Microsoft Store: %LOCALAPPDATA%PackagesSEGAofAmericaInc.Yazawa_s751p9cej88mtSystemAppDatawgs<user-id>. The known file or folder pattern is User-ID-specific save records inside the active storefront directory.. This is the practical starting point because launcher, profile, and storefront context can change which copy is active even when two folders look similar.
Storefront and profile differences
Documented launchers or storefronts: Steam, GOG, Microsoft Store. GOG deliberately uses a different YakuzaLikeADragon_GOG root. Microsoft Store data is not a normal AppData file set. When looking for a missing save, identify the executable/storefront you actually launched and the user/profile that created the progress before copying anything between directories.
Cloud synchronization
Steam Cloud, GOG Galaxy cloud, and Xbox Cloud are documented. A cloud service should be treated as another copy of the save, not as proof that the local folder is disposable. Before a manual restore, let synchronization finish, make an offline backup, and avoid starting the game while files are being replaced.
What the files represent
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. The current filename/folder evidence 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. A location guide does not claim that every file in the directory is safe to edit or that files from another storefront are automatically interchangeable.
If the save is not where expected
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. Also check redirected Documents folders, Steam Play prefixes, account IDs, and launcher-specific containers where applicable. Preserve every candidate copy before testing a restore so troubleshooting does not destroy the only surviving version.
Verification context: Reviewed against current PCGamingWiki Yakuza: Like a Dragon save paths and cloud-sync table.