A backup you cannot restore is not a backup. That is the idea behind every good WordPress backup strategy: decide what to back up, how often, where to keep it, how long to keep it, and then prove it works. Here is how to set one up for a typical business site.

Why Host Backups Alone Aren't Enough

Many hosts include automatic backups, and they are genuinely useful. But relying on them alone has risks:

CISA's ransomware guidance warns that many ransomware variants try to find and delete accessible backups. That is why it recommends keeping offline, encrypted copies. Treat host backups as one layer, and add at least one copy you control.

How Often Should You Back Up WordPress?

WordPress's own backup documentation suggests backing up the database regularly and always before an upgrade. It mentions weekly backups for smaller sites and daily for sites with a lot of activity.

Table suggesting backup frequency for brochure sites, busy content sites, WooCommerce stores and any site before updates
A starting point. Adjust it to how much work you could bear to lose.

The practical question is: how much could you afford to lose? If you publish once a month, a weekly backup loses very little. If you run a WooCommerce store, a day of lost orders could be serious, so you may want daily or more frequent database backups.

If you are deciding whether to let WordPress update itself, my guide to WordPress auto-updates explains how backups fit into that choice.

Files, Database or Both?

A WordPress site has two parts, and you need both. The WordPress documentation is clear that backing up your files does not include your database.

The database changes most often, so many sites back it up more frequently than files. The WordPress documentation also recommends a sensible order: back up the database first, then the files. When restoring, restore the files first, then import the database.

Exclude what you do not need. Cache folders and old backup archives stored inside wp-content can make every backup much bigger. Leave them out, and never store backups inside the site's public folder.

The 3-2-1 Rule for a WordPress Backup Strategy

CISA describes the 3-2-1 rule for small and medium businesses: keep three copies of your data, on two different types of media, with one copy offsite.

Three cards explaining the 3-2-1 backup rule: three copies, two media types and one offsite
Simple enough to remember, and it covers most of the ways backups get lost.

For a WordPress site, that might look like this:

The point is that no single failure, such as a server fault, a hacked hosting account or a mistaken deletion, can take out every copy at once.

Where to Store Backups Safely

The WordPress documentation suggests keeping backups in different places, such as your server, cloud storage and a local copy.

When you choose offsite storage:

Retention: How Long to Keep Backups

Retention is how long you keep each backup before deleting it. WordPress's documentation suggests keeping at least three to five recent backups. In practice, you also want some older copies.

Row of glowing data capsules fading into the distance with one red capsule highlighted, representing backup retention over time
Older copies matter when a problem has been hiding for weeks.

Why older copies matter: malware, spam injections and accidental deletions are not always noticed straight away. If your oldest backup is from three days ago and the problem started three weeks ago, every copy you have may include it.

A common pattern is to keep daily backups for a couple of weeks, weekly ones for a month or two, and monthly ones for longer. Balance that against storage space and privacy. Keeping personal data for longer than needed has its own risks.

How to Test a Backup

WordPress's documentation recommends checking occasionally that automatic backups actually work. CISA goes further and recommends regularly testing the availability and integrity of backups in a disaster recovery scenario.

Seven-step checklist for testing a WordPress backup on a staging site or local copy
Test on a staging site or local copy, never over the live site.

A simple test:

Open crate releasing cubes that rebuild a miniature tower while a red beam scans it, representing restoring and checking a WordPress backup
A restore test proves the backup is complete before you ever need it.

Having a written restore process makes a real emergency much calmer. My step-by-step guide to restoring WordPress from a backup covers the restore itself, and a staging site gives you a safe place to practise.

Never test a restore over your live site. If the backup is incomplete, you could replace a working site with a broken one. Always test somewhere separate.

Frequently Asked Questions

Are my hosting company's backups enough?

They are a useful layer, but they should not be your only one. They are usually stored with the same provider, may have short retention, and may not be easy to restore selectively. Keep at least one copy that you control, somewhere else.

How many backups should I keep?

WordPress's own documentation suggests keeping at least three to five recent backups in different locations. Many sites keep daily copies for a couple of weeks and some older weekly or monthly copies as well, depending on how far back problems might go unnoticed.

Do I need to back up the whole site or just the database?

Both. The database holds your content, settings and users, while the files hold uploads, themes and plugins. Backing up files does not include the database, so a complete backup needs both.

How often should I test a backup?

Test a restore after you first set up backups, after any change to the backup tool or hosting, and regularly after that. Quarterly is a sensible starting point for many small sites; busier sites may want to test more often.

Should backups be encrypted?

Yes, especially offsite copies. Backups contain the same personal data as your live site, such as customer and user details. CISA recommends offline, encrypted backups as part of ransomware preparation.

Final Thoughts

A solid WordPress backup strategy is not complicated. Back up both files and database, as often as your site changes, following the 3-2-1 rule. Store at least one encrypted copy away from your host, keep enough history to go back before a hidden problem began, and test restores regularly. Then you will know, rather than hope, that you can recover.

Backups are a core part of looking after a site. If you would rather someone set them up, monitor them and test restores for you, that is included in my website maintenance service.

Official References

Sources checked on 29 October 2026: