For New Vegas, the save file is only part of a reproducible modded setup. Back up the entire Saves folder and separately record the active mod list before changing load order or moving progress to another PC.
Choose the correct backup boundary
For Fallout: New Vegas, the researched PC save location is Windows: %USERPROFILE%DocumentsMy GamesFalloutNVSaves. The known save file or folder pattern is *.fos save files plus paired metadata/backup artifacts when present. Close Fallout: New Vegas, let the launcher finish any synchronization, then copy the complete documented save directory to a dated folder outside the live path. Preserve companion files rather than selecting only the newest-looking record. 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, GOG, Epic Games Store, Microsoft Store. The active Steam, GOG, Epic Games Store, Microsoft Store installation determines which local profile and cloud copy can overwrite the save. Identify the storefront and account before restoring files.
Account for cloud saves
Cloud support differs by storefront; keep an offline copy of the Saves folder and the mod/load-order context for modded games. 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
New Vegas uses Bethesda Gamebryo save records with the .fos extension. Mods, DLC, load order, and script state can be embedded in progress, so a byte-level file match does not guarantee a safe modded restore. Compatibility note: Treat saves as version-, storefront-, account-, and mod-sensitive unless the game or a separately verified migration workflow proves otherwise. A similar filename or extension is not evidence that two releases are interchangeable. 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 progress is missing after a restore, confirm the active Windows account, storefront/profile, cloud state, and exact directory first. Restore the untouched backup before experimenting with individual files or older autosaves. 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 save location, file-boundary, launcher/cloud, and backup notes were reviewed against the linked game-specific references for Fallout: New Vegas. This Game Hub is documentation only and does not claim a new game-specific Save Editor.
Recorded Phase 40 evidence boundary
This Phase 40 entry is grounded in the researched PC save boundary for Fallout: New Vegas: Windows: %USERPROFILE%DocumentsMy GamesFalloutNVSaves The recorded file or folder pattern is *.fos save files plus paired metadata/backup artifacts when present. These concrete identifiers are retained so backup, transfer, recovery, and editing preparation remain tied to the documented game/storefront context instead of a generic extension guess.