How much do cloud providers charge to move data out, and how do I keep that cost down?

Rule of thumb: for ordinary internet downloads from a major cloud, budget roughly $0.08–$0.12 per GB after any free allowance. The exact bill depends on the provider, source region, destination, service, and whether traffic goes through a CDN or another network product.

For a rough U.S. internet-egress comparison:

So 1 TB of outbound traffic can mean roughly $80–$120, depending on provider and how the bill counts units and free usage. This is only a ballpark: cross-region transfers, inter-cloud moves, storage retrieval, CDN delivery, and NAT or load-balancer processing can have separate charges. For example, AWS lists same-region Availability Zone transfer and public-IPv4 traffic as separate chargeable cases. (aws.amazon.com)

Ways to keep the cost down

• Measure what’s leaving. Use billing reports, cost-allocation tags, and egress alerts to find the services, regions, and destinations driving the bill.
• Serve repeat downloads from a cache or CDN. This can reduce repeated trips from your origin, but compare the CDN’s delivery and request fees with your current egress rate.
• Send less data. Compress responses; resize images and video; avoid sending fields, logs, or files clients don’t need.
• Keep communicating services close together. Put chatty workloads and their databases in the same region, and check whether Availability Zone or cross-region traffic is adding charges.
• Use private or provider-specific paths carefully. They may avoid some public-internet charges, but can introduce their own endpoint, gateway, or interconnect fees—check the whole route.
• For storage with heavy public downloads, compare total cost—not just bandwidth. Cloudflare R2, for example, lists no egress fee, but storage, operations, and—in its Infrequent Access class—retrieval are still billed. (developers.cloudflare.com)
• For a large one-time move, get a specific estimate first. Include retrieval, request, network, and destination-ingress costs—not just the source’s egress line item.

If you share your provider, region, and approximate monthly outbound volume, I can estimate it more closely.

Egress is typically billed at roughly $0.09 per GB on AWS, $0.087 on Azure, and $0.12 on Google Cloud, with lower rates at higher volumes. You can cut it mainly by serving data through a CDN, keeping traffic inside one region, compressing it, and choosing a storage provider with free egress for public downloads.

What it costs

• Base rates: Standard 2026 internet egress rates run from $0.087 to $0.12 per GB on the major hyperscalers. AWS's first tier is $0.09/GB for the first 10 TB per month, after a 100 GB/month free allowance.
• Volume tiers: Rates step down as usage grows. For AWS, $0.085/GB from 10–50 TB, $0.07/GB from 50–150 TB, and $0.05/GB above 150 TB.
• Hidden charges: Transfers between regions or availability zones add cost. Cross-AZ transfer within a region is $0.01/GB each direction, and AWS NAT Gateway charges $0.045/GB processing on top of standard $0.09/GB egress, so internet traffic from a private subnet can cost about $0.135/GB.
• Zero-egress options: Some providers don't charge for egress. Cloudflare R2, Backblaze B2, and Wasabi are listed at $0 per GB, though the terms behind those figures (such as Backblaze's partner-CDN conditions) are worth reading closely.

How to keep it down

1. Put a CDN in front of your data. Cached content is served from the edge, so the origin doesn't pay egress for every repeat request. One guide notes that CloudFront to internet is $0.085/GB versus $0.09/GB for direct S3 egress, and that S3 to CloudFront transfer is completely free.
2. Compress data before sending it. Gzip or Brotli compression for responses and files shrinks the billed volume.
3. Keep traffic in the same region. Co-locate compute, storage, and databases, and avoid cross-region copies unless you need them. For replication, use S3 Replication with filters to replicate only essential data rather than entire buckets.
4. Use private endpoints for AWS service traffic. Enable VPC Gateway Endpoints for S3/DynamoDB so that traffic doesn't pass through a NAT gateway. This is one of the easier savings to get.
5. Cache at every layer. Caching in the browser, at the CDN, and in application tiers such as Redis reduces repeat transfers.
6. Move hot public data to a zero-egress provider. This makes sense for large, frequently downloaded datasets, but it's a migration project.
7. Negotiate committed-use discounts. At scale, enterprise agreements with cloud providers that include discounted egress rates are worth asking about.
8. Monitor egress by workload. Most egress accumulates invisibly. Tag resources and check which services generate the most outbound traffic before optimizing.

