AH Web Works

How to Restore a WordPress Site

How to Restore a WordPress Site: Database, cPanel, & Backup Options

—

by

Alec Holmes, Founder & Website Specialist
in

Losing your WordPress site can feel like losing years of work in an instant. A plugin update crashes everything, a theme tweak wipes your layout, or malware compromises your files. In those moments, panic is natural. But with the right knowledge, restoring your site is almost always possible, often in under an hour.

This master guide will walk you through every restore method, from the easiest one-click solutions on WordPress.com to the more advanced manual approaches using cPanel or a database-only backup. You’ll also learn how to completely delete and restore a site if it’s compromised, and how to prevent disaster by pairing backups with reliable restore tools.

Whether you’re a blogger, small business owner, or running a WooCommerce store, these steps will give you a roadmap back to a working website.

Quick Answer: The fastest way to restore a WordPress site is to use your host’s one-click restore tool or WordPress.com’s built-in backup restore. If you’re on cPanel, you’ll need to upload your WordPress files and import your database manually. If you only have a database backup, import it into a clean WordPress install and then reinstall your theme, plugins, and media.

Table of Contents:

  1. 1. Understanding Your Backup Options
    1. Comparison Table: Restore Methods at a Glance
  2. 2. How to Restore a WordPress Site from Database Backup
  3. 3. How to Delete and Restore a WordPress Site
  4. 4. How to Backup and Restore a WordPress Site
  5. 5. How to Restore a WordPress Site from cPanel
  6. 6. WordPress.com and Managed Hosting: One-Click Restore
  7. 7. After the Restore: Post-Recovery Checklist
  8. FAQ
  9. Final Thoughts


1. Understanding Your Backup Options

Restoration starts with knowing exactly what kind of backup you have. WordPress isn’t a single file, it’s a combination of a database (which holds content, users, and settings) and files (which hold your themes, plugins, and media). That means restoring a site usually involves putting these two pieces back together.

Backup types explained:

  • Full backup (database + files)
    • What it is: A complete snapshot of your site, often created by your host or a plugin.
    • Best for: Fastest restores, minimal risk.
    • Con: Can be large, sometimes missing if your host doesn’t include it by default.
  • Database-only backup
    • What it is: An .sql file with posts, pages, settings, and user accounts.
    • Best for: Salvaging content if files are gone.
    • Con: You’ll need to manually reinstall themes/plugins and reattach media.
  • Files-only backup
    • What it is: Theme, plugin, and upload folders without the database.
    • Best for: Developers who already have DB intact.
    • Con: Useless if you lose the database.
  • Plugin backups (Jetpack Backup, UpdraftPlus, BlogVault)
    • What it is: Cloud-stored, often one-click restore packages.
    • Best for: Beginners, business sites.
    • Con: Requires setup in advance.
  • Host snapshots
    • What it is: Daily/weekly restore points your hosting provider makes automatically.
    • Best for: Quick fixes, hacked sites.
    • Con: Limited retention, may not include yesterday’s changes.

      Pro tip: Always ask your host if they keep emergency snapshots. Many site owners don’t realize they have free backups available until it’s too late.


Comparison Table: Restore Methods at a Glance

MethodSkill LevelTime RequiredBest ForRisks
WordPress.com / One-clickBeginner5–10 minsWordPress.com, managed hostingFew — easiest, but depends on plan level
cPanel RestoreIntermediate30–60 minsShared hosting, VPS usersImport errors, wrong file overwrite
Database-only RestoreAdvanced1–2 hoursSaving content with only SQL fileMissing media, broken links, more manual
Delete & Restore FreshIntermediate1–2 hoursHacked or corrupted installsRisk of incomplete restore if backup weak
Plugin-based RestoreBeginner10–30 minsBloggers, SMB ownersMust have plugin pre-installed


2. How to Restore a WordPress Site from Database Backup

A database backup contains posts, pages, settings, users, and plugin configurations. But it doesn’t contain your theme, media, or plugin files. Think of it as the “brain” of your site without the “body.”

Detailed steps:

  1. Install fresh WordPress – Use Softaculous in cPanel or download from WordPress.org. Try to match the version of your backup for best compatibility.
  2. Create a new database – In cPanel, open MySQL Databases. Add a user, assign privileges.
  3. Import your SQL file – Open phpMyAdmin → select database → Import tab → choose .sql file. For large files, use BigDump script or WP-CLI (wp db import backup.sql).
  4. Update wp-config.php – Adjust DB_NAME, DB_USER, and DB_PASSWORD to match your new database.
  5. Reinstall theme/plugins – Download from WordPress.org or restore from your local files.
  6. Reconnect media – If you have a copy of uploads/, place it inside wp-content/uploads/. Otherwise, media entries may show as broken.

