How to Restore a WordPress Backup: A Step-by-Step Guide

Why Knowing How to Restore a WordPress Backup Matters

Backups are your safety net — but they only help if you know how to use them. Whether your site was hacked, a plugin update broke the layout, or you accidentally deleted something critical, the ability to restore a WordPress backup can mean the difference between five minutes of downtime and losing days of work.

Many site owners assume their hosting provider or backup plugin handles everything. That’s not always true. If you’ve never tested a restore, you’re gambling. The process itself is straightforward, but missing a single step — especially around the database — can lead to broken sites or lost data.

This guide covers the three most reliable methods for restoring a WordPress backup: using a plugin (the simplest route), via cPanel and phpMyAdmin (good for manual control), and through FTP (for emergencies). No fluff, just the steps you actually need.

What You Need Before You Restore

Before you start, gather these essentials. Trying to restore mid-crisis without preparation only adds stress.

• Your backup files — a zip of your WordPress files (wp-content, core files, etc.) plus a .sql database export. Verify these are not corrupted before you begin.
• Access to your hosting control panel — typically cPanel, with File Manager and phpMyAdmin enabled.
• Database credentials — your database name, username, password, and host. These are in your wp-config.php file.
• FTP client (optional) — FileZilla or similar, if you’re using the manual FTP method.
• A clean browser session — clear your cache before testing the restored site.

Checklist before you start:

• Backup files accessible and unzippable
• Your hosting account is active and has disk space
• You know your login credentials for WordPress admin
• You have a recent backup of the current state (just in case)

Method 1: Restoring a WordPress Backup Using a Plugin

This is the most beginner-friendly approach. Plugins like UpdraftPlus handle file extraction and database import automatically, reducing the chance of human error. The trade-off: you depend on the plugin working correctly and being compatible with your PHP version.

Step 1: Install and Activate the Backup Plugin

If you used UpdraftPlus to create the backup, install a fresh copy of the plugin on your site. Go to Plugins > Add New, search for “UpdraftPlus,” install, and activate. If your site is completely down, you can install the plugin by uploading the zip via FTP to /wp-content/plugins/ and then activating it from the database — but that’s more advanced. For most cases, start with a fresh install from the WordPress repository.

Once activated, navigate to Settings > UpdraftPlus Backups and click the Restore tab.

Step 2: Upload or Locate Your Backup Files

UpdraftPlus can re-upload backup zip files you have saved locally. Click the Upload backup files button (or similar, depending on the version) and select your backup zip. The plugin will detect and list the components inside the archive.

If your backup is stored on a remote service like Dropbox, Google Drive, or Amazon S3, you can reconnect that service under the Settings tab, then click Rescan remote storage. The plugin will pull the existing backup sets into the restore list.

Important: The backup file names must be exactly as the plugin created them. Renaming files can break the restore. If you only have a manually created zip, you’ll need Method 2 or 3 instead.

Step 3: Run the Restore Process

Once the backup set appears, click the blue Restore button next to it. A panel will ask which components to restore. By default, everything is selected — database, plugins, themes, uploads, and other content.

Watch for the database option. Restoring the database will overwrite your current posts, pages, users, and settings. If you only need to restore files, uncheck the database box. If you want a full rollback, leave it checked.

Click Restore and let the plugin run. Depending on your server and backup size, this can take anywhere from 30 seconds to several minutes. Do not close the browser tab.

Step 4: Verify the Restore

After the process completes, visit your site’s frontend and admin area (/wp-admin). If everything looks normal, clear your browser cache and test a few pages.

Common issues:

• White screen of death — usually a PHP memory limit issue or a corrupted plugin. Try increasing memory limit via wp-config.php or deactivating plugins via database.
• Database error — your wp-config.php credentials don’t match the database. Double-check the database name, user, and password in the file.



• Missing media files — the uploads folder wasn’t included or the path is wrong. Re-upload uploads manually via FTP if needed.

Method 2: Restoring a WordPress Backup via cPanel and phpMyAdmin

This method is for users who have a manual backup (files + SQL export) or prefer to avoid plugins. It gives you full control but requires careful attention to detail. Use this when your site is completely down and you can’t access wp-admin at all.

Step 1: Upload Your WordPress Files via cPanel File Manager

Log into cPanel and open File Manager. Navigate to the directory where your WordPress lives — usually public_html or a subfolder like public_html/yourdomain.

Delete the existing WordPress files (or move them to a backup folder for safety). Then upload your backup zip file using the Upload button. After upload, select the zip and click Extract. Make sure file permissions are set to 755 for directories and 644 for files. If you see permission errors, adjust them via the File Manager interface.

Step 2: Create a Fresh Database (If Needed)

