Cloudflare R2

Zero egress fees, S3-compatible object storage on Cloudflare's edge. It is S3-compatible, which means blitcp supports it out of the box: pick the r2 preset in creds add, paste your keys, and every transfer gets blitcp's usual treatment — content-hash deduplication before upload, verified writes after, and incremental re-runs that skip unchanged files.

Endpoint

https://<account-id>.r2.cloudflarestorage.com
The account ID is on the right-hand sidebar of the Cloudflare dashboard (R2 section). Region: R2 ignores regions — the preset sets "auto" for you.

Where the keys come from

Cloudflare dashboard → R2 → Manage R2 API Tokens → Create API Token. The token's Access Key ID / Secret Access Key pair is what blitcp stores.

Set it up once

$ blitcp creds add myr2
  Type [s3/azure/gcs/ssh/smb — or a preset: r2/b2/wasabi/…]: r2
  Cloudflare R2 — S3-compatible. Keys: …
  Account: your-account-id
  Endpoint: https://….r2.cloudflarestorage.com
  Access key ID: ********
  Secret access key: ********
  Default bucket (blank = none): backups

Then copy

blitcp ~/photos myr2:backups/photos          # upload, dedup + verify on
blitcp myr2:backups/photos ~/restore     # download

Re-running the same upload only transfers new or changed files. Duplicate content inside the tree is uploaded once. Credentials live in blitcp's AES-256-GCM encrypted credentials file — see the cloud storage guide for the full creds manager.

Notes

Egress is free, which makes R2 a natural offsite-backup target: restores cost nothing.

Also supported: Backblaze B2 · Wasabi · DigitalOcean Spaces · Scaleway Object Storage · Hetzner Object Storage · IDrive e2 · Storj · Oracle OCI Object Storage · iCloud Drive