CloudFront Cost Calculator (bandwidth + request fees)

This CloudFront cost calculator helps you estimate two common CDN line items: bandwidth and requests. Plug in your own $/GB and $ per 10k assumptions, then add them to get a monthly estimate.

Maintained by CloudCostKit Editorial Team. Last updated: 2026-02-23. Editorial policy and methodology.

Best next steps

Use this calculator for the first estimate, then validate the answer with the closest guide or companion tool.

CDN cost calculator (generic) Guide: CloudFront pricing Guide: cache hit rate and origin egress Guide: invalidation pricing

1) Bandwidth

Use monthly GB delivered by the CDN edge to end users. If you start from Mbps charts, convert Mbps to GB/month using the Units Converter.

Inputs

CDN bandwidth (GB / month)
Avg throughput: 30.46 Mbps.
Avg throughput (Mbps)
Est 24,624 GB/month.
Pricing mode
Use tiered mode when pricing changes by volume.
CDN price ($ / GB)
Enter your provider's effective $/GB for the region/path/tier.
Scenario presets

Results

Estimated monthly cost
$600.00
Egress
10,000 GB
Price
$0.06 / GB

2) Requests

If your provider bills per request (often per 10k or per 1M), estimate monthly requests and apply the rate.

Inputs

Requests (per month)
Avg 114.22 req/sec.
Avg RPS
Est 315,187,200 requests/month.
Pricing unit
Per 1M is 100x per 10k.
Price ($ / 10k requests)
Effective rate: $0.75 / 1M requests
Scenario presets

Results

Estimated monthly request cost
$225.00
Requests
300,000,000
Cost per 1M requests
$0.75

CloudFront cost is usually a two-line edge bill, but traffic mix decides which line hurts

This page is strongest when you treat CloudFront as two separate edge charges that happen together: bandwidth delivered to users and request volume at the edge. Many teams only watch one of them, then get surprised when request-heavy traffic or regional mix shifts move the monthly bill.

  • Bandwidth: the edge-delivery line item that usually dominates media-heavy workloads.
  • Requests: the line item that grows faster on small-object, API-heavy, or bot-heavy traffic.
  • Origin side effects: separate from CloudFront itself, but often confused with it during reviews.

Where CloudFront estimates usually drift

  • One blended rate is used even though region mix changes materially across months.
  • Average object size changes, so request fees and bandwidth stop moving together.
  • Teams compare CloudFront edge charges to origin egress and accidentally double-count or undercount adjacent bills.
  • Bot spikes and cache-busting releases increase requests faster than delivered GB.

What to review before trusting the CloudFront baseline

  • Split edge bandwidth and edge requests into separate assumptions instead of forcing one blended story.
  • Check whether your top regions need different effective rates.
  • Review cache hit rate and invalidation habits before assuming request growth is purely user demand.
  • Keep origin egress, log delivery, and invalidation-related work nearby, but not inside the same line item.

Baseline vs request-heavy CloudFront scenarios

Scenario Bandwidth Requests Cache hit rate
Baseline Expected Expected Current
Peak High High Lower under surge

How to review the first real CloudFront month

  • Check whether the miss came from regional rate mix, request growth, or origin-side leakage before rewriting the whole model.
  • Compare edge bandwidth and edge requests separately against billing data so one driver does not hide the other.

Next steps

Guides All calculators CDN cost calculator (generic) Guide: CloudFront pricing Guide: cache hit rate and origin egress Guide: invalidation pricing CDN origin egress

Example scenario

  • Bandwidth: 10,000 GB/month at your $/GB + Requests: 400M/month at your $ per 10k -> estimate monthly CDN cost.
  • If your workload has many small objects, request fees can become a meaningful part of the bill.

Included

  • Bandwidth estimate from GB/month and $/GB pricing assumptions.
  • Request-fee estimate from requests/month and $ per 10k pricing assumptions.

Not included

  • Origin egress and cache fill costs (model separately if billed).
  • Tiered pricing by region unless you use a blended rate or model scenarios.

How we calculate

  • Total = bandwidth cost + request fees.
  • Bandwidth cost = GB/month x $/GB.
  • Request fees = (requests/month / 10,000) x $ per 10k.
  • If pricing is tiered, use a blended rate or run multiple scenarios and sum.

FAQ

Is this an official CloudFront quote?
No. It's a planning estimate based on the assumptions you enter. Always confirm pricing tiers, regions, and units in the official documentation.
What inputs do I need?
Monthly GB delivered to users and monthly request volume. If you only have throughput or RPS, convert them using the Units Converter and RPS-to-monthly tool.

Related tools

CDN cost calculator (generic) Guide: CloudFront pricing Guide: cache hit rate and origin egress Guide: invalidation pricing Guide: CloudFront logs cost Guide: CDN request pricing CloudFront vs Cloudflare cost Origin egress vs CDN bandwidth CDN origin egress Units converter RPS to monthly requests

Related guides

API Gateway vs ALB vs CloudFront cost: what to compare (requests, transfer, add-ons)
A practical cost comparison of API Gateway, Application Load Balancer (ALB), and CloudFront. Compare request pricing, data transfer, caching impact, WAF, logs, and the hidden line items that change the answer.
CloudFront pricing: estimate bandwidth and request costs (without hardcoding prices)
A practical way to estimate CloudFront-style CDN costs using your own bandwidth ($/GB) and request-fee ($ per 10k/1M) assumptions, plus common pitfalls like tiered pricing and origin egress.
CloudFront vs Cloudflare CDN cost: compare the right line items (bandwidth, requests, origin egress)
A practical comparison checklist for CloudFront vs Cloudflare pricing. Compare bandwidth ($/GB), request fees, region mix, origin egress (cache fill), and add-ons like WAF, logs, and edge compute. Includes a modeling template and validation steps.
Azure CDN pricing: estimate bandwidth, requests, and cache fill
A practical Azure CDN estimate: edge bandwidth, request volume, and origin egress (cache fill). Includes validation steps for hit rate, purge behavior, and big endpoints.
Azure Front Door pricing: model requests, bandwidth, and origin traffic
A practical Azure Front Door cost model: edge bandwidth, request volume, logging, and origin traffic (cache fill). Includes a checklist to validate hit rate and avoid double-counting egress.
CDN request pricing: estimate $ per 10k / 1M requests (and when it dominates)
Some CDNs charge request fees in addition to bandwidth. Learn what counts as a billable request, how to estimate requests/month from RPS or analytics, and how to model per-10k vs per-1M pricing without unit mistakes.

Disclaimer

Educational use only. Not legal, financial, or professional advice. Results are estimates based on the inputs and assumptions shown on this page. Verify pricing and limits with your providers and documentation.

Last updated: 2026-02-23. Reviewed against CloudCostKit methodology and current provider documentation. See the Editorial Policy .