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

Incremental vs Full Backups for WordPress

Short answer

A full backup copies every file and database table included in the backup each time it runs. An incremental backup copies only the files and database changes made since the previous backup, so each run is smaller and faster. Use full backups as regular starting points and incremental backups between them when your site changes often.

Key takeaways

  • A full backup copies everything in the backup each time, so it is the simplest restore point.
  • An incremental backup copies only changes since the previous backup, which keeps each run small.
  • A standard incremental restore needs the full backup plus every increment in the chain, in order.
  • A differential backup copies all changes since the last full backup, so it grows until the next full backup.
  • UpdraftPlus Premium runs incremental backups for files, while the database follows its own schedule.
  • Jetpack runs a daily full backup plus real-time backups when posts, orders or settings change.

What is a full backup in WordPress?

A full backup is a copy of every file and database table included in the backup, made in one run.

Your files cover themes, plugins and uploaded media, while the database holds posts, pages, comments and settings. TeamUpdraft notes that a full backup copies all of this each time it runs, even when only a small amount has changed.

The WordPress Developer Resources handbook adds that you need both parts to fully restore a typical site, because downloading the files alone does not back up the database.

A full backup is the simplest restore point because one set holds the whole site at one moment.

If a restore from a full backup fails, our guide to fixing a failed UpdraftPlus backup walks through the common causes.

Full backups take longer and use more storage as a site grows. A site with a large media library can spend a long time copying files that have not changed since the last backup.

What is an incremental backup in WordPress?

An incremental backup copies only the data that has changed since the previous backup, not the whole site again.

BlogVault defines it the same way: an incremental backup holds data changed or created since the last backup, whether that backup was full or incremental.

TeamUpdraft gives a plain example. If 1 GB of files changes by only 20 MB, the next incremental backup only needs to capture those 20 MB.

Changed data can mean new or edited files, database updates, deleted items and renamed items. BlogVault notes that a file-based tool may copy a whole changed file, while a block-based tool may copy only the changed part of a large file.

That smaller size is the main appeal. Each run moves less data, so it often finishes faster and uses less storage than another full copy.

Incremental backups are not a different kind of data. They are a different way of choosing what to copy on each run, and they still need a full backup to start from.

How does an incremental backup chain work?

An incremental backup chain starts with one full backup, and each later backup adds only the changes since the backup before it.

TeamUpdraft shows the chain as a full backup, then increment 1, increment 2, increment 3 and increment 4. To restore the point at increment 4, the tool uses the full backup plus the increments in the chain.

BlogVault gives a weekly example for a store. A full backup runs on Sunday, then one change-only backup runs each evening, and restoring Friday needs Sunday plus the Monday to Friday increments in order.

Restoring only Friday's increment would not rebuild the store. It holds changes since Thursday, not the starting site or the earlier changes.

Some services hide this chain from you. BlogVault notes that a service can combine the parts into one restore point, so you should confirm how your tool presents each date before you rely on it.

Our guide to restoring a backup with UpdraftPlus explains how to pick a restore point and check the result.

How do full, incremental and differential backups compare?

Full backups copy everything, incremental backups copy changes since the previous backup, and differential backups copy all changes since the last full backup.

TeamUpdraft uses one week to show the gap. With 10 MB of new changes on Tuesday, 20 MB on Wednesday and 30 MB on Thursday, incremental runs hold 10, 20 and 30 MB.

Differential runs for the same week hold 10 MB on Tuesday, 30 MB on Wednesday and 60 MB on Thursday, because each one repeats every change since Monday's full backup.

Backup typeWhat each run copiesStorage per runRestore needs
FullEverything includedHighestOne backup set
IncrementalChanges since the previous backupLowestFull backup plus each increment in order
DifferentialAll changes since the last full backupGrows until the next full backupFull backup plus the latest differential

A full backup is usually the slowest run and the simplest restore. An incremental backup is usually the fastest run, but its restore depends on the chain staying intact.

A differential backup sits between the two. It needs fewer sets than a long incremental chain, but each run grows as changes pile up since the last full backup.

How much storage can incremental backups save?

Incremental backups can cut storage sharply when only a small share of a site changes between runs.

TeamUpdraft works through a plain case. Ten full backups of 1 GB of files would need about 10 GB of storage, while one 1 GB full backup plus nine incremental backups of 50 MB each would need about 1.45 GB.

The same idea shows up in a daily example. TeamUpdraft starts with a 2 GB full backup on Monday, then adds 50 MB on Tuesday, 20 MB on Wednesday and 15 MB on Thursday.

Your own savings will vary with compression, how much changes and how your tool stores each increment. A site that changes little between runs saves the most.

Storage is only part of the gain. Smaller runs also mean less data to move to remote storage, which can help when you pay for that storage or back up often.

When should you use incremental backups?

Use incremental backups when your site changes often, is large, or runs on limited hosting resources.

TeamUpdraft lists the best fits: frequently updated sites, large sites, media-heavy sites, WooCommerce stores and sites managed by an agency for many clients.

A store is a clear example. Orders, stock levels, product images and settings can change all day, and copying the whole site after each change would waste time and storage.

BlogVault adds that smaller jobs may allow more restore points, which cuts how much recent work a failure can take from you. That only helps if you watch for failed runs and check the restore points.

  • A blog that publishes daily and adds images most days
  • A WooCommerce store with orders through the day
  • A membership site with new sign-ups and content
  • A large site with several gigabytes of media

