Starfield has two PC storage models that should never be collapsed into one instruction. Standard PC/Steam saves are recognizable .sfs files, while the Microsoft Store/Xbox app build uses the Windows Gaming Services container. That distinction matters for backup, migration, and any future SaveEditor tool. If you use Steam, preserve the complete Starfield Saves directory and, when relevant, its Steam remote copy. If you use the Xbox app, preserve the WGS data first and do not rename opaque WGS files into .sfs files.
Which storefront context matters
Documented Starfield PC launchers/storefronts: Steam, Microsoft Store / Xbox app. Steam and Microsoft Store use materially different storage layouts. Treat WGS data as a separate container workflow instead of renaming files between storefronts. 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
Steam Cloud and Xbox Cloud are documented. The Documents folder may also be synchronized by OneDrive when Windows folder backup is enabled. 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: Standard Windows: %USERPROFILE%DocumentsMy GamesStarfieldSaves
Steam remote copy: <Steam-folder>userdata<user-id>1716740remote
Microsoft Store: %LOCALAPPDATA%PackagesBethesdaSoftworks.ProjectGold_3275kfvn8vcwcSystemAppDatawgs<user-id> | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/1716740/pfx/; Steam Cloud may also use the matching userdata/1716740 area.; the known file or folder pattern is *.sfs. 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
For Steam/standard Windows, copy the full Saves folder. For Microsoft Store, back up the WGS container before attempting any extraction or storefront migration. 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
A visible .sfs file from the standard PC layout is not the same thing as a Microsoft Store WGS container. Storefront conversion requires a purpose-built workflow rather than extension changes. If progress disappears or rolls back, If expected saves are not in Documents, identify the storefront first. OneDrive folder redirection and WGS storage are common reasons the obvious path does not match the active copy. 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, Steam, Microsoft Store, Steam Play, and cloud locations were reviewed against current PCGamingWiki coverage for Starfield.