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.
Start with the least destructive explanation
When Starfield progress appears missing, first verify the active PC location: 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.. Expected files/folders: *.sfs. Many apparent save failures are actually profile, storefront, path-redirection, or cloud-selection problems rather than damaged game data.
Preserve every surviving copy
For Steam/standard Windows, copy the full Saves folder. For Microsoft Store, back up the WGS container before attempting any extraction or storefront migration. Before renaming, moving, replacing, or opening candidate backups, copy them outside the live directory. Do not use the only surviving file as the test specimen for repair or editing.
Check launcher and cloud state
Storefront context: 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. Cloud notes: Steam Cloud and Xbox Cloud are documented. The Documents folder may also be synchronized by OneDrive when Windows folder backup is enabled. A sync client can reintroduce an older or newer version after a manual restore, so recovery work should keep local and cloud copies conceptually separate until the wanted progress is confirmed.
Use format and compatibility clues
The standard PC save files use the .sfs extension. Microsoft Store/Xbox app saves use the Windows Gaming Services (WGS) container instead of the same visible-file layout as the standard Documents save folder. 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 the file exists but is ignored, compare the complete directory structure, slot/profile naming, game edition, mods/DLC, and any companion metadata. Do not assume an extension change or generic checksum tool can repair a game-specific container.
Game-specific troubleshooting
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. If a known-good backup works, preserve it and create a fresh in-game save before further experiments. If no copy works, prefer read-only inspection and source-backed game-specific tooling over repeated writes.
Verification context: Windows, Steam, Microsoft Store, Steam Play, and cloud locations were reviewed against current PCGamingWiki coverage for Starfield.