
Duplicator 5.2 is out, and it changes how you manage WordPress backups. AI assistants can now run Duplicator for you through 48 abilities. You ask in plain language, and it handles the backup work you'd normally do in wp-admin. Here's what's new 🧵

The Best Backup & Migration Plugin for WordPress. Over 1,500,000+ Professionals use Duplicator for Migrations and Backups

Duplicator 5.2 is out, and it changes how you manage WordPress backups. AI assistants can now run Duplicator for you through 48 abilities. You ask in plain language, and it handles the backup work you'd normally do in wp-admin. Here's what's new 🧵

You don't have to manually do WordPress maintenance anymore. Hand it off to Duplicator Pro + WPVibe! Full walkthrough of what you can do with Duplicator 5.2 👇 duplicator.com/new-duplicato…

You stay in control. Deleting data, changing settings, and sharing recovery links are disabled until an admin allows them.

Not sure where to start? Try these prompts: "Back up the full site and set it as my recovery point." "Back up my full site daily at 2 AM and send it to Duplicator Cloud." "Why did my last backup fail?" "Test my Duplicator Cloud connection, then send my latest backup there."

Here's what you can ask it to do: • Send backups to off-site storage • Create backup schedules • Create backup templates • Test your storage connections • Set recovery points • Run incremental backups and check cloud usage • Run AutoTune • And much more!

Backups only work if someone keeps up with them. That means setting up schedules, checking that copies reached off-site storage, and reading the log when one fails. Now your assistant can take all of that off your plate.

Incremental backups are included in Duplicator Pro and Elite. They're stored in Duplicator Cloud, and you can back up as often as every hour.

Want to estimate your own site? The full report has a storage calculator. Plug in your site size and snapshot size 👇 duplicator.com/incremental-b…

On quiet sites, hourly incremental backups beat daily full backups. Over 10 days, the blog's hourly snapshots would use about 1.2 GB. 10 daily full backups would use about 3.9 GB. That's about 68% less storage, with 24 restore points a day instead of 1.

But even the store saved a lot of storage. 24 full backups would take about 85 GB. 24 incremental backups took about 12.8 GB. That's 85% less storage for the same 24 restore points.

On the busy store, each snapshot was about 12% of the site. The full backup is 3.5 GB. Each snapshot was about 400 MB. Why? Between backups, 31 to 58 database tables changed (orders, customers, logs). A changed table is saved in full.

On the quieter sites, each snapshot was about 1% of the site. The blog's full backup is 390 MB. Each hourly snapshot was about 3.5 MB. The course site's full backup is 540 MB. Each snapshot was about 7.5 MB.

The 3 sites we tested: • A quiet blog: 390 MB, backed up every hour • A nonprofit course site: 540 MB, every hour • A busy online store: 3.5 GB, every 2 hours For each one, we compared a typical snapshot to the size of the full site.

First, what's an incremental backup? A normal (full) backup copies your entire site every time. An incremental backup copies your full site once. That's the "baseline." Every backup after that is a small "snapshot" that saves only what changed.

Hourly backups protect your website. But 24 full backups a day consume a lot of storage. Incremental backups are supposed to fix that. So we tested them on 3 real WordPress sites and measured every backup. Here's what we found 🧵

Hourly backups used to mean copying your whole site 24 times a day. Incremental backups copy it once. After that, each run only uploads what changed (13 MB on average on our 540 MB test site). Here's how to set them up in WordPress 👇 duplicator.com/incremental-b…