Data Egress Cost Calculator (AWS, Azure, GCP)

Data egress can be a major driver of cloud spend (including AWS egress cost). Use this calculator to estimate monthly egress cost with flat or tiered pricing, and compare baseline vs peak scenarios.

Inputs

Data transfer (GB / month)
Avg throughput: 7.61 Mbps.
Avg throughput (Mbps)
Est 24,624 GB/month.
Pricing mode
Use tiered mode when pricing changes by volume.
Price ($ / GB)
Enter your provider's effective $/GB for the region/path/tier.
Scenario presets

Results

Estimated monthly cost
$225.00
Egress
2,500 GB
Price
$0.09 / GB

Tips

  • Model multiple scenarios: baseline month vs peak month.
  • Consider a CDN: it can reduce origin egress and shift cost structure.
  • Watch for tiering and minimum charges in provider pricing.
  • Keep internet, cross-region, and cross-AZ traffic as separate line items.

How to get your inputs

  • GB/month: start from billing exports/flow logs; if you only have throughput, convert Mbps to GB/month.
  • Boundaries: separate cross-AZ vs cross-region vs internet egress as separate line items.
  • Effective rates: use your blended $/GB for the traffic mix you expect.
  • Sources: VPC flow logs, CDN logs, and cost exports provide the cleanest counts.

Result interpretation

  • If tiered pricing drives cost, locate the tier where you spend the most.
  • Large gaps between baseline and peak suggest caching or throttling opportunities.

Common mistakes

  • Mixing boundaries and applying the wrong $/GB rate.
  • Ignoring retries/timeouts that multiply traffic during incidents.
  • Applying internet rates to intra-region or cross-AZ traffic.

Advanced inputs to capture

  • Split egress by destination (internet, cross-region, cross-AZ).
  • Account for CDN cache hit rate to reduce origin egress.
  • Compression or image optimization can change GB materially.
  • Model one-time migrations separately from steady traffic.

Scenario planning

Scenario GB/month Rate Notes
Baseline Expected Blended Typical traffic mix
Peak High Blended Incidents or launches

Validate after changes

  • Validate the top transfer paths and AZ/region locality after architecture changes.
  • Re-check during peak windows (that's when hidden multipliers show up).

Next steps

Guides All calculators Guide: egress costs API response transfer CDN bandwidth cost Cross-region transfer
Advertisement

Example scenario

  • If you send 2,500 GB/month and your effective price is $0.09/GB, estimated cost is $225/month.
  • If you have tiered pricing, enter the tier thresholds and compare baseline vs peak traffic.
  • Separate internet egress from cross-region transfer for more accurate blended rates.

Included

  • Bandwidth-only cost estimate from transferred GB and $/GB pricing.
  • Optional Mbps to monthly GB estimator.
  • Optional peak Mbps estimator for spike scenarios.
  • Optional tiered pricing model with multiple rate steps.
  • Baseline vs peak comparison for traffic spikes.
  • Works for internet egress, service egress, or any scenario where you know an effective $/GB.
  • Simple scenarios to quantify the impact of architectural changes.

Not included

  • Free allowances, minimums, and provider-specific rounding unless you model them explicitly.
  • Per-request fees and other service-specific charges.
  • CDN request fees and cache miss charges.

How we calculate

  • Monthly cost = egress GB x price per GB (or sum of tiers in tiered mode).
  • Enter your provider's effective $/GB for the region/path/tier you expect.
  • Compare a baseline month with a peak month to avoid under-budgeting.
  • If you have multiple paths, compute them separately and add them.

FAQ

Why does egress pricing vary so much?
Egress pricing often depends on destination (internet vs cross-region), tiered usage, service (CDN vs origin), and region.
GB vs GiB: which unit should I use?
Cloud billing often uses decimal GB (1 GB = 1,000,000,000 bytes). Some tooling shows GiB (binary). Use the Units Converter to translate.
Does this include request fees or CDN costs?
No. This tool estimates bandwidth-based egress only.

Related tools

Guide: egress costs API response transfer CDN bandwidth cost Cross-region transfer Units converter

Related guides

API Gateway vs ALB vs CloudFront cost: what to compare (requests, transfer, add-ons)
A practical cost comparison of API Gateway, Application Load Balancer (ALB), and CloudFront. Compare request pricing, data transfer, caching impact, WAF, logs, and the hidden line items that change the answer.
Cloud CDN pricing (GCP): bandwidth, requests, and origin egress (cache fill)
A practical Cloud CDN cost model: edge bandwidth, request volume, and origin egress (cache fill). Includes validation steps for hit rate by path, heavy-tail endpoints, and purge/deploy events that reduce hit rate.
CloudFront cache hit rate: how it changes origin egress cost
Cache hit rate strongly influences origin requests and origin egress (cache fill). Learn a simple model, what breaks hit rate, and the practical levers to improve it safely.
GCP load balancing pricing: hours, requests, traffic processed, and egress
A driver-based approach to load balancer cost: hours, request volume, traffic processed, and (separately) outbound egress. Includes a worked estimate template, pitfalls, and a workflow to estimate GB from RPS and response size.
Azure CDN pricing: estimate bandwidth, requests, and cache fill
A practical Azure CDN estimate: edge bandwidth, request volume, and origin egress (cache fill). Includes validation steps for hit rate, purge behavior, and big endpoints.
Azure Front Door pricing: model requests, bandwidth, and origin traffic
A practical Azure Front Door cost model: edge bandwidth, request volume, logging, and origin traffic (cache fill). Includes a checklist to validate hit rate and avoid double-counting egress.
Advertisement

Disclaimer

Educational use only. Not legal, financial, or professional advice. Results are estimates based on the inputs and assumptions shown on this page. Verify pricing and limits with your providers and documentation.

Last updated: 2026-02-23