Does this calculator include CDN request fees, WAF, or DDoS protection?

No. It focuses purely on GB‑based egress charges. Many CDNs bill separately for HTTP requests, WAF rules, bot management, and DDoS protection. To estimate all‑in savings, add those line items separately or compare total monthly invoices before and after changes.

How accurate is the model if my cloud egress pricing is tiered or region‑based?

The calculator uses a single average per‑GB rate for origin and CDN. If your pricing is tiered or varies by region, use recent invoices to compute blended effective rates that reflect your actual traffic mix. For detailed forecasting, you will still want to model tiers and regions separately.

Can I use this for video streaming or other media‑heavy workloads?

Yes, as a rough cut. For video and other large media, compression savings may be much lower than for text or images, and CDN rates may be different. Set compression savings conservatively and plug in the correct media CDN egress rate to avoid overestimating savings.

What if I already use a CDN—does this still help?

It does. You can treat your current situation as the baseline and tweak cache hit rate and compression savings to see how much additional savings you might unlock by tuning. Use actual cache hit metrics and egress costs from your CDN and origin to improve accuracy.

How should I incorporate free tiers or committed‑use discounts?

If you benefit from free egress tiers or committed‑use discounts, adjust your effective per‑GB rates downward to reflect those benefits, or reduce Monthly data out for the portion covered by free tiers. The goal is to make the current and optimized scenarios comparable on a like‑for‑like basis.

Does this account for the performance benefits of a CDN?

Not directly. The calculator is focused on cost. Performance improvements—lower latency, better cache locality, more resilient edge—are real but harder to quantify in dollars. Consider them an additional benefit on top of whatever bandwidth savings you see.

Can I export or share these results with my stakeholders?

While the calculator does not generate reports itself, you can capture key inputs and outputs (current cost, optimized cost, savings, and scenario assumptions) and drop them into your own spreadsheets or slides for planning docs and vendor negotiations.

tech calculator

Cloud Bandwidth Savings Estimator

Estimate bandwidth cost savings from caching and compression versus serving traffic direct from origin.

Results

Current origin bandwidth cost: $900
Optimized delivered GB (after compression): 7500.00
Origin egress GB after caching: 3000.00
Optimized origin cost: $270
CDN egress cost: $150
Total optimized bandwidth cost: $420
Estimated monthly savings: $480

Overview

Cloud bandwidth is one of those line items that quietly creeps up as your product succeeds. Traffic grows, assets get heavier, and suddenly your origin egress bill is a meaningful chunk of your infrastructure spend. Before you start rewriting everything or switching providers, it helps to see how much you could save just by pushing more traffic through a CDN and squeezing more bytes out of each response with compression.

This cloud bandwidth savings estimator gives you a simple, transparent way to model that. You plug in your current monthly data out, the egress rate you pay from origin, and then experiment with realistic cache hit rates, compression gains, and CDN egress pricing. The calculator estimates what your bandwidth bill looks like today and what it could look like if you aggressively cached static assets and applied gzip/Brotli or image optimization, then shows the monthly dollar savings.

It’s intentionally opinionated and high-level: no region‑by‑region modeling, no tiered pricing tables, no per‑request fees. Instead, it focuses on the two biggest levers most teams control—cache hit rate and compression—so you can sanity‑check whether a CDN rollout or tuning project is worth the engineering time and contract negotiation cycle.

How to use this calculator

Look up your recent cloud provider invoice or monitoring dashboards to find your Monthly data out in GB and your effective Origin egress cost per GB. If your pricing is tiered, compute a blended average rate across typical usage.
Enter a realistic Compression savings percentage. For mostly text‑heavy sites with HTML/CSS/JS and some images, 20–40% is common. For media‑heavy use cases, you may want separate models with lower compression on video and higher compression on images.
Set an expected CDN cache hit rate. For static assets on well‑tuned CDNs, 80–95% hit rates are achievable; for personalized or dynamic API traffic, rates may be much lower. Start conservative and then test more aggressive caching strategies.
Add your CDN egress cost per GB using your provider’s public rate card or contract. If pricing varies heavily by region, compute a blended rate that reflects the mix of traffic across regions.
Review the outputs: Optimized delivered GB, Origin egress GB after caching, Optimized origin cost, CDN cost, Total optimized bandwidth cost, and Estimated monthly savings. These numbers show, in one place, what your bandwidth spend looks like today and what it might look like after caching and compression.
Iterate by adjusting cache hit rate, compression savings, and CDN cost inputs to explore best‑case, base‑case, and worst‑case scenarios. Use these ranges when presenting options to stakeholders or when negotiating with vendors.

