18 November 2026 · Cloud Storage & Infrastructure · 5 min read
Serve two terabytes of files out of an S3 bucket in a month and AWS bills $180.00 for the privilege of letting that data leave their network. Serve the same two terabytes from Cloudflare R2 and the egress line reads $0.00. Not a promo, not an intro-tier teaser — that's the standing rate on both sides, pulled straight from our own pricing registry and checked against each provider's current pricing page.
S3 egress costs $0.09 per GB for the first 10TB each month (verified against AWS's own S3 pricing page, 2026-10-29). Uploads are free. It's only outbound traffic — every image, video, or file your app serves to a user — that AWS meters. Here's what that looks like at a few realistic monthly volumes:
| Monthly egress | S3 egress fee ($0.09/GB) | R2 egress fee |
|---|---|---|
| 100 GB | $9.00 | $0.00 |
| 500 GB | $45.00 | $0.00 |
| 1 TB (1,000 GB) | $90.00 | $0.00 |
| 2 TB (2,000 GB) | $180.00 | $0.00 |
| 5 TB (5,000 GB) | $450.00 | $0.00 |
| 10 TB (10,000 GB) | $900.00 | $0.00 |
None of that includes S3's own storage charge, request pricing, or cross-region transfer — it's purely the cost of the data walking out the door. For any app that serves the same files to users over and over (product images, video, downloadable reports, API responses with payloads), that line scales with traffic, not with how much you're storing.
Cloudflare R2's whole pitch is zero egress, and it isn't a teaser rate — $0 at any volume, verified against Cloudflare's own R2 pricing page the same day. But R2 isn't free to run. Storage costs $0.015/GB/month, and that bill shows up whether anyone downloads a single file or not. Storing 500GB on R2 costs 500 x $0.015 = $7.50/month in storage alone — compare that to the $45.00/month S3 would charge in egress fees for serving that same 500GB just once, and the gap is the whole story. R2 didn't make storage free. It moved the meter from "per GB served" to "per GB sitting there," which is a much better deal the moment you serve a file more than once.
It would be a clean story to say "Cloudflare wins everywhere," but the compute side doesn't cooperate. Cloudflare Workers' Paid plan is a flat $5/month for 10 million requests. AWS Lambda charges $0.20 per 1 million requests — about $2.00 for that same 10 million, which is cheaper on the request line alone. Lambda also bills GB-seconds of execution duration on top of that, and that number depends entirely on your function's memory allocation and runtime, so we're not going to invent a blended figure for it. Request pricing favors Lambda. Total compute cost depends on what your function actually does, and that's a number only your own workload can give you.
I don't treat "R2 is free" as the takeaway — it isn't, storage still bills. What changed is which number to ask a vendor for before committing a media-heavy or file-serving workload to one cloud. For a project that serves the same assets repeatedly, the egress line is usually the bigger number by the time traffic grows, and it's the one most teams forget to ask about until the first real invoice.
Run your own numbers on the cloud egress cost calculator (AWS, Google Cloud, Azure, R2, B2, Wasabi side by side) or the object storage cost calculator, check compute separately on the serverless cost calculator, or read the full AWS Lambda and Cloudflare pricing pages. New to usage-based cloud billing in general? Start with the free API-cost guides.
S3 egress and R2 storage/egress figures verified against AWS's and Cloudflare's own pricing pages, 2026-10-29. Lambda and Workers request pricing from the same registry; both providers also bill duration/compute-time separately, which is workload-specific and not included above. Prices change — confirm current rates on the provider's own page before budgeting a high-traffic workload.