Z4M family · General Purposex86_64 · Intel/AMD

z4m-highmem-48

The z4m-highmem-48 machine type has 48 vCPUs and 366 GB of memory. Pricing for this instance starts at $9.86 per hour and $7198.77 monthly in the us-central1 region.

Updated November 21, 2026
vCPUs
48
Memory
366 GB
Network
Up to 100 Gbps
Storage
Local SSD

Save up to $4319/mo on every z4m-highmem-48

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
$9.8613$7198.77 Baseline
1-Year Committed Use Discount (CUD)
$6.7057$4895.15 -32%
3-Year Committed Use Discount (CUD)
$4.3390$3167.45 -56%
Preemptible / Spot
$3.9445$2879.51 -60%
You could save $4319.26/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
$7198.77
730 hrs × $9.8613/hr × 1

Compute

x86_64 · Intel/AMD
vCPUs i48
Memory i366 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 bandwidth100 Gbps
Tier 1 bandwidthN/A
Enhanced networking iYes (gvnic/virtio)
IPv6 supportYes (Dual-stack VPC)

Storage

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

Compare with another instance

vs.
Specz4m-highmem-48z4m-highmem-16Δ
vCPUs4816-67%
Memory366 GB122 GB-67%
Hourly Price$9.8613$3.2871-67%
Monthly Price$7198.77$2399.59-67%
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.