Knowing how to restore WordPress website from backup is the skill you need before you ever need it. When a site is down — after a failed update, a hacked installation, a botched plugin change, or a hosting disaster — the window between the problem appearing and needing to recover is exactly the wrong time to figure out how restoration works. I have helped people restore WordPress website from backup under real-time pressure, and the ones who recover quickly are the ones who have at minimum read through the process once before the emergency. This guide covers every method to restore WordPress website from backup: the plugin-based automated method, the manual method through phpMyAdmin and FTP, the managed hosting one-click approach, and what to do when the restoration process itself encounters problems. We go deeper on the whole subject in our Complete Guide to WordPress How.
Before You Start — Assess the Situation Clearly
Rushing directly to the restore WordPress website from backup process without a brief assessment can turn a recoverable situation into a worse one. Before you start restoring, take sixty seconds to establish three facts that determine which restoration approach is appropriate and how complete the restoration needs to be.
First: what exactly is broken? A site that is returning a 500 error on the front end but has an accessible admin panel is a different scenario from a site whose database is completely corrupted. If the admin panel is accessible and the problem is a single broken plugin or page, restoring the entire site from backup is more destructive than necessary — it overwrites any content created since the backup was taken. The correct response is often a targeted fix rather than a full restore WordPress website from backup operation. If the database is corrupted, the admin panel is inaccessible, or the site has been compromised by malware, a full restoration is the right call.
Second: when was the most recent backup taken, and how much data will the restoration lose? A backup from this morning loses today’s content. A backup from a week ago loses a week of posts, orders, and user registrations. Knowing the backup’s age helps you decide whether a full restore WordPress website from backup is the right move or whether attempting to fix the problem in place (to preserve newer data) is worth the additional complexity. For WooCommerce sites where orders are recorded continuously, losing even a day of order data may not be acceptable — in which case the restoration needs to be paired with manual order recovery from payment processor records.
Third: does the backup include both the database and the files? A complete restore WordPress website from backup requires both components. A database-only restore recovers content and settings but leaves any site files (themes, plugins, uploads) in whatever state they are currently in — which may include the corrupted or malware-infected files that caused the problem. A files-only restore recovers themes and plugins but the database may still be in its damaged state. Only a full restore that includes both database and files returns the site to its exact pre-problem state.
Restore WordPress Website From Backup Using UpdraftPlus
If the backup was created with UpdraftPlus — the most widely used WordPress backup plugin — the restoration process runs through the UpdraftPlus plugin itself and is the most straightforward way to restore WordPress website from backup. The plugin handles both the database restoration and the file restoration in a guided process that does not require manual database or FTP operations.
- Access the WordPress admin panel. If the admin is inaccessible due to the problem requiring restoration, install a fresh WordPress on the same domain first — this gives you a working admin to run the restoration through
- Ensure UpdraftPlus is installed and activated — if restoring to a fresh WordPress, install UpdraftPlus from the Plugin Directory
- Navigate to Settings → UpdraftPlus Backups → Existing Backups tab
- If the backup is stored remotely (Google Drive, Dropbox, Amazon S3), click “Scan remote storage” to retrieve the backup files from your remote storage into the UpdraftPlus interface
- Locate the backup set you want to restore WordPress website from backup with — identify it by date and confirm it includes both the database and files components
- Click the Restore button next to the backup date
- In the restoration options, check all components: Plugins, Themes, Uploads, Others (wp-content), and Database. For a full restoration, all components should be selected
- Click Restore — UpdraftPlus downloads the backup files from remote storage (if applicable), extracts them, and begins the restoration process
- After the database restoration completes, UpdraftPlus will prompt you to log in again with the credentials from the backup — the restoration overwrites the current WordPress installation including user accounts
- After the full restoration completes, verify the site is functioning correctly on both the front end and in the admin panel
The UpdraftPlus restoration process handles most of the technical complexity of how to restore WordPress website from backup automatically — database import, file replacement, configuration updates. The most common issue encountered is the remote storage retrieval step timing out for very large backups on slow hosting connections. If this happens, download the backup files from Google Drive or Dropbox directly to your computer, then upload them to the UpdraftPlus backup directory on the server (wp-content/updraft/), and retry the restoration — UpdraftPlus detects local backup files and uses them rather than re-downloading from remote storage.
Manual Restoration — Restoring the WordPress Database First
When UpdraftPlus is not available — because the backup was created manually, by a different plugin, or by the hosting provider’s backup system — the manual process to restore WordPress website from backup requires two separate operations: database restoration through phpMyAdmin and file restoration through FTP or the hosting file manager. Database restoration should always come first because WordPress requires the database to function, and restoring files without a working database leaves the site non-functional anyway.
To restore the database manually: log in to cPanel and open phpMyAdmin. Select your WordPress database from the left panel. Before importing the backup, the existing database tables may need to be cleared — if the backup is a full export, importing it without clearing the existing tables creates duplicate data. Click the Check All link to select all tables, then from the dropdown choose Drop to delete all existing tables. After the tables are cleared, click the Import tab, choose your backup .sql file, and click Go. phpMyAdmin imports the file and recreates all WordPress tables with the data from the backup. For database files larger than phpMyAdmin’s upload limit, use MySQL’s command-line import instead: mysql -u username -p database_name < backup.sql.
After the database restoration completes, verify it worked by navigating to wp-admin/install.php in the browser — if WordPress finds an existing database with tables, it will not ask you to run the installation again and will redirect you to the login page. Successfully reaching the login page confirms the database restoration worked and the database is now in its backup state. The next step to complete the restore WordPress website from backup process is restoring the files.
Restoring WordPress Files From a Manual Backup
File restoration is the second half of the manual approach to restore WordPress website from backup. The goal is to replace the current server files with the backed-up versions — putting themes, plugins, uploads, and configuration back to the state they were in when the backup was taken. This step is performed via FTP or the hosting file manager.
Connect to the server via FTP or open the hosting file manager. Navigate to the WordPress root directory. The safest approach to file restoration is to delete the directories you are restoring before uploading the backup versions — starting with wp-content/themes/, wp-content/plugins/, and wp-content/uploads/. Deleting before uploading ensures that any files from the current (broken) state that do not have an equivalent in the backup are not left in place. Replace these directories with the corresponding directories from the backup. Upload wp-config.php from the backup if the site’s database credentials have not changed — if you are restoring to a new hosting environment with different database credentials, keep the current wp-config.php rather than restoring the backup version.
After file restoration, attempt to load the site in a browser. A successful restore WordPress website from backup returns the site to its exact backup state — all posts, media, plugin settings, and theme configuration matching the backup’s timestamp. If the site loads but shows incorrect URLs (particularly if the site was at a different domain when the backup was taken), run a database search-and-replace using the Better Search Replace plugin or WP-CLI wp search-replace command to update all domain references in the database to the current domain.
Post-Restoration Checks After Restoring WordPress From Backup
A completed restore WordPress website from backup operation is not finished until the site has been verified through a systematic post-restoration checklist. Restoration processes can occasionally leave the site in a functional-but-imperfect state — a working front end with a broken plugin, a restored database with incorrect URL settings, or an uploaded media file that does not appear correctly because the database reference was not restored alongside it.
- Front end check: Load the homepage, several internal pages, and the blog index. Verify images load, navigation works, and the site appearance matches expectations
- Admin panel check: Log in and verify the WordPress version, all plugins are showing as active, and the theme is correct
- Content verification: Check that recent posts and pages are present and displaying correctly — and note the cut-off point where content from after the backup date is absent
- Functionality check: Test any critical functionality — contact forms, WooCommerce checkout, membership login, booking forms — that was working before the problem requiring restoration
- URL and permalink check: Navigate to Settings → Permalinks and click Save Changes — this regenerates the rewrite rules which are sometimes not correctly restored from backup
- SSL check: Verify the padlock is showing correctly and no mixed content warnings appear in the browser console
If specific functionality is broken after an otherwise successful restore WordPress website from backup, the most common causes are: the backup predates a configuration change that the functionality depends on, a plugin requires reconfiguration after restoration (payment gateway API keys, email service credentials), or the database restoration and file restoration are from different backup dates and are not compatible.
When the Backup Itself Is Damaged or Incomplete
The most difficult scenario in any restore WordPress website from backup situation is discovering that the backup itself is damaged, incomplete, or significantly older than expected. This happens when automated backup processes have been failing silently, when remote storage transfer was interrupted, or when the backup has been stored on the same server that failed.
If the most recent backup is damaged, work backward through older backup copies — restoration to a two-week-old backup is dramatically better than no restoration at all. Use the oldest reliable backup as the restoration base, then manually recreate any content from the gap period that is available from other sources: Google Search Console’s cached versions, the Wayback Machine (web.archive.org) for front-end page content, and the hosting provider’s own control panel backup system which may hold server snapshots independent of any WordPress backup plugin.
Managed WordPress hosting providers often maintain server-level snapshots independently of the WordPress backup system. Kinsta, WP Engine, SiteGround, and Cloudways all take daily snapshots of the entire hosting environment — if a WordPress-level backup is unavailable or damaged, these host snapshots provide an alternative path to restore WordPress website from backup state. Contact the hosting provider’s support team immediately when the WordPress-level backup is unavailable — the host snapshot may be the difference between a successful recovery and data loss.
Our guide on how to backup a WordPress site properly covers the automated backup configuration that prevents the “no usable backup” scenario — the most effective action you can take today to ensure that any future need to restore WordPress website from backup has a reliable starting point. Our guide on how to create a staging site in WordPress covers the pre-change testing environment that reduces the frequency of events requiring restore WordPress website from backup operations on live sites. The UpdraftPlus FAQ documentation covers the edge cases in the plugin-based restoration process, including large backup file handling, remote storage authentication issues, and multisite restoration scenarios. You might also run into How to Speed up WordPress Website Step by Step.
