How many WordPress backups should you keep? There’s no single number that fits every site. Your policy should mainly let you return to a healthy, reasonably recent, and complete copy when you discover a problem.
The WordPress backup retention Retention therefore isn’t just about accumulating archives. It arranges for recent copies for everyday mistakes, and older copies for problems discovered later.
WordPress recommends adjusting frequency to the site’s activity level. The documentation suggests weekly backups for a small, low-activity site and daily backups for a very active site. It also recommends keeping at least three to five recent copies in different locations. See the official guide on WordPress backups for details.
Start by distinguishing frequency and retention
Frequency answers this question: how often do you create a new backup? Retention answers this one: how long do you keep each copy before deleting it?
For example, a daily backup with seven-day retention lets you roll back a week. It won’t help you restore a version from two months ago.
Conversely, keeping a monthly backup for a year doesn’t reduce the amount of data lost between copies. An old archive is useful to recover a previous state. It doesn’t replace a recent copy.
Your strategy should therefore combine multiple horizons. That’s the principle of rotation: you keep more recent copies and fewer copies as they age.
What a retained copy must contain
A retention policy is worthless if your archives are incomplete. To restore a typical WordPress site, you must keep the files and the database that correspond to the same point in time.
The database contains content, comments, and settings, among other things. The files include themes, plugins, uploads, and important files such as wp-config.php. The documentation on backing up WordPress files notes that the database is usually located outside the WordPress directory and that a copy of the files generally does not include it.
Keep each backup as an identifiable set: files, database export, date and time. Avoid keeping an isolated SQL export without knowing which files it corresponds to.
A concrete retention policy based on your site
The following profiles are reasonable starting points. Adjust them according to the actual frequency of changes, the time it takes to notice an error, and the available storage space.
| Site type | Daily copies | Weekly copies | Monthly copies |
|---|---|---|---|
| Low-change brochure site | 7 days | 8 weeks | 12 month |
| Active blog or content site | 14 days | 8 weeks | 12 month |
| Store or site with frequent transactions | 30 days | 12 weeks | 12 month |
These durations are not universal requirements. They provide a simple framework: a short zone for recent incidents, an intermediate zone for errors discovered after a few weeks, and a long zone for larger rollbacks.
For a rarely changed brochure site
A brochure site often receives little new content. You can therefore prioritize backups before each update, extension addition, theme change, or server intervention.
Also keep your scheduled copies. A configuration error, a media deletion, or an unintended change can go unnoticed for several days. Before an update, also follow the precautions described in the method for updating WordPress without breaking your site.
For a blog or active content site
If you publish regularly, daily backups generally become the practical minimum. Weekly and monthly copies then prevent having to keep every daily archive for a long period.
Add an on-demand backup before major changes. Name it clearly, for example «before-homepage-redesign» or «before-extension-update.» Exclude it from automatic deletion for the time needed to validate the changes.
For a WooCommerce store
A store accumulates orders, customer accounts, and sometimes renewals. Backup frequency should follow the volume of activity, especially for the database.
A restore can create a gap between the chosen copy and the current state. WooCommerce documentation notes that a restore can remove orders, accounts, or data collected during that period. See the restoration risks with WooCommerce Subscriptions if your site uses subscriptions.
In this context, keeping thirty daily backups does not make up for insufficient frequency. If your store receives multiple orders per day, first determine the maximum data loss you can accept. Then configure a cadence that meets that objective.
Keep copies that precede an incident longer
Too short a rotation poses an obvious risk: you might delete the last healthy copy before detecting a hack or corruption. This is especially important when an issue appears several days after its occurrence.
The WordPress security guide illustrates this risk with a site compromised on May 1st but detected only on 12 May. Older regular snapshots can then provide a copy from before the compromise. See the section on hardening WordPress security, which also recommends testing backups and keeping snapshots in a reliable location.
After an incident, temporarily suspend automatic deletion. First identify the last known-good backup. Also keep a few copies from before and after, as they can help determine when the problem began.
Calculate space before setting retention periods
Measure the actual size of a full backup, then multiply it by the number of planned copies. Do this calculation separately for daily, weekly, and monthly backups.
For example, if a full copy uses 2 GB, fourteen daily copies require about 28 GB before any other archives. This simple calculation prevents discovering too late that your space is full and new backups are failing.
Also check what your tool actually deletes. Some tools treat archives as complete sets. Others may produce separate files. Never delete a single part of a backup without confirming that restoration will still be possible.
Automate rotation, but protect exceptions
Your backup tool or host can often delete the oldest archives based on a defined limit. This automation simplifies maintenance, provided you verify that a new full backup succeeded before cleanup.
- Keep at least three to five recent full backups.
- Keep daily, weekly, and monthly copies according to your profile.
- Create a manual copy before a major change.
- Temporarily protect copies related to a migration, redesign, or incident.
- Monitor used space and execution logs.
Finally, a retained archive is only useful if you can restore it. Plan a periodic verification in a controlled environment by following this guide to testing a WordPress backup restore. .









