Google Compute Engine Pricing

This page describes the pricing information for Compute Engine. To see the pricing for other products, read the Pricing details 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 230 bytes. This unit of measurement is also known as a gibibyte (GiB).

When charging in local currency, Google will convert the prices listed into applicable local currency pursuant to the conversion rates published by leading financial institutions.

You can also find pricing information with the following options:

Machine type pricing

Google Compute Engine offers two categories of machine types: predefined machine types and custom machine types. Predefined machine types have preset virtualized hardware properties and a set price, while custom machine types are priced according to the number of vCPUs and memory that the virtual machine instance uses.

Machine type billing model

The following billing model applies to all machine types, predefined or custom.

  1. All machine types are charged a minimum of 10 minutes. For example, if you run your virtual machine for 2 minutes, you will be billed for 10 minutes of usage.

  2. After 10 minutes, instances are charged in 1 minute increments, rounded up to the nearest minute. An instance that lives for 11.25 minutes will be charged for 12 minutes of usage.

Predefined machine types

Google Compute Engine currently offers the following predefined machine types in the US, Europe, and Asia. Compute Engine also provides automatic discounts off these prices for sustained use. You can also use our Google Cloud Pricing Calculator to better understand price for different configurations.

Standard machine types

US Europe Asia (Taiwan) Asia (Japan)
Monthly
Hourly
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-321
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.

Shared-core machine types

Shared-core machine types are ideal for applications that don't require a lot of resources. Shared-core machine types are more cost-effective for running small, non-resource intensive applications than standard, high-memory or high-CPU 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.

US Europe Asia (Taiwan) Asia (Japan)
Monthly
Hourly
Machine type Virtual CPUs Memory Price (USD) Preemptible price (USD)
f1-micro 0.2
g1-small 0.5

High-memory machine types

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

US Europe Asia (Taiwan) Asia (Japan)
Monthly
Hourly
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-321 32 208GB
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.

High-CPU machine types

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

US Europe Asia (Taiwan) Asia (Japan)
Monthly
Hourly
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-321 32 28.80GB
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.

Custom machine types

Create a custom machine type with a specific number of vCPUs and amount of memory if predefined machine types are not optimal for your workloads. Custom machine types also save you the cost of running on a larger, more expensive machine type if you don't need to use all the resources of that machine type.

For example, instead of using an n1-standard-8 machine type when you just need a machine type with 6 vCPUs, create a custom machine type instance with 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. The rates for custom machine types are as follows.

US Europe Asia (Taiwan) Asia (Japan)
Monthly
Hourly
Item Price (USD) Preemptible price (USD)
vCPU
Memory

1  32-core machine type availability: 32-core machine types are not available in Sandy Bridge zones us-central1-a and europe-west1-b.

Sustained use discounts

If you run an instance for a significant portion of the billing month, you can qualify for a sustained use discount. When you use an instance for more than 25% of a month, Compute Engine automatically gives you a discount for every incremental minute you use for that instance. The discount increases with usage and you can get up to a 30% net discount for instances that run the entire month. Sustained use discounts are calculated and applied to your bill as your project earns them.

The table below describes the discount at each usage level. These discounts apply for all machine types, but do not apply to preemptible instances.

Usage Level (% of month) % at which incremental is charged Example incremental rate (USD/hour) for an n1-standard-1 instance
0%-25% 100% of base rate $0.050
25%-50% 80% of base rate $0.040
50%-75% 60% of base rate $0.030
75%-100% 40% of base rate $0.020

Sustained use discounts are given on incremental use after certain usage thresholds are reached. This means that you pay only for the number of minutes that you use an instance, and Compute Engine automatically gives you the best price. There’s no reason to run an instance for longer than you need it.

The following graph demonstrates how your effective discount increases with use.

Click to enlarge

For example, if you use a virtual machine for 50% of the month, you get an effective discount of 10%. If you use it for 75% of the month, you get an effective discount of 20%. If you use it for 100% of the month, you get an effective discount of 30%. You can also use the Google Cloud Pricing Calculator to estimate your sustained use discount for any arbitrary workload.

Sustained use discounts for predefined machine types

When Compute Engine calculates use for predefined machine types, equivalently provisioned machines that run non-concurrently are treated as inferred instances. This gives you the flexibility to start and stop instances freely and still receive the maximum sustained use discount that is available across all of your instances.

For example, if you run an n1-standard-1 instance for 75% of the month, your charges are calculated as follows:

  • The first 25% is charged at the full on-demand rate.
  • The next 25% is charged at a 20% discount off the on-demand rate.
  • The last 25% is charged at a 40% discount off the on-demand rate.

