Враћање резервне копије

Restoring a whole site

Sites → your site → Backups, pick the point in time, and confirm. The restore replaces the site's files and its database with the contents of that backup.

⚠️ A restore overwrites what is there now. Anything created since the backup — orders, comments, uploads, posts — is gone once it completes. If the site is a shop, read the next section before you restore.

Restoring one file instead

Most "I need a restore" moments are really one broken file: a theme edit, a bad plugin update, a deleted image. Open a backup and download the single file rather than rolling the whole site back. It takes a minute and costs you nothing else.

Testing a restore without risking the live site

A backup restores over the site it belongs to — there is no restoring one into a staging copy. To check what a backup holds before you roll the live site back, open it and download the files you care about first. To rehearse a risky change instead, make a staging copy (Sites → your site → Staging), try the change there, and keep the backup as your way back.

How far back you can go

Your plan's retention window is shown on the Backups screen. Backups run daily, and a manual backup can be taken at any time — take one before a big plugin or theme update; it is the cheapest insurance there is.

If a restore fails

It leaves the site as it was rather than half-restored. Open a ticket with the backup's timestamp and we will look at that specific one.