Documents
Undo changes in a document
Two things stop you losing work: an undo stack fifty steps deep, and a header that always tells you whether what is on screen has been saved. Both are worth understanding before you need them.

Fifty steps, and edits are grouped
The undo stack holds fifty entries. Changes that happen within half a second of each other are grouped into one entry, so dragging a block or typing a sentence is a single undo rather than forty. That is what makes undo useful: pressing it once takes back the thing you just did, not one keystroke of it.
What the save badge means
The header shows whether the document is saved or has unsaved changes. Saved means the current state is written down. Unsaved means it is not yet, and closing the tab would lose it. It is worth glancing at before you leave, because it is the only signal that matters.
Undo is per session
The stack lives in the editor while you have it open. It is not a history you can come back to tomorrow, and closing the document ends it. If you are about to try something drastic on a document you care about, the safe move is to duplicate it first rather than to rely on being able to step back later.
There is no version history for documents
This is worth stating plainly. Unlike forms and presentations, a document does not keep a list of published versions you can preview and restore. What you have is undo while you are working and the save state. Plan around that: keep a copy before a big rewrite.
How it works, in three steps
Step 1
Work normally
Related changes are grouped, so undo takes back an action rather than a keystroke.
Step 2
Watch the save badge
It is the only signal that tells you whether the current state is written down.
Step 3
Duplicate before a big rewrite
Undo is per session and there is no version history to restore from.
The full walkthrough with screenshots is in the guide Create a document with AI.
Limits worth knowing
- Fifty undo steps, with changes within half a second grouped into one.
- The undo stack is per editing session and ends when you close the document.
- Documents have no version history to preview or restore.
See it on a finished piece
Questions people ask
How many times can I undo?
Fifty steps, with rapid changes grouped into one, so it covers far more than fifty individual edits.
Can I restore yesterday’s version of a document?
No. Documents keep no version history. Undo works while you have the document open, so duplicate it before a big rewrite.
How do I know my work is saved?
The header shows the save state. If it says there are unsaved changes, they are not written down yet.
Make your own document
The button opens the generator with this use case already described. Change the wording to match yours, generate, then edit anything you like.
Create a document with OneCraftRelated pages
Tidy a document layout
Hand editing drifts. Each block is placed relative to the one above it, small errors are inherited, and after twenty edits the top of the document is on a rhythm and the bottom is not.
Numbered clauses in a document
Numbering is what makes an agreement usable. Without it nobody can point at anything, and every conversation about the contract becomes a conversation about which paragraph you both mean.
Document components
There are 45 block types. You will use about twelve of them regularly, and knowing which twelve is most of the difference between a document that reads as designed and one that reads as typed.
More finished work of this kind is on the document examples hub.


