Google Compute Engine Pricing

This page describes the pricing information for Compute Engine. To see the pricing for other products, read the Pricing documentation.

Google Compute Engine charges for usage based on the following price sheet. A bill is sent out at the end of each billing cycle, listing previous usage and charges. Prices on this page are listed in US dollars (USD).

Disk size, machine type memory, and network usage are calculated in gigabytes (GB), where 1 GB is 2³⁰ bytes. This unit of measurement is also known as a gibibyte (GiB).

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

You can also find pricing information with the following options:

• See the estimated costs of your instances and Compute Engine resources when you create them in the Google Cloud Platform Console.
• Estimate your total project costs with the Google Cloud Pricing Calculator.

Always Free Usage Limits

As part of the Google Cloud Platform Free Tier, Compute Engine offers an amount of usage that is free to use, up to a specific limit. These free usage limits are always available even during and after the free trial period. If you go over these usage limits and are no longer in the free trial period, you will be charged according to the price sheet.

• 1 non-preemptible f1-micro VM instance per month in one of the following US regions:
  • Oregon: us-west1
  • Iowa: us-central1
  • South Carolina: us-east1
• 30 GB of Standard persistent disk storage per month.
• 5 GB of snapshot storage per month. Limited to the following regions:
  • Oregon: us-west1
  • Iowa: us-central1
  • South Carolina: us-east1
  • Taiwan: asia-east1
  • Belgium: europe-west1
• Network Traffic Limits:
  • You must use Premium Tier. You cannot use Standard Tier.
  • Traffic must be sent from a GCP region in North America.
  • You can send up to 1GB of egress traffic, in aggregate, to regions except for those in Oceania and China.

For f1-micro instances, you receive free usage equivalent to the number of total hours within the current month, enough to run one instance without interruption for the entire month. For example, August has 744 Hours (31 days x 24 hours). Therefore, you would receive 744 instance hours of free usage for the month.

Preemptible VM instances are not included in the Google Cloud Platform Free Tier.

All usage is aggregated across regions. Always Free Usage Limits are subject to change. Please see our FAQ for eligibility requirements and other restrictions.

Billing model

The following billing model applies to all vCPUs, GPUs, and memory resources. The billing model also applies to several premium images that you run on Compute Engine instances.

1. All vCPUs, GPUs, and GB of memory are charged a minimum of 1 minute. For example, if you run your virtual machine for 30 seconds, you will be billed for 1 minute of usage.

2. After 1 minute, instances are charged in 1 second increments.

Resource-based pricing

Each vCPU and each GB of memory on Compute Engine is billed separately rather than as part of a single machine type. You still create instances using predefined machine types, but your bill reports them as individual vCPUs and memory used per hour.

Resource-based pricing allows Compute Engine to apply sustained use discounts to all of your predefined machine type usage in a region collectively rather than to individual machine types.

Compute Engine machine resources can be broken down into the following categories:

• Predefined vCPUs and memory, which are used in n1-standard, n1-highcpu, and n1-highmem machine types as well as sole-tenant nodes.
• Custom vCPUs and memory, which are used in custom machine types that allow you to select a specific number of vCPUs and memory.
• Memory-optimized vCPUs and memory, which are used in n1-megamem and n1-ultramem machine types that have preset number of vCPUs and a high ratio of memory for each vCPU.
• Shared-core machine types, which use partial vCPUs and are cost-effective for running small, non-resource intensive applications. Shared-core machine types are still billed as a single unit rather than as separate vCPU and memory resources.

Your vCPU and memory usage for each of these categories can receive one of the following discounts:

• Sustained use discounts
• Committed use discounts
• Discounts for preemptible VM instances

Discount types cannot be combined. Preemptible VM instances cannot receive sustained use discounts or committed use discounts.

The following sections describe prices for machine types based on vCPU and memory resources, but also include the calculated cost for each machine type. You can also use the Google Cloud Pricing Calculator to better understand price for different configurations.

Predefined vCPUs and memory

Compute Engine offers several predefined machine types in each region. Predefined machine types have a preset number of vCPUs and amount of memory, but are billed using the resource-based pricing model.

Compute Engine also provides automatic sustained use discounts for all of the predefined vCPU and memory resources that you use in a region. Sustained use discounts for predefined machine types are calculated separately from shared-core machine types, custom machine types, and memory-optimized machine types.

