Fallout 4’s location is straightforward, but modded restoration is not. A base .fos file can reference content from plugins, and F4SE can add a paired cosave. The safest archive therefore includes the full save directory plus enough information to rebuild the mod environment. A failed load after moving PCs is not automatically evidence of file corruption; missing plugins, changed load order, or an absent cosave can be the real cause.
For this PC reference, the documented storage is Windows: %USERPROFILE%DocumentsMy GamesFallout4Saves | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/377160/pfx/. The known file or folder pattern is *.fos
*.f4se (when created by F4SE). Base Fallout 4 saves use .fos. F4SE-enabled installations can create companion .f4se cosaves; preserving only one side of a modded save may remove script-extender state.
Backup guidance: Copy the complete Saves directory. On F4SE setups, keep matching .fos and .f4se files together and record the installed mod/load-order state. Cloud behavior depends on storefront. OneDrive may also synchronize the Documents tree if Windows folder backup is enabled. Launcher and cloud context matters because The standard Documents path is the primary Windows reference. Microsoft Store packaging can differ, so locate the active edition before restoring a file.
Compatibility and recovery should stay conservative. A clean base-game save and a heavily modded save have very different restoration requirements even if both use .fos. If the expected progress is not visible, If an apparently valid save crashes on load after migration, verify missing plugins and script-extender dependencies before replacing more files. Also check whether Documents is redirected by OneDrive. SaveEditor.com only labels a game-specific editor as available when a separate linked Tool has a verified operational runtime; this reference page by itself is not an editor claim.