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.
Identify the exact save you intend to edit
The researched Yakuza: Like a Dragon PC save location is Windows: Steam/Windows: %APPDATA%SegaYakuzaLikeADragon<user-id> ; GOG: %APPDATA%SegaYakuzaLikeADragon_GOG<user-id> ; Microsoft Store: %LOCALAPPDATA%PackagesSEGAofAmericaInc.Yazawa_s751p9cej88mtSystemAppDatawgs<user-id>. Known file/folder pattern: User-ID-specific save records inside the active storefront directory.. Storefront context: Steam, GOG, Microsoft Store. GOG deliberately uses a different YakuzaLikeADragon_GOG root. Microsoft Store data is not a normal AppData file set. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
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. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam Cloud, GOG Galaxy cloud, and Xbox Cloud are documented. If a launcher can synchronize the save, prevent it from silently replacing either the original or edited copy while testing.
Understand the format boundary
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. File-extension context: No single extension is sufficient to identify every relevant save record. Compatibility note: 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. These facts help identify the save but do not automatically reveal every field, checksum, encryption rule, or version-specific structure inside it.
Use only a Tool whose claim matches the file
Generic viewers and diff tools can inspect bytes without claiming game-specific semantics. A game-specific editor should be used only when its Tool page explicitly lists Yakuza: Like a Dragon, a matching supported version/container, and a Verified operational runtime. A planned URL or Game Hub is not evidence that an editor exists.
Test the edited copy safely
Write to a new output file when the Tool supports it, keep the original backup, restore the edited copy into the correct profile/storefront location, and launch the game only after the file operation finishes. If the game rejects it, 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. Return to the untouched backup before trying another change.
Verification context: Reviewed against current PCGamingWiki Yakuza: Like a Dragon save paths and cloud-sync table.