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

Getting started · Guide

How to back up WordPress

Short answer

To back up WordPress, copy both the files (themes, plugins, uploads) and the database, store the copy somewhere other than your web server, and run it on a schedule that matches how often the site changes. A backup only counts once you have restored it to a staging site and logged in.

How to back up WordPress
How to back up WordPress

A backup is a restore you have already done once. Files, database, somewhere else, on a schedule that matches how fast the site changes.

What you'll doPut a restorable copy off the server and prove it works
Time neededAbout an hour, plus a test restore
DifficultyBeginner
Tools neededOne backup plugin and storage that is not the same server

Key takeaways

  • A full backup is files plus database. A posts-only XML export is not a backup.
  • Keep at least one copy off the server, so it survives a suspended account or a dead disk.
  • Run one backup plugin. Two plugins lock tables and fill the disk.
  • Match the schedule to change: weekly for a brochure site, several times a day for a store.
  • Test a restore on staging before you need it.
  • On UpdraftPlus, run 1.26.13 or 2.26.13 or newer after the October 2026 UpdraftCentral incident.
Jump to

1What does a WordPress backup need to include?

A complete WordPress backup includes the files and the database, stored somewhere that survives the server.

A WordPress backup is not a feeling. It is the files and the database, stored somewhere that does not die when the site dies, plus a method that gets them back. The files are the themes, plugins, and uploads.

The database is the posts, orders, users, and settings. Miss either one and the restore is a brochure with no content, or content with no pictures and no code.

A plugin that says “backup” and only exports an XML file of posts is not a backup of the site.

The second half is the failure you are buying insurance for. If the host suspends the account, a copy inside that account is gone. If wp-admin is a white screen, a restore button that only exists inside wp-admin will not start.

If the site is a store, a nightly archive can lose a day of orders. Name the failure first. The backup plugin list is ranked around that question, which is why BlogVault leads for off-server restores and UpdraftPlus leads when you need a real free plan.

Note. Backup duration and memory are still marked testing in progress on the reviews. This guide is about the shape of a restore plan, not a stopwatch.

2Which WordPress backup plugin should you use?

Use one backup plugin: BlogVault when downtime is expensive, UpdraftPlus when you need a solid free option.

Two backup plugins will lock tables, fill the disk, and leave you with two archives that disagree about what “yesterday” means. Choose one. Use the list, or the short comparison UpdraftPlus vs BlogVault, and then stop shopping.

BlogVault pulls an incremental copy onto its own infrastructure and can restore when the dashboard is dead. That is the right product for a store, a membership, or any business site whose downtime costs more than the subscription. There is no ongoing free plan.

Budget the invoice, and know that the history lives with the vendor until you export a copy.

UpdraftPlus is the free plugin we still install on a small site. It schedules files and database to Google Drive, Dropbox, S3 and similar, and the restore from a living wp-admin is clear.

In October 2026, connection keys for UpdraftCentral — the remote dashboard, not the zip format — were stolen and used to plant plugins on sites that had an active remote connection.

Update to 1.26.13 or 2.26.13 so old keys are revoked, reset the vendor password, and look for admin users you did not create. Sites that never turned UpdraftCentral on were outside that path. We still recommend the plugin.

We do not recommend skipping the update.

WPvivid is the budget alternative when you want staging on the free tier or a lifetime licence later. Jetpack VaultPress Backup is the real-time pick, including on the paid backup product rather than only a top bundle, if you already accept a WordPress.com account.

Duplicator is what you open on moving day because the installer can boot on an empty host. It is a poor daily driver if the free version does not schedule and nobody remembers to press the button.

Solid Backups makes sense inside a SolidWP licence and is easy to confuse with old BackupBuddy tutorials. Read the current name before you install.

Warning. Do not keep the old backup plugin “just in case” after you switch. Deactivate and delete it once the new one has a successful test restore.

3How often should you back up WordPress, and where should the copy go?

Back up as often as the site changes, and send every copy to remote storage, not the same server.

A backup you have to remember is a backup you will not have on the week you need it. Set a schedule that matches how fast the site changes. A brochure can be weekly.

A blog that publishes most days can be daily. A store should ask how many orders you can stand to retype. If the answer is “none”, nightly is the wrong product and you want BlogVault’s WooCommerce plan or Jetpack’s real-time backup.

A membership or course site has the same problem: logged-in activity does not wait for your cron.

The destination matters more than the logo. Storage you control — Drive, Dropbox, S3 — means you can fetch the archive without the host and without the plugin vendor. A vendor cloud — BlogVault, Jetpack — means they can start a restore when your server cannot.

Both are valid. A folder in wp-content is not. It fills the same disk you are trying to survive, and some hosts count those files against your inode or storage cap until the site falls over from the weight of its own safety copies.

Keep more than one restore point. A backup that runs after you have already been hacked, and overwrites the only clean copy, is a well-automated mistake. Retention of several days or weeks is the point of the schedule.

Read the cap. A 1 GB vault and an 8 GB uploads folder is how backups silently stop. The plugin will not always email you when the remote drive is full.

Put the storage login somewhere a second person can find. A Drive that only one freelancer can open is not a company backup.

Plugin:
Schedule: weekly / daily / real-time
Destination:
Retention: how many copies
Who can log into that destination:
Last successful test restore:

4How do you test that a WordPress backup works?

Restore the backup to a staging site or a local copy, log in, and check pages, media and forms.

A backup you have never restored is a hope. The test is boring and that is why people skip it. Restore to a staging site or an empty subdomain.

Confirm you can log in. On a store, confirm a recent order is visible and that the checkout page loads. On a membership site, confirm a test user still exists.

Then throw the staging copy away or protect it so search engines do not index a second version of the business.

