Version history

Before you start

• A site that is saved to the cloud

Every cloud-synced site keeps restore points. Some are taken for you as you work; others you create and name yourself before doing something you might want to undo.

Open them from the cloud status icon in the Studio topbar → Version history….

Automatic snapshots

Swebsy snapshots a cloud-synced project as it syncs, at most once every 15 minutes. The first cloud save always gets a restore point. After that, the cadence keeps recent history without turning every keystroke into stored data you pay for.

Automatic snapshots are listed by date and time, described as Auto-save #<revision>. The 10 most recent are kept; older ones are discarded.

Named checkpoints

A checkpoint is a restore point you create on purpose — “before the hero redesign”, “client-approved v1” — and it is not evicted by the automatic ones.

1. Open Version history… from the cloud status icon.

2. Type a name in the Name this checkpoint field (up to 100 characters).

3. Click New checkpoint.

Expected result

“Checkpoint saved” appears, and the new entry is listed with a blue Checkpoint tag and the name you gave it.

Checkpoints are created from the same dialog that lists the automatic snapshots.

Checkpoints ignore the 15-minute cadence — you can take one whenever you want. The 10 most recent checkpoints are kept, counted separately from the automatic ones, so a busy afternoon of autosaves can never push out a checkpoint you named.

Checkpoints do not wait for the autosave timer

A new checkpoint records the current cloud revision immediately. If that exact revision already has an automatic snapshot, Swebsy promotes it to a named checkpoint instead of storing the same revision twice.

Restoring

1. Open Version history….
2. Find the entry you want and click Restore.
3. Confirm.

Restoring is itself undoable

Swebsy snapshots your current state before it restores, so the version you were on appears in the list as a new entry. Restoring the wrong version is a two-click mistake to reverse, not a lost afternoon.

Images and files are pinned to the snapshot that uses them. An image you deleted from the project weeks ago is still there when you restore a version that used it — the restored page renders as it did, rather than coming back with broken images.

Pinned assets keep counting toward storage

Because those files are held for the snapshots that reference them, deleting an image from your project does not immediately reduce your storage. The space is released once every snapshot referencing it has aged out.

Version history vs. backups

They solve different problems and it is worth having both:

	Version history	Project backup
Needs a paid plan	Yes	No
Where it lives	Swebsy’s servers	A file you keep
Created	Automatically, plus your checkpoints	When you export one
Good for	Undoing recent work	Archiving, moving between accounts, keeping a copy Swebsy doesn’t hold

If a site matters, take a backup file at milestones too. Version history is bounded — 10 automatic and 10 named entries — so it is not a long-term archive.

Common issues

“No restore points yet” — the first cloud save normally creates one. Try Sync now, then reopen the list; if it is still empty, check the sync error shown by the cloud icon.

No “Version history…” in the menu — the site is not cloud-linked. Click Save to Cloud first.

Restore fails with an upgrade prompt — you can view history on a lapsed plan, but restoring needs an active subscription. See Plans & billing.

A checkpoint I made is gone — more than 10 checkpoints exist and it was the oldest. For anything you need to keep indefinitely, export a backup file.