Cloud storage egress fees: why the cheapest storage can cost more

Capacity is only one line on the bill

Egress means data leaving a service. Internet downloads, transfers between regions, and traffic to another service can have different billing rules. Start by identifying where your data goes rather than applying one price to every byte.

Consider two fictional plans. Plan A charges $0.01 per stored GB and $0.08 per downloaded GB. Plan B charges $0.02 per stored GB and $0.01 per downloaded GB. With 1,000 GB stored and 100 GB downloaded, their storage-plus-download totals are $18 and $21. With the same storage and 1,000 GB downloaded, they are $90 and $30. The lower storage rate does not guarantee a lower bill. These are invented teaching examples, not provider prices.

Apply allowances to the right traffic

Some allowances are fixed; others depend on average stored data. An allowance shared by a billing account may already be consumed by other workloads. StorageMetric excludes shared account free quotas from its curated AWS, Google Cloud, and Azure estimates because remaining eligibility is unknown. You can use the manual calculator to model your own known allowance.

A published no-egress-fee policy can still have eligibility conditions. A partner-specific transfer arrangement may not apply to ordinary internet downloads. Read the plan notes and source page before assuming traffic is free.

Add requests and observe tier boundaries

Downloading one large object and downloading thousands of small objects can transfer the same total data while generating different request costs. Distinguish reads from writes and listing operations. Some providers also charge other transaction classes, and a hierarchical namespace can have a separate tariff.

Pricing tiers can change at a volume boundary. An estimate using only the first tier should stop at its documented limit rather than silently applying that rate to a much larger workload. StorageMetric marks scenarios outside the verified range as unavailable.

Model the exceptional month

Run a normal month, a traffic spike, and a full restore or migration. Include outgoing traffic from the source and incoming-service operations at the destination. Ask about migration credits, delivery-network arrangements, throttling, and the process required to claim any waiver.

Use average stored capacity and your expected internet downloads in the comparison desk. Review region, destination, rates, and verification dates alongside the result. Taxes, retrieval, early deletion, optional networking, and support remain outside this planning estimate.