Skip to content

How a restore works, step by step

Up to date as of 20 November 2026

A restore puts a saved copy back where the live site runs. For a typical WordPress site, the handbook's order is to restore the files first, then restore or import the database.1

The steps below are general. Your host or platform may differ, so follow its own instructions for your account.

What happens, in order

A typical restore orderPick the right backup setPut the files backImport the databaseCheck the connection detailsOpen the site and look
Files go back first, then the database is imported.

First, choose a backup set. Files and database should match, ideally made around the same time.1 Check the dates before you start.

Next, put the files back. The cPanel documentation describes one manual route for a full backup. You uncompress the tar.gz file, take the files from the public_html folder inside it, and upload them to your account's public_html folder.2 A tar.gz is a bundle of files squeezed into one download.

Then import the database. An export file is just a file. Getting its contents back into MySQL or MariaDB is the import step.1 With phpMyAdmin's quick method, the handbook says the new database should have no tables.3

Check the connection. After a migration with changed database credentials, wp-config.php has to match them.1

Last, look at the site. Open the home page, a few inner pages and the login screen.

What can go wrong

Snag Why it happens
The restore tool refuses the file The file type doesn't match the tool. cPanel says its backup file's extension depends on the portion of the site you backed up.2
A full backup won't restore from the control panel cPanel says you can't automatically restore a full backup file there.2
Database login changed wp-config.php has to be updated to match.1
New host, no database user You need to recreate the database user and its matching password.3
Leftover tables get in the way The quick import expects a database with no tables.3

Full backups and where they restore

The handbook warns about one cPanel trap on the database side. It says not to generate a full backup for this job, because full backups are strictly for archival purposes and can't be restored via cPanel.3 Look for the database-only download instead.

cPanel's own page agrees that automatic restore of a full file is only in WHM, so you'd contact your hosting provider.2 That's why knowing which kind of file you hold matters. What a website backup contains sorts out the kinds.

Before you overwrite anything

A restore replaces what's there now. If the current site is broken but still holds something recent, copy it first, files and database. That's general advice rather than something from the handbook, but it costs little. Then you can go back if the restore doesn't help.

After a hack

If the site was hacked, a restore may bring the problem back along with the files. The sources saved for this site don't cover that case, so ask your host or a trained professional before you restore.

If it doesn't work

Stop and write down what you did and what the screen said. Then contact your host with the exact message. Don't try random fixes on the live site.

The surest way to meet these snags calmly is to practise. The page on practice restores explains how.

Sources used

  1. Backups – Advanced Administration Handbook, WordPress Developer Resources
  2. Backup Wizard, cPanel & WHM Documentation
  3. Backing Up Your Database – Advanced Administration Handbook, WordPress Developer Resources