Cloud Egress Cost Calculator

Pricing preset:

Choose the transfer boundary that most closely matches the bill line you need to estimate.

Monthly data out:

Enter the baseline monthly transfer before cache, compression, and retry adjustments. Use TB/PB for decimal units or TiB/PiB for binary billing exports.

Cache or private-path offload: {{ cache_hit_percent }}%

Set 0 for direct internet egress, or use measured cache-hit/private-path coverage.

Payload reduction: {{ payload_reduction_percent }}%

Use observed byte savings; keep 0 when the transfer metric already reflects compressed bytes.

Peak month multiplier: {{ peak_multiplier }}x

Set 1x for steady state; raise it to estimate peak-month budget pressure.

Monthly budget cap:

Enter 0 to omit the budget check from the summary.

$ / mo

Check egress assumptions

{{ error }}

Included transfer:

Provider presets load common public allowances; edit this for your agreement.

Tier 1 size and rate:

First paid block of traffic after the free allowance.

GB @ $

Tier 2 size and rate:

Second paid block of traffic; set 0 when your price card is flat.

GB @ $

Tier 3 size and rate:

Third paid block of traffic; the final tier covers everything above it.

GB @ $

Final tier rate:

The final tier applies to all remaining billable transfer.

$ / GB

Request add-on:

Leave either value at 0 to model bandwidth-only cost.

M req @ $

Retry overhead: {{ retry_overhead_percent }}%

Use a small reserve when production telemetry shows retries or duplicated transfer.

Metric	Value	Planning note	Copy
{{ row.metric }}	{{ row.value }}	{{ row.note }}

Tier	Charged GB	Rate	Cost	Rule	Copy
{{ row.tier }}	{{ row.gb }}	{{ row.rate }}	{{ row.cost }}	{{ row.rule }}

Lever	Modeled change	Monthly savings	Operator note	Copy
{{ row.lever }}	{{ row.change }}	{{ row.savings }}	{{ row.note }}

Preset	Monthly cost	Delta	Effective rate	Caveat	Copy
{{ row.preset }}	{{ row.cost }}	{{ row.delta }}	{{ row.rate }}	{{ row.caveat }}

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

Cloud egress is the data that leaves a cloud provider, region, storage service, compute service, or network boundary. It is one of the easiest infrastructure costs to underestimate because the meter is not tied to a server count. A small application can produce a large egress bill when media downloads, API payloads, logs, backups, cross-region copies, or user traffic grow faster than expected.

Pricing is usually tiered. Some transfer may be included, the first paid tier may have one rate, and later tiers may use lower per-gigabyte rates. The bill can also change when traffic goes to a different destination, crosses regions, uses a different network class, includes request charges, or benefits from a private contract. Cache hit rate and payload reduction matter because they reduce chargeable bytes before the rate card is applied.

Cost modeling is most useful before architecture choices become expensive to unwind. A CDN cache policy, image compression target, API pagination change, log sampling setting, or backup replication rule can turn into a material spend decision. Peak months matter too. A normal month may fit the budget while a campaign, migration, or seasonal surge crosses a higher spend band.

This calculator estimates egress spend from transfer volume, savings assumptions, editable tier rates, request add-ons, peak traffic, and budget checks. Treat the result as a planning model, then verify the final rate card, region, destination, taxes, credits, and contract terms against your provider billing data.

How to Use This Tool:

Work from expected bytes to provider-style billing. The default presets give a starting point, but the editable rates are the part to trust after you reconcile them with your own account.

Choose a pricing preset or start from custom rates. Provider presets are planning references, not a substitute for your live bill or contract.
Enter the monthly transfer volume and unit. Use decimal units for GB, TB, and PB, and binary units for TiB and PiB.
Set cache hit percentage, payload reduction, and retry overhead. These fields model how much raw traffic becomes billable transfer after common optimizations and retries.
Enter included gigabytes and tier rates. Use 0 for an unused tier boundary only when the model should treat the last rate as open-ended.
Add request charges only when your workload has a separate per-request line item that should be included in the estimate.
Review baseline monthly cost, effective rate, peak-month cost, budget variance, tier ledger, provider comparison, and optimization notes.

For a cost review, match the model to a billing export: same month, same region, same service family, same destination class, and the same definition of transfer out.

Interpreting Results:

