Backups & migration · Practical guide

How to back up a WordPress website safely

Back up both files and the database, then verify you can restore them.

Quick answer

Back up both files and the database, then verify you can restore them.

Start with the checks below. Each step explains what to look for and what to try next.

What a complete backup contains

A WordPress backup needs both website files (themes, plugins, uploads and configuration) and the database (pages, settings, orders and more). Copying only wp-content is not always a complete backup.

A backup is complete only when both parts exist

A backup is complete only when both parts exist

Website files

Themes, plugins, uploads, custom configuration and application files.

Database

Posts, pages, users, settings and other dynamic site content.

Independent storage

Keep a copy outside the same hosting account when practical.

Restore test

Confirm a backup can actually be restored in a safe test environment.

Before you continue: Before restoring to production, make a copy of the current site and confirm the recovery point.

Make a backup

  1. Identify the site’s document root and its database connection settings.
  2. Download the website files using cPanel File Manager, a supported backup tool, or secure transfer.
  3. Export the corresponding database using the available database tool, such as phpMyAdmin.
  4. Store the files and database export outside the live hosting account.
  5. Check the archive contents and periodically test a restore in a safe environment.

When to back up

Before plugin updates, theme changes, migrations, DNS cutovers and major content edits. Back up more often for stores, membership sites or sites with frequently changing data.

Important caution

Do not assume that a provider’s automated backup covers every file or the exact restore point you need. Review the backup features of your purchased plan.

How to confirm the issue is resolved

  1. Repeat the original action that produced the issue.
  2. Check the result in a second browser or network when relevant.
  3. Review logs or status messages for remaining errors.
  4. Keep a short record of what changed so it can be reversed if necessary.

If the issue persists, contact support with the exact error, time, affected domain and actions already tried—never include passwords or secret keys.

Check that your backup can actually restore

A reliable WordPress backup contains both website files and the matching database. A downloaded archive that has never been tested is not yet a confirmed recovery plan.

  1. Check that your backup includes the WordPress content directory, configuration files and a database export.
  2. Record the backup date and whether it was made before or after recent changes.
  3. Where possible, test recovery in a separate staging environment so production data is not overwritten.

Keep a copy outside the hosting account; a backup stored only on the same server may be lost during an account or server incident. See the migration checklist if you are preparing to move providers.

Guidance may vary by plan, control panel version and enabled features. Review the settings available to your account before changing live services.