Safeguard every change with automatic WordPress backups.

Every change on your site is captured as it happens and kept off your server, so no change is missed and any version can be restored, tested or migrated.

No credit card required · 14-day money-back guarantee

Find any site in seconds.

No change is missed.

One click. Five verified stages.

Every backup state. Instantly clear.

Trusted by site owners, agencies and hosts around the world. Bootstrapped, independent, and answerable to nobody but customers.

  • 400,000+Websites protected
  • 2M+Sites migrated
  • 5,000+Webhosts supported
  • 120Countries

Backupsand restores
that are real-world ready

Rated 4.5 / 5 on WordPress.org · 328 reviews

Most site owners never test a restore. 87% find out on the worst day.

BlogVault turns that day into a verified recovery point.

Incremental backups

Only the changes move

After the first full backup, BlogVault fingerprints your site and syncs only what changed since the last run. Site size stops mattering, and no change is missed.

Learn more
Recovery, end to end

Built for every step of a recovery

Tested first. Restored precisely. Stored independently. Processed off your server.

Learn more
Recovery workflowBuilt around your backup
[Processing]

Zipping happens on our machines

Small, interruptible requests on your side; the heavy work on ours.

Learn more
[Storage]

Copies your host can’t reach

Two companies, two countries, two failure domains. None of them your host.

Learn more
[Testing]

Proven before production

Any backup is restored onto our servers first, and checked, before it touches yours.

Learn more
[Restore]

Bring back only what broke

Files, tables, subsites and store data recover on their own. No blunt full-site rollback.

Learn more

From “something broke” to the exact recovery point.

BlogVault turns backup history into a recovery workspace: find the moment, verify what it holds, restore with control. Four surfaces, one set of recovery points.

Restore

Take the site back to the right moment.

Choose a recovery point, define what should be restored, confirm the destination, and follow the recovery from start to finish.

Learn more
9Copies behind every restore
Backup history

Know exactly what you’re restoring.

Open any recovery point to see its health, sync coverage, site details and the activity around it, then test, migrate or restore from the same view.

Learn more
400,000+Websites protected
Backup calendar

Spot a backup gap before it becomes a recovery gap.

Scan successful and failed backups across the month, filter any date range, and jump directly to the day that needs attention.

Learn more
4.5/5From 328 WordPress.org reviews
Files & tables

See, and choose, what your backup contains.

Browse backed-up files and database tables, inspect versions and sizes, change what syncs, and download only what you need.

Learn more
2M+Sites migrated

Restore · Backup history · Backup calendar · Files & tables — four surfaces over one set of recovery points.

Before BlogVault, bringing back a broken WordPress site meant hours of FTP transfers and database imports, and one missed step could make a bad day worse. Now one click brings back the exact version you need, so the team can get back to work that matters.

Your host isn’t your backup.

BlogVault stores every change beyond your host’s reach.

More on data security
▶YOUR WORDPRESS SITEFILES · DATABASE · UPLOADS▶HOST BACKUPSAME DISK · SAME FAILURE DOMAINONLY WHAT CHANGEDFRANKFURT DATA CENTRE2 ENCRYPTED COPIESAMAZON S3UP TO 7 COPIESINDEPENDENT STORAGE9 COPIES

Built around your host’s limits.

  • Hosts may block outbound connections, disable remote reads, cap uploads, or kill long requests.
  • BlogVault can write directly, pull via HTTP chunks, upload in small pieces, resume below timeouts, or use FTP + database credentials.
  • It tests each route until one works with your host.
More on BulletProof Backups
RESTOREROUTESHOST LIMITSWRITEHTTPCHUNKSRESUMEFTP + DBFingerprintsSent firstCompare changesSize + modified time#ChecksumOnly when neededNO FULL FILESChanged files + database rowsZIP OFF-SERVER

Restore what broke. Nothing more.

  1. Test Restore

    Run the restore on a temporary copy first and check it works before anything touches the live site.

  2. Emergency Connector

    Restore even when WordPress is down: a small standalone connector on your server takes over.

  3. Differential Restore

    Only the files and database rows that changed since the backup are written back.

  4. Selective Restore

    Pick a file, a table, a plugin or a subsite and restore just that, leaving the rest alone.

More on reliable restores
Restore point2026-09-07 22:00:00
58sTest restore
Restore modeSelective
Scopewp-content/plugins · wp_options
Left aloneuploads · wc_orders (184 orders kept)
ConnectionEmergency connector · WordPress offline

Move the site first. Switch DNS last.

  1. Point us at the destination

    Choose a host, or connect with cPanel or FTP.

  2. The site is rebuilt there

    Files and database move while the old host stays live.

  3. URLs and serialised data are rewritten

    Domain references are corrected before launch.

  4. You switch DNS when ready

    Both copies are live and verified before cutover.

