Skyrim Special Edition backups should include mod context, not just bytes. The base .ess file is the core save, but SKSE installations can add a matching .skse cosave and the save can reference plugins that are no longer installed. That means a technically intact file may still fail or behave differently on another setup. SaveEditor.com therefore treats the save file, its optional cosave, and the mod/load-order context as separate pieces of compatibility evidence.
Choose the correct backup boundary
For The Elder Scrolls V: Skyrim Special Edition, the researched PC save location is Windows: Steam: %USERPROFILE%DocumentsMy GamesSkyrim Special EditionSaves
GOG: %USERPROFILE%DocumentsMy GamesSkyrim Special Edition GOGSaves | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/489830/pfx/. The known save file or folder pattern is *.ess
*.skse (when created by SKSE). For an unmodded setup, back up the complete Saves folder. For SKSE/modded play, preserve matching .ess and .skse files plus a record of the mod list/load order. 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 Galaxy, Epic Games Launcher, Microsoft Store / Xbox app. Steam and GOG use differently named Documents folders. Microsoft Store packaging differs and should not be treated as the same path simply because the game title is identical.
Account for cloud saves
Steam Cloud, GOG Galaxy, Epic/Xbox cloud support, and optional OneDrive Documents backup can all affect which copy is restored. 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
Base saves use .ess. Modded installations using SKSE can create a paired .skse cosave with the same base name. Treat paired files as one restore set when the mod stack depends on them. Compatibility note: Original Skyrim saves can sometimes be used by Special Edition, but modded saves may fail when required plugins are missing or incompatible. 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
When a save fails after moving PCs, check the mod/plugin environment before assuming the .ess itself is corrupt. OneDrive can also redirect or synchronize the Documents folder unexpectedly. 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: Steam/GOG save paths, original-to-Special-Edition compatibility note, cloud support, and Steam Play behavior were reviewed against current PCGamingWiki coverage.