Item	On-demand price	Preemptible price	1 year commitment price	3 year commitment price
Predefined vCPUs
Predefined Memory

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

The following tables show the calculated cost for n1-standard, n1-highcpu, and n1-highmem machine types. The vCPUs and memory from each of these machine types are billed by their individual predefined vCPU and memory prices, but these tables provide the cost that you can expect using a specific machine type.

Standard machine types

Standard machine types have 3.75 GB of memory per vCPU.

Machine type	Virtual CPUs	Memory	Price (USD)	Preemptible price (USD)
n1-standard-1
n1-standard-2
n1-standard-4
n1-standard-8
n1-standard-16
n1-standard-32
n1-standard-64
n1-standard-96 Skylake Platform only
Custom machine type	If your ideal machine shape is in between two predefined types, using a custom machine type could save you as much as 40%. Read more about Custom Machine Types.

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

High-memory machine types

High-memory machine types have 6.5 GB of memory per vCPU. High-memory instances are ideal for tasks that require more memory relative to virtual CPUs.

Machine type	Virtual CPUs	Memory	Price (USD)	Preemptible price (USD)
n1-highmem-2	2	13GB
n1-highmem-4	4	26GB
n1-highmem-8	8	52GB
n1-highmem-16	16	104GB
n1-highmem-32	32	208GB
n1-highmem-64	64	416GB
n1-highmem-96 Skylake Platform only
Custom machine type	If your ideal machine shape is in between two predefined types, using a custom machine type could save you as much as 40%. Read more about Custom Machine Types.

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

High-CPU machine types

High-CPU machine types have one vCPU for every 0.90 GB of memory. High-CPU machine types are ideal for tasks that require more virtual CPUs relative to memory.

Machine type	Virtual CPUs	Memory	Price (USD)	Preemptible price (USD)
n1-highcpu-2	2	1.80GB
n1-highcpu-4	4	3.60GB
n1-highcpu-8	8	7.20GB
n1-highcpu-16	16	14.40GB
n1-highcpu-32	32	28.80GB
n1-highcpu-64	64	57.6GB
n1-highcpu-96 Skylake Platform only
Custom machine type	If your ideal machine shape is in between two predefined types, using a custom machine type could save you as much as 40%. Read more about Custom Machine Types.

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Custom vCPUs and memory

Custom machine types allow you to set a specific number of vCPUs and GB of memory for your instances to match the needs of your workload. Custom machine types save you the cost of running on a larger and more expensive machine type if your application does not require all of the resources provided by that machine type.

For example, instead of using an n1-standard-8 machine type when you need a machine type with 6 vCPUs, you can create an instance with a custom machine type that has 6 vCPUs and 22.5 GB of memory. Creating a custom machine type can save you up to 40% compared to selecting a larger machine type. Custom machine types are billed according to the number of vCPUs and the amount of memory used.

Sustained use discounts for custom machine types are calculated separately from shared-core machine types, predefined machine types, and memory-optimized types.

Read the Creating Instances with Custom Machine Types to learn how to use these machine types.

For an accurate estimate of your billing with custom machine types, use the Google Cloud Pricing Calculator.

Item	On-demand price	Preemptible price	1 year commitment price	3 year commitment price
Custom vCPUs
Custom Memory

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Extended custom memory

For custom machine types, any memory up to and including 6.5 GB of memory per vCPU is charged at the standard custom vCPU and memory pricing rate. Any memory above the 6.5 GB per vCPU is charged according to the extended memory prices that are described in detail below. See the Extended Memory page to learn how to create instances with custom machine types and extended memory.

Item	Price (USD)	Preemptible price (USD)
Extended custom memory

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Memory-optimized vCPUs and memory

Memory-optimized machine types are ideal for tasks that require intensive use of memory with higher memory to vCPU ratios than n1-highmem machine types. Memory-optimized machine types are available in select regions only. See the Machine Types page to learn more about memory-optimized machine types.

Sustained use discounts for memory-optimized machine types are calculated separately from shared-core machine types, predefined machine types, and custom machine types.

Item	On-demand price	Preemptible price	1 year commitment price	3 year commitment price
Memory-optimized vCPUs
Memory-optimized Memory

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

