Paste a line item from your invoice and find what it bills for, across the Google Cloud services covered so far.
Instance Core running
The vCPU half of a virtual machine.
Google bills CPU and memory as separate SKUs, which is why a single VM appears as several lines on your bill and why per-instance costs are not directly visible without joining them back together.
Billed: Per vCPU-hour, priced per machine family and region. RAM is billed as a separate SKU.
What triggers this charge
- Every second a VM is in the RUNNING state, whether or not it is doing anything, with a one-minute minimum each time it starts.
- Reservations, which bill their vCPUs at standard rates from creation to deletion, whether or not a VM is using them.
- Machine family and region, both of which change the rate materially.
- GKE Standard nodes, Dataproc cluster workers, and managed instance groups, all of which are Compute Engine VMs underneath and bill through this SKU. GKE Autopilot pods and serverless products bill under their own SKUs instead.
How to reduce it
Count the sustained use discount you already get
On a self-serve (online) billing account, N1, N2, N2D, C2, M1 and M2 vCPUs and memory used for more than a quarter of the month earn a sustained use discount automatically. It grows with usage, to 30% for a full month on N1, M1 and M2 and 20% on N2, N2D and C2. Other series, E2 and N4 among them, get none, and only self-serve accounts are eligible. It shows on the bill as a separate credit.
Buy committed use discounts for the steady baseline
One- and three-year commitments are substantially cheaper than on-demand and apply automatically to matching usage. Covered usage gives up its sustained use discount, so measure the saving against that, not list price: the GCP Sustained & Committed Use Discount Calculator does. Size them to the floor of your usage, not the average.
Use Spot VMs for interruptible work
Batch jobs, CI runners, and stateless workers survive preemption fine and attract a much lower rate. The Spot SKU is a separate line, so the saving is visible in the bill.
Stop non-production instances out of hours
A dev VM running nights and weekends is idle about 70% of the time. Scheduled stop/start removes most of that with no capacity risk.
Right-size before you commit
Committing to oversized instances locks in the waste for years. Check utilization first.
Rates
For a dated list price, use the GCP Sustained & Committed Use Discount Calculator (prices verified 1 Nov 2026).
Sources and review
- Explanation reviewed:
- 1 Nov 2026, against VM instance pricing and the sustained use discounts docs.
- Rates verified:
- not yet. No rate is shown on this page until one is loaded from the Cloud Billing Catalog API.
Related charges
Now find out how much of this you are actually paying.
Finitizer breaks your Google Cloud bill down to the SKU, shows how each one has moved since last week, and separates rate changes from usage changes, so you know whether to talk to engineering or to procurement.
See how Finitizer works