Websites

Website version history: three layers of going back

Website version history is the list of earlier states of a site you can look at and bring back. It helps to know which layer you need: a restore in the builder for a change you regret, or a rollback of the live site to an earlier publish.

Create a website with OneCraftThe Versions list in the builder, the publish history in site settings, what Restore and rollback do, and how long earlier publishes last
The Versions card: v4 marked Live, v3 and v2 marked Earlier version with Restore buttons, and v1 marked Failed, each with its date and time
The Versions card in site settings, with sample versions: the live one, earlier ones you can restore, and a publish that failed.

Every change is a version

Every AI change is a commit with a message saying what it did, and Versions in the builder lists the newest 50. Preview pins the builder preview to an older version so you can look without changing anything. Restore makes that version the current site again as a new version and builds it, so nothing is lost, not even the change you are undoing.

Roll back a publish you regret

Every publish is kept as a version of the live site. Publish history in site settings lists them with their dates, marks the live one and leaves out failed publishes. Rolling back points the live site at that earlier publish straight away, without changing the site in the builder, so you can fix it calmly and publish again.

How long earlier versions last

When a new publish replaces the live version, the old one is retired. Its files are kept for 7 days after that, then deleted to save space; the row stays in the history as a record, but it can no longer be put back live. In practice that means you can always roll back the few publishes of the last week, which is when most mistakes are noticed.

The full history comes with the code

A site is a git repository written by the AI, so the history behind the builder's Versions list is real commits. The zip download holds the current version only, without the git folder, so if you want your own archive, download a zip after each important change and name it by date.

A habit that saves trouble

Publish in small steps rather than after a week of changes. A small publish is easy to check and easy to roll back. Before a big change, such as a new look or removing pages, publish the current state first so the last good version is the one just before the change.

How it works, in three steps

  1. Step 1

    Open Versions

    In the builder open Versions to see every change, or Publish history in site settings to see every publish.

  2. Step 2

    Preview or restore

    Preview a version to look at it, Restore to make it current, or roll the live site back to an earlier publish.

  3. Step 3

    Fix and publish

    Ask the chat for the fix and publish again; the new publish becomes the live version.

Limits worth knowing

Questions people ask

Does rolling back a publish change the site in the builder?

No. A rollback changes what visitors see, by pointing the live site at the earlier publish's files. The site in the builder stays as it was, including the changes you regretted, so you can fix them before publishing again. To make the builder match the old version, restore that version in Versions.

Why can I not roll back an older publish?

Its files have been deleted. Publishes replaced more than 7 days ago keep their row in the history but lose their files, and a rollback is refused for them. A failed publish never had files, so it is left out of the list. Restoring an older version in the builder and publishing it works at any age.

Is there a history of every change, not just publishes?

Yes. Every chat turn that changed files is a version in the builder's Versions list, with the message the AI wrote for it. Preview pins any of them in the preview pane, and Restore brings one back as a new version. The newest 50 are listed.

Can I see what changed between versions?

Each version has a message describing the change, and the chat shows the files each turn changed, which you can open read only. There is no side by side comparison. Preview pins an older version in the builder so you can compare it with the current one by switching back and forth.

Does a restore count as a publish?

No. Restoring in the builder makes a new version and builds it for the preview for free, but nothing goes live until you press Publish. Rolling back in site settings changes the live site without a new build. Publishing is on the paid plans.

What happens to my site's data when I restore?

Nothing. Orders, bookings, members and posts live in the site's own database, not in the code, so a restore or rollback never changes them. If a restored version expects a table that a later change removed or altered, ask the chat to check the restored site against the database.

Can I take the whole site offline instead?

Yes. Take offline in the danger zone of site settings unpublishes the site, so its address stops serving pages, while the site in the builder and its versions are kept. Publish again to bring it back. That is useful for a seasonal business or while you rebuild the site.

Make your own website

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 website with OneCraft

Not ready to start? See the AI website builder page first.

Related pages

More finished work of this kind is on the website examples hub.

Sources

Written and checked by the OneCraft team. Last checked .