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.
Choose the correct backup boundary
For Starfield, the researched PC save location 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 save file or folder pattern is *.sfs. For Steam/standard Windows, copy the full Saves folder. For Microsoft Store, back up the WGS container before attempting any extraction or storefront migration. Copying the complete documented save boundary is safer than selecting one visually obvious file, because companion metadata, indexes, backups, or multiple slots can be required together.
Make an offline copy before changing anything
Close the game first, wait for the active launcher to finish writing, then copy the save data to a separate folder that the game and sync client do not watch. Label the copy with the game, storefront, profile, and date. Documented launcher 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.
Account for cloud saves
Steam Cloud and Xbox Cloud are documented. The Documents folder may also be synchronized by OneDrive when Windows folder backup is enabled. Before restoring an older backup, decide which copy should win. If the game or launcher starts while an older manual copy is in place, synchronization can replace it before you confirm that it works. Keep the untouched backup outside the live save path until the restored progress has been opened and saved normally.
Restore without changing format assumptions
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. Compatibility note: 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. Restore into the matching storefront/profile context whenever possible. Do not rename a save extension, move a folder into a different container type, or assume a console/mobile copy is equivalent unless a tested migration path specifically says so.
Recovery fallback
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 the restored copy fails, put the untouched original back first. Then compare location, account/profile, cloud state, and the full directory structure before trying a different backup. The objective is reversible recovery, not repeated destructive experiments on the only copy.
Verification context: Windows, Steam, Microsoft Store, Steam Play, and cloud locations were reviewed against current PCGamingWiki coverage for Starfield.