If you’re restoring to a completely new environment (new server or domain), you need a fresh MySQL database. In cPanel, go to MySQL Databases, create a new database, add a user, and assign all privileges to that user. Write down the database name, username, and password.

If you’re restoring to the same database where the site lived before, skip this step — but be aware the import will overwrite existing tables.

Update your wp-config.php file with the new database credentials if you created a new database.

Step 3: Import Your Database Using phpMyAdmin

In cPanel, open phpMyAdmin. Select the database you intend to use (the one you created or the existing one). Click the Import tab, choose your .sql backup file, and click Go.

Watch for size limits. phpMyAdmin often has a default upload limit of 50MB. If your SQL file is larger, you’ll need to split it into smaller chunks using a tool like BigDump or ask your host to increase the limit temporarily.

Note: If your backup includes a database prefix different from your current one, the restore will still work — tables will just have a different prefix. That’s fine as long as wp-config.php matches.

Step 4: Update Site URLs and Permalinks

After the database import, your site might show broken links or redirect to the old domain. This is common. In phpMyAdmin, run the following SQL query to update the site URL:

UPDATE wp_options SET option_value = 'https://yournewdomain.com' WHERE option_name = 'siteurl' OR option_name = 'home';

Replace wp_ with your actual table prefix and yournewdomain.com with your live domain. After that, log into wp-admin (if possible) and go to Settings > Permalinks — just click Save Changes to flush the rewrite rules. This fixes 404 errors on non-home pages.

Method 3: Full Manual Restore via FTP

This method is useful when cPanel is unavailable or your host only provides FTP access. It’s slower than File Manager, but equally effective.

Steps:

• Connect to your server via FTP (FileZilla works well).
• Navigate to your WordPress root folder (usually public_html).
• Delete existing files (or move them to a local backup).
• Upload your backup zip’s contents to the same directory. This can take a while for large sites.
• Once files are uploaded, use phpMyAdmin (if accessible) or a database management tool like Adminer to import your SQL file as described in Method 2, Step 3.

The FTP method is purely for file transfer — you still need a way to restore the database separately. If you only have SQL access via command line, you can run mysql -u username -p database_name < backup.sql instead of phpMyAdmin.

Common WordPress Restore Problems and How to Fix Them

• White screen of death — Usually a PHP memory error or a plugin conflict. Increase memory limit in wp-config.php: define('WP_MEMORY_LIMIT', '256M');. If that doesn't work, deactivate all plugins by renaming the plugins folder via FTP.
• Database connection error — Your wp-config.php credentials are wrong. Verify the database name, username, password, and host. The host is often "localhost" but some hosts use a specific IP or server name.
• Missing tables error — Your database backup didn't include all tables, or the import was interrupted. Re-run the import. If your SQL file is large, use a tool like BigDump to handle it in chunks.
• Infinite redirect loop — Usually caused by a mismatch between site URL in the database and the actual domain. Double-check the siteurl and home options in the database. Also flush permalinks.
• Login page redirects back to login — Clear your browser cache and cookies. If that doesn't help, check your wp-config.php for any hardcoded site URL settings.

When to Call a Professional (And How We Can Help)

Running a restore yourself is doable, but it's not always the best use of your time — especially if the site is generating revenue or handling customer data. One wrong move during a database import can complicate the recovery further.

If any of these apply to you, it's worth handing off to experts:

• You don't have a recent, verified backup.
• Your backup files are larger than 500MB and you're unsure how to handle them.
• You're restoring a site with custom configurations or complex plugins.
• You simply want it done right without the stress.

At Manage WP Websites, we handle backup restores as part of our managed WordPress support. Our team can restore your site from any backup source, verify all components are working, and ensure you have a fresh backup in place afterward. We also offer proactive monitoring so you're less likely to need a restore in the first place. Reach out to us if you want help — we're available 24/7.

Final Checklist: What to Do After Restoring Your Backup

Once the restore is complete, run through this checklist to confirm everything is solid:

• Visit the homepage and 2–3 inner pages — verify content displays correctly and no broken images or layout issues.
• Test any forms — contact forms, checkout, or newsletter signups. Submit a test entry to catch database-related failures.
• Check plugins and themes — ensure they're active and functioning. Update any that show outdated notices.
• Update passwords — change your admin password and database password if there's any chance of compromise.
• Run a fresh backup — immediately create a new full backup. You now have a restore point that reflects your current state.
• Monitor for 24 hours — keep an eye on error logs and user reports. Some issues only surface after a cache refresh or user interaction.

Knowing how to restore a WordPress backup is a skill every site owner should have. But you don't have to do it alone. Whether you follow this guide step by step or hand it to professionals, the goal is the same — a working, stable site with minimal downtime. Keep a backup strategy in place, test your restores regularly, and you'll be ready for anything.