The following table shows the calculated cost for n1-megamem, and n1-ultramem machine types. The vCPUs and memory from each of these machine types are billed by their individual memory-optimized vCPUs and memory prices, but these tables provide the cost that you can expect using a specific machine type.

Memory-optimized machine types

Memory-optimized machine types are ideal for tasks that require intensive use of memory with higher memory to vCPU ratios than high-memory machine types. Memory-optimized machine types are available in select regions only. Learn more about memory-optimized machine types.

Machine type	Virtual CPUs	Memory	Price (USD)	Preemptible price (USD)
n1-ultramem-40	40
n1-ultramem-80	80
n1-ultramem-160	160
Machine type	Virtual CPUs	Memory	Price (USD)	Preemptible price (USD)
n1-megamem-96	96

Committed Use Discounts apply to memory-optimized machine types only if you buy the commitment type specifically for memory-optimized machine types. You must request access to use committed use discounts for memory-optimized machine types. If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Shared-core machine types

Compute Engine offers shared-core machine types, which are more cost-effective for running smaller applications that do not require as many resources as provided by the other machine types.

Unlike predefined machine types, custom machine types, and memory-optimized machine types, shared-core machine types are not billed on their individual resources. Each machine type has a defined price for both vCPUs and memory.

Sustained use discounts for shared-core machine types are calculated separately from predefined machine types, custom machine types, and memory-optimized machine types.

f1-micro Bursting

f1-micro machine types offer bursting capabilities that allow instances to use additional physical CPU for short periods of time. Bursting happens automatically when your instance requires more physical CPU than originally allocated. During these spikes, your instance will opportunistically take advantage of available physical CPU in bursts. Note that bursts are not permanent and are only possible periodically.

Machine type	Virtual CPUs	Memory	Price (USD)	Preemptible price (USD)
f1-micro	1
g1-small	1

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Sustained use discounts

Sustained use discounts are calculated for each individual vCPU and GB of memory that you use. When an instance uses a vCPU or a GB of memory for more than 25% of a month, Compute Engine automatically gives you a discount for every incremental second that you continue to use those resources. The discount increases with usage and you can get up to a 30% net discount off of the vCPU and memory cost for instances that run the entire month.

Additionally, vCPU and memory usage in each region is calculated separately for each of the following categories:

• Predefined vCPUs and memory, which are used in n1-standard, n1-highcpu, and n1-highmem machine types as well as sole-tenant nodes.
• Custom vCPUs and memory, which are used in custom machine types that allow you to select a specific number of vCPUs and memory.
• Memory-optimized vCPUs and memory, which are used in n1-megamem and n1-ultramem machine types that have preset number of vCPUs and a high ratio of memory for each vCPU.
• Shared-core machine types, which use partial vCPUs and are cost-effective for running small, non-resource intensive applications.

For example, if you run predefined machine types, custom machine types, and memory-optimized machine types in us-west1, Compute Engine calculates the sustained use discount for each of those categories separately. Other regions are also calculated separately from us-west1 resources.

Sustained use discounts are applied automatically and will be calculated and added to your bill as your project earns them. There is no action needed on your part to enable sustained use discounts.

To learn more about sustained use discounts, see the Sustained Use Discounts documentation.

Committed use discounts

Compute Engine offers the ability to purchase a committed use contract in return for heavily discounted prices for VM usage. These discounts are known as committed use discounts. Read the purchasing a commitment page to learn how to create a commitment.

Committed use discounts are available in the following categories:

• General purpose: Committed use discounts for standard, highmem, highcpu, custom machine types, and general purpose sole-tenant nodes
• Memory-optimized: Committed use discounts for memory-optimized machine types

Commitments are appropriate for predictable and steady state usage where you will use a specific amount of vCPUs and memory for future workloads. Commitments allow you to purchase a specific number of vCPUs and amount of memory at up to a 57% discount over full prices for most machine types or custom machine types. The discount is up to 70% for memory-optimized machine types. You commit to the entire usage term and are billed for each month regardless of whether usage has occurred.

To see vCPU and memory pricing for 1 and 3 year commitments compared with other Compute Engine pricing options, see the resource pricing tables.

You must request access to use committed use discounts for memory-optimized machine types.

Sole-tenant nodes

Sole-tenant nodes are physical Compute Engine servers dedicated to hosting only VM instances from your specific project. When you create nodes, you pay for the vCPU and memory that your node occupies as well as a 10% sole-tenancy premium on those resources. After you create the node, you can place your VM instances on that node. These instances run for no additional cost except for the cost of the instances' other resources such as persistent disks and premium images that you use with your instances.

