Also known as named snapshot · named version
A named, unchanging snapshot of your draft at a moment you choose — “Table read,” “Before studio notes.” Unlike autosave, it never quietly overwrites itself, so you can always return to exactly that version.
Treat a save point as a labeled moment you may need to defend later: before studio notes, after a table read, or right before a risky rewrite. Unlike a rolling autosave, the named snapshot stays put, so "the draft that still worked" remains findable on purpose instead of buried in a pile of filenames.
Restore is supported when you need that exact moment back on the draft line you are working on. The save point itself remains in history afterward. Do not expect restore to invent a new parallel document from history; restore returns that snapshot onto your working draft line so you can continue from there.
Name save points the way writers talk -- "Pre-notes," "Post table read" -- so collaborators can find them under pressure. On free plans, named save points are kept even when older automatic history ages out, which is why intentional labels beat hoping yesterday's autosave is still around when you need it.
Autosave tracks the latest state. A save point freezes a moment you named and never mutates it -- so the draft that worked before the rewrite stays findable on purpose.
Yes -- restore puts that named snapshot back onto the draft line you are working on. The save point itself stays in history so the named moment does not disappear.
Before risky rewrites, after table reads, before sharing with a room or exec, and anytime you might need to compare then versus now tomorrow.
Restore returns that snapshot to your working draft line. If you need a full parallel document, open a draft line for the experiment rather than treating restore as a fork.
