Backups & maintenance · Guide
How to Restore WordPress From a cPanel Backup

Short answer
Open Files > Backup Wizard > Restore in cPanel, pick Home Directory to restore files or MySQL Databases to restore a database, upload the backup file, and click Upload. A full account backup cannot be restored through cPanel, so upload the file and ask your host to restore it. Take a fresh backup first.
Key takeaways
- A full account backup cannot be restored through the cPanel interface; your host must restore it.
- A Home Directory restore overwrites files but does not delete files added after the backup date.
- A database restore overwrites the whole database, so anything added after the backup date is lost.
- Once you click Upload in Backup Wizard, the restore starts at once with no further confirmation.
- A fresh backup of the live site is the only way to undo a restore that picks the wrong file.
- Clear every cache after a restore and check the site in a private window.
What can you restore from a cPanel backup?
A cPanel backup can restore your files, your database, or your email settings, but not always in one step.
cPanel offers two kinds of backup: a full account backup and partial backups. A full backup holds everything in the account: files, databases, email accounts, forwarders, filters, and settings. A partial backup holds one piece, such as the Home Directory, one MySQL database, or the email forwarders and filters.
The key limit is that a full backup cannot be restored through the cPanel interface.
Krystal's cPanel backup guide states this plainly: a full backup is for moving the account to another server or keeping a local copy, and restoring data into the account needs a partial backup instead.
The University of Illinois cPanel backup page says the same thing in its own words.
| Backup type | What it holds | Can you restore it in cPanel? |
|---|---|---|
| Full account backup | Files, databases, email, settings | No, your host must restore it |
| Home Directory | All account files | Yes, through Backup Wizard |
| MySQL database | One database as .sql.gz | Yes, through Backup Wizard |
| Email forwarders and filters | Forwarders and filters only | Yes, through Backup Wizard |
What do you need before you start?
Gather the backup file, the database name, and a fresh backup of the current site before you restore anything.
First, find the backup file you want to restore. A Home Directory backup is a .tar.gz file, and a database backup is a .sql.gz file. Check the file date in its name or in your download folder, so you restore the right day and not an older copy.
Second, find the database name. Open wp-config.php in your site root and read the DB_NAME value, or check cPanel > Databases > MySQL Databases for the list. You need the exact name when you restore the database, so write it down.
Third, take a fresh backup of the site as it stands now. A restore overwrites live data, and a fresh copy lets you undo the restore if you pick the wrong file.
HostDango's cPanel backup guide advises taking a fresh database backup first when the live site still works and you are restoring to fix one problem.
Finally, check your disk space. Krystal's cPanel backup guide notes that a backup can fail near or above quota because the temporary files cannot be written. Free space or ask your host to raise the limit before you start.
How do you restore your files with Backup Wizard?
Restore the Home Directory backup when files are missing, changed, or broken.
Follow these steps:
- Log in to cPanel and open Files > Backup Wizard.
- Click Restore.
- Click Home Directory.
- Click Choose File and pick the
.tar.gzbackup file from your computer. - Click Upload and wait for the upload to finish.
cPanel extracts the backup and writes the files back into the account.
HostDango's cPanel backup guide notes that the restore overwrites existing files with the backed-up versions, but it does not delete files that exist on the server and were not in the backup.
A file added after the backup date will still be there when the restore ends.
The Illinois cPanel backup page adds a warning worth reading: once you click Upload, there are no further confirmations, and the restore begins as soon as the upload completes. Double-check the file name before you click.
How do you restore your WordPress database?
Restore the database when posts, settings, or users are missing or wrong.
Follow these steps:
- Log in to cPanel and open Files > Backup Wizard.
- Click Restore.
- Click MySQL Databases.
- Click Choose File and pick the
.sql.gzfile for the right database. - Click Upload and wait for the upload to finish.
The database restore overwrites the existing database with the contents of the backup file, as HostDango's cPanel backup guide explains. Every post, comment, user, and setting returns to the state it had on the backup date. Anything added after that date is gone unless you saved it first.
Do not restore the database while logged-in users are editing the site. Their new posts and comments would be lost with the old data. Pick a quiet time, put the site in maintenance mode if you can, and tell editors to wait until you confirm the restore is done.
If the upload fails, check the file size against your host's upload limit. A large database may need to be split or restored by your host instead. Never edit the .sql file by hand unless you know the format, since one broken line can stop the whole import.
How do you restore a full account backup?
A full backup needs your host's help, because cPanel gives you no button for it.
Upload the full backup file, usually named like backup-username-date.tar.gz, to the home directory of the account. Then open a support ticket and ask the host to restore it.
Krystal's cPanel backup guide describes exactly this flow: upload the CPMove file to the root folder of the account and ask support to restore it.
Give support three facts in the ticket: the file name, the date of the backup, and whether you need the whole account or only the WordPress site.
A full restore replaces everything in the account, including email, so say clearly what you need back. Ask for a time window too, since the restore may take the site offline while it runs.
Some hosts offer their own backup tool, such as JetBackup, as an alternative to the cPanel restore. If your host lists one in cPanel, check its docs before you open a ticket, since it may let you restore the account yourself.
Our guide to cPanel backup vs plugin backup compares these options in more depth.
How do you check that the restore worked?
Check the front of the site, the admin area, and the database content before you call the job done.
First, load the home page in a private browser window and click through five pages, including one post, one page, and the contact page. Look for missing images, broken layouts, and error messages.
Clear the cache first if you use a caching plugin, since a cached copy can hide a broken restore.
Second, log in to Dashboard and check that your users, posts, and settings match the backup date. Open Tools > Site Health and read the status tab for errors. If the database restore went wrong, Site Health and the admin screens will usually show it at once.
Third, check the pieces the restore does not cover. A cPanel backup does not restore an external email service, a payment provider's settings, or files stored outside the account. Confirm those services still work by sending a test email and opening a checkout page.
If the site still shows errors, read our guide to restore a WordPress site from backup for plugin-based options. Keep notes on what you checked, so you can tell your host exactly what still fails if you need help.
How long does a restore take?
A small restore takes 15 to 30 minutes, while a large one can take an hour or more.
The upload sets the pace: a 50 MB backup uploads in minutes on a fast link, while a 5 GB backup can take an hour or more. The extraction and database import add time on top of that, and a large database imports far slower than a small one.
A full account restore by your host usually takes longer than a partial restore you run yourself.
Hosts queue restores with other tickets, so ask for an estimate in the ticket and plan the site to be offline during the window. Budget extra time to run the checks in the last section after the restore ends.
What mistakes should you avoid?
Restoring the wrong file is the most common mistake.
Backup files often share similar names, so read the date in the file name before you upload. Restoring last month's database over this week's posts wipes a month of work, and only the fresh backup you took first can undo it.
A second mistake is restoring only the files when the problem lives in the database, or only the database when files are missing.
Match the restore to the fault: broken theme files need a file restore, while missing posts need a database restore. When both are suspect, restore the files first, then the database, and check the site between the two steps.
A third mistake is skipping the fresh backup. HostDango's cPanel backup guide warns that a database restore overwrites the live database, so a fresh copy is the only way back if the restore makes things worse.
A fourth mistake is forgetting the cache. A cached copy of the broken site can make a good restore look broken, so clear every cache after the restore and check in a private window.
Test your backups on a schedule too, using our guide to test a WordPress backup, so the next restore is routine instead of a scramble.
Frequently asked questions
Can I restore a full cPanel backup by myself?
No, not through cPanel. The Backup Wizard can only restore partial backups: the Home Directory, a MySQL database, or email forwarders and filters. For a full account backup, upload the file to the home directory and open a support ticket asking your host to restore it, giving the file name and backup date.
Will restoring a backup delete my newer posts?
Restoring a database overwrites it fully, so posts, comments, and settings added after the backup date are lost. Restoring files overwrites files with the backed-up versions but leaves newer files in place. Take a fresh backup before you restore, so you can undo it if you pick the wrong file.
What file do I upload to restore my WordPress database?
Upload the .sql.gz file for the right database, made with Backup Wizard > Back Up > MySQL Databases. Find the database name in wp-config.php under DB_NAME, or in cPanel under Databases > MySQL Databases. The file name usually carries the database name and the backup date.
How do I know the restore worked?
Load the home page and five other pages in a private window, log in to the admin area, and check that users, posts, and settings match the backup date. Clear the cache first, since a cached copy can hide a broken restore. Also test email and checkout, which a cPanel backup does not cover.
How long does a cPanel restore take?
A small restore takes 15 to 30 minutes, while a large one can take an hour or more. The upload sets the pace, and a large database imports slower than a small one. A full account restore by your host usually takes longer, since hosts queue restores with other tickets.
Sources
- All about cPanel backup & restore Krystal Hosting Knowledge Base
- How to Create and Restore a Backup in cPanel HostDango
- cPanel, Backup and restore of your website University of Illinois Answers
- WordPress Housekeeping WordPress.org
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.


