Downloading cloud data can cost more than storing it because capacity and delivery use different billing meters. In one illustrative Azure scenario, sending 1 decimal TB to one internet recipient costs about $78.30, while holding the same bytes in Hot locally redundant Blob Storage for seven days costs about $4.52. That roughly 17-to-1 ratio is specific to the assumptions below, not a universal cloud rule.
A dated 1 TB example
This example uses public USD list prices displayed on August 10, 2026: Azure East US, pay as you go, Hot LRS capacity, Microsoft premium global-network routing, no CDN or negotiated agreement, and no tax. Azure's first 100 GB of monthly internet egress is assumed unused. Azure's bandwidth table defines 1 TB as 1,000 GB, while Blob capacity is billed in binary GB; 1,000,000,000,000 bytes is therefore about 931.32 GiB of capacity.
| Meter | Calculation | Illustrative cost | |---|---:|---:| | Internet egress | (1,000 GB - 100 GB free) × $0.087/GB | $78.30 | | Seven days of Hot LRS capacity | 931.32 GiB × $0.0208/GiB-month × 7/30 | $4.52 | | Upload writes using 8 MiB blocks | about 119,210 requests / 10,000 × $0.05 | about $0.60 | | Download reads using the same 8 MiB request size | about 119,210 requests / 10,000 × $0.004 | about $0.05 |
The request count uses a decimal 1 TB payload: 1,000,000,000,000 bytes divided into 8 MiB (8 × 2²⁰-byte) blocks requires about 119,210 requests after rounding up. The important consequence is not merely that egress is “expensive.” It is that storing one copy and delivering it are different activities. Retaining the object for another week adds capacity cost. Sending it to another recipient adds another full set of outbound bytes. Three decimal 1 TB downloads in one month would produce $252.30 of egress—(3,000 GB - 100 GB) × $0.087/GB—because the monthly 100 GB allowance applies once, while the stored capacity remains one copy.
These are author calculations from dated list prices, not a quote, TeraAirlift pricing, or audited TeraAirlift economics. Region, routing, service, monthly band, free-tier consumption, currency, agreement, and tax can all change an invoice.
Why the ratio changes
Source geography matters. On Azure's August 10, 2026 USD list page, after the first 100 GB per month, the premium-network first paid band is $0.087/GB from North America or Europe, $0.12/GB from Asia, Australia, or the Middle East and Africa, and $0.181/GB from South America. A calculation that names only “Azure egress” is incomplete.
Routing matters. Azure separately lists a transit-ISP routing preference. Its first paid North America/Europe band is $0.08/GB, rather than $0.087/GB on the premium global network. Those are different network products, not an automatic discount.
Monthly aggregate volume matters. Azure's premium-network table steps down after successive monthly bands: $0.087/GB for the next 10 TB, $0.083 for the next 40 TB, $0.07 for the next 100 TB, and $0.05 for the next 350 TB from North America/Europe. The free 100 GB also has a proportionally larger effect on a small transfer than on a large account.
Destination and path matter. Internet delivery, transfer between regions, same-zone traffic, a CDN, and private connectivity can use different meters. Model the actual route instead of applying an internet-egress number to every byte movement.
Storage class matters. Cool, Cold, and Archive capacity can look cheaper than Hot storage, but Azure documents minimum recommended retention periods of 30, 90, and 180 days, respectively, with early-deletion charges. Cool and Cold can also add retrieval fees. Cheap capacity is not automatically cheap temporary staging.
Compare providers carefully
Provider comparisons need aligned regions, destinations, units, allowances, and terms. As of August 10, 2026, Google Cloud Storage displayed $0.12/GiB for its first general-internet band to worldwide destinations excluding Asia and Australia, plus an eligible 100 GB monthly allowance from North America. AWS documented 100 GB per month of eligible internet data transfer out free across covered services and regions, followed by region- and destination-specific tiers.
Those examples are orientation, not an apples-to-apples ranking. GB and GiB differ, free allowances have different scopes, and retrieval and operation charges may sit beside bandwidth. Provider programs that waive eligible charges when a customer exits the cloud are also separate from routine customer downloads.
Model the delivery lifecycle
A useful estimate separates:
- capacity by storage class and redundancy;
- write, read, list, and other operations;
- retrieval and early-deletion charges;
- ingress;
- internet, regional, or private-network egress;
- replication or CDN charges; and
- the number of recipient downloads.
Then apply the retention window and expected redownload rate. A delivery workload with short retention and several recipients can be bandwidth-dominated. A long-lived archive that is rarely read can be capacity-dominated. Neither description should be generalized to all cloud storage.
Use the transfer-time calculator to model both network legs, and compare physical-media timing with the shipping-versus-transfer calculator for large one-off deliveries.
Where TeraAirlift fits
TeraAirlift is a Windows-first desktop operations console for large-file delivery rather than an archive. Plans currently start with a 10 TB included allotment; packages can be any size, and volume above the allotment is overage. That wording does not announce a final price, metering unit, billing cadence, or included-download rule. Those details remain under evaluation and are confirmed on a demo.
Sources
- Azure Bandwidth pricing — USD list tiers, routing choices, regions, and free allowance; accessed August 10, 2026.
- Azure Blob Storage pricing — units, access tiers, retention minimums, and early deletion; accessed August 10, 2026.
- Azure Retail Prices API — Storage in East US — capacity and operation inputs; accessed August 10, 2026.
- Google Cloud Storage pricing — internet-transfer bands and qualifications; accessed August 10, 2026.
- Amazon S3 pricing — eligible free data transfer and tiered egress; accessed August 10, 2026.
- NIST — Prefixes for binary multiples — GB/GiB and TB/TiB distinction.
