Backups

A backup is a point-in-time copy of a project's content and settings that you can go back to — before a redesign, a bulk edit or an assistant run. Backups live under Settings › Backups; the Modules page shows them as a built-in tile. They are part of the Tier 2 and Tier 3 plans, with no limit on how many you keep. On another plan the page explains the gate and links to Settings › Plan; backups taken earlier stay readable and deletable after a downgrade.

What a backup holds#

You choose the parts when you take a backup. Each is restored on its own:

All documents of a backup are read as of one moment (the time you started it), so the parts fit together. Files are copied once: a file that is already in an earlier backup of the project is not copied again, so a new backup adds only what changed.

What a backup never holds#

• Ledgers — orders, invoices, carts, stock, credits, payments and the records of installed modules (bookings, for example). A restore never touches them. Use Settings › Advanced › Export when you need an archive.
• The project's wiring — members, tokens, hooks, domains and hosting, installed modules, secrets (a restored service keeps its secret names, never values) and the backup schedule itself.
• Number series — invoice, order and proforma numbers never go back. They keep counting from where they are now.
• Derived data — search keys, the live addresses of documents, folder and form counters. They are rebuilt after a restore.

So a restore rewinds content and configuration, never who can access the project or how it is connected.

Taking a backup#

Create backup opens a dialog: a name (prefilled Backup {date}), an optional note (what is about to change), and the parts with an estimate of the documents and size each holds. Content can be narrowed to some collections and languages. Parts with personal data are marked. The backup runs in the background — the row appears as Waiting to start, shows its progress (Reading documents, Copying files, Finishing) and turns ready. You can leave the page meanwhile.

One backup or restore runs per project at a time; starting another while one runs says so.

The list#

A stat strip shows the number of backups, their total size, the last ready backup and the schedule. Each row shows its number (#n), name and note, its kind — Manual, Scheduled or Before restore —, the parts, the size, who started it (a member, Schedule, or Assistant · approved by …) and when. Filter by kind above the table. A Before restore backup is listed under the backup whose restore it guards.

• Pin a backup to keep it: the schedule never rotates a pinned backup out, and a multi-delete skips it.
• Rename, Browse, Restore… and Delete are in the row menu. Deleting removes the backup's archive for good, together with any stored file no remaining backup uses. A running backup cannot be deleted.

Nothing expires on its own: manual and pinned backups stay until you delete them. The page shows each backup's size and the total.

Downloading a backup#

Owners and admins can download any ready backup from its row menu (Download). The console packages it as one zip — the backup's documents and the files it holds — and opens the link when it is ready (a large media library can take a minute). The link is valid for 15 minutes. Uploading a downloaded backup back into a project is not available yet.

No automatic backups#

Backups are taken by hand only — with Create backup, or by the Assistant after you approve its proposal. There is no schedule (it was removed on 24 October 2026); backups made by the old schedule stay in the list as Scheduled until you delete them. Nothing is removed automatically.

Restoring#

Restore… on a ready backup opens a four-step dialog:

1. Parts — pick what to bring back; everything else in the project stays as it is. Each part has a mode:
   • Replace makes the part exactly as in the backup — documents created since are deleted.
   • Merge brings back missing and changed documents and deletes nothing. Customers and Form submissions restore by merge only, so nobody who registered after the backup is removed.
2. Preview — what would change, per part: Create, Update, Delete, Unchanged and Skipped, with the paths of each. Warnings appear when, for example, a language the backup has content in is no longer on the project, a schema changed since the backup while Web & design is not selected, the design system points at files you did not select, documents of modules that are not installed now would be skipped, or restoring Services moves their live version back. A pending large file upload blocks restoring Files until it finishes. A preview is valid for 15 minutes.
3. Confirm — type the backup's name. The dialog says that a backup of the current state is taken first.
4. Restore — the progress (Backup of the current state, Restoring documents, Finishing), then the result: created, updated and deleted counts.

What happens on the way:

• A backup of now is taken first — a Before restore backup of exactly the parts you restore. Undo restore on the result restores it.
• Only what differs is written. Unchanged documents are skipped. A document that changed between the preview and the restore is left as it is now and listed as a conflict — bring it back on its own from Browse.
• No side effects fire per document. Restored documents send no webhooks and no notification e-mails, write no history entries and never re-process orders. The website's caches are refreshed once at the end, and webhook subscribers receive one bulk event (hooks).
• Content of modules that are not installed now is skipped; documents of installed modules' collections are never deleted by Replace.
• If a restore stops part-way, the project is partly restored. Retry finishes it (documents already restored are skipped) and Undo restore goes back.

One document from a backup#

Browse opens a backup: pick a part, filter its paths, open a document. Its version in the backup is shown beside the live one, with the changed fields, and a state — Same as now, Changed since or Deleted since. Owners and admins can Restore this document (or Bring back this document when it was deleted). This takes no backup of the current state: a content document's current version is saved to its History first, so it can be brought back from there.

The History dialog of a content document links here: Older or deleted? Browse backups — the History keeps the last 20 saves for 90 days, backups keep what you keep.

The assistant's checkpoint#

Before a bulk change — many documents, a schema change, a design commit, a template every page uses — the Studio assistant may ask Back up before these changes? with the parts it would back up (you can change them). Back up and continue takes the backup (shown as Assistant · approved by you) and the assistant waits for it before writing; Continue without goes ahead, and the assistant does not ask again in that chat. Nothing is backed up without your click, and the assistant can never restore — undoing a change is yours, here. MCP clients get a createBackup tool that their own permission prompt approves.

Who can do what#

Space owners and admins are owners of every project in the space.

Where backups are stored#

In the platform's own backup storage in the EU (europe-west1), separate from the project's data — for a project in a space's own cloud too (Space cloud). Deleting a project deletes its backups.