WPVivid vs. Kakapo Backup: Which Backup Plugin Fits?

A backup plugin is judged on exactly one day: the day the restore has to work. Everything before that — schedules, storage destinations, interfaces — only serves that moment. That's why this comparison sorts WPVivid and Kakapo Backup by what counts on the day it matters.

The short answer

WPVivid is an established backup and migration plugin with many cloud destinations and a free version. Kakapo Backup is a paid plugin with no free tier that handles backups — including checksums, schedules, and retention — entirely on your server, using the same framework as the other Kakapo plugins.

In short: if you want to connect many different cloud providers and start with a free version, you'll find more choice with WPVivid. If you want to be able to prove that an archive is unchanged, and want to run Backup, Consent, Security, and the other building blocks under one license, Kakapo Backup is the better fit.

What both can do

• Full backup of the database and files, as a ZIP
• Scheduled backups instead of a calendar reminder
• Offloading to remote storage instead of just the same server
• Restore from the interface, without a database tool
• Migrating an installation to a different address

At this level, there's little between the two. It gets interesting one layer down.

Where the two differ

The difference that counts on the day it matters

You only notice an archive that won't open when you try to restore it — in other words, exactly when there's no time left. Kakapo Backup stores a SHA-256 checksum for every archive and compares it at the push of a button. If it doesn't match, the file was damaged along the way, and you know before you need it.

A backup that has never been tested is a hope, not a backup. Test the restore once a quarter — on a staging copy, not on the live site.

Where the data is stored

Both plugins can store archives off-site. The difference lies in who controls the process: Kakapo Backup writes its archives to wp-content/uploads/kwpb-backups and pushes them from there to the destination you've set up. There's no intermediate step through a vendor service, and without a configured destination, not a single byte leaves your server.

For data processing and privacy documentation, that's the practical difference: you document your storage provider, not the plugin vendor as well.

When WPVivid is the better choice

• You want to start without a budget and decide later
• You need one particular exotic cloud provider that WPVivid supports
• You back up a single site and don't need proof of integrity

When Kakapo Backup is the better choice

• You need to be able to prove that an archive is unchanged
• You want to encrypt archives and keep the key yourself
• You look after multiple sites and want to see them from one interface
• You already use other Kakapo plugins and want one invoice instead of five

Switching: what to do

1. Create one last full backup with the old plugin and download it.
2. Install Kakapo Backup and enter your license key.
3. Set up your destination under “Storage” and start a first backup manually.
4. Verify the checksum of the new archive — it has to match before you continue.
5. Turn on the scheduled backup under “Schedule” and set the retention.
6. Only deactivate the old plugin once a restore on staging has worked.

Keep the old plugin's last backup for another month. A switch is the worst time to be left without a way back.

Frequently asked questions