Troubleshooting:

  • If links show “404”: go to Settings → Permalinks → Save Changes.
  • If login fails: reset password via phpMyAdmin (wp_users table).
  • If SQL import times out: ask host to increase max_execution_time or import via SSH.

Real-world scenario: A blogger accidentally deleted their wp-content folder but still had their SQL dump. Using this method, they rebuilt the site with posts intact, just needing to replace images.


3. How to Delete and Restore a WordPress Site

Sometimes it’s not about fixing an error, it’s about starting fresh after a hack or corrupted installation. Deleting and restoring your site can be the cleanest route.

When to consider this:

  • Malware or backdoors installed.
  • Inability to log in or run updates.
  • Bloated site from years of experiments.

Expanded steps:

  1. Back up current DB if possible – Even a corrupted install may let you export content.
  2. Delete old files – In cPanel File Manager or FTP, remove everything inside /public_html.
  3. Install new WordPress – Use your host’s auto-installer or upload fresh core files.
  4. Import old database – If usable, connect via wp-config.php. If not, restore from a clean backup.
  5. Upload themes, plugins, uploads – Verify files are malware-free before restoring.
  6. Harden security – Update salts in wp-config.php, reset all passwords, install a firewall plugin.

Security tips after delete + restore:

  • Rotate SFTP, cPanel, and database passwords.
  • Run scans with Wordfence or Sucuri.
  • Enable two-factor authentication for admin logins.

This is the “burn it down and rebuild” option, but it ensures hidden backdoors don’t come back to haunt you.


4. How to Backup and Restore a WordPress Site

Restoration is only smooth if you have reliable backups. That’s why the best restore strategy begins long before disaster hits.

Plugin options:

  • Jetpack Backup – Real-time backups, one-click restore, cloud storage. Paid, but highly reliable.
  • UpdraftPlus – Free tier allows scheduled backups to Dropbox/Google Drive. Manual restore requires re-upload.
  • BlogVault – Includes staging environment, developer-friendly.

Restoring with Jetpack Backup:

  1. Log into your WordPress.com account.
  2. Navigate to Backups in your dashboard.
  3. Choose a restore point from the timeline.
  4. Click Restore → site rolls back automatically.

Restoring with UpdraftPlus:

  1. Go to Settings → UpdraftPlus Backups.
  2. Upload your backup zip files if necessary.
  3. Click Restore → select files + database.
  4. Confirm, wait for completion.

Pro tip: Always test your backups. Schedule a quarterly “mock restore” on a staging site to confirm everything works. Many site owners don’t discover their backups are corrupted until it’s too late.

how to recover wordpress site cpanel


5. How to Restore a WordPress Site from cPanel

Most shared hosting accounts use cPanel, making this a common recovery path.

Expanded process:

  1. Log in to cPanel. Go to File Manager → public_html.
  2. Upload your site files. Either drag-and-drop via File Manager or use FTP (FileZilla). FTP is slower but handles big transfers better.
  3. Import your database. In phpMyAdmin, select your DB, drop all tables, then import your .sql.
  4. Edit wp-config.php. Make sure the database name, user, and password match your setup.
  5. Test your site. Visit homepage and wp-admin.

Common errors:

  • White screen = PHP errors. Enable WP_DEBUG in wp-config.php.
  • “Error establishing database connection” = wrong DB user privileges. Grant ALL PRIVILEGES.
  • Large imports timing out = split .sql file or use command line (mysql -u user -p dbname < backup.sql).

This method feels technical, but it’s the most reliable option for people on shared hosting.


6. WordPress.com and Managed Hosting: One-Click Restore

If you’re on WordPress.com, Pressable, or another managed host, you have the luxury of one-click restore. This is the fastest and safest path for most users.

How it works on WordPress.com:

  1. Go to Tools → Activity Log.
  2. Scroll to the restore point before your issue.
  3. Click Restore to this point.
  4. Wait — site rolls back automatically.

Benefits of managed restore:

  • Restores files + database in sync.
  • No manual database imports.
  • Fewer technical errors.

Host comparison:

  • WordPress.com – Activity log timeline, single-click restore.
  • Pressable – Daily snapshots, selective restores, staging options.
  • SiteGround – Daily backups with restore tool.

Pro tip: Managed hosts often allow you to restore on a staging site first, so you can test before pushing live. This prevents downtime for customers.

For entrepreneurs and small businesses, paying for a managed host often pays for itself during the first crisis you avoid.


