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.
Prepare the source PC
On the source system, identify the actual Starfield save root: 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 expected file/folder pattern is *.sfs. Close the game, let the active launcher finish writing and synchronizing, then make a complete offline copy rather than transferring a file that may still be open.
Preserve storefront and profile identity
Documented 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. A transfer between two PCs is simplest when both systems use the same storefront/account/profile context. If the destination uses a different store or container, treat that as a migration problem rather than an ordinary restore.
Move the complete save boundary
For Steam/standard Windows, copy the full Saves folder. For Microsoft Store, back up the WGS container before attempting any extraction or storefront migration. Put the copied data on the destination only after confirming the destination save path. If the game creates a new empty save first, keep that new folder as another backup so you can compare structures and revert.
Handle cloud sync deliberately
Steam Cloud and Xbox Cloud are documented. The Documents folder may also be synchronized by OneDrive when Windows folder backup is enabled. Decide whether the local transferred copy or cloud copy should be authoritative before launching the game. If possible, preserve both. After the transferred save loads correctly, make a fresh in-game save and let the launcher synchronize normally.
Check compatibility before blaming the transfer
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. If the destination does not see the transferred progress, 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. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Windows, Steam, Microsoft Store, Steam Play, and cloud locations were reviewed against current PCGamingWiki coverage for Starfield.