If your site fits one of these cases, pair a regular full backup with frequent incremental runs between full backups.

If you use Jetpack instead, our guide to Jetpack VaultPress Backup costs lists the pricing for its backup plans.

When is a full backup the better choice?

A full backup is the better choice when your site rarely changes or when you want the simplest possible restore.

A small brochure site that changes once a month gains little from incremental runs. A scheduled full backup gives it one clear restore point with no chain to manage.

Full backups also suit the moment before risky work. The WordPress Developer Resources handbook says to back up your database regularly and always before an upgrade, and a fresh full backup is the safest starting point for that.

BlogVault agrees that a small site that rarely changes may prefer automated full backups instead of change-only runs.

Jetpack takes this approach by default. Its support pages say Jetpack runs a daily full backup and adds real-time backups when posts, pages, comments, media, themes, plugins, settings or users change.

Our review of Jetpack VaultPress Backup covers its plans and restore options in more detail.

How do you set up incremental backups with UpdraftPlus?

In UpdraftPlus Premium, you start with a full backup, then schedule incremental backups to capture file changes between full backups.

The manual route is short. Open Settings, then UpdraftPlus Backups, run a full backup with Backup Now, then click the link under it that reads Add changed files (incremental backup). The UpdraftPlus docs show each of these steps.

You then choose what to include, such as plugins, themes, uploads and other folders inside wp-content, and click Backup Now on the pop-up.

For a schedule, open the Settings tab and set how often full backups run and how many to keep. Then set incremental backups to run every hour, every 2, 4, 8 or 12 hours, or daily.

The database follows its own schedule in UpdraftPlus Premium. TeamUpdraft notes that incremental backups apply to files, while database backups run on the schedule you set for the database.

If you prefer the command line, run a full backup with wp updraftplus backup, then add --incremental for later runs.

How do you check that your backups will restore?

You check a backup by restoring it somewhere safe, such as a staging site, and confirming the site works there.

BlogVault recommends testing recovery in a separate location and checking the admin area, pages, media, forms, logins and key business functions.

WordPress guidance also says to back up automatic backups with a manual backup once in a while, to confirm the process is working. The WordPress Developer Resources handbook gives that advice in its backup pages.

Keep at least 3 to 5 recent backups, as the WordPress handbook advises, so one damaged set does not leave you with nothing to restore.

Check the backup list after each scheduled run. A success message only says the job reported completion, so confirm the expected files, database data and restore point are present.

  • The restore point date matches the run you expect
  • The database file is present and has a recent timestamp
  • Uploads, themes and plugins are listed in the set
  • The staging copy lets you log in and view pages

What mistakes should you avoid?

The most common mistake is treating an incremental backup as a full copy of your site.

  • Deleting the starting full backup while increments still depend on it
  • Keeping only one recent backup, so a damaged set leaves no restore point
  • Backing up files but forgetting the database
  • Never restoring a backup until an emergency forces you to try
  • Storing the only copy on the same server as the site

BlogVault warns that a standard restore may need the full backup and every needed increment, so a missing or damaged part can slow or block recovery.

Retention can cause the same problem. BlogVault notes that keeping only recent versions can remove an older restore point you still need, such as when a problem goes unnoticed for days.

Host backups have their own limits too, as our comparison of UpdraftPlus vs host backups explains.

If you are unsure whether your chain is sound, take a fresh full backup now and confirm it restores on a staging copy before you delete older sets.

Frequently asked questions

Can you restore a single incremental backup by itself?

Usually not in a standard chain. A single increment holds only the changes since the backup before it, so a restore needs the starting full backup plus each increment up to that point, in order. Some services combine the parts into one restore point, so check how your tool handles restores before you rely on it.

Do incremental backups cover the WordPress database too?

It depends on the tool. In UpdraftPlus Premium, incremental backups apply to files, while the database follows its own schedule, so you set database frequency separately. BlogVault and Jetpack cover database changes as part of their backup runs. Always confirm that your setup backs up both files and the database.

How often should you take a full backup if you use incremental backups?

Take a fresh full backup on a regular cycle, such as weekly for an active site, and run incremental backups between full backups. A new full backup also makes sense before an upgrade, a migration or a large bulk edit. Shorter cycles keep the chain shorter and easier to restore.

Are incremental backups safe for WooCommerce stores?

Yes, when the setup covers the database as well as files, because orders and stock live in the database. Jetpack backs up WooCommerce orders in real time, so restoring to an earlier point does not erase an order placed after it. Test a restore on staging to confirm orders, products and checkout still work.

What happens if one increment in the chain is missing or damaged?

A standard restore can fail or stop at the last good increment, because later increments build on the ones before them. That is why you should keep the starting full backup until the chain is replaced, watch for failed runs, and take a fresh full backup if any part of the chain looks wrong.

Sources

  1. How Incremental Backups Save Time and Storage in WordPress TeamUpdraft
  2. Create incremental backups in WordPress TeamUpdraft Documentation
  3. Incremental Backup: How It Works, With Examples and Pros and Cons BlogVault
  4. Back up your site with Jetpack VaultPress Backup Jetpack
  5. Backups WordPress Developer Resources

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