Pick up where
you left off.
Private checkpoints split database export, archive creation, and transfers into smaller worker requests. Interrupted work can continue without starting the whole job again.
You built it.
Keep a copy on your terms.
Start with a free license for your website. Choose Pro for scheduled backups to storage you control, resumable jobs, verified transfers, and a clear view of what ran—and what didn’t.
A backup deserves a little
more follow-through.
Private checkpoints split database export, archive creation, and transfers into smaller worker requests. Interrupted work can continue without starting the whole job again.
Read-back verification compares every uploaded chunk with the local archive using SHA-256, before a job is marked successful or older copies are pruned.
See the active stage, next run, last success, and recent results. Configure failure emails and overdue-backup reminders instead of guessing from a schedule.
Choose daily or weekly backups and keep 1–100 copies. Retention targets only this installation’s new-format archives—not unrelated files or legacy backups.
Use your own account, bucket, or server. BackupBank Pro supports SFTP, cloud destinations, and private downloads in one plugin.
Explore BackupBank ProBoth plans need an account
and a setup domain.
Pro connects your site on first use.
Start with a free, domain-bound BackupBank license. No card or paid subscription required.
$0Free · one website
Get BackupBank Free An account and website domain are required. Free keys do not unlock Pro cloud destinations. A Pro license is a separate paid signup.Scheduled, resumable WordPress backups to your own server, cloud storage, or a private download.
$25USD / month · one website
Order BackupBank Pro Renews monthly until canceled in Billing settings. Your first valid API request links the license to your site; www and non-www count as one site. A valid Pro license is required for cloud destinations. Storage-provider costs are separate.BackupBank Pro requires WordPress 6.2+, 64-bit PHP 8.2+, working cron, and persistent private disk space. Storage is provided by your own account—not bundled with the plugin.
Save your destination and credentials. Run the connection test before enabling your backup schedule.
Choose daily or weekly runs, retained copies, and alerts. Use a regular system cron trigger for reliable scheduling.
Review the verified result in history. Restore a copy into a separate staging site before relying on your backup plan.
A verified transfer is not a verified restore. BackupBank creates archives; it does not automatically restore them. Pause database and filesystem writes for a consistent backup, and test recovery separately.
No magic claims.
Know what you’re running.
A ZIP64 archive containing database.sql and files/ for the WordPress home-directory tree. Symlinks, cache directories, Git directories, and recognized legacy BackupBank artifacts are excluded. Files outside that tree, stored database routines, and scheduled database events are not included.
No. BackupBank does not provide automatic restoration. Extract the archive, restore the SQL and files into an isolated WordPress installation, and verify login, content, media, plugins, and themes. Practice that process before you need it.
BackupBank reads every uploaded byte back and compares SHA-256 for each 1 MiB chunk with the local archive before success and retention. History records a labeled SHA-256 digest chain, not a standard whole-file checksum. The bundled verification tool can check a downloaded copy. Read-back uses additional provider requests and bandwidth; it does not guarantee the destination stays unchanged later.
Jobs resume from private checkpoints, but host limits still apply. ZIP64 archives are uncompressed, so allow disk space for the site archive and SQL dump, plus full read-back bandwidth. A single large database row or slow operation can exceed a worker’s time budget. Current S3 multipart uploads support approximately 78 GiB per archive. Test your own host and provider.
Saved credentials use authenticated, site-specific encryption. The backup archives themselves are not encrypted at rest by the plugin. Restrict access to private workspaces and destination storage, enable appropriate provider-side protections, and configure the optional SFTP host-key fingerprint to verify server identity.
Pause both database and filesystem writes for a consistent backup. A database export spread across requests is not a single transaction snapshot. If writes cannot pause, use a database-native snapshot or replica strategy rather than assuming the export is application-consistent.
No. Failure and overdue alerts require working WordPress, cron, the database, and mail delivery. They cannot alert you when that entire stack is offline. Use independent uptime and backup monitoring, and test actual email delivery.
Not by itself. Pro’s admin-only local downloads expire after 24 hours, or sooner if retention removes them. Download and store a copy independently; do not use local-only files as your disaster-recovery destination. Use one worker host with persistent private storage. Multisite network activation and independent multi-host workers are not validated.
BackupBank Pro. $25 USD per month, for your website and your storage.