Skip to content
Game save workbench
Local-first tools No installation Support status shown
SAVEEDITOR.COM
Browse tools
DEVICE-LOCAL Favorites and recent pages stay in this browser.

Save Editors

Vampire Survivors Save Editor

Edit coins, run coins, and lifetime coins in the explicitly legacy 2022 SaveData.sav JSON family and recompute its SHA-256 checksum locally.

Vampire Survivors PC

01 / Tool workbench

Use the runtime only when it is actually ready.

The application shell fails closed. An input interface is not enabled merely because a WordPress Tool record exists; the declared engine must be registered in the current build.

Vampire Survivors Save Editor
BROWSER LOCAL

Checking whether the declared runtime module is loaded. No input has been processed.

Session change summary

No output has been built in this session.

What this game-specific editor changes

Edit coins, run coins, and lifetime coins in the explicitly legacy 2022 SaveData.sav JSON family and recompute its SHA-256 checksum locally.

Verified input boundary

The selected file must be UTF-8 JSON with the legacy Coins/RunCoins/LifetimeCoins/SelectedCharacter/SelectedStage arrays and a valid 64-hex checksum matching the documented canonical JSON formatting rule.

What is deliberately not claimed

Current post-2022 save containers are not inferred from the .sav extension. Unlocks, achievements, modern platform formats, Steam Cloud migration, and repair of an already-invalid checksum are not claimed.

Output

A separate canonicalized UTF-8 SaveData.sav JSON copy with the selected coin fields changed and a freshly computed lowercase SHA-256 checksum.

Instructions

Use only a legacy SaveData.sav from the documented family, keep a backup, select it locally, confirm character/stage evidence, edit coin values, and download the rebuilt copy.

Verification

Verified against the published legacy editor checksum routine and field model, with independent SHA-256 vectors, valid/invalid fixtures, checksum mutation tests, original immutability, and post-write reopen.

02 / Compatibility

Know the supported input before opening a file.

Compatibility fields are intentionally explicit. Missing values stay unclaimed rather than being filled with generic assumptions.

Accepted extensions

.sav

Platforms

PC

Supported versions / editions

Vampire Survivors legacy 2022 SaveData.sav JSON/checksum family.

Input constraints

The selected file must be UTF-8 JSON with the legacy Coins/RunCoins/LifetimeCoins/SelectedCharacter/SelectedStage arrays and a valid 64-hex checksum matching the documented canonical JSON formatting rule.

Known limitations

Current post-2022 save containers are not inferred from the .sav extension. Unlocks, achievements, modern platform formats, Steam Cloud migration, and repair of an already-invalid checksum are not claimed.

Output / result

A separate canonicalized UTF-8 SaveData.sav JSON copy with the selected coin fields changed and a freshly computed lowercase SHA-256 checksum.

03 / Instructions

Use a reversible workflow.

File-oriented workflows start with an untouched original. Tool-specific instructions add only details documented for this utility.

  1. 01Keep the original

    Preserve an untouched copy before creating or transforming binary output.

  2. 02Confirm scope

    Match the file size, format, platform, and version to the support information on this page.

  3. 03Process locally

    Use the runtime only when the page reports that its declared engine is loaded.

  4. 04Validate output

    Compare or test the result before replacing any working source file.

Tool-specific steps

Use only a legacy SaveData.sav from the documented family, keep a backup, select it locally, confirm character/stage evidence, edit coin values, and download the rebuilt copy.

04 / Privacy and processing

The processing mode is part of the product contract.

SaveEditor.com should state local processing only when the implementation truly keeps file contents in the browser. Server or hybrid processing must be disclosed just as clearly.

Declared mode

Browser local

Runtime state

Operational

Tool-specific privacy notes

The selected save is processed entirely in the browser after explicit selection. Phase 37 game profile and codec scripts contain no fetch, XMLHttpRequest, WebSocket, or sendBeacon calls. The original bytes are kept immutable; a separate output is produced only after exact profile matching and a successful post-write reopen.

05 / Troubleshooting

When a file is rejected, do not force it.

A rejection can indicate an unsupported size, format, version, platform, or byte sequence. Preserve the original and correct the input instead of bypassing validation.

Wrong file or size

Re-check the documented input type and browser size limit before retrying.

Unsupported format

A generic converter does not imply support for every game-specific container, signing scheme, or serialization format.

Source was modified

Return to the untouched source instead of repeatedly processing a damaged or partially transformed file.

Known Tool issues

A newer format, missing legacy keys, malformed JSON, or checksum mismatch is rejected. Renaming another .sav file does not bypass detection.

06 / Verification

Support claims should be traceable.

The verification date, method notes, and public references are kept separate from marketing language so compatibility can be reviewed over time.

Last verified2026-08-08
Profilevampire-survivors-legacy-json-v1

Method notes

Verified against the published legacy editor checksum routine and field model, with independent SHA-256 vectors, valid/invalid fixtures, checksum mutation tests, original immutability, and post-write reopen.

Public references

  1. https://github.com/benediktwerner/vampire-survivors-save-editor/blob/master/index.html

07 / FAQ

Questions to answer before editing.

These answers are generated from the Tool record and current runtime state rather than generic compatibility promises.

Is Vampire Survivors Save Editor ready to use?
The Tool record is verified and declares an operational runtime. The page enables its input controls only when the declared engine module is loaded in the current build.
Does processing stay in the browser?
Yes for this declared mode. The loaded runtime processes the explicit input in the browser; Tool-specific privacy notes describe the exact scope and limits.
Should I keep the original file?
Yes. Keep an untouched source file until any generated output has been validated.
What if my version is not listed?
Treat unlisted versions as unverified. Do not assume two releases use identical save layouts, checksums, signing, or serialization.

Related tools

Continue with the same tool family.

Only index-ready verified records from the same Tool Family are shown here.

Related guides

Read the guidance connected to this tool.

Only reviewed, index-ready Guides that explicitly reference this Tool are included.