Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Backups & maintenance · Explainer

How Often Should You Back Up WordPress?

Short answer

Back up daily if your site changes most days, weekly if it rarely changes, and always before an update, move or redesign. WordPress itself suggests weekly backups for smaller sites and daily backups for high-activity sites. The right schedule is the one where losing the work since the last backup would not hurt.

Key takeaways

  • WordPress suggests weekly backups for small sites and daily backups for busy ones.
  • Always back up before an update, a move, a theme change or a redesign.
  • Files and database need separate schedules, since they change at different speeds.
  • Keep at least 3 to 5 recent copies in different places.
  • A store or booking site may need hourly or real-time backups, not daily ones.
  • A schedule means nothing until you check that a restore works.

How often should you back up WordPress?

Back up daily if your site changes most days, weekly if it rarely changes, and always before any update.

The gap between backups is the work you can lose. If you post once a week, a weekly backup loses at most a week of work, but if you take orders each day, a daily backup can still lose a full day of sales.

WordPress gives a simple starting point in its handbook, and the rest of this guide turns it into a schedule for your kind of site. The WordPress handbook suggests weekly backups for smaller sites and daily backups for high-activity sites (Backups).

Downtime and lost work cost real money and trust, which is why the schedule matters more than the tool. Our guide to website downtime statistics shows how often sites go down and what it costs.

What does WordPress itself recommend?

WordPress suggests weekly backups for smaller sites and daily backups for high-activity sites as of November 2026.

The handbook says the choice depends on how often you blog and how you would feel if your database were lost along with a few posts. That feeling is the real test: if losing a week of posts would hurt, back up more often than weekly (Backups).

The same page gives one rule with no exceptions: back up your database regularly, and always before an upgrade. An update is the most likely moment for a site to break, so the backup before it matters most.

The handbook also says to check automatic backups with a manual backup once in a while, so a silent failure does not leave you with nothing. A schedule that stopped running months ago is worse than no schedule, because it feels safe.

Ask what changes fastest on your site before you pick a number. Posts and orders change the database each day on a busy site, while a brochure site may go weeks without a single edit. Your answer should follow the fastest-changing part, not the slowest.

How does your site type change the answer?

The busier your site, the shorter the gap between backups should be.

Site typeSuggested scheduleWhy
Personal blog, a few posts a monthWeeklyLittle new work to lose
Business site with weekly postsDailyPosts, pages and enquiries change often
Online storeHourly or real-timeEach order is money that cannot be remade
Membership or course siteDaily, or hourlyLesson progress and signups change daily
News or community siteDaily, or hourlyComments and posts arrive all day

A store shows why daily is not always enough. Jetpack notes that VaultPress Backup saves each change as it happens, so a new order is never a day old in the backup (VaultPress Backup).

If real-time backups fit your store, our guide to whether Jetpack VaultPress Backup is worth it weighs the trade-offs.

You can also check how much Jetpack VaultPress Backup costs before you pick a plan.

A quiet brochure site can stay on weekly backups, but only if nothing on it changes between backups. Contact form entries, comments and small edits all count as changes, so count them before you pick weekly.

Should files and database run on the same schedule?

No, run them on separate schedules, because the database usually changes faster than the files.

The developer handbook explains that a full backup needs both parts: files hold themes, plugins and uploads, while the database holds posts, comments and settings. Treat files and database taken around the same time as one backup set (Backups).

A daily database backup with a weekly files backup suits many blogs. New posts change the database each time, while themes and plugins change only when you update them.

For a store, run both daily at least, since new orders change the database and new product images change the files. If either part is stale, the restore may not match the live site.

Keep the two parts close in time. A files backup from last month paired with a database backup from today can clash, since the database may point at images or plugins that the files copy does not hold.

How often should you back up before updates and changes?

Take a fresh backup before every update, theme change, move or redesign, even if the last scheduled backup ran an hour ago.

WP Engine advises making a fresh checkpoint before updates, so you can revert fast if something breaks. Its daily checkpoints run on their own, yet a manual checkpoint right before the change is the one you will restore from (Backup and Restore).

SiteGround gives the same advice in its knowledge base: back up before any major change, such as an update, migration or redesign, and back up regularly if your content changes often (How to download a full backup).

Make the backup part of the change itself, not a step you do when you remember. Update the plugin, then check the site, and keep the backup until you are sure the change worked.