Caveats: Many of the figures above come from vendor or reseller blogs, and the savings percentages in those guides are estimates, not measured results. Rates also differ by region and change over time, and some sources disagree slightly (for example, Azure's first-tier price appears as both $0.087 and $0.08 depending on routing). Check the current pricing pages for your provider and region, and use your provider's cost-analysis tools on your own bill before deciding which changes to make.

Data egress fees—the cost of moving data out of a cloud provider’s network—are a common source of "bill shock" because they are often ignored until they become a major line item.

How Much Do Providers Charge?

While data ingress (moving data into the cloud) is almost always free, egress (moving data out) is typically metered and billed per gigabyte.

• Standard Hyperscaler Rates: For the "Big Three" (AWS, Azure, Google Cloud), internet egress typically costs between $0.05 and $0.12 per GB for pay-as-you-go customers, depending on the region and total volume.
• Tiered Pricing: Most providers use a tiered model where the cost per GB decreases as your monthly volume increases.
• The "Hidden" Costs: Egress isn't just for data leaving to the public internet. You may also be charged for:
  • Inter-region transfers: Moving data between different geographic cloud regions.
  • Inter-zone transfers: Moving data between availability zones (data centers) within the same region.

Note: Some specialized cloud providers (often in the GPU or object storage space) offer "zero-egress" or significantly cheaper bandwidth as a competitive advantage.

How to Keep Egress Costs Down

You can significantly reduce these costs by focusing on architectural changes and optimizing how data is served.

1. Implement Caching and CDNs

• Use a Content Delivery Network (CDN): Services like CloudFront or Cloudflare cache your content closer to the user. Because CDNs have different (and often lower) pricing structures for data delivery, they can significantly reduce the amount of data pulled directly from your primary cloud storage (the "origin").
• Cache at Every Layer: If you have an application server or database, implement local caching layers to prevent repetitive, unnecessary data transfers.

2. Optimize Data Volume

• Compress Data: Always compress files (using gzip, zstd, or brotli) before transferring them. Reducing the payload size by 30–60% directly scales down your egress costs.
• Minimize "Chatty" Architectures: Ensure that services that exchange large amounts of data are co-located in the same availability zone or region to avoid cross-zone or cross-region fees.

3. Architectural Best Practices

• Use VPC Endpoints: For services like AWS S3 or DynamoDB, use VPC Gateway Endpoints. This keeps your traffic on the cloud provider’s internal backbone and often bypasses NAT Gateway charges, which can be a significant hidden cost.
• Consolidate Data: If you have fragmented analytics stacks (e.g., data moving constantly between a lake, a warehouse, and BI tools), consider unifying these into a single platform or "lakehouse" architecture to eliminate the need for constant data copying.

4. Strategic Planning

• Monitor Patterns: Use cloud cost-monitoring tools (like AWS Cost Explorer or third-party FinOps platforms) to identify which services are generating the most egress traffic. You cannot fix what you do not measure.
• Consider Multi-Cloud Carefully: While a multi-cloud strategy provides flexibility, moving data between two different cloud providers is generally the most expensive form of egress. Minimize these "cross-cloud" hops whenever possible.
• Check Provider "Free Tiers": Most providers offer a monthly allowance of free egress (often 100 GB). Structure your workflows to stay within these limits if your volume is relatively low.

Cloud “egress” (data sent out to the public internet) commonly costs around $0.08–$0.12 per GB at modest monthly volumes in the US/Europe, then often gets cheaper at higher volumes. The exact bill depends on provider, region, destination, service, and transfer path.

Indicative examples from current published rates:

• AWS: The first 100 GB/month of internet data transfer out is free, pooled across eligible AWS services and regions. Beyond that, rates vary by service and destination; AWS’s S3 page, for example, lists $0.09/GB for S3 data out from its Ireland region to the internet. ³⁹
• Azure: The first 100 GB/month is free. After that, for North America and Europe, published tiers start at $0.087/GB on Microsoft’s Premium network or $0.08/GB via its transit-ISP routing option; rates decline at higher volumes. ²
• Google Cloud: General internet egress in North America and Europe starts around $0.12/GiB for the first tier, then falls to $0.11 and $0.08/GiB at higher monthly volumes. Pricing varies by destination and service. ⁵

These are ballpark list prices, not a quote. GB and GiB are different units, and a product’s pricing page may not match general network pricing. Also check for transfer charges between regions, availability zones, or services—not just internet egress.

Ways to keep the cost down

1. Measure where the bytes go. Break usage down by service, region, destination, and traffic type; compare billing reports with actual traffic. Look for repeat downloads, backups, logs, and cross-region transfers.
2. Cache content close to users. For websites, downloads, and media, a CDN can serve repeat requests from edge locations instead of repeatedly fetching from your origin. Check the CDN’s delivery and origin-transfer charges before switching.
3. Reduce how much you send. Compress responses and files, resize images/video, remove unnecessary payloads, and avoid sending duplicate or overly chatty API data.
4. Keep communicating services close together. Co-locate workloads and data in the same region where practical, and avoid unnecessary cross-region or cross-zone traffic. Verify the provider’s specific internal-transfer rates.
5. Choose the right transfer path. Some providers offer alternate routing or private-connectivity pricing, but private links can have fixed port or connection fees, so compare the total cost rather than just the per-GB rate.
6. Use provider credits or negotiated rates where eligible. For example, Azure advertises free egress for qualifying customers moving data out to another provider or on-premises; check the eligibility and claim process. ²
7. Set budgets and alerts. Track egress as its own cost category and alert on unusual growth before it becomes a surprise.

For a useful estimate, calculate monthly outbound GB × the rate for your service, region, and destination, then add any CDN, inter-region, or private-connectivity fees. The provider pricing pages are the best place to verify your exact rate.