The price of vCPUs and memory in a sole-tenant node is a base resource price plus a 10% sole-tenancy premium. For example, each vCPU and each GB of memory in the us-west1 region has the following price per hour:

$0.031611 for 1 vCPU + $0.0031611 for the 10% premium = $0.0347721/hour

$0.004237 for 1 GB of memory + $0.0004237 for the 10% premium = $0.0046607/hour

Sole-tenant vCPU, memory, and premium costs

The following table compares the base values for vCPUs, memory, and the 10% sole-tenancy premium charge. The vCPUs and memory not covered by a committed use discount are eligible for sustained use discounts. If you do use committed use discounts, the base prices for these resources are the commitment prices. The 10% sole-tenancy premium for committed use vCPUs and memory is the same as the premium for non-committed use.

The following table shows the base price for sole-tenant vCPUs and memory and also shows the 10% sole-tenancy premium. The base vCPU and memory prices are eligible for either sustained use discounts or committed use discounts. The 10% sole-tenancy premium is eligible only for sustained use discounts.

For the purposes of calculating sustained use discounts, the vCPUs and memory used by sole-tenant nodes also are billed as predefined vCPUs and memory.

	vCPUs	Memory
Base price
Premium 10% cost

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Calculating sole-tenancy pricing including discounts

Sustained use discounts apply to the vCPU, memory, and the sole-tenancy premium. For example, if you create an n1-node-96-624 node and run it for a full 730 hours per month in the us-west1 region, you receive the following sustained use discount price using the calculated vCPU and memory hourly prices:

