All pricing

This page lists all the pricing for Compute Engine.

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 U.S. dollars (USD).

For Compute Engine, 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 Platform Pricing Calculator.

General-purpose machine types

N1 machine types

N1 standard machine types

N1 high-memory machine types

N1 high-CPU machine types

N1 custom vCPUs and memory

N1 extended custom memory

N2 machine types

N2 standard machine types

N2 high-memory machine types

N2 high-CPU machine types

N2 custom vCPUs and memory

N2 extended custom memory

Memory-optimized machine types

vCPUs and memory

M1 memory-optimized machine types

M2 memory-optimized machine types

Compute-optimized machine types

C2 vCPUs and memory

C2 machine types

Shared-core machine types

Premium images

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

SLES 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 SLES images are charged a 1 minute minimum. After 1 minute, SLES 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 a custom machine type 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.

Disk pricing

Persistent disk pricing

Local SSD pricing

Custom image storage

If you import or create custom images in Compute Engine, these images incur a storage cost. The cost of these custom images depends on the location where you store the image.

Network pricing

General network pricing

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

Internet egress rates^*

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).

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 are charged $0.025/hour. If you have 3 forwarding rules, you are still charged $0.025/hour. However, if you have 10 rules, you are 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 Google Cloud Armor charges

If a backend service has a Google 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 Google 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

Network logs generate charges. You are charged for the following products:

• VPC flow logs
• firewall rule logs
• NAT logging (starting at NAT logging GA. No charge for logs generation during beta.)

Traffic through external IP addresses

When you send traffic between virtual machines through the external IP addresses, it is 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 U.S. regions, are charged at Internet egress rates.

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 can't determine the zone of a virtual machine through the external IP address.

External IP address pricing

If you reserve a static external IP address but do not use it, you'll 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 won't be charged for it.

VPN

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

For definitions of Classic VPN and HA VPN, see the Cloud VPN overview.

Classic VPN pricing

Select the location of the VPN gateway in Google Cloud Platform to view pricing.

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

HA VPN pricing at Beta

The pricing below applies during the HA VPN Beta period.

Cloud Router pricing

See the Cloud Router pricing page.

Sole-tenant vCPU, memory, and premium costs

Calculating sole-tenancy pricing including discounts

GPU pricing