ZED ZONE Save File Location: Where Saves Are Stored and How to Back Up

Where Are ZED ZONE Save Files Located on Windows?

Because ZED ZONE has no Steam Cloud, knowing the exact ZED ZONE save location is the difference between a five-minute fix and a lost 60-hour survivor. There are two paths worth checking on a Windows install, and you should confirm which one your setup actually uses before touching anything.

Path 1 — the Unity LocalLow folder (most commonly reported). Since Early Access, community reports consistently place saves here:

C:\Users\<YourName>\AppData\LocalLow\LevenLiu\ZEDZONE

This follows the standard Unity engine convention for per-user game data, and the LevenLiu folder matches solo developer Leven Liu’s name — a strong signal this is the genuine primary path. AppData is hidden by default; paste the path straight into the Explorer address bar, or enable View → Hidden items. The saves are not stored in an easily editable text format, so this folder is for backup and migration, not editing.

Path 2 — the Steam userdata branch. SteamDB’s file-system page for the game (appid 1211600) notes that no Steam Auto-Cloud is configured and that files may instead live under:

<SteamInstall>\userdata\<Steam3AccountID>\1211600\

Which branch holds your live progress can depend on how the 1.0 build routes its save calls, and the exact 1.0-era subfolder structure is community verification in progress — the developer has never published an official path, and the save system was reorganized as recently as the final beta. The safe method: search both locations for recently modified files while the game is closed, and treat whichever folder updates when you save in-game as the live one.

How Do Character Saves and World Saves Work in 1.0?

The 1.0 save system changed in a way that matters for every backup you make. The final pre-release beta, 0.9.99.9.7 (November 3, 2026), separated character saves from world saves. Your character file carries your backpack contents, equipped gear, attributes and skill unlocks, while the world file holds the island state — looted buildings, placed structures, vehicles and the passage of time.

This separation is also the plumbing behind 1.0 co-op: because your survivor is portable, you can bring your own character into a friend’s world instead of starting fresh. It has two practical consequences. First, you need to back up both halves or you will restore a mismatched pair. Second, mixing a new character with an old world — or vice versa — can produce strange results after major patches. The early 1.0 builds proved the risk: hotfix 1.0.5 specifically fixed multiplayer character progress rolling back, so keep snapshots from before long co-op sessions.

How Do I Back Up and Restore ZED ZONE Save Files?

The full routine takes under two minutes once you know the path. How often you repeat it depends on how you play: a daily snapshot is cheap insurance during an active build, while weekly is fine for relaxed runs — the one non-negotiable moment is before every major update, since 1.0-era patches can migrate your save forward automatically.

1. Close the game completely. ZED ZONE writes save data at rest points, and copying files while the game is running can capture a half-written state.
2. Copy the entire save directory, not individual files. Because character and world data are split across multiple files, grabbing one file by name is the most common way backups fail.
3. Zip it with a label. Name the archive something like zedzone-backup-1.0.11-world-char-2026-11-08.zip so you know exactly which game version and save pair it belongs to.
4. Store one copy off the PC. A USB stick or cloud drive counts; the same disk does not protect you from disk failure.
5. To restore, quit the game, delete or rename the current save directory, drop your backup folder in at the identical path, and relaunch. If the game shows no save after a restore, you almost always copied the folder one level too deep — the save directory itself must sit directly at the path above, not inside an extra wrapper folder.

The developer itself recommends manually backing up save files before testing major updates — sensible advice given the hotfix tempo of the 1.0 launch window, when eight patches landed within 48 hours. Our update tracker is the fastest way to see whether a new patch is save-critical.

How Do I Transfer Saves to Another PC or Roll Back a Bad Update?

Moving to a new machine is a straight copy: recreate the same folder path on the target PC (LocalLow or userdata, whichever your install uses), paste the directory, and launch. Because character and world saves are separate, you can also migrate only your survivor to join friends quickly — just copy the character files and let a new world generate around them. If you switch Steam accounts, note that multiplayer identity is tied to the account, even though the files themselves move freely.

Rolling back after a broken patch follows the restore routine above, with one addition: never restore an old world file onto a game build newer than the backup without checking patch notes first. A world saved under 1.0.11 opened under a future 1.1.x may be migrated forward automatically and irreversibly. Keep the pre-update snapshot untouched, copy it elsewhere, and experiment on the copy. If a rollback ever leaves your character stripped of gear, the built-in spawn console can replace lost items — see our console commands reference for the item ID table.

One last habit worth building: before every co-op session with strangers, back up. Guest actions in your world — intentional or not — are the most common way save states get scrambled, and the co-op multiplayer guide explains exactly how progression syncs between host and guests. And if you install mods from the Workshop, snapshot your saves first, since a removed mod can leave a world referencing content that no longer exists.