AWS data transfer vs Cloudflare

This comparison holds monthly internet bytes constant and looks only at the public on-demand data-transfer line. It does not include CloudFront, Magic Transit, or enterprise contracts. Open the egress calculator with the same gigabytes to read the current snapshot for AWS us-east-1 after the free grant, and Cloudflare’s documented zero internet egress for R2/Workers.

Same 2 TB to the internet

On AWS us-east-1, 2,048 GB minus the 100 GB free grant leaves 1,948 GB on the first paid internet tier — run that figure on the egress calculator. Cloudflare documents zero egress for those bytes. The rest of the Cloudflare bill (Workers requests and CPU-ms, or R2 storage and Class A/B) is not zero, and the Workers Paid platform fee applies if you are on that plan.

At 50 GB/month both sides can land near zero after free allowances. The gap opens when downloads, APIs, or asset libraries cross a few hundred gigabytes.

When AWS is still the rational default

If the bytes never leave us-east-1, AWS same-region traffic is often free on the data-transfer SKU. If you already run the application, database, and IAM story on AWS, moving only the download path has an engineering cost the calculator cannot see. Credits and the 12-month Free Tier also change year one.

How to rerun the comparison

Open the egress calculator, set destination to Internet, enter your monthly GB, and toggle free tier. The comparison table uses a peer region in the same geography so you are not matching Tokyo AWS against Iowa GCP by accident.