A backup plugin has been quietly running on your site for a year. Nobody has ever opened the file it produced. That’s not a backup strategy — it’s a folder of untested assumptions, and the first time you actually need it is the worst possible moment to find out it doesn’t work.
Knowing how to backup a WordPress site is easy: install a plugin, pick a schedule, done in ten minutes. Knowing that the backup will actually restore your site — cleanly, completely, on the day you need it — takes a bit more discipline. This guide covers the 3-2-1 rule for WordPress, the real difference between full and incremental backups, how to pick a plugin, and the restore test almost everyone skips.
What Is the 3-2-1 Backup Rule for WordPress?
The 3-2-1 rule means keeping 3 total copies of your site, on 2 different types of storage, with 1 copy stored off-server. For WordPress specifically: your live site counts as copy one, a plugin backup sent to cloud storage counts as copy two, and a separate host-level snapshot counts as copy three.
The part site owners get wrong most often is the “off-server” piece. A backup plugin that saves files to the same hosting account as the live site protects you from a bad plugin update — it does nothing if the server itself goes down, gets hacked, or gets suspended by the host.

What’s the Difference Between Full, Incremental, and Differential Backups?
A full backup copies every file and database table every time it runs. An incremental backup copies only what changed since the last backup of any kind. A differential backup copies everything that’s changed since the last full backup, so each one grows larger until the next full backup resets it.
| Backup Type | What It Copies | Storage Use | Restore Speed |
|---|---|---|---|
| Full | Every file + full database, every run | Highest | Fastest — one file to restore |
| Incremental | Only changes since the last backup (full or incremental) | Lowest | Slowest — rebuilds step by step through a chain |
| Differential | Everything changed since the last full backup | Grows between full backups | Moderate — needs the last full + one differential |
Incremental backups can cut storage use dramatically compared to running a full backup every day — Duplicator, one of the plugins that offers the feature, documents reductions of up to roughly 97% for sites with infrequent content changes. The tradeoff is restore complexity: rebuilding from an incremental chain means the tool has to replay every step in order, and a single missing link breaks the chain.
For most small-to-midsize WordPress sites, the practical answer is a weekly full backup as the anchor, with daily incremental or database-only backups filling the gaps in between.
What Does a Complete WordPress Backup Actually Include?
A backup that only grabs the database, or only grabs the files, isn’t complete — restoring it gets you a broken site. A full WordPress backup needs both halves:
- The database — every post, page, product, comment, user account, and setting stored in MySQL. This is where WooCommerce orders and form submissions live.
- The
wp-contentfolder — themes, plugins, and theuploadsdirectory (every image and media file ever added). - Core WordPress files — lower priority since they’re identical across every install of the same version, but useful for a faster full restore.
- The
wp-config.phpfile — not always included by default in every plugin; store it separately if not, since it holds database credentials and salts a restore needs.
Skipping the uploads folder is the single most common incomplete-backup mistake — the site “restores” but every product photo and blog image comes back as a broken link.
Which WordPress Backup Plugin Should You Use?
The three most-used dedicated backup plugins take different approaches to where backups actually live, which matters more than any feature checklist.
| Solution | Where Backups Live | Free Tier | Real-Time Backups | Starting Price | Best For |
|---|---|---|---|---|---|
| UpdraftPlus | Your own cloud storage (Google Drive, Dropbox, S3, FTP) | Yes | No | ~$70/year for 2 sites | Sites that want full control over storage and already have a Google Drive or Dropbox account |
| BlogVault | BlogVault’s own remote servers, separate from your host | Trial only | No, but frequent scheduled runs | ~$49/year (1–2 sites) | Agencies managing several client sites who want backups fully off the host |
| Jetpack VaultPress Backup | Automattic’s cloud, via Jetpack | No | Yes | ~$60–120/year | WooCommerce stores where losing even one order between backups is unacceptable |
| Host-level snapshots (WP Engine, Kinsta, SiteGround, etc.) | The host’s own infrastructure | Included in hosting | Varies, usually daily | Included in plan | A convenient second copy — not a substitute for an off-host backup |
Pricing above reflects each vendor’s published rate as of July 2026 — confirm the current figure before quoting a client, since backup vendors adjust tiers a few times a year. Notice that host-level snapshots don’t satisfy the “off-server” leg of the 3-2-1 rule on their own: if the host’s account is compromised or suspended, both the live site and its snapshot are affected together. Pair one with a plugin sending copies somewhere else entirely.