Inputs explained

Monthly data out: Total monthly data transferred out of your origin (in GB). Use a recent billing period or an average over several months to smooth out spikes.
Origin egress cost per GB: What your cloud provider charges per GB of outbound data from origin. If your rate is tiered, use an effective average rate across your typical usage band.
CDN cache hit rate: Percentage of requests (or bytes) that are served from CDN cache instead of hitting origin. Higher hit rates significantly reduce origin egress and, therefore, origin bandwidth cost.
Compression savings: Average percentage reduction in response size from applying gzip/Brotli and basic image optimization across your traffic mix. Enter 0 if you do not plan to change compression settings.
CDN egress cost per GB: The per‑GB rate your CDN charges to deliver data to end users. If you have region‑specific pricing, use a blended rate that reflects your actual traffic split.

Outputs explained

Current origin bandwidth cost: Your estimated monthly egress spend today if all traffic is served directly from origin at the origin egress rate.
Optimized delivered GB (after compression): The estimated total GB delivered after applying your compression savings percentage to current traffic.
Origin egress GB after caching: How many GB still need to be fetched from origin after both compression and CDN cache are accounted for—this is what drives your optimized origin egress bill.
Optimized origin cost: Your new monthly origin egress cost after caching and compression reduce how much traffic hits origin.
CDN egress cost: The amount you would pay the CDN to deliver the optimized traffic to users at your CDN per‑GB rate.
Total optimized bandwidth cost: The combined monthly cost of origin egress plus CDN egress under your caching/compression assumptions.
Estimated monthly savings: The difference between your current origin‑only bandwidth cost and the optimized CDN + compression cost. Positive values indicate savings.

How it works

You start by entering your current Monthly data out (in GB) and the Origin egress cost per GB you pay your cloud provider. Multiplying those two gives your baseline Current origin bandwidth cost, which represents an “all traffic direct from origin” scenario without CDN help.

Next you specify a Compression savings percentage. This is a simple average that reflects how much smaller your responses become when you enable gzip/Brotli for text assets and apply basic optimization to images and other media. The calculator applies this percentage to your Monthly data out to estimate Optimized delivered GB (after compression).

You then enter a CDN cache hit rate percentage. This represents the share of traffic that is served from the CDN cache rather than going back to origin—static images, scripts, stylesheets, and other cacheable content. The calculator assumes that only the cache miss portion of your compressed traffic actually hits origin, so Origin egress GB after caching = Optimized delivered GB × (1 − cache hit rate).

With Origin egress GB in hand, the tool computes Optimized origin cost by multiplying that number by your Origin egress cost per GB. It also computes CDN egress cost by multiplying Optimized delivered GB by your CDN egress cost per GB input.

Total optimized bandwidth cost is then Optimized origin cost + CDN egress cost. This represents the blended cost of serving compressed traffic through a CDN, with the origin only seeing cache misses.

Finally, Estimated monthly savings is simply Current origin bandwidth cost − Total optimized bandwidth cost. Positive numbers indicate that the CDN + compression combo is cheaper than serving everything from origin; negative numbers would indicate that, at your assumptions, the CDN layer costs more than it saves (for example, if your cache hit rate is low or CDN egress is unusually expensive).

All of these calculations are linear and use your inputs directly. There is no hidden magic—just enough math to give you a rough financial impact before you invest in detailed per‑region modeling or vendor quotes.

Formula

Current cost = Data out × Origin $/GB
Compression factor = 1 − Compression%
Optimized delivered GB = Data out × Compression factor
Origin egress GB = Optimized delivered GB × (1 − Cache hit rate)
Origin cost = Origin egress GB × Origin $/GB
CDN cost = Optimized delivered GB × CDN $/GB
Optimized total cost = Origin cost + CDN cost
Monthly savings = Current cost − Optimized total cost

