CDN Cache Hit Savings
Quantify how much a stronger CDN cache hit rate trims origin egress bills. Enter monthly traffic and your origin $/GB; optional fields capture hit rate and CDN transfer pricing so you can see absolute and per-GB savings versus serving everything from origin.
Pricing estimator only; confirm actual CDN and origin rate cards, regional pricing, and minimums before budgeting.
Examples
- 25,000 GB/month, $0.08 origin, 80% hit rate, $0.05 CDN ⇒ Origin-only cost: $2,000.00 USD • With CDN at 80.00% hit: $1,650.00 USD • Monthly savings: $350.00 USD ($0.01 USD/GB).
- 40,000 GB/month, $0.10 origin, defaults for hit rate and CDN cost ⇒ Origin-only cost: $4,000.00 USD • With CDN at 80.00% hit: $2,800.00 USD • Monthly savings: $1,200.00 USD ($0.03 USD/GB).
FAQ
How do I model tiered CDN pricing?
Use an average blended CDN $/GB that reflects your expected tier mix, or rerun the calculator for each tier and weight by traffic share.
Does this include request fees?
No. It focuses on transfer costs. Add per-request origin or CDN charges to the $/GB inputs if you want to include them implicitly.
What if I improve cache hit rate?
Increase the hit-rate input to quantify the incremental savings from better caching rules, TTL tuning, or image optimization.
Can I use it for object storage egress?
Yes. The origin $/GB input works for any egress source—object storage, compute, or colocation—so long as you know the per-GB rate.
Additional Information
- Result unit: U.S. dollars for total cost with and without CDN, plus dollars saved per GB.
- Hit rate controls how much traffic still reaches origin; higher rates reduce origin egress proportionally.
- CDN costs are added across all delivered traffic; defaults assume $0.05/GB if left blank.