Undo, autosave and version history
Undo keeps the latest 15 snapshots, autosave saves as you work, and Version history lets you save, compare and restore named copies of your site.
For the complete documentation index, see llms.txt. This page is also available as Markdown.
#Undo and redo
- Undo and Redo are buttons in the top bar, dimmed when there is nothing to undo or redo. CmdZ undoes, CmdShiftZ or CmdY redoes.
- The history keeps the latest 15 snapshots of your pages, and the current state is one of them. Older steps are dropped as you work.
- On a very large site the history also has a memory cap of 30 MB and may keep fewer than 15 snapshots, but never fewer than 2.
- One AI chat turn counts as one undo step, however many things it changed.
- Undo and redo clear the selection. They restore pages and also the Brand Kit: colours, fonts and favicon.
- CmdS shows a Saved message and adds an undo step. It is not a save.
#Autosave
The editor saves 800 milliseconds after you stop changing things. It saves to your browser's local storage and, when you are signed in, to your account. It also saves when you hide or close the tab.
| If a save fails you may see | What it means |
|---|---|
| "This site was changed in another tab or device since you opened it, so this tab stopped saving to avoid overwriting that. Reload to get the latest; your edit here is kept in Version history." | Another tab or device saved newer work. Reload to continue. Your edit is kept as an automatic version named "Kept from this tab (changed elsewhere)". |
| "This project was deleted from another tab or device, so this tab stopped saving it. Your edits here are only in this browser." | The project no longer exists on your account. |
This change couldn't be saved on this device (storage full). It will still sync to the cloud — don't close the tab until it does. | Browser storage is full. A signed-in site still syncs to your account. |
This site is too large to save in this browser, and you're not signed in — so there is no copy anywhere else. Claim it now to keep it. Closing this tab would lose it. | A guest site that does not fit in browser storage has no other copy. Sign up to keep it. |
Cloud save failed — your latest change may not appear on previews or other devices yet. Retrying on your next edit. | The account save failed once. The next edit tries again. |
- A site you started as a signed-out guest exists only on that device until you claim it.
- Publishing from a stale tab shows
This site was changed in another tab or device. Reload to get the latest before publishing — your edit here is kept in Version history.
#Version history
Open Version history in the icon rail, or choose it from the project menu or the settings cog menu. Versions belong to the site, so they are the same on every device you sign in on.
| Control | What it does |
|---|---|
| Name this version (optional) | A name of up to 80 characters. Press Enter or Save a version. Without a name it is called Version — <time> |
| Restore | Asks "Roll the site back to this version?" and puts the version back, with its colours, fonts and Brand Kit. UOVA first saves a Before restore version. The restore itself resets the editor's undo history, so CmdZ cannot reverse it. Restore the Before restore version instead |
| Changes | Compares that version with your site as it is now: pages, elements and words. It needs the account history, and a device-only list shows Comparing versions needs the cloud history — sign in to use it. |
| Rename | Click the name or the pencil. Enter saves and Esc cancels |
| Delete | Asks "Delete version?" first |
Each version shows a badge: Saved for versions you save, Auto for those UOVA makes, and Published for a kind that publishing does not currently create. A row also shows its age, its page count and the device it came from.
- The server keeps 50 versions per project. When the limit is reached, automatic versions are removed first, so a version you saved yourself is kept longest.
- UOVA makes automatic versions before a restore, and named "Unsynced copy from this device" or "Kept from this tab (changed elsewhere)" when it keeps an edit that could not be saved.
- An empty list reads "No versions yet" and says UOVA keeps one automatically before any restore.
- If the server cannot store versions, or you are signed out, the panel falls back to a list on this device and a banner says so. Versions saved on a device are moved to your account later, with a message such as "1 version from this device is now on your account".
- Restoring a version changes your editor, not the live site. Publish to put it live. Publishing does not save a version. See Versions and republishing.
#Common questions
Autosave runs shortly after each change. If you are signed out as a guest, the site is saved on this device only.
Not with undo, which keeps a short history and starts empty after a reload. Restore a saved version if you have one.
It only shows a Saved message and adds an undo step. Autosave does the saving.
It replaces the editor's pages with the version. UOVA saves your current state first as a Before restore version, so you can go back. Undo cannot do this, because a restore resets the undo history.