File Storage · head to head
Cloudflare R2 vs Wasabi

Cloudflare R2
File Storage
S3-compatible object storage that charges nothing for egress to the internet
- From
- Free
- Rated
- -
The short version
- Only Cloudflare R2 has a free tier, so it costs nothing to try first.
- Each has a real cost: Cloudflare R2 there is no archive tier below Infrequent Access, so genuinely cold data costs roughly ten to fifteen times what it would cost in a deep archive class and there is nowhere cheaper to lifecycle it to.; Wasabi 90-day minimum storage duration with no option to delete before full period without penalty
- They diverge on capability: Cloudflare R2 covers Zero egress billing, Wasabi covers Hot Cloud Storage.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Cloudflare R2 and Wasabi actually diverge.
| Attribute | Cloudflare R2 | Wasabi |
|---|---|---|
| Starting price | Free | $7.99/month |
| Pricing model | Per gigabyte stored per month | Unknown |
| Free tier | Yes | No |
| Category | File Storage | Cloud |
| Founded | Unknown | 2015 |
Identical on both: platforms (Web, API), user rating (Not yet rated).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Cloudflare R2
- Zero egress billing
- S3 API compatibility
- Worker binding
- Jurisdictional restriction
- Infrequent Access tier
- Custom domain serving
Only in Wasabi
- Hot Cloud Storage
- S3 Compatible API
- Object Lock
- Versioning
- Multi-region
- Data Migration Tools
- Immutability
- Ransomware Protection
What people use each for
The jobs each tool is most often brought in to do.
Cloudflare R2
- Serving a large media or asset library to the public where transfer out, not storage, is the dominant costnot Wasabi
- Hosting a container or artefact registry that thousands of CI runners pull from every daynot Wasabi
- Distributing model weights or open datasets that are downloaded far more often than they are updatednot Wasabi
- Moving off S3 specifically to stop paying data transfer charges on a read heavy bucketnot Wasabi
Wasabi
- Backup and recoverynot Cloudflare R2
- Media storagenot Cloudflare R2
- Archive replacementnot Cloudflare R2
- Ransomware protectionnot Cloudflare R2
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Cloudflare R2
- There is no archive tier below Infrequent Access, so genuinely cold data costs roughly ten to fifteen times what it would cost in a deep archive class and there is nowhere cheaper to lifecycle it to.
- Class A operations are billed at 4.50 USD per million, so a workload that writes millions of small objects can spend more on operations than on the storage those objects occupy.
- Infrequent Access carries both a retrieval fee and a thirty day minimum storage duration, so data that is deleted or re-read sooner ends up more expensive than if it had stayed on Standard.
- You choose a location hint rather than a region, so you cannot prove to an auditor which datacentre holds an object unless you use a jurisdiction restricted bucket, and jurisdictions are limited.
- Support level follows your Cloudflare account plan rather than the storage spend, so a team on a low tier account gets ticket support with no storage specific SLA, and an R2 incident is a Cloudflare incident you cannot fail over from because the free egress only exists inside Cloudflare.
Wasabi
- 90-day minimum storage duration with no option to delete before full period without penalty
- Significantly smaller global footprint than AWS with only 16 regions, resulting in higher latency for users in underserved regions
- Performance can degrade with high-volume transactions requiring throughput management strategies
- Hot storage only, no cold/archival storage tier for long-term data at lower cost
- Support responsiveness gaps with teams experiencing multi-day waits for critical issue resolution
Pricing, plan by plan
Cloudflare R2
Free- Free tierFree
- 10 GB stored per month
- 1 million Class A operations
- 10 million Class B operations
- Standard$0.015/month
- Per gigabyte stored per month
- 4.50 USD per million Class A operations
- 0.36 USD per million Class B operations
- Infrequent Access$0.01/month
- Per gigabyte stored per month
- Per gigabyte data retrieval fee
- Thirty day minimum storage duration
Wasabi
$7.99/monthNo published plan breakdown. See the Wasabi review.
Which should you pick?
Choose Cloudflare R2 if
- You need zero egress billing.
- You want to start without paying.
- You work on Web, API.
- You also want s3 api compatibility.
Choose Wasabi if
- You need hot cloud storage.
- You work on Web, API.
- You also want s3 compatible api.
Questions people ask
- Is Cloudflare R2 or Wasabi better?
- Neither clearly leads. Cloudflare R2 starts at Free and Wasabi at $7.99/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Cloudflare R2 or Wasabi?
- Cloudflare R2 has a free tier; the other does not. Paid plans start at Free for Cloudflare R2 and $7.99/month for Wasabi.
- Does Cloudflare R2 or Wasabi run on more platforms?
- Both run on Web, API, so platform support will not decide this one for you.
- Can I use Cloudflare R2 for free?
- Yes. Cloudflare R2 has a free tier, so you can try it without paying. Wasabi starts at $7.99/month.
- What is Cloudflare R2 best used for?
- Cloudflare R2 is most often used for serving a large media or asset library to the public where transfer out, not storage, is the dominant cost, hosting a container or artefact registry that thousands of ci runners pull from every day, distributing model weights or open datasets that are downloaded far more often than they are updated, moving off s3 specifically to stop paying data transfer charges on a read heavy bucket. Of those, serving a large media or asset library to the public where transfer out, not storage, is the dominant cost and hosting a container or artefact registry that thousands of ci runners pull from every day are not what Wasabi is typically brought in for.
- What can Cloudflare R2 do that Wasabi cannot?
- Cloudflare R2 covers Zero egress billing, S3 API compatibility, Worker binding, Jurisdictional restriction. Wasabi covers Hot Cloud Storage, S3 Compatible API, Object Lock, Versioning.
Answered from the vendors’ own pages
Cloudflare R2: Is egress really free, with no hidden transfer charge?
Yes for data served out of R2 to the internet. You still pay per operation for the requests that serve it, and if you pull data into R2 from another provider you pay that provider the egress on the way in.
Wasabi: What is Wasabi's pricing structure?
Wasabi offers pay-as-you-go pricing at $7.99 per TB per month as of July 2026, with no egress or API request fees. Reserved capacity plans are available for multi-year terms with volume discounts.
SourceCloudflare R2: How does the total cost compare with S3 for a public download bucket?
Storage is more expensive per terabyte than S3 Infrequent Access, but S3 charges roughly 90 USD per terabyte served. Any bucket that serves more than about a fifth of its stored volume each month is cheaper on R2.
Wasabi: Does Wasabi charge for data downloads or API calls?
No. Wasabi includes zero egress fees and zero API request fees, which is a major cost advantage over AWS S3. Customers can plan their budget to the penny without worrying about surprise data transfer charges.
SourceCloudflare R2: Can I use R2 without using the rest of Cloudflare?
Yes, it works through the plain S3 API from anywhere. You lose the Worker binding and the free CDN caching in front of it, which is where a lot of the practical benefit sits.
Wasabi: Is there a minimum storage duration requirement?
Yes. Wasabi enforces a 90-day minimum storage term. Users who delete data before 90 days are still charged for the full 90-day period.
SourceCloudflare R2: Does R2 have a cold archive class like Glacier?
No. Infrequent Access is the coldest tier, at two thirds of the Standard rate plus retrieval fees.
Wasabi: Is Wasabi S3-compatible?
Yes. Wasabi Hot Cloud Storage is fully S3-compatible, meaning organizations can integrate it into existing workflows without rewriting application code used with AWS S3.
Related pages
More on Cloudflare R2
Other head to heads
- Cloudflare R2 vs Storj
- Cloudflare R2 vs Tigris
- Cloudflare R2 vs Backblaze
- Cloudflare R2 vs IDrive e2
- Cloudflare R2 vs Scality RING
- Cloudflare R2 vs MinIO
- Cloudflare R2 vs Cloudian
- Cloudflare R2 vs Panzura
- Cloudflare R2 vs Ceph
- Cloudflare R2 vs pCloud
- Cloudflare R2 vs Nasuni
- Cloudflare R2 vs TrueNAS
- Cloudflare R2 vs Sync.com
- Cloudflare R2 vs AWS (Amazon Web Services)
- Cloudflare R2 vs DigitalOcean
- Cloudflare R2 vs Hetzner Cloud
- Cloudflare R2 vs Scaleway
- Cloudflare R2 vs Linode
- Cloudflare R2 vs Vultr
- Cloudflare R2 vs Zeabur
- Cloudflare R2 vs Porter
- Cloudflare R2 vs Contabo
- Cloudflare R2 vs Encore
- Cloudflare R2 vs Google Cloud Platform
- Cloudflare R2 vs Microsoft Azure
- Cloudflare R2 vs HAProxy
- Cloudflare R2 vs IBM Cloud
- Cloudflare R2 vs kind
- Cloudflare R2 vs Koyeb
- Cloudflare R2 vs Kustomize
- Cloudflare R2 vs Linkerd
- Wasabi vs Storj
- Wasabi vs Tigris
- Wasabi vs Backblaze
- Wasabi vs IDrive e2
- Wasabi vs Scality RING
- Wasabi vs MinIO
- Wasabi vs Cloudian
- Wasabi vs Panzura
- Wasabi vs Ceph
- Wasabi vs pCloud
- Wasabi vs Nasuni
- Wasabi vs TrueNAS
- Wasabi vs Sync.com
- Wasabi vs AWS (Amazon Web Services)
- Wasabi vs DigitalOcean
- Wasabi vs Hetzner Cloud
- Wasabi vs Scaleway
- Wasabi vs Linode
- Wasabi vs Vultr
- Wasabi vs Zeabur
- Wasabi vs Porter
- Wasabi vs Contabo
- Wasabi vs Encore
- Wasabi vs Google Cloud Platform
- Wasabi vs Microsoft Azure
- Wasabi vs HAProxy
- Wasabi vs IBM Cloud
- Wasabi vs kind
- Wasabi vs Koyeb
- Wasabi vs Kustomize
- Wasabi vs Linkerd