7. After the Restore: Post-Recovery Checklist

Your site is back, now it’s time to ensure it stays that way.

Expanded checklist:

  • Flush permalinks – Settings → Permalinks → Save.
  • Test key pages – Homepage, blog, contact form, checkout if eCommerce.
  • Check media files – Make sure images load. Regenerate thumbnails if broken.
  • Reset all passwords – WordPress admin, hosting, FTP.
  • Update salts – Refresh keys in wp-config.php with WordPress.org generator.
  • Update everything – WordPress core, themes, plugins.
  • Install monitoring – UptimeRobot, Jetpack Monitor, or host alerts.
  • Set up auto backups – Jetpack, BlogVault, or your host.

For WooCommerce stores, always place a test order after a restore to ensure checkout, payment gateways, and confirmation emails are functional.


FAQ

1. Can I restore a WordPress site without a backup?
Not fully. You may be able to recover posts using Google Cache or the Wayback Machine, and your host might have emergency snapshots, but a complete restore requires a real backup.

2. Will restoring overwrite my current content?
Yes. Restoring replaces your current database and files with the backup state. Always export your latest database first, so you don’t lose recent posts or orders.

3. What if I only have database access?
You can import the .sql file into a fresh WordPress install. Your posts and settings will return, but you’ll need to reinstall your theme, plugins, and reattach images.

4. How do I restore only a single post or page?
WordPress.com’s Jetpack Backup lets you roll back individual items. Otherwise, export the content from another site copy or manually copy it from a database dump.

5. How do I restore media files like images or PDFs?
If you still have your uploads/ folder, copy it back into wp-content/uploads/. Without it, the posts will still exist, but images will show as broken.

6. Can I restore my site to a different domain or hosting provider?
Yes. Import your database and files, then run a search-replace on URLs (using WP-CLI or a plugin like Better Search Replace). Update DNS to point the domain to the new host.

7. How long does a WordPress restore usually take?

  • One-click restore: 5–10 minutes.
  • cPanel restore: 30–60 minutes.
  • Database-only rebuild: 1–2 hours.
    Time depends on site size and backup method.

8. My site is hacked. Can I just restore from a backup?
Yes, but also take extra steps: delete all old files, reset passwords, update salts, and scan your database. Otherwise, hidden backdoors may reinfect your site.

9. Can I restore my site using FTP only?
Yes, but it’s slow. You’ll need to manually upload your files with FTP, then restore the database via phpMyAdmin or WP-CLI.

10. What’s the difference between restoring files and restoring the database?
Files handle your design, plugins, and uploads. The database stores your content and settings. Most restores require both.

11. My restore “worked,” but my site is blank. What now?
Check for PHP errors by enabling WP_DEBUG in wp-config.php. This often reveals missing plugins or theme files.

12. Can I restore a WooCommerce store without losing orders?
Only if you have a recent backup. If you restore from an older backup, you’ll lose orders placed after that date. Some plugins (like Jetpack Backup) support real-time backups that capture every order.

13. Do I need to restore WordPress core files too?
Usually not, you can always download fresh core files from WordPress.org. Just be sure to keep your wp-config.php and wp-content/ folder intact.

14. How do I test a restore without affecting my live site?
Use a staging environment (many managed hosts offer this). You can restore to staging, check everything, then push changes live.

15. What if my backup is too large to upload via phpMyAdmin?
Use WP-CLI (wp db import backup.sql) or ask your host to import via command line. Alternatively, split the SQL file into smaller parts.

16. Can I schedule automatic restores?
Not exactly, but you can schedule automatic backups. Some tools (like BlogVault) let you restore with one click on demand.

17. My permalinks don’t work after restoring. How do I fix them?
Log in → Settings → Permalinks → Save (without changing anything). This flushes rewrite rules.

18. Is there a way to confirm my backups actually work?
Yes, do a test restore on a local or staging site. A backup is only as good as its ability to be restored.


Final Thoughts

A broken WordPress site isn’t the end of the world. With the right approach, you can usually restore it faster than you think. The key is understanding what kind of backup you have and which restore method fits best.

If you’re serious about your site, especially if it drives your business, don’t gamble on manual backups. Platforms like WordPress.com and tools like Jetpack Backup provide real peace of mind with reliable, testable restores.

Remember: the best time to think about restoring is before you need to. Set up backups now, test them regularly, and you’ll never have to panic when something goes wrong.

👉 Want a hosting environment that makes restores effortless? Tap here to explore WordPress.com plans with built-in backup and restore


Internal Links

External Links

Comments

What do you think?