Comparison

Updated October 25, 2026

· ~2 min read

S3 vs Cloudflare R2 in 2026: Egress, Request Pricing and When R2 Actually Saves Money

S3
Cloudflare R2
Egress
Object Storage
Cost Optimization

R2's pitch is one line: S3-compatible storage with no egress fees. It is accurate, and for some workloads it saves most of the bill. For others it saves nothing, because the egress was never going to be paid at S3's internet rate.

The question is where your bytes go. To browsers through a CDN, to another cloud, or nowhere at all.

List prices

Amazon S3 (US East)

Cloudflare R2

Storage

Standard $0.023/GB-month (first 50 TB); colder classes down to Glacier Deep Archive

Standard $0.015/GB-month; Infrequent Access $0.01 with $0.01/GB retrieval

Writes

$0.005 per 1,000 PUT/COPY/POST/LIST ($5 per million)

Class A $4.50 per million

Reads

$0.0004 per 1,000 GET ($0.40 per million)

Class B $0.36 per million

Egress to internet

$0.09/GB for the first 10 TB, after 100 GB free per month account-wide

Free

Egress to CloudFront

Free

Not applicable

Free tier

100 GB transfer out per month (account-wide, always-free)

10 GB storage, 1M Class A, 10M Class B per month

Worked example: 1 TB stored, 5 TB served per month, 10M reads, 1M writes

Setup

Approximate monthly cost

Notes

S3 serving directly

~$484

Egress is $452 of it

S3 behind CloudFront, pay-as-you-go

~$375

First 1 TB from CloudFront is free, then $0.085/GB

S3 behind CloudFront Pro flat-rate ($15)

~$40

10M requests and 50 TB included; 50 GB S3 credit; requires a WAF web ACL

R2 with a custom domain

~$15

Reads and writes fit the free tier

Where R2 wins outright

Traffic that cannot go through a CDN. Dataset downloads by other companies, model weights pulled into another cloud's GPUs, multi-cloud replication, customer exports, a public API that returns large files. None of it is cacheable at an edge and all of it is billed by S3 at internet rates. Here R2 is not 20% cheaper; it removes the line item. R2 also suits teams already on Cloudflare: a Worker can read and write a bucket with no credentials to manage, and public buckets work on a custom domain.

What you give up with R2

R2 implements the core S3 API, so most SDKs and tools work with an endpoint change. It is not S3's whole surface. There are no deep-archive storage classes, no S3 event notifications into Lambda, SQS or EventBridge, no Athena or Redshift Spectrum reading it in place, no S3 Tables or S3 Vectors, and no IAM policies. Access is through Cloudflare API tokens. The hidden cost is everything inside AWS that reads the data. A Lambda or Glue job in us-east-1 reading from R2 pulls bytes over the internet: free to leave R2, but slower than in-region S3 and outside your VPC endpoints and IAM model.

Which one

Question 1 of 2

Who downloads the data?

Our verdict

**Serving files to the internet through a CDN:** S3 behind CloudFront on a flat-rate plan is now close to R2 on cost, and you keep S3's features and IAM. **Serving data directly to other clouds, partners or customers' systems:** R2. That traffic does not go through a CDN, and $0.09/GB adds up fast. **Data that mostly sits still, or is read inside AWS:** S3. Egress is not your cost; storage classes, lifecycle rules and in-region access are.

Related solutions

AWS Cost Optimization & FinOps Sprint

Reduce your AWS bill by 20–60% while improving performance and reliability.

1–3 weeks
$6k–$18k
View

AWS Architecture Review

A focused, senior-level review of your current AWS architecture, with a prioritized list of what to fix and why.

1 week
$4k–$8k
View

Get your storage and delivery costs modeled

We work with startups and growing companies on AWS architecture decisions. Tell us about your situation and we will recommend the right approach.

As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.