More on WordPress migrations
OLD HOSTSTILL LIVEFILES + DBNEW HOSTVERIFIEDDNS LASTOLD HOSTVISITORS STAY LIVENEW HOSTSITE REBUILTLIVE SITEVERIFIEDVISITORS STAY LIVEREADY BEFORE CUTOVER0s DOWNTIMEDNS SWITCHES LAST

Stage changes without touching live

BlogVault builds a private cloud copy. Test safely, then merge only what you choose.

More on staging
STG[STAGING URL]|

Recover your store.Keep every new order.

Restore without losing orders

Choose what your live store keeps.

Keep latest ordersKeep new contentRun pre-checks
|
Select a clean backup

Choose the last healthy version before the store broke.

Retain latest orders

Keep orders placed after that backup—no sales disappear.

Preserve new content

Retain recent posts, pages and media from the live store.

Check, then restore

Pre-checks verify access before recovery begins.

One network. Every subsite covered.

Back up the whole Multisite at once, or bring back a single subsite without touching the rest.

Protect the whole network, at once

Activate BlogVault once and back up every subsite—without managing each one separately.

Subsite ID001
Main site
Subsite ID124
Store subsite
Subsite ID248
Learning subsite

Restore one subsite—not the whole network

Recover only the affected subsite while every other site stays live and current.

Restoring subsite 042…
038
039
040
041
042
043

One install. Complete coverage.

Subdomain or sub-directory, the entire Multisite is protected as one managed site.

Contain the disruption

A broken update on one subsite no longer requires a network-wide rollback.

Scale without admin overhead

Handle hundreds or thousands of subsites with database processing built for large networks.

Keep every other site current

Restore the selected subsite without discarding newer changes elsewhere.

Move the whole network

Migrate every subsite, domain and URL—not only the primary site.

Network files2025-11-02 14:32:11All subsites2025-11-02 14:45:27
Database tables2025-11-02 14:28:33All subsites2025-11-02 14:41:09
Domain + URL rewrite2025-11-02 14:25:17All subsites2025-11-02 14:39:52

Select. Restore. Reopen.

Choose the subsite and clean restore point; BlogVault returns only its required data.

Site 041 – Live2025-10-15 10:24:17
Site 042 – Restoring2025-10-15 11:03:26
Site 043 – Live2025-10-15 09:18:52
The problem

A plugin update broke checkout. The only host backup was 24 hours old—restoring it meant losing 187 paid orders.

  • Data lossOrders and content gone, with little chance of recovery.
  • Lost customersEvery minute of downtime sends buyers elsewhere.
  • Google penaltiesRepeated downtime costs search rankings.
The response

You shouldn’t have to choose between fixing checkout and keeping every paid order.

How BlogVault compares to host backups and plugins

BlogVaultWhat you get
Where the copy livesNine copies, two providers, off-host
Test a restore firstYes, on our servers before production
Load on your serverBounded. The work happens off-site
Restore granularityFile, table, plugin, or subsite
Orders since the backupJournalled, and kept through a rollback
Works when the site is downYes. FTP and DB credentials are enough
Where the copy livesNine copies, two providers, off-host
Test a restore firstYes, on our servers before production
Load on your serverBounded. The work happens off-site
Restore granularityFile, table, plugin, or subsite
Orders since the backupJournalled, and kept through a rollback
Works when the site is downYes. FTP and DB credentials are enough

Host backups

Usually stored on the same machine as the site and restored wholesale from the host panel. There is no test restore, no file or table granularity, and orders taken since the snapshot are lost.

Typical backup plugins

Zipping runs on your own server, so backups are heavy and slow. Restores are usually whole-site and rarely rehearsed, and when the site is down the plugin cannot run at all.

16 years of making WordPress failure recoverable.

One continuous proof line—from the first backup problem to recovery at scale.

2010

The problem

A crashed blog exposed the need for dependable recovery.

2014

Product proof

Public plugin and real-time WooCommerce protection.

2017

Migrate Guru

Built from experience across 500K+ migrations.

2019

WP Remote joins

Site management enters the BlogVault product family.

2022

Recovery without FTP

Restore even when WordPress is unavailable.

SCALE

450K+

WordPress sites backed up.

PROOF

1M+

Successful website restorations.

2026

50–80%

Faster large-site backups across 40K+ sites.

Public milestones · Verified September 2026

Sites backed up450K+
Milestone · 2010

A crashed blog, and no dependable way back.

Successful restores1M+
Milestone · 2017

Migrate Guru launches, built from 500K+ real migrations.

WordPress.org rating · 328 reviews4.5 / 5
Trust · 2026

Bootstrapped and independent since 2010. Large-site backups now 50–80% faster.