For this example, sustained use discounts resulted in a net discount of 20% for this instance. The table below demonstrates this example, based on US pricing:

Usage level (% of month) for an n1-standard-1 instance % of base rate usage charge Example rate (USD/hour) Calculated charges, assuming 30-day month
First 0-25% of usage 100% $0.050 (base rate)
  • 30 days x .25 = 7.5 days
  • 7.5 days x 24 hours = 180 hours
  • 180 hours x $0.050 USD/hour = $9.00
Usage between 25%-50% of the month 80% $0.040
  • 180 hours x $0.040 USD/hour = $7.20
Usage between 50%-75% of the month 60% $0.030
  • 180 hours x $0.030 USD/hour = $5.40

The total charge for this instance is $9.00 + $7.20 + $5.40 = $21.60.

This charge will appear on your bill at the end of the billing cycle. Without sustained use discounts, the same n1-standard-1 instance running for the same amount of time would cost 20% more:

  • 30 days per month x .75 = 22.5 days
  • 22.5 days x 24 hours per day = 540 hours
  • 540 hours x $0.050/USD hour = $27.00
Inferred instances

When computing sustained use discounts for predefined machine types, Compute Engine gives you the maximum available discount using inferred instances. An inferred instance combines multiple, non-overlapping instances in the same zone into a single instance for billing. With inferred usage, you are more likely to qualify for sustained use discounts. Non-overlapping instances running the same predefined machine type in the same zone are combined to create one or more inferred instances.

The example below shows a customer's usage that comprises five distinct instances. The instances are combined to find the smallest number of simultaneous running instances, which are called "inferred instances". In this example, Compute Engine combines the instances to make three inferred instances with the longest possible duration. Compute Engine then calculates sustained use discounts based on the percentage of time that each of these inferred instances were running.

inferred instance diagram

Sustained use discounts for custom machine types

For custom machine types, Compute Engine calculates sustained use discounts based on vCPU and memory usage, and applies the discounts described by the sustained usage discount table. Compute Engine uses your custom machine types to combine your usage into the longest possible duration of resources.

For example, consider a scenario where you have two instances that have different shapes and run at different times of the month. Compute Engine breaks down the number of vCPUs and amount of memory used across all custom instances and combines resources to qualify for the biggest sustained usage discounts possible:

Diagram for sustained use
  discounts for custom machine types

In this case, Compute Engine applies the following sustained use discounts:

  • You would receive a 30% discount off the cost of using 2 vCPUS and a 30% discount off the cost of using 4 GB of memory because you used each resource for the whole month.
  • You would receive a 10% discount off the cost of using 2 vCPUs and a 10% discount off the cost of 2 GB of memory because you used each resource for half of the month.

On your bill, you will see two line items, one for the total sustained use discount for CPUs and one for total sustained use discount for memory usage. To calculate the cost of running 2 vCPUs for 75% of the month:

  • 2 vCPUs ($0.034 * 2) = $0.068 per hour (full price)
  • First 25% of the usage is charged at full price: $0.068 * 180 = $12.24
  • Second 25% of the usage is charged 80% of the full rate: ($0.068 * .8) * 180 = $9.79
  • Last 25% of usage is charged at 60% of the full rate: ($0.068 * .6) * 180 = $7.34
  • Total: $12.24 + $9.79 + $7.34 = $29.74

Without sustained use discounts, the same 2 vCPUs would cost $36.72, which is 20% more expensive than the price with sustained use discounts.

Viewing sustained use discounts

Sustained use discounts will automatically appear on your bill at the end of the billing cycle as separate line items that are credited to your account. You can view this discount in the Google Cloud Platform Console billing history. These discounts will appear as credits, with "Sustained Use" in the description. For example, the billing history might look like the following for an n1-standard-1 instance with sustained use discounts:

Date Description Debits ($) Credits ($)
Mar 1 - Mar 31 Google Compute Standard Intel N1 1 VCPU running in NA: 13567 Minutes (Project:1234567895) $11.30
Mar 1 - Mar 31 Google Compute Standard Intel N1 1 VCPU running in NA Sustained Use Discount: 3381 Minutes (Project:1234567895) $2.81

Instance uptime

Instance uptime is measured as the number of minutes 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.

Instance uptime is rounded up to the nearest minute. For example, if you run two separate n1-standard-1 virtual instances for 14.5 minutes each, you will be billed for 15 minutes per instance, at the n1-standard-1 machine type pricing.

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

Premium images

The price for a premium image is different depending on which machine type you use. For example, a 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.400 + $0.11 = $0.51 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) images

  • $0.06 USD/hour for machine types with 4 or fewer virtual CPUs
  • $0.13 USD/hour for machine types with more than 4 virtual CPUs

