What it does
An offsite destination is storage you own that a site's backups can stream to directly, in addition to the local restore point on the server itself — the archive goes straight from the site to your storage; it never passes through WPClientHub.
How to
- Open Backups and scroll to Offsite storage. Press Add S3 or SFTP for an S3-compatible bucket (AWS S3, Backblaze B2, Wasabi, Cloudflare R2) or an SFTP server — or, on Studio and above, Connect Google Drive / Connect Dropbox to use your agency’s own account (see Google Drive & Dropbox backups).
- For SFTP, you can authenticate with a password or an SSH key.
- Saving runs the check — every destination is write-tested from one of your sites before it can be used, so a bad credential or a locked-down bucket is caught immediately rather than on the night a client actually needs a restore. Check runs it again any time.
- Attach the destination to a site’s backup schedule: on the site’s Backups tab, under Schedule & offsite copy.
Limits & defaults
| Setting | Default |
|---|---|
| Credential storage | Encrypted at rest in the hub's database; delivered per-job inside the cryptographically signed backup command and wiped when the job finishes |
| Verification | Every destination is write-tested on save |
| Kinds | S3-compatible and SFTP on every plan; Google Drive and Dropbox on Studio and above |
| Permissions | Only owners and admins can see or change storage credentials |
| Health score effect | A backup profile with no offsite destination costs a site 10 health-score points — see The health score, explained |
Troubleshooting
Verification keeps failing
Double-check the bucket region/endpoint (for S3-compatible services) or the host/port/key (for SFTP); the write test uses the exact credentials you entered, so a typo there is the most common cause.
The health score still says no offsite destination after I added one
The destination has to actually be attached to that site's backup schedule, not just exist for the organization.