Restore and download
A restore puts a site’s files and database back the way they were in a backup, in place. A download gives you the backup’s four files, to keep somewhere else or to restore by hand.

Restore a backup
Section titled “Restore a backup”- Open the site’s Backups tab, or find the backup under Backups → All backups.
- Choose Restore on the backup, then Restore in the dialog.
- Follow the job. The site is briefly stopped.
Restore appears on a complete backup whose files are on the site’s server. A remote only backup needs Fetch back first, as Offsite copies explains.
What a restore does
Section titled “What a restore does”The job checks the backup’s checksums, then takes a Before a restore backup of the site as it is now. If either step fails, nothing has changed and the site keeps running.
Then it stops the site and pauses the site’s FTP and SFTP logins. It replaces the database with the
backup’s and swaps in the files. A database added to the site is replaced too, and one deleted since
the backup is made again, unless another site has taken its name. One added since the backup stays as it is. The previous files stay next to the new ones, in
wordpress.pre-restore-<time>, for at least a day. A backup taken on another PHP version moves the
site back to that version, if the panel still offers it. A backup whose tables have another prefix
gives the site that prefix: that happens when a site restores a backup of a deleted site that had
the same name.
Last, it starts the site. Before that, it checks the PHP settings in the files that came back, because an old backup can hold lines PHP-FPM cannot use. See Change a PHP setting. If the site’s address changed since the backup, WordPress’s URLs are rewritten to the current one, and the site’s recipes run for the new address. A site that does not answer afterwards is a warning in the log, not a failed job.
A failure after the site was stopped leaves the site in Error. The job’s log then says where the previous files are.
On a PHP site, a restore rewrites no URLs and keeps the site’s web root. Its database is optional, so a restore does one of these:
| The backup | The site now | What happens |
|---|---|---|
| Has a database | Has one | The database is replaced, as above |
| Has a database | Has none | The database is made first, then filled. Its user gets a new password. Put it in the site’s config, from the Database tab |
| Has none | Has one | The database is left as it is |
What changes for logins and jobs
Section titled “What changes for logins and jobs”- WordPress accounts and their passwords are those in the backup.
- FTP and SFTP logins work again once the restore is over, and see the restored files.
- The site keeps its mail login: the panel writes the current one again.
- No other job runs for the site while the restore does, and its backups cannot be deleted meanwhile.
Download a backup
Section titled “Download a backup”Choose Download on a complete backup, then what to download. Each file is named after the site and the backup’s time, and streams from the server that keeps the backup.
| Choice | What you get |
|---|---|
| Everything | One .tar file that holds the four backup files. |
| Files | The site’s files, as files.tar.gz. They are its wordpress folder. |
| Database | The site’s own database, as one .sql.gz file. Import on a site’s Database tab takes it as it is. A backup of a site with no database has none. |
To restore a hosted site without the panel, follow Manual recovery without the panel.
Restore a site hosted elsewhere
Section titled “Restore a site hosted elsewhere”A site hosted elsewhere has no Restore. Put a backup back on its host by hand:
- Choose Download on the backup, then Files. Do it again for Database.
- Unpack the files. Copy what is in the
wordpressfolder over the site’s WordPress folder, by FTP or with the host’s file manager. - Import the database into the site’s database, with phpMyAdmin or with
mysql:
gunzip < shop-20261009-030000-database.sql.gz | mysql -u wp_user -p wp_databaseThe files hold the site’s wp-config.php, with the database settings it had at the time of the
backup. On a host where they changed since, keep the current wp-config.php. WPL7 Connect’s
settings are in the database, so the site stays connected after a restore.
A container app’s restore puts back its files, its databases and the image the backup was taken with. An image that left the server is pulled again by its digest. The app keeps its settings and secrets as they are now. A mount kept out of backups stays as it is.
On another image, the app runs as that image’s user, and its Deploys tab lists the restore. Automatic updates leave alone the image the restore went back from, until the tag names a newer one.
Limits
Section titled “Limits”- A restore replaces everything that changed since the backup: posts, orders, comments and uploads.
- A restore stops before it changes anything when a database in the backup is now another site’s, or sits on the server unused.
- A backup restores only onto the site of the same name, on the server that holds the backup. From another server, fetch it back from an offsite copy, or move the site back first.
- A PHP site’s backup restores only into a PHP site, and a WordPress site’s only into a WordPress site. A container app’s restores only into a container app.
- A container app’s backup of an uploaded image no longer on the server does not restore. Upload the image again first.
- A deleted site’s backup has no Restore. Create a site with the same name first.
- A site hosted elsewhere is restored by hand, as above.
- The panel’s own database is restored by hand, never from the panel.
- The files a restore set aside are deleted by the nightly housekeeping, a day or more later.
- An API key needs Manage access to restore, and Full access to download the panel’s own database.