WordPress Hosting Backup and Restore Guide: A Practical Recovery Checklist
WordPressbackupssite recoveryhostingdisaster recovery

WordPress Hosting Backup and Restore Guide: A Practical Recovery Checklist

HHostingFreeWebsites Editorial Team
2026-11-12
7 min read

Learn what to back up in WordPress, compare backup methods, test restores, and follow recovery checklists for updates, outages, and migrations.

A WordPress backup is useful only if it contains the right data and can be restored. This practical checklist explains what to back up, how hosting and plugin backups differ, how to test recovery safely, and what to do when an update, migration, or hosting failure breaks your site.

Overview

A complete WordPress backup has two essential parts: the site files and the database. You generally need both to recreate the site as it existed at a particular point in time.

  • Database: Posts, pages, comments, users, settings, menus, widget data, plugin settings, and other structured content.
  • Files: The WordPress core files, themes, plugins, uploads, configuration files, and any custom files used by the site.

The wp-content directory deserves particular attention. It commonly contains your active theme, installed plugins, media uploads, and sometimes custom code. The wp-config.php file contains important connection and configuration details, while server-level files such as .htaccess may affect redirects, security rules, and caching. Do not publish these files or store them carelessly.

A useful backup plan has more than one copy and more than one recovery path. Your WordPress hosting provider may create server backups, a backup plugin may send archives to separate storage, and a manual database or file copy may provide an additional fallback. These methods can complement one another, but none should be assumed to cover every need without checking its settings.

Backup method comparison

MethodStrengthsPoints to verify
Host backupOften integrated with the hosting account and control panel; may support account-level recovery.Retention period, backup scope, restore access, storage location, and whether databases and files are included.
WordPress backup pluginCan schedule site-specific backups and send them to separate storage.Whether it captures the full database, uploads, themes, plugins, configuration files, and usable restore instructions.
Manual database exportProvides a direct copy of the database and is useful for targeted recovery or migration.It does not replace a complete file backup; confirm the export completed and is readable.
Manual file copyProvides direct access to themes, plugins, uploads, and configuration files.It may omit the database and can be incomplete if hidden files or large uploads are missed.

For a site that matters to a business, keep at least one backup outside the hosting account. If a hosting account becomes inaccessible, a backup stored only inside that account may not help. Choose a retention schedule that matches how often the site changes. A frequently updated shop or publication needs more recovery points than a rarely edited brochure site.

Checklist by scenario

Before a WordPress, theme, plugin, or PHP change

  1. Record the current WordPress version, PHP version, active theme, and important plugins.
  2. Confirm that a recent backup completed successfully, rather than relying only on a scheduled task.
  3. Check that the backup includes the database and the wp-content directory at minimum.
  4. Save a copy outside the hosting account or confirm that your backup destination is separate.
  5. Note the current site URL, administrator login route, and hosting control-panel access.
  6. Update one component at a time where practical, so a failure is easier to identify.

If the change causes an error, avoid repeatedly updating or deleting components while the cause is unknown. First preserve the current state, review the error details, and decide whether a targeted rollback or a full restore is safer.

After a broken update or visible site error

  1. Check whether the issue affects the whole site, only the administration area, or a specific page.
  2. Record the time the problem began and the last change made.
  3. Look for a hosting error log, WordPress recovery notice, or plugin-specific message.
  4. Consider temporarily disabling the suspected plugin or switching to a known-compatible theme only if you can do so safely.
  5. If the site remains unstable, restore a backup from before the change to a staging location first when possible.
  6. Compare the restored staging site with the live site before replacing production data.

For errors involving the web server or PHP process, a backup may not be the only issue. Use the troubleshooting steps in this guide to 502, 503, and 504 errors to separate application problems from hosting or server problems.

When the hosting account is unavailable

  1. Confirm whether the problem is an outage, an account access issue, a domain or DNS problem, or a site-level failure.
  2. Use an independently stored backup if the hosting panel and its backup directory cannot be reached.
  3. Prepare a clean WordPress installation on the destination hosting account.
  4. Restore the database and files, then update the configuration values needed by the new environment.
  5. Test the site on a temporary address or staging environment before changing DNS.
  6. Review permalinks, media URLs, forms, email delivery, SSL, redirects, and administrator access.

