Azeroth Survivors save editor: edit a copy, keep your progress

Where is the Azeroth Survivors save editor?

The community browser editor is maintained by Shilen at yssadora.github.io/azeroth-survivors-editor. It reads an exported .sav, edits a copy and downloads another file. It is an unofficial editor, not a live cheat console, a cloud-save service or a tool operated by RadiantGames.

Start in the original game at Options → Saves → Export Save. Keep that untouched file separately before opening a copy in the editor. Importing back into the game replaces the whole destination save; it does not merge the new talents with progress you earned after exporting.

What has actually been checked?

On 1 November 2026 we checked editor v1.5.3 with its own example Warrior save: added one Improved Heroic Strike rank, exported the sealed .sav and loaded that exported file back into the editor. The rank and Talent XP remained visible. This proves that example’s editor round trip, not successful import or long-term persistence in the current game.

The original menu checked the same day was v0.135.1. We did not overwrite an existing game save to claim compatibility. The editor’s Armory describes 498 equipment IDs, while the current original Rogue screen showed a collection of 60 pieces for that class. Those observations are a reason to check current coverage, not proof that the editor understands every new item.

A backup-first editing workflow

1. Export from the original game immediately before editing. Put the untouched .sav in a dated backup folder.
2. Open a copy in the community editor. Confirm the expected class, character and talent information before changing anything.
3. Make one small change first. Leave the game-rule limit in place and avoid combining talent, equipment, zone and perk edits in the same compatibility test.
4. Export once and keep the modified file under a different name. Reopen it in the editor to confirm the intended values still appear.
5. Only if you accept replacing the destination progress, use the original game’s Import Save control. Read its confirmation before proceeding.

A newer game session may already have progressed beyond an older export. Always take a fresh backup, rather than repeatedly importing yesterday’s edited file.

Talents, equipment and zones are different records

The editor exposes talent ranks and XP, an equipment collection, zone progression and experimental perk-reset controls. Its own notice disables zone editing when that class has no initialized progression records. Start that class in the game and export again instead of treating a disabled control as a broken download.

For a first experiment, talent planning is easier to compare than several unrelated unlocks. Use the build overview to choose a route, then verify the live game’s prerequisite text. A point limit override in a utility does not mean the original game accepts that allocation.

After importing, check again after a run

First inspect the class, equipment and progression immediately after import. Export another file at that point, then compare again after a completed run and a normal return to the menu. A file that looks correct in an editor can still be rejected, superseded or not persisted by the game.

The maintainer reports one player’s edited save persisting in Chrome and the downloaded game but reverting in Firefox after a run. The underlying cause is unconfirmed. That report is neither a universal Firefox diagnosis nor a guarantee for Chrome. If values revert, stop making further edits, keep the files and restore your untouched backup through the game.

When the editor and game disagree

If import fails, check that the file came from the same original project and was not replaced by an HTML download page or an empty file. Renaming a file to .sav does not convert its format. Do not clear browser data as a first troubleshooting step: it may remove the very progress you want to preserve.

Use the original Saves panel’s available backups or your separate export for recovery. A RadiantGames favourite keeps this page’s address only. Return to save and restore help for the distinction between browser storage, exported files and a desktop installation.