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 230 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 Console.
- Estimate your total project costs with the Google Cloud Pricing Calculator.
- View and download prices from the Pricing Table in the Cloud Console.
- Use the Cloud Billing Catalog API for programmatic access to SKU information.
Certain images available on Compute Engine are considered premium images and incur charges to use. These images include:
- Red Hat Enterprise Linux (RHEL and RHEL for SAP)
- SUSE Linux Enterprise Server (SLES and SLES for SAP)
- Windows Server
- SQL Server
The price for a premium image depends on which machine type
you use. For example, a standard SLES 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 for using an
n1-standard-8 instance with an SLES image is the sum of the machine
type cost and the image cost:
n1-standard-8 cost + SLES image cost =
$0.379998 + $0.11 = $0.49 per hour
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
- $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.
SLES and SLES for SAP images
- $0.02 USD/hour for
- $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.023 USD/hour for
- $0.046 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,
machine-types with 4 vCPUs, and are charged at $0.184 USD/hour (4 x $0.046
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 not use SQL Server images on
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.
Each VM instance has at least one disk attached to it. Each disk incurs a cost, described in this section. In addition, if you use snapshots, there are separate snapshot charges.
All disk-related charges in this section are prorated based on a granularity of seconds. This includes all 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.
Provisioned disk space includes all used and unused space. If you provision a 200 GB disk, you are billed for that entire disk space, regardless of how you use it, until you relinquish it.
Persistent disk pricing
Persistent disks are priced by 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 by 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 are no longer charged for that disk.
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 storage location of the snapshot.
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 2 TB of disk space on a 5 TB persistent disk, your snapshot size is charged for 2 TB, rather than the full 5 TB of provisioned disk space. Compute Engine also provides incremental snapshots, which contain only the 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 follow standard Cloud Storage network pricing, but are billed under Compute Engine.
A persistent disk can be stored in a
Compute Engine zone or region, but a
snapshot is stored in either 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
europe-north1 region, and
europe-north1 is part of the
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
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.
Because 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.
You can reserve local SSDs in a specific zone, with or without a commitment. Without a commitment, you pay normal on-demand prices, including sustained-use discounts. For committed-use discounted pricing for local SSDs, a reservation must be created when purchasing the commitment. For more information, see Reserving zonal resources.
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.
The cost of using a machine image depends on the size of the machine image, and the location where it is stored.
There is also a one time network transfer fee if you are storing a machine image in a different location than the source instance, or if you create an instance from a machine image that is stored in a different location from the instance.