Site snapshots and administrator-assisted recovery

Documentation / Saving, recovery, and troubleshooting

A site snapshot captures wider site JSON for recovery. It is different from a page backup, editor cloud draft, custom-design draft, or shell revision. Use the narrowest recovery that covers the incident; restoring an entire site can reverse unrelated changes made after the snapshot.

Find available snapshots

An authorized super administrator can open Super Admin > Sites, edit the intended site, and select Snapshot. The panel provides a Snapshot creation action and lists saved captures with their dates, file counts, and locations. It does not provide a general one-click restore button.

The panel identifies whether storage is local or R2. Production snapshots are stored within the website's workspace storage. Local snapshots concern local files; they are not automatically uploaded to production.

Understand the capture

The production service copies site content JSON and records a manifest. Local capture recursively copies JSON files. These are content captures, not backups of every external asset, hosting setting, DNS record, credential, or vendor account. Keep original media and infrastructure recovery arrangements separately.

Do not infer that a scheduled backup exists or is recent merely because the snapshot interface exists. Confirm the actual stored captures, their completeness, and applicable retention.

Request a reviewed recovery

Give the administrator the website ID, incident time, affected resources, and the desired recovery point. Ask for an inventory of what the proposed restore would overwrite and preserve. Have the current state captured before a wider reversal where appropriate.

Approve the exact production mutation separately. Do not run broad local-to-production sync commands as a shortcut. After recovery, check pages, navigation roots, templates, legal settings, translations, and active shared design, plus media references and visitor access.

If a snapshot is incomplete or absent, preserve remaining history and assess other retained backups. See saving and recovery and site administration.