Normalized comparison

Cloudflare Workers vs AWS Lambda Limits

Workers separates active CPU from wall time, while Lambda uses function timeout and memory allocation; compare workload shape, not one duration number.

Verified Aug 22, 2026Cloudflare WorkersAWS Lambda
Values are comparable only within the scope shown. Runtime, plan, model, invocation mode, and account-specific capacity can change the effective result.

Quick comparison

CriterionCloudflare WorkersAWS LambdaComparability note
Primary compute durationCloudflare Workers30 seconds default; up to 5 minutesWorkers PaidCloudflareAWS Lambda900 seconds (15 minutes)A function-level configuration ceiling; the configured timeout may be lower.Amazon Web ServicesActive CPU milliseconds and wall-clock invocation duration are fundamentally different.
MemoryCloudflare Workers128 MBFree and PaidCloudflareAWS Lambda128 MB to 10,240 MBPer functionAmazon Web ServicesWorkers memory is per isolate; Lambda memory is configured per function environment.

Which is best for your requirement?

Choose Cloudflare Workers when

Its documented primary compute duration scope fits your measured workload and the caveats shown in the comparison.

Choose AWS Lambda when

Its documented execution or account model better matches the exact requirement rather than a vendor-wide headline.

Validate before migration

Test payload, duration, throughput, concurrency, failure behavior, billing scope, and recovery with representative traffic.

Validate the decision with your workload

Before choosing between Cloudflare Workers and AWS Lambda, reproduce the comparison with the exact plans, models, regions, runtimes, and invocation paths you intend to operate. The reviewed rows cover primary compute duration and memory; they do not turn different pricing, reliability, developer experience, or ecosystem tradeoffs into one universal score.

  1. Capture representative request sizes, token usage, duration, concurrency, storage, and failure behavior at realistic percentiles.
  2. Test the boundary and the recovery path on both candidates, including throttling, timeouts, partial failure, retries, and cost controls.
  3. Record which scoped observation drove the choice and recheck its official source before migration or a major traffic increase.

Official sources

Related

Inspect the underlying limits