WPShift — backups
WordPress server backups that survive the worst day.
WordPress server backups on WPShift are scheduled or manual archives of files plus database, stored off-server by design, so a dead disk never takes the backups with it. You choose from eight storage destinations, AWS S3, DigitalOcean Spaces, Hetzner Storage Box, Cloudflare R2, Wasabi, Backblaze B2, WPShift Cloud, or any S3-compatible bucket, and restore any backup in one click, to the original server or a different one. They exist for anyone who cannot afford to lose a site: agencies with client SLAs, freelancers holding the only copy, shops with orders in the database. Backups run on every plan; what varies is included WPShift Cloud backup storage, 500 MB on Personal (€5.99/mo), 2 GB on Professional (€14.99/mo), 5 GB on Agency (€29.99/mo), with your own buckets billed by your storage provider.
Off-server by design.
Retention is policy-driven: set what to keep per site and WPShift prunes old archives automatically. Any individual backup can be pulled as a time-limited signed download when you need to ship it elsewhere.
A backup on the same disk as the site is a copy, not a backup: whatever kills the server kills both. WPShift ships every archive off-server to the destination you choose, and destination credentials are stored encrypted.
You can route different sites to different destinations from the same panel, so the agency portfolio and the side project do not need to share storage. An existing bucket at AWS, Cloudflare or Backblaze plugs straight in; if you would rather not manage storage at all, WPShift Cloud is one of the eight destinations.
Manual backups are one click and a useful safety net before a plugin update, a wp-config change, or handing a site over to a client.
What you get.
Scheduled and manual backups
Daily, weekly or custom schedules, with separate cadences for files and database if you want them. Manual backups are one click before a risky change.
Eight storage destinations
AWS S3, DigitalOcean Spaces, Hetzner Storage Box, Cloudflare R2, Wasabi, Backblaze B2, WPShift Cloud, or any S3-compatible provider. Credentials stored encrypted.
One-click restore
Pick a backup, pick a target server, restore. Works to the original server or a different one, so a failed primary does not mean lost work.
Retention with auto-pruning
Set a retention policy per site and let WPShift prune old archives automatically, whatever fits the compliance bar.
Signed download links
Pull any backup as a time-limited signed download for an external restore or a regulator request.
Restore is the feature.
Backups only matter when the restore works. On WPShift a restore is pick a backup, pick a target server, restore, and it works across servers. A failed primary does not stall the business: spin up a replacement, restore, repoint DNS, and the site is back.
Retention is set per site: keep the last 30 days, keep one per week beyond that, whatever fits the compliance bar. Old archives are pruned automatically, so storage does not creep, and any individual backup can be pulled as a time-limited signed download for an external restore or a regulator request.
Who it’s for.
Anyone for whom losing a site is not an option.
- 01
Agencies
Per-site retention policies and per-client destinations, so each contract’s backup obligations are met without a spreadsheet tracking who backs up where.
- 02
Freelancers
The one-click manual backup before every risky update is the cheapest insurance in the business, and the cross-server restore means a dead droplet is an hour’s inconvenience, not a disaster.
- 03
Shops and busy sites
Separate cadences for files and database mean order data can be backed up more often than the theme folder.
How it works.
- 01
Pick a destination
Connect one of the eight destinations or any S3-compatible bucket. Different sites can route to different destinations from the same panel.
- 02
Set schedule and retention
Choose daily, weekly or a custom cadence, separately for files and database if needed, and define what gets kept for how long.
- 03
Backups run off-server
Files plus database are archived to your destination on schedule. Old archives are pruned automatically by your retention policy.
- 04
Restore in one click
On the bad day, pick the backup and the target server. Restore to the original machine or a fresh one, repoint DNS, and the site is back.
How it’s priced.
Backups run on every plan. Plans only set how much WPShift Cloud backup storage is included.
See all plans and pricing- Included WPShift Cloud backup storage: 500 MB on Personal (€5.99/mo), 2 GB on Professional (€14.99/mo), 5 GB on Agency (€29.99/mo).
- Your own destinations, S3, Spaces, Storage Box, R2, Wasabi, B2 or any S3-compatible bucket, are billed by your storage provider, not by WPShift.
- Scheduling, retention, cross-server restore and signed downloads are on every tier, no feature gating.
- The 7-day free trial runs full Professional features, no credit card required.
Questions, answered.
Where are my backups stored?
Off-server, at a destination you choose: AWS S3, DigitalOcean Spaces, Hetzner Storage Box, Cloudflare R2, Wasabi, Backblaze B2, WPShift Cloud, or any S3-compatible provider.
Can I restore to a different server?
Yes. Restore works to the original server or any other server you manage, which is what makes a failed primary recoverable: spin up a replacement, restore, repoint DNS.
What is included in a backup?
Files plus database. You can run separate schedules for each if, say, the database changes far more often than the files.
Can I take a backup right before a risky change?
Yes. Manual backups are one click, a useful safety net before a plugin update, a wp-config change or a client handover.
How does retention work?
Set a policy per site, for example keep the last 30 days and one per week beyond that. WPShift prunes old archives automatically, and any backup can be exported as a time-limited signed download.
Be ready for the worst day before it happens.
Start your 7-day free trial with full Professional features. No credit card required, cancel anytime.