(((96vCPUs * ($0.031611 base) + (624GB * $0.004237) base) + ((96vCPUs * $0.0031611 premium) + (624GB * $0.0004237 premium)) * 0.7 discount) * 730.0 hours  = 3191.9095824

For committed use discounts, your commitments on vCPUs and memory cover the cost of vCPUs and memory on sole-tenant nodes. You still pay the 10% sole-tenancy premium for resources consumed by the sole-tenant nodes, but those premiums are eligible for sustained use discounts even if the vCPUs and memory are already covered by a committed use discount. You can calculate the price of an n1-node-96-624 node using a formula similar to the following example, which shows a 3 year committed use discount on 96 vCPUs and 624 GB of memory as well as a separately calculated sustained use discount on the sole-tenancy premium for running this node for a full 730 hours during the month:

(((96vCPUs * $0.014225 commitment price) + (624GB * $0.001907 commitment price)) + ((96vCPUs * $0.0031611 premium) + (624GB * $0.0004237 premium)) * 0.7 discount) * 730.0 hours  = 2155.7382384

The following table shows the predicted total cost per vCPU and memory to run sole-tenant nodes using either hourly pricing, monthly pricing with the sustained use discount, or one of the committed use discount options. These values include the 10% sole-tenancy premium, and any applicable sustained use discounts.

Item	Price (USD)	1 year commitment price (USD)	3 year commitment price (USD)
Total cost per vCPU
Total cost per GB of memory

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

GPU pricing

Attach one or more GPUs to your instances to accelerate specific workloads or offload work from your vCPUs. Each GPU adds to the cost of your instance in addition to the cost of the machine type. GPUs are subject to the same billing policy as vCPUs and memory.

GPU devices attached to non-preemptible instances receive sustained use discounts similar to vCPUs. For GPUs attached to preemptible instances, you will be charged at the preemptible prices for GPUs but will not receive sustained use discounts.

GPU prices are listed by region. GPU devices are available only in specific zones within some regions. Read GPUs on Compute Engine to see a complete list of regions and zones where GPU devices are available.

Model	GPUs	GPU memory	GPU price	Preemptible GPU price
NVIDIA® Tesla® T4	1 GPU	16 GB GDDR6
	2 GPUs	32 GB GDDR6
	4 GPUs	64 GB GDDR6
NVIDIA® Tesla® P4	1 GPU	8 GB GDDR5
	2 GPUs	16 GB GDDR5
	4 GPUs	32 GB GDDR5
NVIDIA® Tesla® V100	1 GPU	16 GB HBM2
	2 GPUs	32 GB HBM2
	4 GPUs	64 GB HBM2
	8 GPUs	128 GB HBM2
NVIDIA® Tesla® P100	1 GPU	16 GB HBM2
	2 GPUs	32 GB HBM2
	4 GPUs	64 GB HBM2
NVIDIA® Tesla® K80	1 GPU	12 GB GDDR5
	2 GPUs	24 GB GDDR5
	4 GPUs	48 GB GDDR5
	8 GPUs	96 GB GDDR5
NVIDIA® GRID® Virtual Workstation GPUs
NVIDIA® Tesla® T4 Virtual Workstation	1 GPU	16 GB GDDR6
	2 GPUs	32 GB GDDR6
	4 GPUs	64 GB GDDR6
NVIDIA® Tesla® P4 Virtual Workstation	1 GPU	8 GB GDDR5
	2 GPUs	16 GB GDDR5
	4 GPUs	32 GB GDDR5
NVIDIA® Tesla® P100 Virtual Workstation	1 GPU	16 GB HBM2
	2 GPUs	32 GB HBM2
	4 GPUs	64 GB HBM2

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Use the Google Cloud Platform Pricing Calculator to help determine the total cost of your instances including both the cost of GPUs and machine type configurations.

To learn more about how you can use GPUs to accelerate your applications, see GPUs on Compute Engine.

Cloud TPU pricing

Information about billing for Cloud TPU resources is available on the Cloud TPU pricing page.

Premium images

The price for a premium image is different depending on which machine type you use. For example, a standard SUSE image costs $0.02 per hour to run on an f1-micro instance, but the same image costs $0.11 per hour to run on an n1-standard-8 instance. The prices for premium images are the same worldwide and do not differ based on zones or regions.

All prices for premium images are in addition to charges for using a machine type. For example, the total price to use an n1-standard-8 instance with a SUSE image would be the sum of the machine type cost and the image cost:

n1-standard-8 cost + SUSE image cost = $0.3800 + $0.11 = $0.49 per hour

Note: Preemptible instances do not reduce the costs of premium images and do not change the way that you are billed for the use of those images. If Compute Engine terminates a preemptible instance that runs a premium image, you are billed for that image as if you terminated the instance yourself. The charges for minimum usage still apply, and bills for premium images are still calculated by rounding up to the nearest usage increment.

Red Hat Enterprise Linux (RHEL) and RHEL for SAP images

RHEL images:

• $0.06 USD/hour for instances with 4 or fewer vCPUs
• $0.13 USD/hour for instances with more than 4 vCPUs

RHEL for SAP Apps and RHEL for SAP HANA images:

• $0.06 USD/hour for instances with 4 or fewer vCPUs
• $0.13 USD/hour for instances with more than 4 vCPUs

RHEL for SAP with HA and Update Services images:

• $0.10 USD/hour for instances with 4 or fewer vCPUs
• $0.225 USD/hour for instances with more than 4 vCPUs

All RHEL and RHEL for SAP images are charged a 1 minute minimum. After 1 minute, RHEL images are charged in 1 second increments.

Google reports your billing entity name and total hours of Red Hat premium OS usage on Compute Engine to Red Hat, which complies with the Red Hat licensing requirements.

SUSE images and SLES for SAP images

SLES images:

• $0.02 USD/hour for f1-micro and g1-small machine types
• $0.11 USD/hour for all other machine types

SLES for SAP images:

• $0.17 USD/hour for instances with 1 - 2 vCPUs
• $0.34 USD/hour for instances with 3 - 4 vCPUs
• $0.41 USD/hour for instances with 5 or more vCPUs

All SUSE images are charged a 1 minute minimum. After 1 minute, SUSE images are charged in 1 second increments.

Windows Server images

Public images for several versions of Windows Server are available in either the Server Core configuration or the Server with Desktop Experience configuration. Both configurations are available at the following prices:

• $0.02 USD/hour for f1-micro and g1-small machine types
• $0.04 USD per core/hour for all other machine types

Standard machine types, high-CPU machine types, and high-memory machine types are charged based on the number of CPUs. For example, n1-standard-4, n1-highcpu-4, and n1-highmem-4 are machine-types with 4 vCPUs, and are charged at $0.16 USD/hour (4 x $0.04 USD/hour).

Windows Server images are charged a 1 minute minimum. After 1 minute, Windows images are charged in 1 second increments. SQL Server images are charged a 10 minute minimum. After 10 minutes, SQL Server images are charged in 1 minute increments.

SQL Server images

SQL Server images incur costs in addition to the cost for Windows Server images and the cost for the selected machine type.

• $0.399 USD per core/hour for SQL Server Enterprise
• $0.1645 USD per core/hour for SQL Server Standard
• $0.011 USD per core/hour for SQL Server Web
• No additional charge for SQL Server Express

Microsoft SQL Server licensing requires a core license to be assigned to each virtual CPU on your virtual machine instance, with a four core minimum for each instance. Instances with fewer than 4 vCPUs will be charged for SQL Server at 4 x $0.1645 USD/hour ($0.658 USD/hour) to comply with these requirements. For instances with 4 or more vCPUs, Compute Engine charges you for Microsoft SQL Server licenses in increments of 2. However, instances with custom machine types will be charged for the number of SQL Server licenses that is equal to the number of vCPUs.

Google recommends that you do not use SQL Server images on f1-micro or g1-small machine types based on Microsoft's minimum hardware and software recommendations.

Unlike other premium images, SQL Server images are charged a 10 minute minimum. After 10 minutes, SQL Server images are charged in 1 minute increments.

Instance uptime

Instance uptime is measured as the number of seconds between when you start an instance and when you stop an instance, the latter being when the instance state is TERMINATED. In some cases, your instance can suffer from a failure and be marked as TERMINATED by the system; in these cases, you will not be charged for usage after the instance reaches the TERMINATED state. If an instance is idle, but still has a state of RUNNING, it will be charged for instance uptime. The easiest way to determine the status of an instance is to use gcloud compute with the gcloud compute instances list command or to visit the Google Cloud Platform Console.

Note that Google Compute Engine bills for a minimum of 1 minute of usage, so if you run an instance for 30 seconds of uptime, you are billed for 1 minute. After 1 minute, your instance is billed on a per-second basis. For more information, see the billing model.

Network pricing

General network pricing

Traffic type	Price
Ingress	No charge, unless there is a resource such as a load balancer that is processing ingress traffic. Responses to requests count as egress and are charged.
Egress1 to the same zone	No charge
Egress to Google products (such as YouTube, Maps, Drive), whether from a VM in GCP with an external IP address or an internal IP address	No charge
Egress to DoubleClick in the same region	No charge
Egress to a different Google Cloud Platform service within the same region using an external IP address or an internal IP address, except for Cloud Memorystore for Redis, Cloud Filestore, and Cloud SQL	No charge
Egress2 between zones in the same region (per GB)	$0.01
Egress to Cloud Memorystore for Redis is charged at the rate of "Egress between zones in the same region"
Egress to Cloud Filestore is charged at the rate of "Egress between zones in the same region"
Egress to Cloud SQL is charged at the rates described in Traffic through external IP addresses
Egress between regions within the US (per GB)	$0.01
Egress between regions within the US and Canada (per GB)	$0.01 starting on April 18, 2019. Traffic between the US and Canada charged at Internet egress rates before April 18, 2019.
Egress between regions within Europe (per GB)	$0.02 starting on April 18, 2019. At Internet egress rates before April 18, 2019.
Egress between regions within Asia (per GB)	$0.05 starting on April 18, 2019. At Internet egress rates before April 18, 2019.
Egress between regions within South America (per GB)	$0.08 starting on April 18, 2019. At Internet egress rates before April 18, 2019.
Intercontinental egress (excludes Oceania) (per GB)	$0.08 starting on April 18, 2019. At Internet egress rates before April 18, 2019.
Oceania3 to/from any region (per GB)	$0.15 starting on April 18, 2019. At Internet egress rates before April 18, 2019.

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Internet egress rates^*

Monthly Usage	Network (Egress) Worldwide Destinations (excluding China & Australia, but including Hong Kong) (per GB)	Network (Egress) China Destinations (excluding Hong Kong) (per GB)	Network (Egress) Australia Destinations (per GB)	Network (Ingress)
0-1 TB		$0.23	$0.19	Free
1-10 TB		$0.22	$0.18	Free
10+ TB		$0.20	$0.15	Free

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Load balancing and forwarding rules

The following applies to all types of load balancing and forwarding rules (protocol forwarding).

Item	Price per Unit (USD)	Pricing Unit
First 5 forwarding rules		Per Hour
Per additional forwarding rule		Per Hour
Ingress data processed by load balancer		Per GB

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Load balancing ingress and egress charges

• The Load balancing and forwarding table above contains the charge for ingress data processed by load balancers.
• Normal egress rates are charged for traffic outbound from a load balancer.
• There is no additional load balancer egress cost beyond normal egress rates.

Forwarding rules charges

Compute Engine charges for forwarding rules that are created for load balancing or other uses of forwarding rules.

The following examples use US pricing:

Up to 5 forwarding rules you create are charged at $0.025/hour. For example, if you create one forwarding rule, you will be charged $0.025/hour. If you have 3 forwarding rules, you will still be charged $0.025/hour. However, if you have 10 rules, you will be charged:

• 5 forwarding rules = $0.025/hour
• Each additional forwarding rule = $0.01/hour

$0.025/hour for 5 rules + (5 additional rules * $0.01/hour) = $0.075/hour

User-defined request headers and Cloud Armor charges

If a backend service has a Cloud Armor policy associated with it, you can use the user-defined request headers feature with that backend service without any additional charge for the user-defined request headers feature.

If a backend service does not have a Cloud Armor policy associated with it, the charges are $0.75 per million HTTP(S) requests sent to those backend services that use the user-defined request headers feature.

These charges become effective after the user-defined request headers feature becomes available in General Availability (GA).

Network Telemetry

VPC network logs, including VPC flow logs and firewall rule logs, generate charges.

VPC Flow Log and Firewall Log generation	Price
0–10 TB per month	0.50/GB
10–30 TB per month	0.25/GB
30–50 TB per month	0.10/GB
>50 TB per month	0.05/GB

Traffic through external IP addresses

When you send traffic between virtual machines through the external IP addresses, it will be charged as follows:

• Traffic sent between the external IP address of two virtual machines in the same region will be charged as Egress between zones in the same region, even if the virtual machines are in the same zone.
• Traffic sent between the external IP address of two virtual machines in different regions within the US will be charged as Egress between regions within the US.
• Traffic sent between the external IP address of two virtual machines in different regions, not including traffic between US regions, will be charged at Internet Egress pricing.

It is not possible to charge traffic through the external IP address of two virtual machine instances in the same zone as Egress to the same zone because Compute Engine cannot determine the zone of a virtual machine through the external IP address.

VPN

Cloud VPN pricing is based on the location of the VPN endpoint and the number of tunnels per hour.

Component Billed	Price (USD)
Per tunnel (per hour)
IPsec traffic	Charged as if the traffic were regular egress traffic. If the Cloud VPN tunnel connects to a gateway in GCP, egress pricing to the region containing that gateway applies. See General network pricing. If the Cloud VPN tunnel connects to a gateway outside of GCP, Internet egress rates apply.
Public IP for VPN Gateway	Charged according to IP address pricing.

Google does not charge for forwarding rules that send traffic to the VPN gateway.

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Unused IP address pricing

If you reserve a static external IP address but do not use it, you will be charged for the IP address according to the table below. If you reserve a static external IP address and use it with a Compute Engine resource, such as VM instance or a forwarding rule, the address is considered in use and you will not be charged for it.

Type	Price/Hour
Static IP address (assigned but unused)
Static IP address (assigned and in use)	No charge
Ephemeral IP address (attached to instance or forwarding rule)	No charge

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

You can check whether a static external IP address is in use by making a gcloud compute addresses list request. This command returns a list of static external IP addresses and their statuses:

gcloud compute addresses list

NAME          REGION  ADDRESS        STATUS
address-1             130.211.8.68   IN_USE
address-2             35.186.217.84  RESERVED

In this example, IPv4 address-1 is in use and would not be charged while IPv4 address-2 is reserved but not being used. address-2 would be charged according to the unused IPv4 address pricing.

Disk pricing

All disk-related charges in this section are prorated based on a granularity of seconds. This includes both types of persistent disk types, snapshot storage, and local SSD pricing.

For example, based off US pricing, a 200 GB standard persistent disk volume would cost $8.00 for the whole month. If you only provisioned a 200 GB volume for half a month, it would cost $4.00. Likewise, a 200 GB SSD persistent disk volume would cost $34.00 for the whole month. If you only provisioned a 200 GB volume for half a month, it would cost $17.00.

Persistent disk pricing

Persistent disks are charged for the amount of provisioned space per disk. Persistent disk I/O operations are included in the charges for provisioned space and persistent disk performance grows linearly to the size of the persistent disk volume, so you might want to create a larger or smaller persistent disk to account for your I/O needs. For more information, see the persistent disk specifications.

After you successfully delete a persistent disk, you will no longer be charged for that disk.

Type	Price (per GB / month)
Standard provisioned space
SSD provisioned space
Regional standard provisioned space
Regional SSD provisioned space (Beta Promo)
Snapshot storage
IO operations	No additional charge

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Persistent disk snapshots

All snapshots that exist in your project incur monthly storage fees. Whenever you create or restore a snapshot, you might also incur network fees based on the snapshot's storage location.

Storage charges for snapshots

A snapshot incurs monthly storage charges as long as it exists in your project. Persistent disk snapshots only incur charges for the total size of the snapshot. For example, if you only used 2TB of disk space on a 5TB persistent disk, your snapshot size will be charged for 2TB, rather than the full 5TB of provisioned disk space. Compute Engine also provides incremental snapshots, which means that after the initial snapshot, subsequent snapshots only contain data that has changed since the previous snapshot, providing for a generally lower cost for snapshot storage. When you delete a complete or incremental snapshot, some of its data may move to the next incremental snapshot in the snapshot chain. This additional data increases the storage cost because you are using more space in the storage system.

Note that snapshot storage charges, like disk-related charges, are prorated based on a granularity of seconds.

Network charges for snapshot creation and restoration

Network charges for snapshot creation and restoration will follow standard Cloud Storage network pricing, but will be billed under Compute Engine.

A persistent disk can be stored in a Compute Engine zone or region, but a snapshot is stored in a Cloud Storage region or multi-region. Note that Compute Engine regions and Cloud Storage regions have similar names. Each multi-region contains multiple regions, and each region contains multiple zones. For example, the zone europe-north1-a is part of the europe-north1 region, and europe-north1 is part of the eu multi-region.

If you create or restore a snapshot that is stored in a location that is different from the location of your disk, the data travels over the network between those locations and may incur network fees. Snapshots incur the same fees as Cloud Storage egress.

For example, if your disk is located in the us-central1 region, and you want to create a snapshot in europe-west1, you will incur a cross-regional network charge.

Local SSD pricing

Local SSD devices are charged for the amount of provisioned space per device for the lifetime of the instance it is attached to. The prices for local SSDs differ depending on the region. For example, in the Iowa, Oregon, Taiwan, and Belgium regions, local SSDs cost $0.080 per GB per month. As mentioned earlier, local SSD charges are prorated to a granularity of seconds.

Since local SSDs can only be purchased in 375 GB increments, the cost per month for a single device is the monthly rate multiplied by 375 GB. For example, at a monthly rate of $0.080, the cost would be $30.00 per device per month. Actual data storage and usage are included in that price and there is no additional charge for local traffic between the virtual machine and the local SSD device.

Type	Price (per GB / month)	Preemptible price (per GB / month)	Estimated cost per device*
Local SSD provisioned space

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Image storage

Type	Price
Image Storage (per GB / month)

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Simulated maintenance event pricing

Running simulated maintenance events incurs the following charges:

• Simulated maintenance on instances configured for live migration incur costs for each of the following instance resources:
  • Price per vCPU on the instance, where f1-micro and g1-small are each equivalent to 1 vCPU: $0.040
  • Price per GB of memory: $0.010
  • Price per GB of local SSD space: $0.001
• Simulated maintenance on preemptible VM instances: Free
• Simulated maintenance on instances configured to terminate and restart: Free

Viewing usage

The Google Cloud Platform Console provides a transaction history for each of your projects. This history describes your current balance and estimated resource usage for that particular project.

To view a project's transaction history, go to the estimated billing invoice page.

Pricing calculator

To help you understand how your bill is calculated, use the Google Cloud Pricing Calculator.

What's next?

• Refer to the Pricing Overview documentation.
• Try the Pricing Calculator.
• Learn more about Compute Engine storage options.
• Learn more about Compute Engine machine types.
• Learn more about Compute Engine operating Systems.
• Learn more about Compute Engine IP addresses.
• Learn more about Compute Engine load balancing.