Document backup
Cloud Storage
Backup signed documents to seven cloud providers
Keep primary copies on your WordPress server, then auto-sync signed PDFs to Google Drive, Dropbox, OneDrive, Amazon S3, Wasabi, Cloudflare R2 or Backblaze B2.
Sign complete → upload · folder rules · TLS in transit
Self-hosted first, cloud as redundancy
WPsigner stores documents on your WordPress site first. Cloud integrations add secondary backups you control — not a mandatory SaaS vault.
Seven providers
Google Drive, Dropbox, OneDrive, Amazon S3, Wasabi, Cloudflare R2 and Backblaze B2.
Automatic after signing
Upload signed PDFs as soon as the signing process completes — no manual export.
Folder organization
Structure backups by date, document type, signer or custom paths your team already uses.
How cloud backup works
Connect a provider once, set folder rules, and every completed signature can sync automatically.
- 1
Connect a provider
Authorize Google Drive, Dropbox, OneDrive or configure S3-compatible credentials for S3, Wasabi, R2 or Backblaze B2.
- 2
Choose folders and naming
Define year/month, document type, signer name or a custom folder structure WPsigner creates for you.
- 3
Complete a signature
When signing finishes, the signed PDF stays on WordPress and a backup copy uploads to the cloud.
- 4
Verify and share
Open the cloud copy for team access while the authoritative file remains on your server.
Consumer drives and S3-compatible object storage
Use familiar drives for teams on Google or Microsoft 365, or enterprise object storage with bucket policies, encryption and lifecycle rules — including Backblaze B2 for cost-efficient S3-compatible backups.
- Google Drive, Dropbox and Microsoft OneDrive
- Amazon S3 with custom bucket policies
- Wasabi and Cloudflare R2 (S3-compatible)
- Backblaze B2 for affordable object storage
- TLS/SSL encrypted uploads in transit
What you can configure
- Google Drive auto-sync
- Dropbox backup folders
- OneDrive for Business
- Amazon S3 buckets
- Wasabi cloud storage
- Cloudflare R2
- Backblaze B2
- Per-provider folder structures
Built for redundant document archives
Team shared drives
Drop signed contracts into a shared Google Drive or Dropbox folder for ops visibility.
Microsoft 365 shops
Land backups in OneDrive for Business alongside existing SharePoint workflows.
Object-storage compliance
Push PDFs to S3, Wasabi, R2 or Backblaze B2 with encryption and lifecycle policies.
Disaster recovery
Keep WordPress as source of truth plus an off-site copy if the host fails.
Frequently asked questions
Which cloud storage providers does WPsigner support?
Seven providers: Google Drive, Dropbox, Microsoft OneDrive, Amazon S3, Wasabi, Cloudflare R2 and Backblaze B2. Signed documents can upload automatically after signing completes.
Are documents stored locally and in the cloud?
Yes. WPsigner is self-hosted, so documents live on your WordPress server first. Cloud integrations create additional backup copies — secondary storage you choose, for sovereignty plus redundancy.
Can I organize cloud backups by folder?
Yes. Configure folder structures per provider — by year/month, document type, signer name or custom paths. WPsigner creates folders automatically.
Is the cloud upload encrypted?
Yes. Uploads use TLS/SSL in transit. At-rest encryption depends on your provider settings (S3 encryption, Drive encryption, B2 server-side encryption, and so on).
Why include Backblaze B2?
Backblaze B2 is S3-compatible object storage with competitive pricing. It fits teams that want off-site redundancy without locking into a single hyperscaler.
Do I have to use cloud storage?
No. Cloud backup is optional. You can keep documents only on WordPress if that matches your policy.
Never lose a signed document
Automatic cloud backup to seven providers — self-hosted WordPress plus the redundancy you choose.
Stop paying per envelope
Choose an annual or lifetime license with unlimited documents and no per-envelope fees. Keep control of your data and signing workflows.