The same rule holds for moves and staging pushes. Kinsta makes a system backup before staging pushes and other risky steps, so a push that goes wrong can be undone. Your own manual backup before the push gives you a second way back.

How many backups should you keep?

Keep at least 3 to 5 recent backups, stored in different places, so one bad or missing copy does not leave you with nothing.

The WordPress handbook suggests keeping 3 to 5 recent backups, with copies in different places, such as the host, cloud storage and your own computer. If one copy fails or is lost, another can still work (Backups).

Old copies matter when a problem is found late. Malware can sit in a site for weeks, so a single recent backup may hold the same bad code as the live site.

Host copies age out fast, so your own copies fill the gap. Hostinger keeps weekly backups for 6 weeks and daily backups for 7 days, then removes older copies for good (How to download backups at Hostinger).

Our guide to whether Hostinger includes backups lists its retention limits in more detail.

More copies need more space, so watch the size of each backup as your site grows. A large media library can make daily full backups heavy, and that is when a tool with incremental backups, which only stores what changed, earns its keep.

How do you set a schedule with a plugin?

Set the schedule in your backup plugin, point it at cloud storage, and run one manual backup to confirm it works.

  1. Install UpdraftPlus from Plugins > Add New in your WordPress dashboard.
  2. Open Settings > UpdraftPlus Backups, then the Settings tab.
  3. Set Files backup schedule and Database backup schedule to match your site type.
  4. Pick remote storage, such as Google Drive or Dropbox, and save the settings.
  5. Click Backup Now and check that the copy lands in your cloud storage.

UpdraftPlus lists more than 4 million active installs on WordPress.org as of November 2026, and its free version can run on a schedule from every 2 hours to monthly. It can send copies to Dropbox, Google Drive, Amazon S3, FTP or email (UpdraftPlus).

When the schedule runs, you can restore from the same screen. Our guide to restoring a backup with UpdraftPlus shows the steps.

If the first run fails, our guide to fixing UpdraftPlus backup failures covers the common causes.

Check the first scheduled run the next day, not next month. Open the cloud folder, confirm the new files arrived, and note the time they landed. A schedule that runs but never sends the copy off site is the same as no schedule at all.

What mistakes should you avoid?

Avoid one schedule for every site, long gaps on busy sites, and a plan you never check.

  • Backing up weekly when your store takes orders every day.
  • Keeping every copy on the same server as the site.
  • Letting the oldest copy age out before you notice a hack.
  • Skipping the backup before an update because the last one ran yesterday.
  • Never restoring a copy to see if it works.
  • Setting a schedule, then never checking that the copies reach your cloud storage.
  • Forgetting to back up the database when you only copy the files.

Frequently asked questions

How often should a small blog back up?

Weekly is enough for a small blog that posts a few times a month, as long as you also back up before every update. WordPress itself suggests weekly backups for smaller sites. If comments or form entries arrive daily, switch the database backup to daily, since those entries live in the database.

Do I need to back up every day if I rarely post?

No, weekly can be fine if the site truly rarely changes. Check what changes between backups: comments, form entries, small edits and new media all count. If any of those arrive most days, move the database backup to daily and keep the files backup weekly.

Should I back up more often during a redesign or migration?

Yes, back up before each step, not just once at the start. Take a copy before the move, another after the move works, and one more after the redesign goes live. Keep the pre-move copy until you are sure the new site works, since it is your way back.

How long should I keep old backups?

Keep at least 3 to 5 recent backups, stored in different places, as WordPress suggests. Keep them longer if you can, since a hack found late may sit in every recent copy. Host copies age out fast, so your own off-site copies are the ones that last.

What if my host already backs up daily?

A host copy is a good start, but it is not a full plan. Hosts often keep daily backups for only 7 to 30 days, and some charge for downloads. Add your own scheduled copy in cloud storage you control, and check now and then that a restore works.

Sources

  1. Backups — Advanced Administration Handbook WordPress Developer Resources
  2. Backup and Restore WP Engine Support
  3. How to download a full backup of my website? SiteGround Knowledge Base
  4. How to download backups at Hostinger Hostinger Support
  5. VaultPress Backup: Real-Time WordPress Backups Jetpack
  6. UpdraftPlus: WP Backup & Migration Plugin WordPress.org

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test