Current documented 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 |
| CPU time per HTTP requestCPU time excludes waiting on network requests and other I/O. | 10 ms | Workers Free | CloudflareAug 22, 2026 |
| Configurable CPU time per HTTP requestThe maximum is configurable with limits.cpu_ms; wall-clock duration is a separate concept. | 30 seconds default; up to 5 minutes | Workers Paid | CloudflareAug 22, 2026 |
| Memory per isolateIncludes the JavaScript heap and WebAssembly allocations; one isolate can serve concurrent requests. | 128 MB | Free and Paid | CloudflareAug 22, 2026 |
| Worker requestsAccount plan limit shown in Cloudflare's Workers limits table. | 100,000 per day | Workers Free | CloudflareAug 22, 2026 |
How to apply Cloudflare Workers limits safely
The monitored baseline covers maximum request body, CPU time per HTTP request, Configurable CPU time per HTTP request, Memory per isolate, Worker requests. Treat these as separate constraints rather than one platform-wide capacity number: a workload can fit one row and still fail another because the plan, model, endpoint, runtime, region, invocation mode, or account scope differs.
- Match the production workload to the exact scope printed beside each value and confirm it in the active Cloudflare Workers console, configuration, or response headers.
- Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
- Check every adjacent layer—client, SDK, gateway, proxy, queue, database, and downstream service—for a smaller effective limit before changing architecture.
Specific limit pages
These pages exist because the constraint has a distinct implementation or troubleshooting intent. Closely related keyword variations stay consolidated.
Cloudflare Request Body Limits
Cloudflare Request Body Limits, verified against Cloudflare Workers's official documentation with scope, implementation impact, caveats, and a direct check.
Cloudflare Workers CPU time
Current Workers Free and Paid CPU-time limits, wall-time distinction, configuration, and exceeded-resource behavior.
Cloudflare Workers memory
The current Cloudflare Workers isolate memory limit, what it includes, concurrency caveats, and practical diagnostics.
Errors linked to these limits
Error 520 — web server returns an unknown error
Cloudflare Error 520: Web Server Returns Unknown Error: direct meaning, scoped diagnosis, corrective action, official source, and linked current limit.
Error 521 — web server is down
Cloudflare Error 521: Web Server Is Down: direct meaning, scoped diagnosis, corrective action, official source, and linked current limit.
Error 522 — connection timed out
Cloudflare Error 522: Connection Timed Out: direct meaning, scoped diagnosis, corrective action, official source, and linked current limit.
Error 524 — a timeout occurred
Diagnose Cloudflare 524 when the proxy connects to the origin but the origin does not return a response within the read-timeout window.
Compare alternatives
Cloudflare Workers vs AWS Lambda Limits
Cloudflare Workers vs AWS Lambda Limits using the same verified structured observations as each underlying limit page, with scope and comparability caveats.
Netlify vs Cloudflare Workers Limits
Netlify vs Cloudflare Workers Limits using the same verified structured observations as each underlying limit page, with scope and comparability caveats.
Vercel vs Cloudflare Workers
Compare current function duration, CPU, memory, and payload constraints without treating unlike execution models as identical.