Backups & storage
How to back up a WordPress site: complete copies and offsite recovery
Build a WordPress backup plan that covers files, database, independent storage, and a restore path you can actually use.
A useful WordPress backup gives you a way to rebuild the site when the current installation or hosting account is unavailable. Start with both the database and the files, keep a copy outside the hosting account, and confirm that you can restore it somewhere else.
A backup notification is a useful signal, but it does not tell you whether uploads were excluded, the archive is readable, or the restore button requires a paid plan. Those details belong in your backup plan before an emergency.
Back up the parts needed to rebuild
The WordPress backup handbook separates the database from the installation’s files. You need a consistent set of both. A content export from the Tools menu is not a substitute for a complete site backup.
| Part | What to include or record |
|---|---|
| Database | Posts, settings, users, and application data such as orders. |
| Site files | Uploads, themes, plugins, custom code, and required configuration. |
| External services | Where email, offloaded media, DNS, and integrations are managed. |
| Recovery access | Who can retrieve the archive, decrypt it, and restore the destination. |
For an active store, ask how the backup method keeps database and file changes consistent. A database copied hours before the media library can describe a different site state. Also check whether separate object storage or an external booking system has its own recovery process.
Choose a method you can operate
A host’s backup interface is convenient when you need to reverse a recent change. A maintained WordPress backup plugin can provide scheduling and an external storage destination. A manual file transfer plus database export gives experienced administrators more direct control, but requires a repeatable procedure.
Whichever method you choose, inspect its exclusions, archive format, retention period, and restore requirements. If a plugin stores its only archive inside the same WordPress account, losing that account can lose both the site and its backup.
Download a sample archive while the account is healthy. Confirm what tools and permissions another host would need to restore it. cPanel’s documentation, for example, says automatic restoration of a full account backup requires WHM rather than the ordinary cPanel interface. A download option does not imply a matching self-service restore option.
Make the offsite copy independent
For WordPress offsite backup, use storage that remains accessible if your hosting subscription is suspended or its login is compromised. Separate account ownership and recovery credentials matter as much as physical location. Protect archives because they may contain personal data, credentials, and unpublished content.
Keep multiple recovery dates. A backup taken after a bad update or unnoticed intrusion may faithfully preserve the problem. Define how many historical copies you need and who receives a failure alert. Store any encryption recovery key securely outside the account it protects.
Set frequency around acceptable data loss
A brochure site edited weekly has different needs from a store taking orders throughout the day. Decide how much recent work the business could recreate. Use that answer to choose the database schedule, then account for changes to files and integrations.
Take an additional recoverable copy before major updates or a migration. Check available disk space first: generating a local archive can consume the capacity you need to keep the live site running. Retention cleanup should follow a verified copy, not precede it.
Prove the recovery path
Restore a recent backup into an isolated environment with outgoing mail, payment actions, and scheduled business jobs disabled. Check administrator access, representative pages, images, and the business data you expected to recover. Keep a brief record of the backup date, destination, problems, and person responsible.
Our WordPress restoration guide covers the recovery sequence. Revisit it after changing backup tools, hosts, or storage arrangements. The useful outcome is a known path back to a working site, with a realistic estimate of what data and time recovery could cost.