A full migration requires more than copying WordPress files. The website migration checklist covers the related DNS, email, and SEO checks.

When preparing a planned migration

  1. Take a fresh backup immediately before the migration.
  2. Export the database and copy the complete site files, including hidden files where applicable.
  3. Lower the risk of content differences by recording when the final backup was made.
  4. Test the copy on the new host before pointing the domain to it.
  5. Keep the old hosting account available until the new site is verified and the transition is stable.

Check the destination PHP version and extension requirements before moving. A compatibility mismatch can look like a failed restore even when the backup itself is sound. Review how to choose a PHP version for your website before committing to the new environment.

What to double-check

Backup completeness

Open the backup record and confirm its contents. Look for a database export, uploads, active and required plugins, themes, and configuration files. If the tool offers separate database and file jobs, confirm that both jobs completed. A successful status for one task does not necessarily mean the entire site was captured.

Restore instructions

Write down the actual restore path while access is available. Depending on the setup, this may involve a hosting control panel, a backup plugin, a database management tool, SFTP, or a support request. Record where the backup is stored, which credentials are needed, and whether the restore overwrites existing files or creates a separate copy.

Database and URL details

WordPress stores site addresses and links in the database. After a restore or migration, verify the site URL and home URL, then check serialized data carefully if a domain has changed. Use a WordPress-aware search-and-replace method rather than a basic text replacement that may damage serialized values.

Staging tests

A staging site is the safest place to test a restore. Confirm that the homepage, representative posts, images, forms, navigation, login, search, and important plugins work. Also check scheduled tasks, ecommerce functions if relevant, and any integrations that depend on API keys or webhooks. Keep test emails from reaching real customers by using a safe mail configuration.

Security after recovery

Review administrator accounts, passwords, salts, file permissions, SSL, and security plugin settings. If the incident involved suspicious access, do not assume restoring files alone removes the problem. Investigate the hosting account and related credentials, and change exposed passwords through trusted channels.

Common mistakes

  • Backing up only the database: This preserves content but not necessarily themes, plugins, images, or custom files.
  • Keeping every copy on the same host: A hosting problem can make all of those copies inaccessible at once.
  • Trusting a completion email without testing: A backup can finish while excluding a directory, exceeding storage limits, or producing an archive that cannot be opened.
  • Restoring directly over the live site: If the restore fails, you may lose the current state and make diagnosis harder. Preserve the live copy when practical.
  • Ignoring email and DNS: A restored website can work while domain records, mailboxes, SPF, DKIM, or DMARC remain incorrect.
  • Restoring an old backup without checking changes: You may remove new orders, posts, comments, accounts, or settings created after the backup date.
  • Changing several variables at once: Updating WordPress, PHP, a theme, and multiple plugins together makes rollback and troubleshooting less precise.

If storage limits, CPU usage, or inode limits interfere with backup jobs, review your hosting resource usage rather than repeatedly rerunning the same task. The hosting resource monitoring guide can help identify those constraints.

When to revisit

Use this checklist before major WordPress, plugin, theme, or PHP changes; before renewing or moving hosting; after changing domain or DNS settings; and before high-traffic seasonal periods. Revisit it whenever your backup plugin, hosting control panel, storage destination, or WordPress workflow changes.

Schedule a restore test at an interval appropriate to the site’s risk and update frequency. The test does not need to replace the live site. Restore a recent copy to staging, record how long the process takes, and confirm that the result is usable. Update your recovery notes if a menu path, plugin option, PHP setting, or hosting procedure has changed.

For a practical monthly or quarterly review, complete these actions:

  1. Verify the latest database and file backup dates.
  2. Open the backup destination and confirm that archives are present.
  3. Check available storage and failed-job notifications.
  4. Test one restore on staging.
  5. Record the restore date, backup version, test result, and any missing components.
  6. Update emergency contacts and hosting access details.

Keep this page with your site maintenance notes and use it before the next update. A tested WordPress backup turns recovery from an uncertain emergency into a repeatable hosting and site-management task.

Related Topics

#WordPress#backups#site recovery#hosting#disaster recovery
H

HostingFreeWebsites Editorial Team

Senior SEO Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.