When to use it

Building a quick business case to justify rolling out a CDN for a web application that currently serves everything directly from origin.
Estimating whether it is worth investing engineering time into tuning cache headers, cache‑key strategies, and edge rules to increase hit rates on static assets.
Quantifying the dollar impact of turning on Brotli compression for text assets or switching to modern image formats and more aggressive optimization.
Comparing different CDN vendors by plugging in their respective egress pricing and realistically achievable cache hit rates for your workload.
Providing finance and leadership teams with an understandable, scenario‑based view of bandwidth savings when evaluating infrastructure budget cuts.
Stress‑testing how growth in traffic (higher Monthly data out) would impact bandwidth spend with and without a CDN strategy in place.

Tips & cautions

Segment your traffic mentally when choosing inputs: static assets often support 80–95% cache hit rates, while APIs and highly personalized pages may stay much lower. Use the blended hit rate that matches your mix.
If your provider has sharply tiered egress pricing, compute a weighted average rate using your last invoice as a guide. That makes the model more realistic without replicating the entire pricing table.
Use conservative compression savings so you do not overpromise. It is better to show a base‑case 20–30% savings and then over‑deliver than the other way around.
Treat the outputs as a conversation starter with your CDN vendor. You can use the monthly savings number to set expectations for return on investment and ask for rate reductions that make the numbers work.
Remember that bandwidth is often only part of your edge stack cost. Request fees, WAF, and DDoS protection can be significant; keep those in mind when evaluating the all‑in impact of a CDN move.
If you already run a CDN, use your real cache hit metrics and CDN egress rates instead of guesses—then adjust origin egress pricing if you plan to move more traffic off origin.
Revisit your assumptions regularly. As traffic patterns change, new features ship, or media usage grows, your optimal cache/compression strategy and potential savings will change too.
Uses a simplified linear model based on average per‑GB rates. It does not model tiered or region‑specific pricing tables in detail.
Ignores CDN request fees, WAF/DDoS charges, log egress, and add‑on products. For some workloads, these can be substantial and should be considered separately.
Treats compression savings as a single percentage across all traffic, even though real‑world savings vary significantly by content type (HTML vs images vs video).
Models cache hit rate as a single number rather than separate rates for different asset types or paths. In practice, you may want to run separate models for static assets and APIs.
Assumes that all optimized traffic flows through a CDN. If you plan to leave certain endpoints uncached or off‑CDN, you will need to adjust Monthly data out accordingly.
Does not incorporate overage penalties, committed‑use discounts, or long‑term rate renegotiations that may meaningfully change your effective pricing.
The savings number is an estimate based entirely on your inputs—always validate against actual invoices and monitoring data before making contractual commitments.

Worked examples

10,000 GB/mo, $0.09 origin, 60% cache hit, 25% compression, $0.02 CDN

Current cost = $900
Optimized delivered ≈ 7,500 GB; Origin egress ≈ 3,000 GB
Origin cost ≈ $270; CDN cost ≈ $150
Optimized total ≈ $420; Savings ≈ $480/mo

20,000 GB/mo SaaS app with higher cache hit rate

Monthly data out = 20,000 GB; Origin egress = $0.08/GB.
Compression savings = 30%; CDN cache hit rate = 70%; CDN egress = $0.015/GB.
Current cost (no CDN, no extra compression) ≈ 20,000 × $0.08 = $1,600.
Optimized delivered GB = 20,000 × (1 − 0.30) = 14,000 GB.
Origin egress GB after caching = 14,000 × (1 − 0.70) = 4,200 GB.
Optimized origin cost ≈ 4,200 × $0.08 = $336.
CDN cost ≈ 14,000 × $0.015 = $210.
Total optimized ≈ $546; Estimated savings ≈ $1,600 − $546 = $1,054 per month.

Lower traffic app where CDN still helps

Monthly data out = 2,000 GB; Origin egress = $0.09/GB; compression savings = 20%; cache hit = 60%; CDN = $0.02/GB.
Current cost ≈ 2,000 × 0.09 = $180.
Optimized delivered GB ≈ 1,600; origin egress ≈ 640 GB.
Optimized origin cost ≈ $57.60; CDN cost ≈ $32.00; optimized total ≈ $89.60.
Savings ≈ $90.40/month—enough to matter over a year, even at modest scale.

