Learn
Best Video Streaming CDN in 2026? 7 Providers Compared With Real Performance Data
Best CDN for Video Streaming in 2026: 7 Providers Compared A single rebuffer event at the two-second mark costs you 8% ...
A single misconfigured price class on CloudFront can inflate your monthly bill by 40% without delivering a measurable latency improvement to your actual user base. That is not a hypothetical — it is the kind of discovery teams make when they finally sit down with a CloudFront pricing calculator and model their real traffic distribution against the rate card. As of Q2 2026, CloudFront's tiered pricing spans nine geographic regions with per-GB rates ranging from $0.020 in the cheapest tier to $0.170 in the most expensive. Request charges, Lambda@Edge invocations, CloudFront Functions executions, origin shield fees, and real-time log delivery each add their own line items. This article gives you the exact rate tables, a workload-profile decision matrix you will not find in the AWS docs, and a direct cost comparison so you can run your own numbers this week.

The AWS pricing page lists the components. What it does not do is tell you which ones dominate for your workload. Here is a rank-ordered breakdown of the cost drivers that matter at scale, updated for the rates published in 2026.
DTO is almost always the largest line item. CloudFront uses a declining tiered model per region. For the United States, Mexico, and Canada tier, the first 10 TB per month costs $0.085 per GB. From 10 TB to 50 TB, it drops to $0.080. At 150 TB to 500 TB, you hit $0.060, and at 5 PB+, the rate falls to $0.020 per GB. Europe follows a nearly identical curve. South America and India, however, start at $0.110 and $0.109 per GB respectively, and their floor rates never dip below $0.040. If your calculator does not let you split traffic by region, the output is noise.
Requests are the stealth cost for workloads that serve many small objects — API responses, tracking pixels, font files. As of 2026, HTTPS requests in the US/Europe tier cost $0.0100 per 10,000 requests. In India, that jumps to $0.0090 for HTTP but $0.0120 for HTTPS per 10,000. High-request-count, low-byte workloads can see request charges rival or exceed DTO.
Lambda@Edge charges $0.60 per million invocations plus $0.00005001 per 128 MB-second of compute. CloudFront Functions cost $0.10 per million invocations with no duration charge. If you are running header manipulation or A/B routing at the edge, model the invocation count carefully — a site serving 500 million requests per month racks up $50/month on CloudFront Functions alone, versus $300+ on Lambda@Edge for equivalent logic.
Origin Shield adds $0.0090 per 10,000 incremental requests in most regions. Real-time log delivery costs $0.01 per million log lines. These are small individually but compound fast on high-traffic distributions.
The AWS Pricing Calculator lets you add a CloudFront estimate and input monthly DTO, request counts, and region splits. Here is how to avoid the three mistakes that produce misleading numbers.
First, do not use a single-region model. Pull your CloudFront access logs or use CloudWatch metrics to get the actual percentage of bytes served from each edge region. Weight your DTO inputs accordingly. Second, separate HTTP from HTTPS request volumes — they carry different rates. Third, include invalidation costs ($0.005 per path after the first 1,000 free paths per month) if you run frequent cache busts during deployments.
The calculator updates its output in real time as you adjust inputs. Use it to run at least three scenarios: baseline month, peak month (product launch, sale event, or live stream), and a projected 12-month growth case. The delta between baseline and peak is where budget surprises live.
This is the section most CloudFront pricing guides skip entirely. AWS exposes three price classes that control which edge locations serve your content. Choosing the wrong one either wastes money or adds latency for users you care about.
| Price Class | Regions Included | Effective DTO Range (per GB) | Best For |
|---|---|---|---|
| Price Class 100 | US, Canada, Europe, Israel | $0.020 – $0.085 | North America/Europe-only SaaS, internal tools, B2B APIs |
| Price Class 200 | Price Class 100 + Asia, Africa, Middle East | $0.020 – $0.140 | Global consumer apps with moderate APAC traffic |
| Price Class All | All CloudFront edge locations | $0.020 – $0.170 | Global streaming, gaming, e-commerce requiring South America/Australia coverage |
The decision matrix: if fewer than 5% of your requests originate from South America or Australia, Price Class 200 saves you the South America premium ($0.110/GB floor) without meaningful latency impact. If your user base is entirely North America and Europe, Price Class 100 eliminates the Asia-Pacific surcharge. Run your CloudFront access logs through a geo-IP aggregation to get the actual distribution before choosing.
Raw rate cards mean nothing without traffic context. Below are four modeled scenarios using 2026 CloudFront rates with Price Class All, US-weighted traffic, and HTTPS requests.
| Workload | Monthly DTO | Requests | Est. CloudFront Cost |
|---|---|---|---|
| SaaS platform (static + API) | 5 TB | 200M | ~$625 |
| Video streaming service | 100 TB | 500M | ~$7,350 |
| Game patch distribution | 500 TB | 50M | ~$32,500 |
| E-commerce (global, peak season) | 50 TB | 1B | ~$5,100 |
Notice how the e-commerce scenario pays almost as much as the streaming scenario despite pushing one-half the bytes — request charges at a billion HTTPS requests add roughly $1,000. Your CloudFront pricing calculator needs to account for this ratio, not just raw throughput.
CloudFront's tiered model rewards very high volume at the top of the curve but starts expensive for workloads between 10 TB and 200 TB — the range where most mid-market companies sit. Committed-use discounts (CloudFront Security Savings Bundle) can reduce the bill by up to 30%, but they require a 1-year minimum commitment and only apply to DTO and security request charges, not compute or logs.
For teams that want predictable costs without a commitment lock-in, BlazingCDN offers a direct alternative with flat, volume-based pricing: $100/month covers up to 25 TB ($0.004/GB), scaling down to $0.002/GB at the 2 PB tier. That translates to a 50–75% cost reduction against CloudFront's standard rates for equivalent delivery volumes, with 100% uptime SLA, fast scaling under demand spikes, and flexible configuration. Clients like Sony use BlazingCDN for high-volume delivery where cost efficiency at scale is the deciding factor.
Multiply your monthly data transfer by the tiered per-GB rate for each region, then add HTTPS request charges at $0.0100 per 10,000 requests (US/Europe, as of 2026). The AWS pricing calculator lets you input both values and see a combined estimate. Always split by region — a single blended rate will under- or over-estimate by 20–40%.
Price Class 100 restricts delivery to US, Canada, Europe, and Israel — the cheapest edge locations. Price Class 200 adds Asia, Africa, and the Middle East, which carry higher per-GB rates. If your user base is concentrated in North America and Europe, Price Class 100 can cut your bill significantly with negligible latency impact for those users.
The AWS Pricing Calculator allows you to add Lambda@Edge and CloudFront Functions as separate line items within the same estimate. You need to input invocation counts and, for Lambda@Edge, the average execution duration and memory allocation. CloudFront Functions are simpler: $0.10 per million invocations with no duration component.
AWS advertises up to 30% savings on CloudFront DTO and security request charges with a 1-year commitment. The actual savings depend on your baseline spend and how predictable your traffic is. If your monthly volume swings more than 40% seasonally, the committed spend floor may exceed your low months, reducing net savings.
Yes. AWS offers 1 TB of data transfer out, 10 million HTTP/HTTPS requests, and 2 million CloudFront Functions invocations per month at no charge, perpetually (not limited to the 12-month free tier). This covers light development and staging workloads but is irrelevant for production traffic at any meaningful scale.
Pull your last 90 days of CloudFront usage from the AWS Cost Explorer, broken down by region and usage type. Feed those numbers into the AWS CloudFront pricing calculator with three scenarios: current baseline, 2x growth, and peak-event spike. Compare the output against at least one alternative provider's rate card at the same volumes. If the delta exceeds 30%, you have a procurement conversation worth having. If it does not, you at least have a defensible cost model for the next budget cycle. Either way, you leave with a number instead of a guess.
Learn
Best CDN for Video Streaming in 2026: 7 Providers Compared A single rebuffer event at the two-second mark costs you 8% ...
Learn
Video CDN Providers Compared: BlazingCDN vs Cloudflare vs Akamai for OTT If you are choosing a video CDN for an OTT ...
Learn
Video CDN Pricing Explained: How to Stop Overpaying for Streaming Bandwidth Video already accounts for 38% of total ...