Projects
Versions and history
Autosave, named snapshots, and why restoring an old version never destroys a newer one.
There are three separate mechanisms here, and it is worth knowing which one you are relying on.
| Mechanism | Scope | Survives a reload? |
|---|---|---|
| Undo / redo | The current editing session | No |
| Autosave | The live design | Yes |
| Versions | Named snapshots you create | Yes — indefinitely |
Autosave
Edits are persisted continuously as you work — there is no Save button to forget. When several people are in the same design, their edits merge rather than overwrite; see Real-time collaboration.
Saving a version
Press Ctrl / ⌘ + S in an editor, or use the versions panel, to freeze the current state under a name. Name it after the decision it represents — *"core moved north"* beats *"v3"* three weeks later.
Restoring is append-only
This is the most important property of the history, so it is worth stating plainly: restoring an old version does not delete anything. The restored state is added to the top of the history as a new entry. Everything that came after the version you restored is still in the list, and you can go straight back to it.
In other words, the history only ever grows. There is no sequence of restores that can lose a state you saved.
If someone else is in the design
A restore replaces what everybody sees. Collaborators in the same design at the time will be moved onto the restored state — tell them before you do it, rather than after.