Do this quarterly on a small site and monthly on a store. Write the date in the note from the last step. If the restore fails, you still have a live site and a weekday to fix the plugin, the storage login, or the plan limit.

If you discover the failure during an outage, you have a crisis and a theory. The difference is the test.

Know which restores need a living WordPress and which do not. UpdraftPlus and WPvivid restore from wp-admin. If the host is gone, you need the archives plus a manual rebuild or a migration package.

Duplicator’s installer and the vendor-cloud restores from BlogVault and Jetpack are the tools for “the dashboard will not load” and “the account is suspended”. Read that sentence again before you buy the cheapest plugin for a site that makes money.

The BlogVault review and the UpdraftPlus review spell out the same split.

Tip. The first restore will take longer than the plugin’s marketing page implies. Do it once while nothing is on fire so the second time is a procedure.

5Is your web host's backup enough?

No. A host snapshot is a useful extra copy, but it lives with the host and can disappear with the account.

Many hosts include a daily snapshot. Use it. Also assume it has a short retention, lives on their platform, and may not be downloadable on the day you are angry.

Ask three questions and write the answers down: how many days they keep, whether you can download the backup, and whether you have ever restored one. If any answer is no or “we think so”, you do not have a backup yet. Add the plugin.

Cloud and managed hosts are not exempt. A platform backup is often better than a shared-host snapshot, and it is still one vendor. An off-server copy is how you leave that vendor without negotiating for your own database.

The hosting guide tells you to check this before you pay. This guide tells you to test it after you pay.

6When should you take a manual WordPress backup?

Take a fresh backup right before PHP updates, theme switches, new builders and host migrations.

The afternoon people lose sites is the afternoon they update PHP, switch themes, install a new builder, or migrate hosts. The scheduled backup from last night may be fine. Take one the same day anyway, before you touch anything.

Duplicator or the host’s snapshot plus your normal plugin is a reasonable belt. The speed guide assumes you can undo the work. That assumption is this step.

Migrations deserve a package you can upload, not only a cloud button. DNS can be pointed back if the new host is worse. You cannot point DNS back to a site you deleted.

Keep the old host until the new one has survived a day of real traffic, including a test order if you sell anything. Email DNS is the other half of a move. A successful website migration that breaks mail is still a broken Monday.

Pause and check MX records before you cancel the old plan.

7How should WooCommerce and membership sites be backed up?

Stores and membership sites need real-time or several-times-a-day backups, because a nightly copy can lose a day of orders.

WooCommerce writes orders, stock and customer accounts all day. A membership or LMS writes progress and subscriptions. A backup that runs at 2 a.m. restores the site to 2 a.m.

Everything after that is retyping, or a conversation with a customer who paid and has no order. If you can accept that window, say so out loud and keep the nightly job. If you cannot, pay for real-time or a short incremental window.

Jetpack’s backup product includes real-time on the paid plan. BlogVault’s shorter window sits on the WooCommerce tier, not on every personal plan. Read the tier.

“The plugin can do real-time” and “your invoice includes real-time” are different sentences.

Exclude nothing that holds orders. Do not let a file-only backup skip the database to save space. Do not let a security plugin’s “activity log” convince you it is a backup.

A log is a story. A backup is a copy. You want the copy.

Pair it with a host that can actually run checkout. A perfect archive will not make a $3 shared plan survive a product launch. That is the hosting decision, and it comes next, not a second backup plugin.

8What should you do once backups are running?

Check once a month that storage is receiving files and the last run succeeded, then leave the setup alone.

Once a schedule is green and a restore has worked, resist the urge to add another backup brand because a video said it was faster. Check, once a month, that the remote storage is receiving files and that the last run did not fail quietly.

Update the plugin when the vendor ships a security release — the UpdraftCentral note is the example, not a special case you can ignore because your site is small.

If you change the storage account password, update the plugin the same day or the next run will fail and you will not notice until you need it.

If you are an agency, the backup belongs in the runbook with the host, the region, and the person who can restore. A client site whose backup login is in a former freelancer’s email is not backed up. Write it down.

Then go do the work the site is for. A backup is successful when you forget it for a month and it is still there.

WordPress backup checklist

Tick these off on this browser. The ticks stay in local storage on this device. They are not an account.

WordPress backup FAQ

Is a host snapshot enough?

Only if you have restored it and you can get a copy off that host. A snapshot on the same disk dies with the disk. Treat it as a convenience, not the only copy.

How often should I back up?

A brochure that changes twice a month can be weekly. A store that takes orders all day should not rely on a nightly zip. Real-time or several times a day belongs on the commercial site.

Is UpdraftPlus safe to use after October 2026?

Update to 1.26.13 or 2.26.13 so pre-incident UpdraftCentral keys are revoked. Sites that never connected UpdraftCentral were outside that path. The backup format was not the thing that failed.

Can I back up WordPress without a plugin?

Yes. Copy the files over SFTP and export the database with phpMyAdmin or WP-CLI. It works, but it is manual, so most people schedule a plugin instead.

Where should I store WordPress backups?

Outside the hosting account: cloud storage such as Google Drive, Dropbox or Amazon S3, or the backup vendor's own servers. Make sure a second person can log in to that storage.

Sources

Primary documentation we checked for this page. Product claims come from our own notes and the vendors' pages.

  1. WordPress Backups WordPress Developer Resources
  2. wp db export (WP-CLI command) WordPress Developer Resources
  3. UpdraftPlus plugin page and changelog WordPress.org Plugin Directory
  4. BlogVault plugin page WordPress.org Plugin Directory

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

We write restore plans, not feature grids. The October 2026 UpdraftCentral note is based on vendor and Patchstack statements. About the site · How we test

Last updated. Nov 2026: included the UpdraftPlus 1.26.13 update in the setup steps, not only on the list.