Quick answer
Cloudflare Workers documents maximum request body as Plan dependent. Workers plan CPU and Cloudflare account request-body limits are separate products scopes.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| maximum request bodyWorkers plan CPU and Cloudflare account request-body limits are separate products scopes. | Plan dependent | Cloudflare account plan | CloudflareAug 22, 2026 |
Why does this limit matter?
Upgrading Workers compute alone may not change the zone account's upload ceiling.
This value is scoped to Cloudflare account plan; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Confirm the zone account plan and inspect Content-Length before Worker processing.
- 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
- Response bodies and streamed responses follow different rules.
- 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