Cloud Egress Cost Calculator

Draw the path from the resource that sends the bytes to the resource or user that receives them. Record the cloud product, source region or zone, destination geography, whether traffic crosses regions or zones, and whether a CDN, load balancer, gateway, private interconnect, or object store participates. The bill is usually attributed to the sending service, but processing products along the path can add their own charges.

Inbound internet transfer is often priced differently from outbound transfer, and a response to an inbound request is outbound data. Avoid netting uploads against downloads unless the provider's documentation explicitly bills that way. Also separate customer delivery from replication, backups, log export, cross-region database traffic, and origin fills; each can follow a different pricing table.

Monthly transfer should come from measured bytes where possible. For this comparison, use the public-internet bytes that leave the named source service. Product analytics such as video plays or file downloads are not direct inputs when a CDN or another delivery layer serves users; trace and measure every billed route separately, including cache fill, partial downloads, retries, range requests, and protocol overhead where material.

Cloud pages may quote gigabytes or gibibytes, and the labels are not interchangeable. One decimal gigabyte is one billion bytes; one gibibyte is 1,073,741,824 bytes. The calculator accepts decimal GB and converts that same byte count to GiB for a provider that bills in GiB. At large scale, silently treating equal GB and GiB numerals as equal traffic creates a visible forecasting error.

Assume a service delivers 5,000 GB in a month. If the applicable official schedule provides a 100 GB allowance for that exact account and route, 4,900 GB remains billable. At an illustrative flat rate of USD 0.08 per GB, the transfer estimate is USD 392. The allowance and rate are example inputs, not a quote for AWS, Google Cloud, Cloudflare, or any other provider.

The interpretation should state what the 392 excludes. If the traffic passes through a load balancer, CDN, gateway, or request-priced object store, the architecture may incur other charges. If the rate card is tiered, applying 0.08 to every billable GB may also be wrong: each volume band should be priced separately unless the provider says the achieved tier applies to all usage.

A CDN can reduce traffic leaving an origin when users are served from cache, but a cache miss is not automatically billed as the origin's standard direct-to-internet route. Origin-to-CDN transfer can be waived, discounted, or charged as cache fill under a separate schedule. Measure those bytes and price the named CDN path separately instead of multiplying end-user delivery by a generic cache-miss percentage.

Cloudflare documents no egress charge for R2 object delivery, while R2 storage and request operations have their own pricing. Workers can add request and compute charges depending on the plan and workload. This is a useful reminder that a zero rate in one column does not mean the full architecture has zero marginal cost. Keep storage, requests, compute, logging, and network processing as separate lines.

A central forecast should be based on recent measured source-service internet egress per active user or per transaction. A lower case can reflect lighter use or a verified routing improvement; a higher case should include growth, larger assets, retries, and route changes. CDN cache-hit assumptions belong in a separate delivery-path model. Do not manufacture false precision by forecasting traffic to the last gigabyte while using an unverified unit price.

The calculator converts one entered decimal-GB byte volume into each provider's labeled billing unit, then applies the published progressive tiers and free allowances for three narrowly scoped presets. It does not derive origin traffic from CDN delivery, or price other destinations, committed-use or negotiated agreements, taxes, currency conversion, CDN cache fills, inter-zone traffic, private connectivity, NAT, load balancing, DDoS services, or request operations. It cannot determine the route from a hostname or architecture description.

Use separate runs for materially different paths, then add them. Reconcile the estimate with billing-export data after deployment. A large variance usually indicates a missing route, a unit mismatch, an incorrect allowance, or an adjacent network-processing product—not necessarily a failure of the basic multiplication.

The source set below was reviewed on 20 July 2026. Cloud providers revise prices, free allowances, region lists, product names, and aggregation rules, so the date is not a guarantee that a copied rate remains current. Reopen the exact official table before a commitment and preserve a dated reference alongside the scenario.

Revisit the model after a region move, CDN or storage migration, network-tier change, large traffic shift, or cache-policy change. Monthly billing reconciliation is the strongest check because it exposes paths that architecture diagrams omit. Do not publish a universal provider ranking from one route: the relevant answer depends on geography, traffic mix, surrounding products, and operational requirements.