All RHEL images are charged a 1 hour minimum. After 1 hour, RHEL images are charged by 1 hour increments, rounded up to the nearest hour. For example, if you run a RHEL image for 45 minutes, you will be billed for an hour. If you run an RHEL image for 63 minutes, you will be billed for 2 hours.

SUSE images

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

All SUSE images are charged a 10 minute minimum. After 10 minutes, SUSE images are charged by 1 minute increments, rounded up to the nearest minute.

Windows Server images

  • $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 4-core machines, and are charged at $0.16 USD/hour (4 x $0.04 USD/hour).

All Windows images are charged a 10 minute minimum. After 10 minutes, Windows images are charged by 1 minute increments, rounded up to the nearest minute.

SQL Server images

SQL Server images incur costs in addition to the base cost for normal Windows Server images.

  • $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 applied to each virtual CPU on your virtual machine instance with a four core minimum for each instance. For example, on instances with fewer than 4 vCPUs, Compute Engine charges for SQL Server at 4 x $0.1645 USD/hour ($0.658 USD/hour).

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 receive a 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.

All SQL Server images are charged a 10 minute minimum. After 10 minutes, SQL Server images are charged by 1 minute increments, rounded up to the nearest minute.

Network pricing

General network pricing

Traffic type Price
Ingress No charge
Egress* to the same zone No charge
Egress to a different Google Cloud Platform service within the same region No charge
Egress to Google products (such as YouTube, Maps, Drive) No charge**
Egress* between zones in the same region (per GB) $0.01
Egress between regions within the US (per GB) $0.01
Inter-continental Egress At Internet egress rates
*These charges are for egress through internal IP addresses. There are different charges for egress through external IP addresses, regardless of whether the instances are in the same zone. The prices are used regardless of network or subnet. The price for traffic within a zone using internal IP addresses is the same even if the traffic is to a different subnet or network. The price on traffic between zones in the same region is the same if the two instances are in the same subnet, different subnets, or different networks. Pricing is the same whether the instances are in a subnet mode network or a legacy network.
**Promotional pricing

Internet egress rates*

US Europe Asia (Taiwan) Asia (Japan)
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

*These rates do not apply for Cloud CDN, CDN Interconnect, Cloud Interconnect, or Direct Peering traffic. Instead, see pricing for Cloud CDN, CDN Interconnect, Cloud Interconnect, or Direct Peering.

Load balancing and protocol forwarding

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

US Europe Asia (Taiwan) Asia (Japan)
Item Price per Unit (USD) Pricing Unit
First 5 forwarding rules Per Hour
Per additional forwarding rule Per Hour
Data processed Per GB

Compute Engine charges for forwarding rules that are created for load balancing or protocol forwarding. A load balancing rule is a forwarding rule that is used to load balance a pool of instances and a protocol forwarding rule is a forwarding rule that is used to route packets of selective protocols to a single instance.

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

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 continents 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

US Europe Asia (Taiwan) Asia (Japan)
Component Billed Price (USD)
Per tunnel (per hour)
IPsec traffic Encrypted traffic (base traffic plus IPsec overhead) has the same rates as regular traffic. See General network pricing.
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.

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.

US Europe Asia (Taiwan) Asia (Japan)
Type Price (per GB / month)
Standard provisioned space
SSD provisioned space
Snapshot storage
IO operations No additional charge

Persistent disk snapshots

Persistent disk snapshots are only charged 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 around 2TB, rather than the full 5TB of provisioned disk space. Google Compute Engine also provides differential 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.

Note that snapshot storage is also calculated based on a prorated rate.

Network charges for snapshot restoration

Standard network pricing applies to snapshot restore. For example, a snapshot restore across regions or continents incurs the same fees as Google Compute Engine egress. Addition of egress fees for restore will be delayed as a promotional offer until September 30, 2016.

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, at a rate of $0.218 per GB per month. As mentioned earlier, local SSD charges are prorated to a granularity of seconds.

Since local SSD can only be purchased in 375 GB increments, a single device costs approximately $81.75 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.

US Europe Asia (Taiwan) Asia (Japan)
Monthly
Hourly
Type Price (per GB / month) Estimated * cost per device
Local SSD provisioned space
*Based on a 730 hour month; actual monthly costs may vary.
Local SSD devices are only offered in one size, at 375 GB per device.

Image storage

US Europe Asia (Taiwan) Asia (Japan)
Type Price
Image Storage (per GB / month)

IP address pricing

US Europe Asia (Taiwan) Asia (Japan)
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

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?

Send feedback about...

Compute Engine Documentation