Restore

Restore downloads an archive from your storage and writes it back onto the WordPress server. ConstellaWP only presigns URLs and tracks the job. The agent must report the restore capability (current ConstellaWP Agent). Older backups that only contain wp-content plus the database are flagged as partial.

Owners and admins start restore from the site Backups list. Members cannot.

What restore overwrites

A full restore replaces:

WordPress core, themes, plugins, and uploads
The entire database (posts, users, WooCommerce orders, and everything else created after the backup are lost)

The site is put in maintenance mode for the duration.

Partial (legacy agent) backups restore wp-content and the database only. Core files are left untouched.

Safety backup (recommended)

The confirmation dialog defaults to Create a safety backup first. ConstellaWP uploads a snapshot of the current site to your destination before anything is overwritten. Safety backups are tagged in the list and kept for 7 days.

If you turn the checkbox off, you must type the site domain to confirm. Without a safety backup, a restore that fails halfway can leave the site unusable with no automatic rollback.

Constraints

Restore is blocked while another backup or restore job is queued or running on that site.
The destination that holds the archive must still exist and accept downloads. If you deleted the destination in ConstellaWP, restore cannot presign a GET URL.
Download URLs for restore stay valid long enough for the safety backup step (about 2 hours), not the 15-minute window used for manual downloads.

After restore

Watch the job until success.
Load the front-end and wp-admin.
If you used a safety backup and the result is wrong, restore that safety backup the same way.
Flush caches (plugin cache and, if linked, hosting cache purge where supported).

Hosting-provider snapshots (cPanel lists, Cloudways) are not restored from this page. Use the host panel for those; ConstellaWP shows them as information only.