Go back to an earlier version
Every saved change creates a version. Learn how to open the history, restore an old version and what happens to the live site and to your data.
How versions work
The project saves a version with every change: a request the AI applied, an edit of yours, a restore and, in the visual editor, each publish. Versions are numbered, and the newest one is the current one.
Restoring never deletes anything: the version you pick comes back as a new version at the top of the list. If you change your mind, restore the one you had before. Restoring uses no credits.
In the visual editor
Open the history
Click the History icon at the top of the chat, press H or choose History in the project menu.
Find the version
The Version history panel lists versions from newest to oldest, with their source (AI builder, Manual edit, Restored or Published) and date. The newest one shows as Current.
Click Restore
The site in the editor goes back to that version right away.
In the chat itself, every applied request has a Restore to vN button, which takes the site back to how it was right after that request.
In code mode
Open the History tab
Find the version
Each one shows its number, its source (Starter, Converted from the template, AI, Edited, Imported, GitHub or Restored), a summary of what changed and the date. The list shows the 50 most recent versions.
Click Restore
The preview switches to that version.
You can also ask in the chat “go back to version 3”: instead of using the AI, the chat offers a free Restore version 3 button. And right after a change, Undo this change returns to the previous version; see Attachments and context.
The live site
Restoring changes the version you are working on, not the published site. To put the restored version live, publish again. In the visual editor, the publish panel says You have changes that aren't live yet. See Publish.
What about the site's data
In code projects, restoring brings back that version's code. The site's data, such as sign-ups, tasks and orders, doesn't go back with it and stays as it is. If the old version defines a field with a different type from what is already stored in the database, the restore is refused to protect the data.
Compare versions
There is no screen yet to compare two versions side by side. What exists today: in code mode, each AI reply lists the new, changed and deleted files, and the Code tab shows the lines of the last change; in the visual editor, a Plan mode proposal lists the changes before you apply them.
Frequently asked questions
Do I lose the newer versions when I restore an old one?
No. They stay in the history, and you can restore any of them later.
I restored, but the live site didn't change.
That's expected: the published site only changes when you publish again.
I got a warning about the data model when restoring.
The old version doesn't fit the data already saved, because a field would change type. Ask the AI to adjust the current version instead of restoring.
Are plan versions here too?
No. The Plan mode plan has its own versions, in the Plan tab. See Plan mode.
Related articles
Still need help?
Our team answers within one business day.