Degrees of Lewdity Save Editor

  • .save

Edit Degrees of Lewdity save files online. DoL is a Twine game, so its exported save is LZString-compressed story state — upload it to change money, stats and story flags in a tree.

The part people get stuck on is not the editing but getting the save out of the game at all: it lives in the browser until you export it. Once exported, everything the playthrough has set is in that one file, and this page is where you change it.

How to edit a Degrees of Lewdity 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 stat or flag you want to change.
  4. Download the edited save and import it back through the same Saves menu.

What you can change

  • Money and other numeric stats the story tracks
  • Skills, traits and progression counters
  • Story flags controlling scenes and events
  • Inventory and wardrobe entries

Where the saves are stored

Nothing lands on disk by itself. The game keeps its slots in browser storage, and exporting writes a copy — the slot you exported from stays where it was, so an export is a snapshot rather than a move. Importing the edited file back is a separate step in the same menu, and it does not overwrite the other slots.

What the format actually is

Inside the compressed blob is the SugarCube story state, and it identifies itself: the save carries the game id and a version marker alongside the variables the story has set. That marker is what a newer build looks at when it decides whether to accept a save, which is why an edit made under one release can be refused by the next.

Warning:The game is updated often and its save structure changes with it. A save edited under one version may not be accepted by a newer one, so keep the untouched original: the editor works on a copy and never overwrites your file.

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

Questions

Which slot should I export?

Export the slot you actually want to change, not the newest one. The exported file is a copy of that single slot, so if you export the wrong one you will edit a playthrough you did not mean to and wonder why nothing changed in game.

Will a long playthrough with a big save work?

Yes. Long playthroughs produce large saves, and text-heavy fields such as journal notes can carry awkward character data that breaks naive tools. Saves of exactly that kind are part of the test corpus, and the editor round-trips them.

The game updated — will my edited save still load?

Because the save records the version it was written by, a build newer than that version may refuse it. Keep the file you exported: the editor works on a copy and never touches your original, so a refused import costs you nothing but the edit.

Other formats