No Man’s Sky has evolved over many years, so older profile directories can contain naming conventions that differ from current saves. That makes destructive cleanup risky. Archive the whole NMS directory before renaming or moving anything, and keep Microsoft Store WGS data separate from normal desktop .hg files. A future game-specific tool should identify the exact generation and container before writing; Phase 23 only documents the storage and backup boundaries.
Which storefront context matters
Documented No Man's Sky PC launchers/storefronts: Steam, GOG Galaxy, Microsoft Store / Xbox app. Desktop storefront files and Microsoft WGS containers are different migration surfaces. Older installations can also contain legacy storage*.hg naming. The active storefront/account should be identified before any restore because cloud and local storage may not use the same path or container across editions.
Documented cloud behavior
Storefront cloud support can synchronize the same profile. Cross-platform/cross-save features should be treated as service workflows rather than proof that arbitrary local files are byte-compatible. Cloud synchronization is useful for continuity, but it can also turn a restore into a conflict-resolution event. Let synchronization settle before making a manual backup, and keep an offline copy outside any folder monitored by the launcher or operating-system sync service.
Local save roots still matter
The researched local save boundary is Windows: %APPDATA%HelloGamesNMS
Microsoft Store: %LOCALAPPDATA%PackagesHelloGames.NoMansSky_bs190hzg1sesySystemAppDatawgs | macOS: $HOME/Library/Application Support/HelloGames/NMS/ | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/275850/pfx/; the known file or folder pattern is save*.hg
mf_save*.hg (current/metadata family; older installs may contain storage*.hg names). A cloud-enabled game still has concrete local data involved in ordinary play, and that local context is what you need when identifying which copy was modified most recently.
Avoid accidental overwrite loops
Copy the entire NMS profile directory, including metadata companions, before editing or migrating. For Microsoft Store, preserve the WGS container separately. When restoring, close the game and launcher, preserve both the current local copy and the backup you want to test, then place the intended data in the matching profile/storefront location. Do not repeatedly open the game between different copies without noting which side the cloud client selected.
Compatibility and conflict checks
Older 2016/2017 file naming and current save naming can differ. Do not rename historical .hg files blindly without retaining the originals. If progress disappears or rolls back, If an older save is not listed, first preserve every .hg record and compare modification times. PCGamingWiki documents historical storage-to-save rename cases, but any rename attempt should be reversible. Resolve identity/path/cloud questions first. A cloud conflict is not proof that the save itself is corrupt, and a successful upload is not proof that files from another storefront are compatible.
Verification context: Windows/macOS/Microsoft Store/Steam Play locations and historical .hg naming notes were reviewed against current PCGamingWiki coverage.