Cloud Egress Cost Calculator: Data Transfer and Monthly Bandwidth Charges
Estimate provider-neutral cloud data transfer cost with a free allowance, successive volume tiers, an optional per-GB processing charge, and a prorated fixed monthly fee. The results also show the average bandwidth represented by the entered transfer volume.
Traffic and pricing inputs
The fixed monthly charge is prorated on a 30-day month.
Use the same currency for every rate and fee.
Outbound data transfer
Combine only traffic with the same applicable destination rate.
Allowance for this account, service, route, and period.
Successive egress pricing tiers
Each tier size is incremental, not a cumulative threshold. Enter zero to skip a tier.
Additional charges
Optional route or service processing fee; enter zero if none.
Prorated as entered fee × period days ÷ 30.
Tip: press Ctrl/⌘ + Enter to recalculate.
Estimated egress cost
Enter valid inputs to calculate cloud egress cost.
Advertisement
Worked example: 25 TB of monthly cloud egress
The starting values are a hypothetical scenario, not a provider price quote. From 25 TB of outbound transfer, a 100 GB allowance leaves 24,900 GB billable. The first 10 TB at 0.09 per GB costs 900, and the next 14.9 TB at 0.085 per GB costs 1,266.50, for a tiered egress charge of 2,166.50.
A 0.01 processing charge applied to all 25,000 outbound GB adds 250, while a fixed monthly charge of 20 brings the 30-day total to 2,436.50. Moving 25 TB evenly over 30 days represents about 77.16 Mbps of average bandwidth; it does not predict the workload's peak throughput.
Cloud egress cost and bandwidth formulas
Billable egress: max(0, total outbound GB − free allowance GB)
Tier usage: min(remaining billable GB, tier capacity GB)
Tier cost: tier usage GB × tier price per GB
Processing charge: total outbound GB × processing price per GB
Prorated fixed charge: fixed monthly charge × period days ÷ 30
Period total: all tier costs + processing charge + prorated fixed charge
30-day run rate: period total × 30 ÷ period days
Annualized run rate: period total × 365 ÷ period days
Average bandwidth: outbound GB × 1,000,000,000 × 8 ÷ period seconds
Data units are decimal billing units: 1 GB = 1,000,000,000 bytes, 1 TB = 1,000 GB, and 1 PB = 1,000 TB. The fixed-charge proration is a scenario assumption; replace the result with the actual billed fee if the provider does not prorate by day.
How the tiered transfer model works
The calculator subtracts the free allowance once, then fills each configured tier in order. Tier sizes are incremental: with tier sizes of 10 TB, 40 TB, and 100 TB, tier 2 covers the next 40 TB after tier 1, so the first two tiers together cover 50 TB. Any remaining billable data uses the fourth rate.
| Input | Use it for | Common pitfall |
|---|---|---|
| Total outbound transfer | Measured response or download bytes for one service, route, and period | Combining internet, inter-region, and same-region traffic with different prices |
| Free allowance | A transfer allowance actually available to the modeled account and route | Applying one shared allowance independently to several separate estimates |
| Tier capacities and rates | Successive volume blocks from the applicable rate card or contract | Entering cumulative thresholds when the fields expect incremental tier sizes |
| Processing price | An additional fee that applies to every outbound GB in this model | Adding a fee that applies only to a subset of traffic |
| Fixed monthly charge | A port, connection, or commitment fee to include in the scenario | Assuming a contractual fee is prorated exactly as this model does |
How to build a reliable egress estimate
- Separate traffic by source service, source region, destination, network path, and billing period.
- Use billing exports or byte counters rather than request counts when transfer volume is available.
- Confirm whether the free allowance is per account, billing profile, product, region, or route.
- Translate cumulative rate-card thresholds into incremental tier sizes before entering them.
- Model services with different rates separately, then add their totals.
- Compare the estimate with a recent invoice and include negotiated discounts, credits, taxes, and commitments separately.
Cloud data transfer pricing is route-specific. Internet egress, cross-region transfer, cross-zone transfer, CDN delivery, storage retrieval, and private connectivity can be separate charge types even when they involve the same payload. Use only rates that apply to the bytes being modeled.
Cloud egress cost FAQs
What is cloud egress?
Cloud egress is data transferred from a cloud service to the public internet, another region, another provider, or an on-premises network. The destination and path can change the price.
How does the calculator apply tiered egress pricing?
It removes the free allowance first, fills tiers 1 through 3 in order, then sends any remaining billable volume to the last rate. A zero-size tier is skipped.
Are cloud egress prices always charged per GB?
No. Some products use commitments, port charges, destination-specific flat fees, or percentile billing. This calculator models volume pricing plus an optional monthly charge, not every commercial model.
Does average bandwidth represent peak bandwidth?
No. Average bandwidth spreads the entered transfer evenly across the whole period. Real traffic can be bursty, and peak link or application throughput can be much higher.
Should data transfer use GB or GiB?
Use the unit on the applicable rate card or invoice. This calculator uses decimal GB, TB, and PB. Convert measured binary units before entry if billing is expressed in GiB or TiB.
Does the estimate include every network service fee?
No. Taxes, credits, discounts, support, minimum commitments, requests, load balancers, NAT gateways, CDN charges, and other services are excluded unless their cost is represented by an entered rate or fee.
Are my traffic and pricing inputs uploaded?
No. Calculations, copied results, and CSV creation run locally in your browser.
Limits and disclaimer
This calculator is a budgeting aid, not a provider quote, invoice, tax calculation, or financial recommendation. Pricing can vary by region, service, destination, protocol, transfer direction, account aggregation, commitment, contract, and date. It does not automatically model binary billing units, minimum charges, 95th-percentile bandwidth billing, burst pricing, request fees, retrieval fees, taxes, discounts, credits, or currency conversion. Confirm production budgets and architecture decisions with current provider documentation, contract terms, billing exports, and representative traffic measurements.