A WordPress backup is only useful if it is complete, stored safely, and known to restore. This guide compares hosting backups, backup plugins, and manual copies, then gives you a reusable schedule, storage checklist, restore drill, and recovery verification worksheet.
Overview
The best WordPress backup method is usually a layered one rather than a single tool. Your hosting provider may create automatic snapshots, a backup plugin can package your site on a schedule, and a manual export gives you an independent copy for migrations or emergency work. The right combination depends on how often your site changes, how quickly it must be recovered, and how comfortable you are working with files and databases.
A usable WordPress backup normally includes two related parts:
- Database: Posts, pages, comments, users, settings, plugin data, and other content stored in MySQL or MariaDB.
- Files: Themes, plugins, uploads, and configuration files that make the site operate and display correctly.
A database-only export will not recreate your media library or theme files. A files-only copy will not restore your latest posts, settings, or user accounts. Before relying on any backup, confirm what it contains, where it is stored, how long it is retained, and whether you can restore it without overwriting the live site unexpectedly.
WordPress backup method comparison
| Method | Best use | Advantages | Limitations to check |
|---|---|---|---|
| Hosting backups | Routine recovery and server-level incidents | Often automated and connected to the hosting account; restoration may be available from the control panel or support team | Retention, restore access, backup scope, and storage location vary by provider and plan |
| Backup plugin | Scheduled site-level backups and portable copies | Can combine database and files, send copies to external storage, and provide a WordPress dashboard workflow | Large sites may need exclusions or longer run times; plugin compatibility and remote-storage settings require review |
| Manual database and file backup | Migrations, troubleshooting, and independent emergency copies | Gives you direct control over the database export and site files; useful when dashboard access is unavailable | More technical, easier to omit a component, and not practical as the only routine process for most site owners |
For many small business sites, a sensible baseline is automated hosting backups plus a separate plugin or manual copy stored outside the hosting account. Treat that as a starting workflow, not a universal rule. Review the exact features and retention limits of your provider and tools before choosing a schedule.
Checklist by scenario
For a normal operating website
- Set a backup frequency that matches site activity. A frequently updated store or publication needs more frequent copies than a rarely changed brochure site.
- Back up both the database and files.
- Send at least one copy to storage outside the hosting account.
- Keep enough historical versions to recover from an error discovered later, not just the most recent copy.
- Record the backup date, method, destination, and result in a simple log.
- Run a small recovery check regularly and a full restore drill at a planned interval.
Before a major update or redesign
- Make a fresh backup immediately before changing WordPress core, a theme, a plugin, or important site settings.
- Confirm the backup completed successfully rather than assuming a scheduled task ran.
- Download or otherwise verify access to the backup outside the WordPress dashboard.
- Write down the change being made and the intended rollback point.
- Update one logical group at a time, test the site, and preserve the pre-change backup until the result is accepted.
For a safer update workflow, see How to Update WordPress Safely.
Before a migration or hosting move
- Create a complete copy of the current files and database.
- Check the database export for a successful completion message and a plausible file size.
- List special items such as scheduled tasks, custom server rules, redirect files, DNS settings, and email configuration.
- Keep the old site available until the new installation has been tested and the DNS change is stable.
- Do not delete the source backup immediately after migration.
Simple backup schedule template
| Task | Suggested trigger | Record |
|---|---|---|
| Automated backup | According to publishing and transaction frequency | Date, time, scope, completion status |
| Backup access check | Monthly | Can the file be located, downloaded, and opened? |
| Restore drill | Quarterly or after a major tool change | Restore time, errors, and verification results |
| Provider and plugin review | Quarterly or after a plan, policy, or workflow change | Retention, pricing, compatibility, and restore interface |
What to double-check
Storage-location checklist
- Independence: At least one recovery copy should be outside the same hosting account and preferably outside the same failure path.
- Access: Confirm that the account, password, encryption key, or recovery code needed to retrieve the backup is available to the site owner.
- Retention: Note how many versions are kept and whether older copies are automatically removed.
- Security: Restrict access to backup files because they can contain private content, user information, and configuration data.
- Integrity: Check that files can be downloaded and opened, and that an archive is not merely present with a failed or incomplete job behind it.
- Recovery path: Identify whether restoration happens through a hosting panel, plugin dashboard, command line, or support request.
Restore drill
- Choose a recent backup and write down its timestamp.
- Restore it to a staging site, local environment, or temporary installation rather than testing by overwriting the live site.
- Record how long the process takes and any warnings or missing files.
- Check the front page, several posts or pages, images, forms, navigation, login, and key plugin features.
- Confirm that links do not point to the temporary address and that private or test content is not exposed.
- Document the exact recovery steps so another administrator can repeat them.
Recovery verification worksheet
After each drill, record: backup timestamp; source and destination; database restored; files restored; media visible; theme working; plugins active; forms tested; user login tested; scheduled tasks reviewed; errors found; total recovery time; and next corrective action. A failed drill is useful information: fix the process while the original site is still available.
Common mistakes
- Keeping every copy on the same server: A hosting failure, account issue, or accidental deletion can affect both the site and its backups.
- Backing up only the database: This commonly leaves uploads, themes, and plugins behind.
- Assuming a backup is valid because it exists: Completion messages, archive access, and test restores matter more than a filename or timestamp.
- Ignoring restore permissions: The person who can create a backup may not be the person who can restore it. Define access in advance.
- Restoring directly over the live site during a first test: Use a staging or temporary destination until the workflow is understood.
- Updating the backup tool without reviewing its destination: Plugin changes, expired storage connections, or altered schedules can silently change the workflow.
- Forgetting the surrounding systems: DNS, domain access, email records, payment settings, and third-party integrations may need separate documentation. A backup does not automatically recreate every external service.
Backups are one part of a broader operating routine. Pair them with a security review using the WordPress Security Hardening Guide, and document the site before launch or migration with the Website Launch Checklist.
When to revisit
Revisit this workflow monthly to confirm that the latest backup exists and can be accessed. Run a restore drill at least quarterly, before a seasonal planning cycle, and whenever the site becomes more active or business-critical. Repeat the review immediately after changing hosts, backup plugins, remote storage, WordPress versions, themes, or major plugins.
During each review, verify the provider's current backup scope, retention limits, restore interface, compatibility, and any plan or policy changes. Also check that the recovery contacts and credentials are current. If you cannot explain where the latest complete backup is and how you would restore it, treat that as an unfinished task.
Next action: create one fresh backup today, store a copy outside the hosting account, and complete the first recovery verification worksheet. Then put the monthly access check and quarterly restore drill on the calendar.