Adjusted transfer is the raw monthly volume after cache hit savings, payload reduction, and retry overhead are applied. This is the volume that moves through the included allowance and paid tiers.

Total monthly cost combines tiered transfer cost and optional request cost. Effective rate divides that total by adjusted gigabytes, which makes it easier to compare a mixed tier result with a flat-rate assumption.

Peak-month cost applies the same model to the selected traffic multiplier. This is useful for launch plans and seasonal windows, but it assumes the optimization percentages and tier card stay the same during the peak.

Tier ledger shows which portions of adjusted transfer landed in each rate band.
Optimization brief estimates the effect of cache, payload, retry, and peak containment changes.
Provider comparison gives a planning view across preset cards, but service eligibility and destination rules still need separate verification.

Technical Details:

The calculation converts the entered volume to gigabytes, reduces that volume for cache hits and payload savings, increases it for retry overhead, subtracts included transfer, then walks the remaining gigabytes through tier bands. Tiered billing means the last gigabyte can be cheaper than the first paid gigabyte, while the effective average rate lands somewhere between the bands actually used.

Provider presets are intentionally editable because public pages, regional tables, service-specific exceptions, taxes, and negotiated credits change. A model that cannot be corrected to match the invoice is less useful than a conservative worksheet that exposes every rate assumption.

Formula Core:

The model treats traffic reductions before billing tiers. Percent fields are clamped by validation so the adjusted transfer cannot become negative.

\begin{array}{lcl} G_{raw} & = & entered transfer converted to GB \\ G_{adjusted} & = & G_{raw} \times (1 - cache) \times (1 - payload) \times (1 + retry) \\ G_{paid} & = & \max (0, G_{adjusted} - included GB) \\ Transfer cost & = & \sum_{tiers}^{} (charged GB in tier \times tier rate) \\ Total cost & = & transfer cost + request cost \\ Effective rate & = & \frac{total cost}{G_{adjusted}} \end{array}

Cloud egress assumptions and cautions
Assumption	Effect on cost	Check before using the estimate
Cache hit percentage	Reduces the raw transfer volume before tier billing.	Use origin egress avoided, not browser cache requests served locally.
Payload reduction	Models compression, image resizing, pruning, or smaller API responses.	Measure after protocol overhead and object format changes where possible.
Retry overhead	Increases adjusted transfer for repeated downloads or failed attempts.	Check logs for client retries, partial downloads, and batch restarts.
Included transfer	Offsets adjusted transfer before paid tiers are charged.	Confirm which services, regions, and destinations share the allowance.
Peak multiplier	Models a high-traffic month using the same rates and savings assumptions.	Campaign and migration traffic may also change cache behavior.

The preset comparison is a starting point for architecture discussion. It does not decide provider selection by itself because storage cost, compute cost, latency, support, compliance, private connectivity, and discount programs can dominate the final decision.

Worked Example:

For 12 TB of raw monthly transfer with 35% cache hit rate, 12% payload reduction, and 3% retry overhead, the adjusted transfer is much lower than the raw traffic. The included allowance is subtracted first, then the remaining gigabytes move through the tier card. A peak multiplier of 1.8 estimates the same workload during a month with 80% more raw traffic.

If a compression project raises payload reduction by 10 percentage points, the savings come from fewer adjusted gigabytes crossing every paid tier. If most traffic already fits inside the included allowance, the same compression project may have little immediate transfer-cost effect but can still improve latency.

FAQ:

Why do provider pages and invoices sometimes disagree with a model?

Invoices can include regional rules, destination classes, credits, taxes, private rates, service-specific exceptions, and aggregation rules that a simple public rate card cannot fully capture.

Should cache hit rate be entered as CDN hit rate?

Use the percentage that reduces origin or provider-billed egress. A high edge hit rate is useful only if it actually avoids the billed transfer being modeled.

What is the difference between TB and TiB?

TB is decimal, so 1 TB is 1,000 GB. TiB is binary, so 1 TiB is 1,024 GiB. The selected unit changes the converted gigabytes before pricing.

Can this estimate cross-region transfer?

Yes, if you enter a cross-region-style rate card. Confirm the provider's exact source, destination, service, and direction rules before using it in a budget.

Cloud Egress Cost Calculator

Introduction:

How to Use This Tool:

Interpreting Results:

Technical Details:

Formula Core:

Worked Example:

FAQ:

References: