Backups & restore

Backups let you roll a site back to how it looked at an earlier point in time.

How backups are created

• Automatically, each time you publish. The backup captures the version that was live, so it is always a state you know worked.
• Automatically, before any restore — so restoring the wrong one is never the end of the story.
• By hand, whenever you like. In Backups, press Create Backup and give it a name. This one captures your current draft, which makes it the right move before a big experiment.

Restoring

In the editor, switch to Files in the header and open Backups (also reachable from Content → Files & backups). Backups are listed by date. Restoring copies the backup into your draft — review it in the editor, then publish to make it live.

Restoring replaces your current draft. A backup of that draft is taken first, so nothing is actually lost, but it is one extra step to undo.

Backup limits per plan

When you reach your plan's limit, the oldest backup makes room for the next new one. On Free, that means only the single most recent snapshot is kept — treat it as a safety net for the last publish, not as a history.

Downloading your site

Backups live inside Vashana. A download is the copy you keep yourself.

On the Creations list, press Download on any site. You get a zip containing your pages, your pictures — including the full-size originals — and the finished HTML. Open dist/index.html in a browser and the site works, with no Vashana involved.

You can put one back too: importing a zip replaces a creation's draft with its contents. Two things are deliberately not carried over, so an imported site cannot quietly act as someone else's:

• Store and analytics keys are left out. Reconnect them and the site picks up where it left off.
• Custom scripts are left out. Add them again in the editor, where they are checked against the allowed list.

Downloading and importing are on every plan, including Free.