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.
Identify the exact save you intend to edit
The researched Starfield 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.. Known file/folder pattern: *.sfs. 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. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
For Steam/standard Windows, copy the full Saves folder. For Microsoft Store, back up the WGS container before attempting any extraction or storefront migration. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam Cloud and Xbox Cloud are documented. The Documents folder may also be synchronized by OneDrive when Windows folder backup is enabled. If a launcher can synchronize the save, prevent it from silently replacing either the original or edited copy while testing.
Understand the format boundary
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. File-extension context: .sfs 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. These facts help identify the save but do not automatically reveal every field, checksum, encryption rule, or version-specific structure inside it.
Use only a Tool whose claim matches the file
Generic viewers and diff tools can inspect bytes without claiming game-specific semantics. A game-specific editor should be used only when its Tool page explicitly lists Starfield, a matching supported version/container, and a Verified operational runtime. A planned URL or Game Hub is not evidence that an editor exists.
Test the edited copy safely
Write to a new output file when the Tool supports it, keep the original backup, restore the edited copy into the correct profile/storefront location, and launch the game only after the file operation finishes. If the game rejects it, 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. Return to the untouched backup before trying another change.
Verification context: Windows, Steam, Microsoft Store, Steam Play, and cloud locations were reviewed against current PCGamingWiki coverage for Starfield.