Quick answer
Google Cloud Run documents http/1 payload ceiling as 32 MiB request; 32 MiB non-streamed response. The request limit does not apply to HTTP/2 servers, and streaming changes response behavior.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| HTTP/1 payload ceilingThe request limit does not apply to HTTP/2 servers, and streaming changes response behavior. | 32 MiB request; 32 MiB non-streamed response | HTTP/1 services | Google CloudAug 22, 2026 |
Why does this limit matter?
Protocol and transfer mode can change whether a large payload is accepted.
This value is scoped to HTTP/1 services; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Confirm HTTP version, response streaming, Content-Length, and upstream gateway limits.
- 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
- Gateways, clients, frameworks, and memory can impose smaller effective limits.
- 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