Skip to content

How often a website should be backed up

Up to date as of 20 November 2026

There's no single right schedule. The WordPress handbook says it depends on how often you publish and how often you want to do it. It also depends on how you'd feel if your database were lost along with a few posts.1

That last part is the real test. Ask what you'd have to redo if the site went back to its last copy.

Three common rhythms

Rhythm Suits Cost of getting it wrong
Weekly A site that changes rarely, such as a club page with a few posts You could lose up to a week of changes
Daily A site with a lot of new posts, comments or orders A day's changes at most, but more copies to store
Before every change Any site, ahead of updates, moves or edits One-off copies pile up if you never clear them

The handbook's general suggestion matches the first two rows. Smaller sites with fewer posts, once a week. High-activity sites with many posts, daily.1

The table's right-hand column is simple arithmetic about change. It isn't from a source. The NCSC says the same thing from the other direction: the more often backups are made, the less data you lose if you have to recover.2

Before a change

The handbook says to back up your database regularly, and always before an upgrade.1 The same page says to back up before a move to a new location.1

A scheduled backup may be hours old when you click "update". A one-off copy right before gives you a clean point to return to.

Choosing a backup rhythmNote how often the site changesDecide how much you'd redoPick a scheduleAdd one before big changes
Start from how much change you could lose.

Let it run on its own

A backup you have to remember tends to get skipped. CISA's advice is to choose a backup solution that runs automatically and regularly.3

The WordPress handbook agrees that backups can be automated, with a catch. It recommends backing up those automatic backups manually once in a while, to confirm the process is working.1

A way to decide

Work through these questions in order:

  1. How often does the site change? Posts, comments, orders and form entries all count.
  2. How much could you rebuild by hand? Retyping one post is different from losing a week of orders.
  3. Does the platform let you schedule copies? If so, set the rhythm there.
  4. Are any big changes coming, like updates or a move? Plan a one-off copy first.

If you're unsure, pick the shorter gap. A daily copy of a quiet site costs a little storage. A weekly copy of a busy shop can cost real work.

What frequency doesn't fix

A frequent backup that sits on the same server as the site is still one copy in one place. The page on storage places covers that. And a frequent backup that has never been restored is untested. See testing that a backup restores.

Your host may also keep only a limited number of days of its own copies, which limits how far back you can go. The host-or-own comparison has a worked example from one host's documentation.

Sources used

  1. Backups – Advanced Administration Handbook, WordPress Developer Resources
  2. Offline backups in an online world, National Cyber Security Centre (UK)
  3. Back Up Business Data, CISA (US Cybersecurity and Infrastructure Security Agency)