Quick answer
Google Cloud Functions documents maximum function memory as 1st gen: 8 GiB; 2nd gen: 32 GiB. Project and regional quotas also govern aggregate memory use.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| maximum function memoryProject and regional quotas also govern aggregate memory use. | 1st gen: 8 GiB; 2nd gen: 32 GiB | Generation specific | Google CloudAug 22, 2026 |
Why does this limit matter?
A generation migration can change the selectable per-function memory range and scaling behavior.
This value is scoped to Generation specific; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Read the deployed generation, memory setting, instance count, and regional quota.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- The default allocation is much lower than the maximum.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related