PROVIDER Β· WordPress backup standard
UpdraftPlus
UpdraftPlus is among the most installed WordPress backup plugins, pushing archives to Google Drive, Dropbox, S3, and similar remote storage for free, with Premium adding scheduling, incremental backups, and site migration.
Pros
Cons
Product Information
Detailed Notes
Overview
Maintained by Team Updraft in the United Kingdom, UpdraftPlus is one of the most installed backup plugins in the WordPress ecosystem. It treats backup, restore, and migration as one flow, pushing archives to Google Drive, Dropbox, OneDrive, S3, and other remote storage, and restoring an archive onto a new site completes a full migration.
The free plugin covers the basics most small sites need, with manual backups, remote storage, and one-off restores, while scheduling, incremental backups, migrations, and multisite support sit in Premium. That split works well, since you can validate the flow for free and upgrade by how critical each site is.
As a Backup & Migration option its value is standardisation rather than feature count. The classic failure is nobody checking whether backups are restorable, and putting the schedule, retention policy, and restore entry on one screen reduces that risk.
Core Strengths
- The free plugin pushes archives straight to Google Drive, Dropbox, OneDrive, S3, and more without using local disk
- Backups can be split by database, plugins, themes, and uploads to trade archive size against restore granularity
- Retention rules and an archive list enable point-in-time rollback, avoiding overwritten good data
- Premium adds incremental backups and site migration that can move a site in tens of minutes
Product Ecosystem
Backup and retention
Files and the database can follow separate schedules and retain by count or age. The critical calculation is copies times site size, because sites with large uploads fill remote storage faster than expected.
Restore and migration
Restores select components individually, while migration lifts a full archive into a target site. After migrating, verify permalinks, upload permissions, and plugin licences, the three usual causes of a migration that reports success but behaves badly.
Drawbacks
- Incremental backups, scheduling, and migration are Premium features, so the free plugin is not enough for production
- Archives for large sites are bulky, and restores can exceed PHP time and memory limits
- Remote storage quotas and fees belong to the cloud provider, so more backups cost more and retention rules matter
- The plugin does not verify that backups are usable, which still requires scheduled restore drills
Use Cases
- WordPress content sites and blogs (β β β β β ) - The free plugin covers routine backups at near-zero cost
- Agencies migrating sites often (β β β β β) - Premium migration standardises whole-site moves and cuts manual error
- WooCommerce stores (β β β β β) - Database backups and component restores matter for order data, so shorten intervals
- Multisite networks (β β β β) - Supported but complex, so weigh Premium licensing against network size
Pricing
| Plan | Price | Scope |
|---|---|---|
| Free | $0 | Manual backups, remote storage, one-off restore |
| Premium | Annual licence | Scheduling, incremental backups, migration, multisite |
| Agency / Unlimited | Annual licence | Multi-site licensing and bulk management |
Licences are annual and scale with site count, with current pricing on the official site. Budget separately for remote storage, since 30-day retention on a mid-size site often costs as much as the licence itself.
FAQ
-
Can the free plugin run in production? It can back up and restore, but without scheduling or incremental backups it rarely meets production needs. Validating on free and licensing Premium for production avoids the situation where backups were assumed but never ran.
-
Where should archives live? Put them in object storage from a different vendor than the host, so a host failure does not take the backups with it. Alibaba OSS, Tencent COS, and Backblaze B2 are common targets, and egress cost plus restore speed should drive the choice.
-
What if the site breaks after migration? Check permalink rules and upload permissions first, then confirm plugin licences did not expire with the domain change. Most migration failures come from stale domain names inside serialised data, which a search-replace pass clears.