Scenario with marginal savings due to expensive CDN

Monthly data out = 5,000 GB; Origin egress = $0.05/GB; compression savings = 25%; cache hit = 50%; CDN = $0.045/GB.
Current cost ≈ $250.
Optimized delivered GB ≈ 3,750; origin egress ≈ 1,875 GB.
Optimized origin cost ≈ $93.75; CDN cost ≈ $168.75; optimized total ≈ $262.50.
Savings ≈ −$12.50/month (a small loss), illustrating that with aggressive CDN pricing and modest origin egress, you may not save money purely on bandwidth.

Deep dive

Use this cloud bandwidth savings calculator to estimate how much money you can save by pushing more traffic through a CDN and turning on better compression. Enter your current monthly data out, origin egress rate, expected cache hit rate, compression savings, and CDN egress rate to see current spend, optimized spend, and net savings side by side.

The tool helps infrastructure, DevOps, and finance teams answer a simple question: is it worth doing the work to tune caching and compression for this app? By modeling origin egress reduction, CDN delivery costs, and total optimized bandwidth cost in one place, it gives you a directional ROI signal long before you talk to vendors or rewrite any code.

Because the calculator uses a transparent linear model, you can easily plug in different CDN quotes, traffic growth scenarios, or policy changes and immediately see the impact on your bandwidth budget.

FAQs

Does this calculator include CDN request fees, WAF, or DDoS protection?: No. It focuses purely on GB‑based egress charges. Many CDNs bill separately for HTTP requests, WAF rules, bot management, and DDoS protection. To estimate all‑in savings, add those line items separately or compare total monthly invoices before and after changes.
How accurate is the model if my cloud egress pricing is tiered or region‑based?: The calculator uses a single average per‑GB rate for origin and CDN. If your pricing is tiered or varies by region, use recent invoices to compute blended effective rates that reflect your actual traffic mix. For detailed forecasting, you will still want to model tiers and regions separately.
Can I use this for video streaming or other media‑heavy workloads?: Yes, as a rough cut. For video and other large media, compression savings may be much lower than for text or images, and CDN rates may be different. Set compression savings conservatively and plug in the correct media CDN egress rate to avoid overestimating savings.
What if I already use a CDN—does this still help?: It does. You can treat your current situation as the baseline and tweak cache hit rate and compression savings to see how much additional savings you might unlock by tuning. Use actual cache hit metrics and egress costs from your CDN and origin to improve accuracy.
How should I incorporate free tiers or committed‑use discounts?: If you benefit from free egress tiers or committed‑use discounts, adjust your effective per‑GB rates downward to reflect those benefits, or reduce Monthly data out for the portion covered by free tiers. The goal is to make the current and optimized scenarios comparable on a like‑for‑like basis.
Does this account for the performance benefits of a CDN?: Not directly. The calculator is focused on cost. Performance improvements—lower latency, better cache locality, more resilient edge—are real but harder to quantify in dollars. Consider them an additional benefit on top of whatever bandwidth savings you see.
Can I export or share these results with my stakeholders?: While the calculator does not generate reports itself, you can capture key inputs and outputs (current cost, optimized cost, savings, and scenario assumptions) and drop them into your own spreadsheets or slides for planning docs and vendor negotiations.

Related calculators

tech

Bandwidth Calculator for Concurrent Users

Estimate aggregate network bandwidth and safe headroom for concurrent users, streams, or sessions.

tech

Image Inference Cost Calculator

Estimate inference cost for image jobs using per-image and per-second rates.

tech

PDF Splitting Cost Calculator

Estimate cloud costs to split/process PDFs, including API calls, storage, egress, and invocations.

This cloud bandwidth savings estimator is a simplified planning tool. It uses average per‑GB rates, a single cache hit rate, and a single compression savings percentage to illustrate the directional impact of CDN adoption and compression tuning on bandwidth cost. It does not model tiered pricing, regional differences, request fees, WAF/DDoS charges, overage penalties, discounts, or contractual nuances. Treat all outputs as rough estimates and validate them against your provider’s official rate cards and actual invoices before making budget, architecture, or vendor decisions.