Twine Save Editor

Twine and SugarCube games keep every variable your playthrough has set — money, stats, inventory, flags — inside the save you export from the game. Upload it, change what you need, and load the result back.

How to edit a Twine save

1. In the game, open the saves menu and export a save to disk.
2. Upload the exported file here.
3. Search for the variable or the current value and edit it.
4. Download the file and load it back through the same in-game saves menu.

What you can change

• Story variables the passage scripts set — money, stats, affection
• Inventory contents and item counts
• Chapter, day and passage progress
• Unlocked scenes, endings and journal entries

Where the saves are stored

There is usually no file until you make one: browser games keep their state in the browser local storage. The game saves menu is the only reliable way out — export to disk, edit, then import the edited file back in the same menu.

What the format actually is

A Twine save-to-disk file is the story state serialised to JSON and then LZString-compressed into base64 — which is why it looks like a wall of characters starting with "N4Ig" rather than anything readable. The editor decompresses it and shows the variable table as a tree, then recompresses on the way out. In SugarCube that state is a history rather than one snapshot: the first moment is stored whole, each later one only as what changed since, and loading rebuilds them and resumes at the moment you saved at. The values Quick edits offer are written into the moment the game reads them from.

Related guide: Which games and engines does Save Editor support?

Questions

Where is my Twine save? There is no file

Twine games run in the browser, so the state normally lives in browser storage rather than on disk. Use the game own save menu and pick the option that writes a file — usually called "Save to Disk" or "Export" — and edit that file.

I edited a value but nothing changed in the game. Why?

A SugarCube save keeps the recent moments of the story, and loading rebuilds them and resumes at the one you saved at. If a value changed again before you saved, the game reads that later copy, so an edit to the first one is overwritten on load. Quick edits write money, when the story calls it money, cash or gold, and the numbers and switches the game changed recently into the copy the game reads. The tree edits the file exactly as it is, so if a change made there does not show up in the game, the game may be reading a later copy of that value, or loading a different save than the one you edited.

Which Twine formats are supported?

The save-to-disk files produced by SugarCube-style games, which is what most long-form Twine games use, Degrees of Lewdity and Course of Temptation among them. The file is identified by its contents, so if yours opens, it works; if it does not, the upload is logged and counts towards building support.

Will it handle a big save from a long playthrough?

Yes — long-running games with very large save states are part of the test corpus, including saves that carry awkward text data the naive tools choke on. Size is not the limiting factor.