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.
Known The Elder Scrolls V: Skyrim Special Edition save-file structure
The researched filename or folder pattern is *.ess
*.skse (when created by SKSE). File-extension context: .ess, .skse The documented format notes are: 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.
Why an extension is not enough
A save filename can identify a likely container, but it does not prove the internal schema, game version, checksum rules, encryption state, or editability. Original Skyrim saves can sometimes be used by Special Edition, but modded saves may fail when required plugins are missing or incompatible. SaveEditor therefore separates file identification from Tool compatibility and only labels a game-specific Tool Verified when its exact profile/version evidence passes the runtime gate.
Where the format is stored
PC save locations: 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/. Storefront 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. This matters because two releases can use different containers or companion files even when the visible slot name is similar.
Back up before inspecting or editing
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. A read-only viewer is lower risk than a writer, but the live save should still be copied first. Cloud context also matters: Steam Cloud, GOG Galaxy, Epic/Xbox cloud support, and optional OneDrive Documents backup can all affect which copy is restored. Keep the original bytes available so any experiment can be reversed without relying on a cloud service or automatic backup.
What this reference does not claim
This page does not infer an undocumented checksum algorithm, encryption key, compression layer, or cross-store conversion from the file extension. Troubleshooting evidence: 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. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.
Verification context: Steam/GOG save paths, original-to-Special-Edition compatibility note, cloud support, and Steam Play behavior were reviewed against current PCGamingWiki coverage.