Z4M family · General Purposex86_64 · Intel/AMD

z4m-highmem-16

The z4m-highmem-16 machine type has 16 vCPUs and 122 GB of memory. Pricing for this instance starts at $3.29 per hour and $2399.59 monthly in the us-central1 region.

Updated November 21, 2026
vCPUs
16
Memory
122 GB
Network
Up to 32 Gbps
Storage
Local SSD

Save up to $1440/mo on every z4m-highmem-16

Connect Google Cloud — we'll find the optimal pricing model for your workload.

All pricing options

us-central1 · USD · monthly = 730 hrs
Prices exclude local taxes
Term / TierHourlyMonthlySavings
On-Demand
$3.2871$2399.59 Baseline
1-Year Committed Use Discount (CUD)
$2.2352$1631.72 -32%
3-Year Committed Use Discount (CUD)
$1.4463$1055.82 -56%
Preemptible / Spot
$1.3148$959.84 -60%
You could save $1439.75/mo on this instance with the right pricing model.
Find my savings

Monthly cost estimator

Estimate your spend based on actual usage.
730 h
1h365h730h (24/7)
1
Estimated monthly
$2399.59
730 hrs × $3.2871/hr × 1

Compute

x86_64 · Intel/AMD
vCPUs i16
Memory i122 GB
Physical processorIntel Emerald Rapids
Nested VirtualizationNot supported
Sole TenantNot supported
GPUNone
Within Z4M family
z4m-highmem-16
16 vCPU
z4m-highmem-32
32 vCPU
z4m-highmem-48
48 vCPU
z4m-highmem-192
192 vCPU
z4m-highmem-192-metal
192 vCPU

Lock in this rate across your fleet — typically save 30–40%

Connect your Google Cloud account to apply this pricing logic to every running instance automatically.

Networking

Max egress bandwidth32 Gbps
Tier 1 bandwidthN/A
Enhanced networking iYes (gvnic/virtio)
IPv6 supportYes (Dual-stack VPC)

Storage

Max persistent disks32
Max disk size257 TB
Local SSDsSupported (Scratch Disk)

Compare with another instance

vs.
Specz4m-highmem-16z4m-highmem-32Δ
vCPUs1632+100%
Memory122 GB244 GB+100%
Hourly Price$3.2871$6.5742+100%
Monthly Price$2399.59$4799.18+100%
Cost optimization

GCP recommender alerts can cut this bill ~30-40%.

Connect your GCP account. We'll identify every underutilized z4m.* instance and show exactly where downsizing, cleaning up orphaned disks, or shifting to CUDs saves money — with zero code changes.