CDN Bandwidth Cost Calculator: Edge Delivery Planning for Media, Images, and Launch Peaks

Use this calculator when the first question is edge delivery cost: how many GB the CDN serves to viewers, what effective $/GB you are really paying, and how much a launch or media spike can change the month.

Maintained by CloudCostKit Editorial Team. Last updated: 2026-04-19. 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.

Full CDN cost planner Guide: CDN cost diagnosis Request fee calculator Origin leakage calculator

Use this calculator first when...

You are planning video, media, or download delivery where delivered edge GB is the main bill driver.
You run an image-heavy storefront and want to see how asset weight and campaign traffic affect edge cost first.
You need a separate launch or campaign peak month instead of one blended average.

This page is for edge delivery planning. It keeps delivered viewer traffic, request pricing, and origin leakage in separate lanes so your bandwidth model stays clean.

Inputs

CDN bandwidth scenarios

Delivered edge bandwidth (GB / month)

Current baseline throughput: 12.18 Mbps.

Effective edge rate ($ / GB)

Use the blended rate that matches your regional mix.

Throughput helper

Avg Mbps

Peak Mbps

Estimate helper

Est 39,398 GB/month.

Include peak month

Peak month multiplier (%)

Helper suggests 183%.

Results

Baseline bandwidth cost

$240.00

Delivered edge GB

4,000

Effective rate

$0.06

Peak month cost

$384.00

Baseline vs peak bandwidth month

Scenario	GB / month	Monthly cost
Baseline	4,000	$240.00
Peak	6,400	$384.00
Delta	2,400	$144.00

Bandwidth interpretation

Custom edge-delivery scenario

This model is about delivered edge GB first, then rate quality and peak timing.

Modeled surface: edge delivery to viewers, not origin cache-fill traffic.
Dominant bandwidth risk: Regional mix and premium delivery pricing likely matter as much as raw GB.
Baseline vs peak gap: $144.00 additional spend in the peak month.

Next action

Validate delivered edge GB against CDN analytics before changing the rate assumption.
Split peak delivery windows from the steady month so launch traffic does not distort the baseline.

Which CDN bandwidth scenario looks most like your month?

Video library / streaming delivery: large delivered GB, stable requests, and heavy regional mix sensitivity.
Image-heavy storefront: merchandising, asset weight, and campaign bursts move the edge bill.
Software downloads: release windows can create a second month of edge delivery in days.
Launch or campaign burst: peak-week delivery often matters more than the calm-week average.

What this estimate still misses

Request fees: if requests are a material line item, pair this with the request calculator.
Origin leakage: cache fill, revalidation, or low hit rate belong in the origin side model.
Adjacent charges: WAF, logs, image optimization, and edge functions still sit outside this bandwidth-only estimate.

Why bandwidth pages go wrong

Teams copy a headline $/GB instead of the effective blended rate that matches the real regional mix.
Peak-week delivery is hidden inside a monthly average even though the launch window drives procurement anxiety.
Viewer-facing edge traffic is mixed with origin-side refill traffic, which makes the bandwidth page feel fuzzy and low-trust.

Next step after edge-delivery math

Request fees are moving the bill

Go here when small objects, bots, or cache-key sprawl make request pricing material.

Origin leakage is the next question

Go here when cache misses, refill traffic, or revalidation still leave the origin paying real money.

Need the full CDN planner

Use the main planner when bandwidth, request fees, and origin egress all need to stay visible together.

Need diagnosis before more math

Use the guide when you still need to decide which CDN line item moved first.

Example scenario

Image-heavy storefront: 9,500 GB/month at $0.055/GB -> about $523/month before request fees and origin leakage.
Video or download delivery: 48 TB/month at $0.045/GB -> about $2,160/month, with peak weeks often driving the real budget risk.
Campaign or launch burst: model the baseline month and a separate peak month so the first-week spike does not hide inside one average.

Included

CDN-specific bandwidth scenarios for video, image-heavy storefront, software downloads, and launch traffic.
Baseline vs peak month comparison for delivered edge GB.
Decision-support output for dominant bandwidth risk and next optimization step.

Not included

Request-fee pricing (use the CDN request calculator when requests are material).
Origin cache-fill pricing (use origin egress tools separately if the origin is billed).

How we calculate

Bandwidth cost = delivered edge GB/month x effective $/GB.
Use the blended rate that matches your regional traffic mix and plan tier.
Keep peak delivery windows separate because launch weeks and media events can compress a month of traffic into days.
Treat this as an edge-delivery model, not a generic transfer estimate.

FAQ

Use this calculator first when?

Use it first when you already know edge delivery is the dominant line item and want a fast baseline-vs-peak bandwidth model before deeper CDN bill analysis.

What traffic fits this page best?

Video or media delivery, image-heavy storefront traffic, software downloads, and campaign or launch bursts where delivered GB is the primary cost surface.

Does cache hit rate matter here?

It matters for origin leakage, but this page keeps the edge-delivery bill separate so you do not blur viewer bandwidth and origin fill costs.

What should I validate before trusting the number?

Match delivered edge GB and the effective $/GB to billing or CDN analytics, then check peak windows separately from the ordinary month.

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.

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.

Cloud CDN pricing (GCP): bandwidth, requests, and origin egress (cache fill)

A practical Cloud CDN cost model: edge bandwidth, request volume, and origin egress (cache fill). Includes validation steps for hit rate by path, heavy-tail endpoints, and purge/deploy events that reduce hit rate.

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 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 Cost Comparison Guide: Compare Pricing, Per-GB Rates, and Provider Trade-Offs

Compare CDN pricing across providers with a practical framework for bandwidth, requests, per-GB rates, regional mix, and origin egress. Built for CDN cost comparison and provider-decision workflows.

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-04-19. Reviewed against CloudCostKit methodology and current provider documentation. See the Editorial Policy .