The Egress Tax: Why the Same 100 GB Costs $1.35 or $38.30
28× — S3 vs R2 for the same workload the number that matters here
By Stan K.
Storage pricing pages quote $/GB stored. The bill that arrives is dominated by bandwidth out. The same 100 GB stored plus 500 GB served costs 28× more on AWS S3 than on Cloudflare R2 — and the gap compounds with scale.

Object storage pricing pages are designed around the number you understand ($/GB stored) and quiet about the number that dominates your bill ($/GB delivered). Here is the same modest workload priced across five providers, verified from official pricing pages:
100 GB stored, 500 GB served per month.
| Provider | Storage | Egress rule | Monthly bill |
|---|---|---|---|
| Cloudflare R2 | $0.015/GB (10 GB free) | $0.00/GB, unlimited | ~$1.35 |
| Backblaze B2 | $6.95/TB (10 GB free) | Free ≤3× stored, then $0.01/GB | ~$2.63 (≈$0.63 via Cloudflare) |
| Hetzner Object Storage | €6.49 base (1 TB + 1 TB incl.) | included | €6.49 |
| Wasabi | $7.99/TB, 1 TB minimum | “free” ≤1× stored (fair use) | $7.99* |
| AWS S3 | $0.023/GB | $0.09/GB after 100 GB free | ~$38.30 |
*Wasabi’s row hides its own trap — the 5:1 served-to-stored ratio violates its fair-use policy. See below.
$36.00 of the $38.30 S3 bill is egress — 94%S3, 100 GB + 500 GB workload
Storage costs $2.30. Moving the data out costs $36.00. The product you thought you were buying is a rounding error on the product you were actually sold.
The gap compounds
Scale the same ratio to a media app — 2 TB stored, 8 TB served monthly, 5M GET requests:
- AWS S3: ~$759/month ($46 storage + $711 egress + requests)
- Cloudflare R2: $30/month (storage only; requests covered by the free tier)
At that point egress is 25× the entire R2 bill. This is why “which storage provider” is usually the wrong question — “who charges for egress” is the question.
The known workaround, priced
AWS’s own mitigation: serve S3 through CloudFront. Transfer from S3 to CloudFront is free, and CloudFront includes 1 TB/month of free egress before $0.085/GB kicks in. For the media-app example that cuts the bill from ~$759 to roughly $140–180/month — still 5–6× the R2 bill, but no longer absurd. If you’re committed to the AWS ecosystem, it’s mandatory. If you’re not, R2 and the B2+Cloudflare combination simply don’t have the tax.
The three honest fine-print traps
1. Wasabi’s three-way squeeze. The 1 TB minimum floor ($7.99/month whether you store 10 GB or 900 GB), a 90-day minimum retention billed even for deleted objects, and “free” egress capped at 1× your stored volume per month. Serve 500 GB from 100 GB stored and you’re not a customer anymore — you’re a policy violation. Wasabi remains excellent for exactly one job: write-once archives you rarely read.
2. Hetzner’s base package. €6.49/month includes 1 TB storage and 1 TB egress — poor value at 100 GB, exceptional at 1 TB. The right provider flips as you scale up, not down.
3. B2’s 3× rule and its escape hatch. Direct egress is free up to 3× your average stored volume, then $0.01/GB — but routed through Cloudflare’s Bandwidth Alliance, egress is free with no cap. The catch: rclone restores and server-to-server transfers bypass Cloudflare and fall back on the 3× allowance. The configuration recipe is in B2 + Cloudflare: Free Egress, Done Right.
Operations: the other quiet line item
S3 charges $0.005 per 1,000 PUTs and $0.0004 per 1,000 GETs. R2 charges Class A $4.50/M and Class B $0.36/M. B2 makes Class A/B/C operations free — only deletes (Class D) bill at $0.004/10K. For chatty workloads (many small objects, frequent listings) the operations line can rival small egress bills; for archives it’s noise. Full operation pricing per provider is in the Cloud storage hub tables.
Decision rules
- Serving files to users at any scale → zero-egress provider (R2, or B2 via Cloudflare). The egress tax is a bug of legacy pricing, not a feature you should pay for.
- ~1 TB+, EU-friendly, predictable → Hetzner. The base package stops being a floor and starts being a bargain.
- Write-once archives → Wasabi, accepting the floor, retention and fair-use rules as the price of flat billing.
- Already on AWS → CloudFront in front of S3 is non-negotiable.
And before you store anything: a disk in your own machine is not cloud storage, and the failure mode is different — we wrote about that too.
Run your own numbers: plug your storage and traffic into the free egress calculator and see the bill — storage + egress as one number — before you commit.