A Sons of the Forest save is a folder of coordinated state files. Copy the whole slot directory and identify whether it is SinglePlayer or Multiplayer before any manual restore.
Known Sons of the Forest save-file structure
The researched filename or folder pattern is SinglePlayer/Multiplayer slot directories containing JSON/binary state records. File-extension context: No single extension is sufficient to identify every relevant save record. The documented format notes are: Sons of the Forest uses account-scoped LocalLow save directories with separate single-player and multiplayer branches. Preserve a complete slot folder so linked state records stay consistent.
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. 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. 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: %USERPROFILE%AppDataLocalLowEndnightSonsOfTheForestSaves<account-id>. Storefront context: Steam. The active Steam installation determines which local profile and cloud copy can overwrite the save. Identify the storefront and account before restoring files. 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
Close Sons of the Forest, 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. 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 can synchronize local saves; co-op host data is the authoritative persistent world copy. 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: 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. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.
Verification context: Windows save location, file-boundary, launcher/cloud, and backup notes were reviewed against the linked game-specific references for Sons of the Forest. 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 Sons of the Forest: Windows: %USERPROFILE%AppDataLocalLowEndnightSonsOfTheForestSaves<account-id> The recorded file or folder pattern is SinglePlayer/Multiplayer slot directories containing JSON/binary state records. 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.