Origin data transfer scenario · byte-based inputs
CDN cache hit savings scenario calculator
Estimate theoretical monthly origin-transfer reduction from cache-eligible traffic and a byte-based CDN cache hit share. No price or provider savings are assumed.
Estimate a theoretical monthly reduction in origin data transfer from a byte-based cache hit share. Use traffic measured for the same period and scope in your CDN or host analytics where available. The result is a scenario, not a prediction or price estimate.
Enter all three values and calculate.
Method and assumptions
Modeled origin transfer after cache = eligible origin transfer × (1 − byte hit share) + non-cacheable origin transfer. Modeled reduction = eligible origin transfer × byte hit share. This assumes the hit percentage applies to transferred bytes, uses one consistent month and traffic scope, and that a hit avoids sending the response body from the origin.
Use a data-transfer or bytes-based cache metric if your CDN provides one. A request hit ratio is not necessarily a byte hit ratio: small and large objects can have different hit behavior. Cloudflare Cache Analytics has separate Requests and Data Transfer views; its documentation describes Data Transfer as useful for cost analysis and notes that revalidated requests count differently between those views. Match the metric and scope before using it here.
What this does not estimate
This arithmetic does not measure your CDN, determine cache eligibility, account for cache fills, purges, revalidation traffic or tiered-cache behavior, or predict provider billing. It excludes request counts, origin compute, performance, CDN fees, and traffic not included in the inputs. Check the service's analytics, caching rules, and billing definitions for your actual setup. A lower modeled origin transfer is not a guaranteed cash saving.
Sources
- Cloudflare Cache Analytics — separates Requests and Data Transfer views and explains what each represents; last updated October 27, 2026, checked November 3, 2026.
- Cloudflare Cache overview — describes caching and cache rules; last updated April 16, 2026, checked November 3, 2026.
For a page-view transfer scenario from user-entered traffic assumptions, see the page-view bandwidth calculator. For a provider-term checklist, read the bandwidth limits guide.
How it works
Enter monthly cache-eligible origin transfer, the hit share of eligible data transfer, and non-cacheable origin transfer, all for the same period and traffic scope. The calculator models remaining origin transfer and theoretical reduction; it does not measure your CDN or estimate cost savings.
Good to know
Can I enter a request hit ratio?
Only if it reasonably represents the share of transferred bytes served from cache. Request ratios and byte ratios can differ when object sizes vary. Prefer a data-transfer metric from your CDN analytics.
What counts as non-cacheable transfer?
Enter origin transfer for traffic outside the cache-eligible amount, such as requests your cache configuration bypasses or does not cache. Confirm the categories and accounting with your CDN analytics.
Does the result show money saved or CDN cost?
No. It estimates an arithmetic origin-transfer scenario from your inputs. Provider billing, cache-fill traffic, revalidation, CDN charges and plan terms are not modeled.
Impact — TODO: apply/approval and configure referral URL — referral link not configured.
CJ Affiliate — TODO: apply/approval and configure referral URL — referral link not configured.
PartnerStack — TODO: apply/approval and configure referral URL — referral link not configured.