Infinite Wealth uses its own LikeADragon8 directory, and that distinction matters when a player already has several Like a Dragon games installed. Backing up the wrong Sega subfolder is an easy mistake because the titles share publisher, engine lineage, and similar naming. SaveEditor therefore records the exact product root and the Steam user-ID layer. The Microsoft Store release is separated again through WGS, so this page treats it as a different storage container rather than promising drag-and-drop compatibility.
Identify the exact save you intend to edit
The researched Like a Dragon: Infinite Wealth PC save location is Windows: Steam: %APPDATA%SegaLikeADragon8Steam<user-id> ; Microsoft Store: %LOCALAPPDATA%PackagesSEGAofAmericaInc.ProjectElvis_s751p9cej88mtSystemAppDatawgs<user-id>. Known file/folder pattern: Steam save records beneath LikeADragon8Steam<user-id>; Microsoft Store data is WGS-contained.. Storefront context: Steam, Microsoft Store. Steam data is account-specific under the Steam subfolder. Microsoft Store uses a separate package/container identity. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
Back up the whole LikeADragon8 Steam user-ID folder or the full Microsoft WGS container. Keep a date and storefront label with the copy. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam Cloud and Xbox Cloud are documented for the matching editions. If a launcher can synchronize the save, prevent it from silently replacing either the original or edited copy while testing.
Understand the format boundary
Infinite Wealth uses a dedicated LikeADragon8 profile root for Steam. Microsoft Store again uses WGS, so store-to-store restoration is not merely a directory rename. File-extension context: No single extension is sufficient to identify every relevant save record. Compatibility note: Do not merge Infinite Wealth data with Yakuza: Like a Dragon directories; the games have different roots and data versions even though they share a series and engine lineage. 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 Like a Dragon: Infinite Wealth, 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 a backup is not detected, verify you restored it under LikeADragon8 rather than YakuzaLikeADragon and check cloud conflict dialogs before launching repeatedly. Return to the untouched backup before trying another change.
Verification context: Reviewed against current PCGamingWiki Infinite Wealth save-location/cloud data and current Steam community path references.