Model egress, cache efficiency, request fees, and bursts. Analyze origin pull, shielding, and regional rates. Plan reliable content delivery budgets with clearer financial confidence.
Large screens use three columns, smaller screens use two, and mobile uses one.
These sample scenarios help compare different traffic levels, cache efficiency, and blended cost outcomes.
| Scenario | Monthly Requests | Avg Asset Size | Cache Hit Ratio | Delivered Traffic | Estimated Monthly Cost |
|---|---|---|---|---|---|
| Brochure site | 800,000 | 220 KB | 94% | 151.18 GB | $10.21 |
| SaaS dashboard | 4,000,000 | 480 KB | 91% | 1,647.95 GB | $108.37 |
| Media portal | 18,000,000 | 1.10 MB | 88% | 17,402.34 GB | $1,171.66 |
| Streaming edge | Direct 42 TB | Direct input | 96% | 43,008.00 GB | $2,709.54 |
Estimate mode delivered traffic
Delivered GB = Monthly Requests × Asset Size in GB × (1 − Compression Savings)
Direct mode delivered traffic
Delivered GB = Direct Monthly Transfer converted to GB
Traffic with operational overhead
Overhead GB = Delivered GB × (1 + Burst Margin) × (1 + Redundancy Overhead)
Billable CDN transfer
Billable Transfer GB = max(0, Overhead GB − Free Transfer Allowance)
Origin fill traffic
Origin Fill GB = Delivered GB × (1 − Cache Hit Ratio) × (1 − Shield Savings)
Effective CDN transfer rate
Effective Rate = Base CDN Rate × Regional Multiplier
Request pricing
Request Cost = Billable Requests ÷ 10,000 × Request Fee
Total monthly cost
Total Cost = (CDN Transfer Cost + Origin Cost + Request Cost − Commit Discount) + Fixed Add-on Cost
It estimates monthly CDN spending using delivered traffic, cache efficiency, request fees, origin pull cost, regional pricing adjustments, discounts, and fixed platform add-ons.
Use estimate mode when you know traffic patterns as requests and average file size. It is helpful during forecasting, proposal planning, or pre-launch budgeting.
Direct mode is better when monitoring tools already show monthly bandwidth. It avoids assumptions about asset size and uses known transfer values instead.
A higher cache hit ratio means more content is served from edge locations. That reduces repeated origin fetches and usually lowers total delivery cost.
Some providers charge more for certain geographies or global traffic mixes. The multiplier lets you model that premium without changing every rate manually.
Yes. It includes billable requests after subtracting any free allowance. This helps when providers charge separately for request volume and transfer.
Yes. You can place WAF bundles, real-time logs, image optimization, support plans, or any recurring charge in the fixed add-on field.
No. It is a planning model. Real invoices may vary because of tiered pricing, regional splits, minimum commitments, taxes, and special contract terms.
Important Note: All the Calculators listed in this site are for educational purpose only and we do not guarentee the accuracy of results. Please do consult with other sources as well.