Menu
The editor
Undo and redo
How undo and redo work in the editor, what they cover, and why you should rely on checkpoints for safety.
| Action | Mac | Windows |
|---|---|---|
| Undo | Cmd+Z |
Ctrl+Z |
| Redo | Cmd+Shift+Z |
Ctrl+Shift+Z |
There are no undo or redo buttons in the top bar; use the keyboard. Some messages, such as the one after you delete an element or move a page, include an Undo button too.
After each undo or redo, a short message names what changed, for example Undid: … or Redid: ….
What undo covers
Undo steps back through changes you make yourself in the editor, such as:
- text, link and image edits on the canvas
- styling changes
- elements and sections you add, move or delete
- page moves, renames, deletes and publish-state changes
- component renames, moves and deletes
- site setting changes
The editor keeps your most recent 50 changes.
What undo doesn't cover
- The AI's work. Each AI request becomes a version in the AI panel. Step back through versions or click Reject there instead. See AI sessions: versions, Save and Reject.
- CMS items. The CMS has its own history. See History and restore.
- Text you're typing. While you're editing text on the canvas or typing in a field,
Cmd/Ctrl+Zundoes typing in that text, as usual.
Undo history doesn't last forever
Undo history is short-lived. It's cleared when your changes are saved into a version (for example when you send the AI a new request), when you restore a checkpoint, and when the editor restarts after going to sleep. Don't rely on undo to get back to something from earlier in the day.