How Do You Set Up Automatic WordPress Backups?
- Pick a destination away from your host — Google Drive, Dropbox, Amazon S3, or a service like BlogVault that stores copies on its own servers.
- Install a backup plugin (or confirm your host’s built-in snapshot tool) and connect it to that storage destination.
- Schedule database backups daily — this is the lightest, fastest backup and covers most day-to-day content changes.
- Schedule full-file backups weekly, or immediately after installing a new plugin or theme.
- Set retention to keep 3–5 recent backups, not just the latest one — a corrupted or incomplete backup is only a problem if it’s your only copy.
- Turn on failure notifications by email or Slack. A backup job that’s been silently failing for two months is worse than having no backup plugin at all, because it creates false confidence.
Backups are one of the few WordPress maintenance tasks that automate almost perfectly once configured — our breakdown of what you can and can’t automate on a WordPress maintenance schedule covers where that reliability starts to run out for other tasks. It also fits into a broader WordPress maintenance task checklist alongside updates, uptime monitoring, and security scans.
Why Do Most WordPress Backups Fail When You Actually Need Them?
Most WordPress backups fail at the restore step, not the backup step — because nobody ever tested whether the backup file actually works until the site was already down. A corrupted archive, a missing database table, or credentials that changed since the last backup all look completely fine sitting in a folder and only reveal themselves mid-emergency.
Backup plugins are good at the copying part; almost none of them verify that a restore actually works. That verification step is the owner’s job, and it’s the one step a “set and forget” backup schedule skips by design.
How Do You Test a WordPress Backup Restore?
- Spin up a staging copy of the site using your host’s staging tool or a plugin like WP Staging — never test a restore on the live site.
- Restore your most recent backup onto that staging environment and note how long the process actually takes.
- Click through the pages that matter most — homepage, checkout or contact form, and your highest-traffic landing page.
- Confirm the database restored correctly by checking a recent post, order, or form entry dated after the backup was taken.
- Write down the restore time. That number — not the vendor’s marketing claim — is your real recovery time if the site goes down today.
Run this quarterly, and always before a major plugin update, theme change, or hosting migration. It’s also the first thing to check before you migrate your website to a new host — a fresh, tested backup is cheap insurance against a migration that goes sideways halfway through.

How Often Should You Back Up a WordPress Site?
Match backup frequency to how often content actually changes, not a generic default:
- E-commerce and membership sites: real-time or at minimum every few hours — every missed backup window is a potential lost order.
- Active blogs or news sites: daily database backups, weekly full backups.
- Brochure or low-update sites: weekly database backups, monthly full backups is usually enough.
- Before any update, migration, or code change: always take a manual backup first, regardless of your regular schedule.
If your site does get compromised despite all of this, a tested, off-server backup is the difference between a bad afternoon and a bad month — our step-by-step WordPress hack recovery plan assumes you already have one ready to restore from.
Not confident your current backup would actually restore cleanly? Web Help Agency’s WordPress site maintenance service includes managed off-server backups with quarterly restore testing built in, so nobody finds out the backup was broken on the day it mattered. We’ve run this across 500+ projects and hold a 5.0 rating on Clutch from 41 reviews.
Frequently Asked Questions
Daily database backups plus weekly full-file backups cover most sites. E-commerce stores should back up more frequently — ideally in real time — since every gap between backups is a potential lost order or customer record.
Most backup plugins include a one-click restore for straightforward cases. A developer becomes necessary when the restore fails partway through, the site has custom server configuration, or the backup needs to move to different hosting entirely.
Yes. Host-level snapshots live on the same infrastructure as your site, so they don’t protect you if that host account is compromised, suspended, or has an outage. Pair them with a plugin sending copies to separate cloud storage.
Keep at least 3–5 recent backups rather than just the latest one. Malware or content corruption sometimes goes unnoticed for days or weeks, and a single very recent backup can end up restoring the same problem.
A WordPress export (via Tools → Export) only saves posts, pages, and comments as an XML file — no themes, plugins, media files, or settings. A backup captures the entire site and database, which is what you need for a real disaster recovery restore.
Yes — restoring rolls the entire database back to the moment the backup was taken, including any orders, comments, or form entries submitted after that point. This is exactly why real-time or high-frequency backups matter for stores and lead-gen sites.
You Might Also Find Useful
- Automated WordPress maintenance — what backup automation covers and where human judgment still matters
- WordPress maintenance tasks — the full recurring checklist backups fit into
- WordPress site hacked? A recovery plan — the runbook a tested backup makes possible
- Migrate your website to a new host — why a fresh backup comes first
- WordPress site maintenance services — managed backups with restore testing included
