CloudFront price classes cost: paying less by serving fewer regions

Quick answer

CloudFront price classes control which edge locations serve your content, and the more expensive regions cost more per GB. Price Class All uses every edge location at each region's rate (South America and India are the priciest, around $0.11 to $0.17 per GB). Price Class 200 excludes the most expensive locations. Price Class 100 uses only North America, Europe, and Israel, the cheapest tiers at about $0.085 per GB. Choosing a lower class caps your per-GB rate but routes distant users to farther edges, adding latency. The trade: if few users are in expensive regions, a lower price class cuts cost with little user impact.

CloudFront charges for data transfer out to viewers, and the rate depends on which edge location served the request. Some regions, notably South America and India, cost roughly twice the North America and Europe rate. Price classes let you exclude the expensive regions entirely, capping the per-GB rate you pay in exchange for routing viewers there to a farther, cheaper edge.

The three price classes

Price class	Regions served	Effect on cost
Price Class All	All edge locations worldwide	Highest reach, highest max rate
Price Class 200	Excludes the most expensive locations	Lower cost, near-global reach
Price Class 100	North America, Europe, Israel only	Lowest cost, limited reach

With Price Class All, a viewer in Sao Paulo is served from a local edge at the South America rate, around $0.11 to $0.17 per GB. With Price Class 100, that same viewer is served from a North American or European edge at about $0.085 per GB, cheaper per byte but with more latency because the content travels farther. Price Class 200 sits in between, keeping most of the world's fast edges while dropping only the priciest.

How much you actually save

The saving depends entirely on where your viewers are. If nearly all your traffic is North American and European, Price Class 100 changes almost nothing on cost because those regions are already the cheapest tier, but it prevents an occasional expensive-region request from being billed at the high rate. If you have real traffic from South America, India, or Australia, a lower price class routes it to a cheaper edge and can meaningfully cut the per-GB blended rate, at the cost of higher latency for those users. For 50 TB a month with 10 percent expensive-region traffic, the difference can be a few hundred dollars.

The latency trade

The catch is user experience. Serving a Sydney user from a US edge adds real round-trip latency, which hurts page load and video start times. Price classes are therefore a cost lever for content where a lower price class does not meaningfully harm the users you care about, for example internal tools, region-specific applications, or workloads whose distant traffic is low-value. For a global consumer product where every user's latency matters, Price Class All is usually worth the higher rate.

Choosing the right class

Look at your viewer geography first. If your audience is concentrated in North America and Europe, Price Class 100 costs the same for those users and caps any stray expensive-region charges, so it is often a free win. If you serve a global audience where distant users matter, weigh the per-GB saving against the latency. This is one lever among many in CloudFront cost optimization, alongside cache hit ratio and request fees, and part of the broaderCDN cost picture.

The right price class depends on data volume and viewer distribution, both of which you can estimate up front. Price your CloudFront distribution against the resource catalog so the class you choose reflects real traffic geography rather than a default.

FAQ

What are CloudFront price classes?

Price classes control which edge locations serve your content. Price Class All uses every edge location at each region's rate. Price Class 200 excludes the most expensive locations. Price Class 100 uses only North America, Europe, and Israel, the cheapest tiers at about $0.085 per GB. A lower class caps your per-GB rate by routing distant viewers to farther, cheaper edges, trading some latency for cost.

How much can price classes save on CloudFront?

It depends on viewer geography. If nearly all traffic is North American and European, a lower class changes little because those regions are already cheapest, but it caps stray expensive-region charges. If you have real traffic from South America, India, or Australia (regions costing up to about $0.17 per GB), a lower class routes it to a cheaper edge and can cut the blended per-GB rate meaningfully, sometimes hundreds of dollars a month.

What is the downside of a lower CloudFront price class?

Higher latency for viewers in the excluded regions. Serving a Sydney or Sao Paulo user from a US or European edge adds round-trip time that hurts page load and video start. Price classes are a cost lever for content where distant users are low-value or tolerant of latency, such as internal tools or region-specific apps. For a global consumer product where every user's latency matters, Price Class All is usually worth the higher rate.

Which CloudFront price class should I choose?

Look at your viewer geography. If your audience is concentrated in North America and Europe, Price Class 100 costs the same for those users and caps any stray expensive-region charges, so it is often a free win. If you serve a global audience where distant users matter, use Price Class 200 or All and weigh the per-GB saving against the latency impact for those viewers.

Do price classes affect cache hit ratio or requests?

No, price classes only change which edge locations serve content and therefore the data transfer rate. Cache hit ratio, request fees, and origin fetch costs are separate levers. A lower price class can slightly change caching behavior because fewer edges are used, but the main effect is on the per-GB data transfer rate. Optimize price class alongside cache hit ratio and request reduction for full CloudFront savings.

How does C3X help with CloudFront cost?

C3X prices your CloudFront distribution from Terraform before you deploy, including the price class and expected data transfer, so the per-GB cost is visible in the pull request. That lets you choose a price class based on real traffic volume and viewer geography at design time, rather than defaulting to Price Class All and paying the highest rates for regions your users may not even be in.

What to do next

Price your CloudFront distribution before you deploy it. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.