In 2026, the proof isn’t a promise. It’s in the restore log, one site at a time.

None of them lets you test a restore before you commit to it.

A host backup is disaster recovery for the host. It is sized, retained and restored around their operational needs, not around the day your checkout breaks. That’s not a criticism; it’s a different job.

Testimonials

Agencies, developers and site owners on backing up, restoring
and moving their WordPress sites with BlogVault.

“BlogVault is the most reliable backup and restore tool we’ve ever used at SiteCare.”
Ryan SullivanSiteCare
Battle-tested at scale400,000+sites backed up by BlogVault
“Backing up and restoring is so easy with BlogVault. It’s transformed how we migrate sites with its 1-click migration. Very useful for web designers and site owners. Fantastic support.”
Mickey KayNerdWallet
One-click migrations for a whole team5,000+web hosts supported
“It is a game-changer! Very simple and easy to set up. We backed up our site and made a staging environment in minutes. It can handle anything we throw at it: WP version updates, new themes, plugins, everything, flawlessly, the first time.”
Mark TullWebsite Essentials
Backed up and staged in minutes1 clickto create a staging site
“In my opinion it is the best backup plugin you can get. Easy to set up, back up, and restore if necessary, with excellent support. I never got disappointed and it saved me several times. Worth the money!”
Jennifer CarelloTech Care
It saved me several times1M+successful restores
“If you’re ever confused about something, their support will respond quickly and patiently walk you through all the steps. The reliability is a big green flag.”
Alex CalinovBrilliant Digital
Extremely reliable and upfront4.5out of 5, from 328 WordPress.org reviews

Built to survive the bad day

The questions people only ask a backup service after something has gone wrong, answered up front.

  • Privacy & GDPR

    A backup of customer data is still customer data

    Names, emails and orders sit inside every backup, so GDPR applies to the copy as much as to the live site. Yours are encrypted at rest and in transit, and they stay in EU data centres.

    Learn more
  • Access & keys

    No storage keys left on your site

    Plugins that push to your own cloud bucket keep its keys in wp-config, where an attacker can read them and delete the backups too. BlogVault signs every instruction and checks it against a public key on your site. Storage keys never touch your install.

    Learn more
  • Accountability

    A record of who did what

    The activity log keeps every update, backup and restore with the person who ran it. When a site breaks at the wrong moment, you can see what changed just before, and who to ask.

    Learn more

Frequently asked questions

Doesn't my host already back up my site?
Usually, yes — and for a simple site that changes rarely, it may well be enough. The differences that matter are where the copy lives (often the same machine as your site), how far back it goes, whether you can restore one thing instead of everything, and whether you can test a restore before committing to it. Host backups are built to recover the host's infrastructure; that's a different job from recovering your business.
Will it slow my site down?
Not in the way a normal backup plugin does. Nothing is zipped or compressed on your server — our machines do that work. What runs on your side is a series of small, interruptible requests that read a batch of rows or a chunk of a file. That isn't literally zero load, and we'd rather say so, but it's a very long way from a plugin that tries to archive your whole site in one PHP process.
What does “real-time” mean for a WooCommerce store?
When an order is placed — or stock changes, or a refund is issued — your site immediately notes it in a small queue: just which table and which record. We collect that queue continuously and fetch exactly those rows. The guarantee is that nothing is missed between scheduled backups — not that the copy is instantaneous.
Can I restore if my site is completely down?
Yes. If WordPress still loads at all, our callback runs before your theme or admin does, so a fatal error doesn't block a restore. If WordPress won't boot at all, the Emergency Connector restores over FTP and database credentials without needing the plugin to run.
Can I keep backups in my own S3 bucket?
No — and it's a fair thing to weigh up. Storage is managed by us: nine encrypted copies across two providers, included in the price, nothing for you to configure or pay for separately. If you need custody in your own bucket, that is a genuine gap today.
How big a site can it handle?
Plans cover sites up to 20 GB, 50 GB and 100 GB respectively, and we've handled considerably larger. The reason large sites work is mechanical rather than promotional: fingerprints are compared and only the changes move, so a 47 GB media library is a one-off first backup and a small daily delta after that.
What support do I actually get?
A small team that answers properly, and quickly on weekdays — support is the thing customers mention most often in reviews. To be straight with you: it isn't 24/7. Weekdays 9–6, with a 12–24 hour turnaround at weekends.
Is there a WP-CLI command or an API?
Not today. Everything is driven from the dashboard. If you need scripted backups or restores as part of a deployment pipeline, that's a genuine gap for now — worth knowing before you buy rather than after.

Backups built for scale. Restores for the bad day.

No credit card · 14-day money-back guarantee

© 2026 BlogVaultWhatever breaks, you'll get it all back.