Every provider, ranked by egress cost
Same outbound volume, all providers side by side. Rates are per-GB internet egress after each provider's free tier.
| Provider | Rate / GB | Free / mo | Cost / mo | Cost / yr |
|---|
Why egress is the cloud bill's quiet killer
Storing data is cheap. Moving it out is where the hyperscalers make margin. AWS, Google Cloud and Azure all charge roughly $0.08–$0.12 per GB of data sent to the public internet, after a small free allowance — while data coming in is free. Because egress scales with traffic, not storage, a viral file, a chatty API or a video workload can quietly add hundreds or thousands of dollars a month. The fix is almost always architectural: cache at the edge, compress responses, or move egress-heavy storage to a zero-egress provider.
Zero-egress providers change the math
Cloudflare R2 charges $0 for egress entirely, and Backblaze B2 gives very generous free egress (especially through its Cloudflare bandwidth-alliance partnership). For a 2 TB/month media workload that costs ~$180/mo on AWS, the same egress on R2 is $0. You still pay for storage and operations, but the line that grows with your success disappears. The trade-off is fewer regions and a smaller ecosystem — fine for static assets, downloads and media, less ideal if you're deeply tied to one cloud's services.
Cut egress before you switch clouds
Even on AWS or GCP you can slash egress: put a CDN in front so most bytes are served from cache (egress to a same-provider CDN is cheaper or free), gzip/brotli your API and HTML, serve modern image formats, and avoid chatty endpoints. Model the rest of your bill with the API stack cost calculator, size a download or storage API with the API request cost calculator, and read more in the API costs that double your bill.
Related tools & guides
API stack cost calculator · API alternatives finder · market-data APIs · free API tiers