GCP egress costs: Google Cloud data transfer pricing & how to reduce it

Key takeaways

• Data entering Google Cloud carries no transfer charge, so moving data in costs nothing, and moving it out later does not. Services in the path, such as Cloud NAT, can still bill for processing in both directions.
• Premium Tier internet egress starts at US$0.12 per GB, the highest entry rate among major providers. Standard Tier runs at US$0.085 and undercuts both AWS and Azure.
• Traffic between zones in one region costs US$0.01 per GB in each direction, so a round trip inside a single region is charged twice.
• Only same-zone traffic over internal addresses is free, which makes zone placement a billing decision.
• Google now offers free egress to customers fully leaving the platform, but that does nothing for the daily transfer an active workload generates.

Google Cloud carries the highest headline egress rate of the three large hyperscalers. It also offers a cheaper network tier that most comparisons leave out. Which of those two facts applies to you depends on a setting many teams never change.

This guide covers what Google charges for outbound data and how the tiers work. It also covers how to estimate a bill before it arrives, and the levers that reduce it.

What is GCP egress cost?

GCP egress cost is what Google charges when data leaves its network. Inbound traffic costs nothing, so the entire data transfer bill sits on the outbound side.

Two things make it harder to predict than a single rate suggests. The charge varies by where the traffic is going, with internet destinations costing the most, cross-region less and cross-zone less again. It also varies by which network tier the project uses, and the default is the expensive one.

Data that never leaves a zone and travels over internal addresses is free. Almost everything else is metered.

Components of GCP egress cost

Five categories account for nearly all of these costs:

• Internet egress: The headline charge, tiered by volume. The rate depends on your network tier and the source region.
• Inter-region transfer: Charged between Google Cloud regions, and inter-region transfer costs work the same way on AWS and Azure. Intercontinental pairs cost more than neighbouring ones.
• Cross-zone transfer: US$0.01 per GB in each direction inside one region.
• Same-zone traffic on internal addresses: Free between virtual machines. This is the only genuinely free path.
• Cloud CDN delivery: Metered on its own schedule rather than as internet egress.

Traffic to another cloud provider is billed as internet egress. There is no separate multi-cloud rate, which is one of the hidden costs in a multi-cloud environment worth knowing when comparing quotes.

Google Cloud data transfer pricing

Google runs two network tiers, and the difference between them is the largest single lever on this bill.

Premium buys lower latency and more predictable routing. Standard costs roughly 29 per cent less at the entry rate and comes with a far larger free allowance.

Because Premium is the default, projects that never make an explicit choice pay the higher rate. For latency-tolerant traffic such as backups, log shipping and batch exports, that difference is money spent on a benefit the workload cannot use.

How much does Google Cloud charge for egress?

These are Premium Tier internet egress rates for North American destinations, verified against Google Cloud's network service tiers pricing in July 2026.

Worked at those rates, 1 TB of monthly egress costs about US$123 and 10 TB costs about US$1,137. The same 10 TB runs to roughly US$913 on AWS and US$882 on Azure, which is why Google reads as expensive in headline comparisons.

Standard Tier changes that picture. At US$0.085 per GB it costs around US$853 for 10 TB, below both, and the advantage widens above that because Standard steps down to US$0.065 per GB where Premium holds at US$0.08.

How GCP egress costs are calculated

Four mechanics decide the number on the invoice:

• Per gigabyte delivered: Google meters per GiB actually delivered, not per gigabyte requested.
• By source region: The rate follows where the traffic originates, so identical workloads in different regions bill differently.
• Tiered across the month: Volume accumulates through the billing period and the rate steps down as thresholds are crossed. Each gigabyte is charged at the rate of the band it falls into.
• Meters stack: Cross-zone and inter-region charges are billed separately and do not count towards the internet egress tiers. A single piece of data can attract more than one charge on its way out.

How to estimate egress with a GCP cost calculator

Google publishes a pricing calculator that covers network transfer alongside compute and storage. To get a usable number from it, you need three inputs: monthly outbound volume in GB, the source region, and the destination continent.

A GCP egress cost calculator will not tell you what you are transferring today. For that, use billing reports filtered to networking SKUs and break the spend down by project and service before modelling any change.

Treat calculator output as a planning figure. It models the headline meter well and tends to understate the internal transfer, cross-zone traffic and CDN delivery that sit alongside it.

How to reduce GCP data transfer costs

Six levers cut the bill, roughly in order of effort required. Tier choice and zone placement cost nothing to fix and address most of the avoidable spend; the rest compound on top.

• Check which network tier you are on: This is the fastest saving available here, and the starting point for reducing cloud egress costs across any provider. Move latency-tolerant traffic to Standard Tier and leave user-facing traffic on Premium.
• Keep chatty components in one zone: Same-zone traffic over internal addresses is free. Splitting an application and its database across zones adds a per-gigabyte charge to every query.
• Serve through Cloud CDN: Cached delivery moves traffic onto a different meter and cuts repeated origin fetches.
• Compress before sending: Gzip or Brotli on text-based payloads reduces billed bytes directly, and the saving applies to every request.
• Use private interconnection at volume: A dedicated connection into Google Cloud carries a lower per-gigabyte rate than public internet egress and removes exposure to variable transit performance.
• Set budget alerts on networking SKUs: Egress is usage-linked with no commitment mechanism, so the first warning is usually the bill unless you configure one.

Common mistakes to avoid

Most of this bill is self-inflicted rather than unavoidable. The five patterns below account for the majority of egress spend that a closer look would have caught:

• Accepting the default tier: Premium applies unless you change it. Paying backbone rates for backup traffic is the most common avoidable cost ere.
• Treating cross-zone traffic as internal: It looks internal on an architecture diagram and bills as transfer. Multi-zone databases with replicas generate this continuously.
• Comparing providers on headline rate alone: AWS and Azure look cheaper at entry volume until Standard Tier enters the comparison.
• Scheduling large transfers in bursts: Batch jobs concentrated into short windows create spikes that are harder to forecast than steady transfer.
• Modelling without measuring: Estimating from a calculator before pulling actual billing data produces a figure that matches nothing.

How Tata Communications reduces multi-cloud transfer costs

Egress economics change once traffic stops crossing the public internet. IZO™+ Multi Cloud Connect (MCC) provides private, direct connections into Google Cloud and other providers, reaching them from more than 700 access locations and over 160 cloud on-ramps. Setup takes under 10 minutes.

One insurer consolidating a fragmented multi-cloud estate onto a common multi-cloud hub reduced internet egress cost by approximately 30 per cent, alongside 25 to 30 per cent lifecycle cost savings. For traffic moving between providers, the Tata Cloud Router, part of the MCC Flex variant, carries it cloud-to-cloud without hair-pinning through your own data centre.

Begin A Free Trial Now.

See how IZO+ Multi Cloud Connect provides private, direct connectivity into Google Cloud. View GCP Interconnect

Discuss your transfer volumes, regions and tier strategy with our cloud connectivity specialists. Schedule A Conversation

Model what private connectivity would save against your current egress spend. Calculate Your Savings