Should I upgrade to Cloudflare Workers Free Tier 100K Requests/Day and 10ms CPU Limit now?
Workers free plan caps at 100K requests/day and 10ms CPU time per invocation. Paid plan ($5/month minimum) raises the per-invocation CPU default to 30 seconds (configurable up to 5 minutes) and adds 10M requests/month. Teams hitting the free tier ceiling must decide whether to upgrade to Workers Paid or reconsider their edge architecture.
Blockers
- Lock-in via capability/workers-free-100k-requests-day
- Lock-in via capability/workers-free-10ms-cpu-invocation
- Lock-in via capability/workers-paid-30s-default-cpu
- Lock-in via capability/workers-paid-5min-max-cpu
- Lock-in via capability/workers-paid-10m-requests-month
Who this is for
- serverless
- cost-sensitive
- high-scale
- low-ops
- small-team
Candidates
Cloudflare Workers Free Plan
The Workers Free plan provides 100,000 requests/day and 10ms CPU time per invocation at no cost, as of 2026-03-18. Worker bundle size is capped at 3 MB compressed, with 50 subrequests per request, 100 Workers per account, and 5 Cron Triggers per account. The decisive differentiator is the 10ms CPU hard cap — it cannot be configured higher and rules out any workload involving JSON parsing of large payloads, cryptographic operations, or multi-step data transformation.
When to choose
Best for serverless + small-team projects where traffic stays well under 100K daily requests and logic is genuinely thin — a simple header injection, geolocation redirect, or static asset rewrite. The single most decisive factor is whether 10ms of CPU time is sufficient; anything involving database calls, auth token validation, or non-trivial payload processing will exceed the cap.
Tradeoffs
Pros: zero cost, no credit card required, instant global deploy, Workers KV reads (100K/day), D1 row reads (5M/day), and Durable Objects requests (100K/day) all included. Cons: 10ms CPU per invocation is a hard ceiling with no configuration path; 100K requests/day resets daily with no grace period or overflow billing; 3 MB compressed bundle limits dependency inclusion; 50 subrequests per request caps fan-out patterns; 5 Cron Triggers per account.
Cautions
The 10ms limit is CPU time, not wall-clock time — network I/O via fetch() does not count, but JSON.parse() on a moderate payload or a synchronous crypto operation can exhaust the budget instantly. When the 100K daily request cap is hit, Workers return HTTP 429 for the remainder of the calendar day with no burst allowance or paid overflow option on the free plan.
Cloudflare Workers Paid Plan
The Workers Paid plan starts at $5/month minimum and includes 10 million requests/month and 30 million CPU milliseconds/month, with overages at $0.30/million requests and $0.02/million CPU milliseconds, as of 2026-03-18. CPU time per invocation defaults to 30 seconds and is configurable up to 5 minutes per request, removing the free-tier 10ms bottleneck entirely. The decisive differentiator is the 3,000× increase in per-invocation CPU budget, enabling real-world workloads including database queries, auth flows, and data transformation.
When to choose
Best for serverless + high-scale or cost-sensitive production workloads where any single invocation performs non-trivial computation, traffic regularly bursts above 100K requests/day, or the Worker bundle exceeds 3 MB compressed. The single most decisive factor is CPU budget per request — if any invocation requires more than 10ms of CPU, the paid plan is the only Cloudflare Workers path forward.
Tradeoffs
Pros: 30-second default CPU per invocation (configurable to 5 minutes), 10M requests/month included, 10 MB compressed bundle limit, 500 Workers per account, 10,000 subrequests per request, 250 Cron Triggers per account, no daily request ceiling. Cons: $5/month minimum even for low-traffic production workloads; CPU millisecond overage at $0.02/million can accumulate rapidly for compute-heavy Workers; subrequests beyond 1,000 require enabling the higher limit explicitly.
Cautions
Monthly CPU millisecond billing is account-wide — a single compute-heavy Worker can exhaust the 30M included CPU ms allowance before request volume alone would suggest it, leading to unexpected overage charges. Both free and paid tiers share a 128 MB memory per isolate limit and 16 KB URL size limit that cannot be configured higher regardless of plan.
Try with your AI agent
$ npm install -g pocketlantern $ pocketlantern init # Restart Claude Code, Cursor, or your MCP client, then ask: # "Should I upgrade to Cloudflare Workers Free Tier 100K Requests/Day and 10ms CPU Limit now?"