Hosting Radar
Cloudflare Workers pricing: how much does it cost in 2026?
Cloudflare Workers pricing starts at $0 for the Free plan, which covers 100,000 requests per day, and $5 per month on the Paid plan, which includes 10 million requests and 30 million CPU milliseconds as of October 2026. Anything beyond those allotments bills per million.
What matters
- The Workers Free plan gives 100,000 requests per day with 10 ms of CPU time per invocation, and Cloudflare charges nothing for duration.
- The Workers Paid plan carries a $5 per month minimum per account and bundles 10 million requests and 30 million CPU milliseconds; overage is $0.30 per additional million requests and $0.02 per additional million CPU ms.
- Workers bills requests and CPU time on separate meters, so a high-traffic, light-logic Worker is far cheaper than a low-traffic one doing heavy computation.
- Cloudflare's October 2026 acquisition of Deno puts Deno Deploy on a six-month clock before shutdown, with migration support for paying customers moving to Workers.
What is Cloudflare Workers?
Cloudflare Workers is a serverless computing platform that runs JavaScript, TypeScript, and WebAssembly on Cloudflare's edge network instead of on a server you manage. You deploy a Worker, and Cloudflare routes requests to its nearest data center, so there is no origin server to patch and no idle capacity to pay for. The trade-off is a sandboxed isolate runtime rather than a full virtual machine, which shapes both the pricing model and the limits below.
Per Cloudflare's official pricing page, Workers is billed on two axes: requests and CPU time. That split is the whole game, because the two are metered separately and at very different rates.
Cloudflare Workers pricing tiers: Free vs Paid
Cloudflare offers two self-serve tiers. The Workers Free plan costs nothing and caps you at 100,000 requests per day with 10 milliseconds of CPU time per invocation. Cloudflare states there is no charge for duration on the free tier: you are limited, not billed.
The Workers Paid plan is where the usage math starts. It carries a $5 USD per month minimum per account and bundles an initial allotment of 10 million requests and 30 million CPU milliseconds. Beyond that, Cloudflare charges $0.30 for each additional million requests and $0.02 for each additional million CPU milliseconds.
How the Cloudflare Workers bill is actually calculated
Cloudflare's own worked example makes the split concrete. A project serving 15 million requests per month, at roughly 7 ms of CPU time per request, pays $5.00 in subscription, $1.50 in request overage (5 million requests past the 10 million included, at $0.30 per million), and $1.50 in CPU overage. Total: $8.00 per month.
Two things follow. Request pricing is cheap enough that a Worker serving tens of millions of requests still lands in single-digit dollars. CPU time is the variable that bites: a Worker doing heavy computation on fewer requests can cost more than a high-traffic Worker doing almost nothing. If your Workers resize images, transform large JSON payloads, or run cryptography at scale, budget CPU milliseconds, not requests.
The $5 minimum also covers Workers KV, Hyperdrive, and Durable Objects usage, each with its own allotment and overage rate layered on top of the base request and CPU meters. R2 object storage is metered separately on storage volume plus two operation classes (Class A and Class B), and Cloudflare charges no egress bandwidth on R2. Those secondary meters rarely dominate a small bill, but a cache-heavy Worker leaning on KV reads or Durable Objects can outspend its request pricing several times over.
What Cloudflare's Deno acquisition changes for Workers buyers
In October 2026, Deno announced it is joining Cloudflare. The announcement spells out a short timeline for existing customers. Deno says it will support the Deno runtime for another year with monthly bug-fix and security releases, after which Cloudflare ends development of the runtime. Deno Deploy, the managed hosting product that competed most directly with Workers, "will continue operating for six months before shutting down," and Cloudflare will provide migration support for paying Deno Deploy customers moving to Workers.
For a buyer, that turns a comparison into a migration. Deno Deploy's paid tiers are now on a countdown rather than a roadmap, and only JSR, Deno's package registry, explicitly continues, with its infrastructure moving to Cloudflare. If you picked Deno Deploy for its pricing, the honest read is that Workers is the destination.
Cloudflare Workers vs Deno Deploy vs Vercel: what each costs
With Deno Deploy leaving, the realistic comparison is Workers against Vercel or a plain VPS. Workers and Deno Deploy share the same shape: a free tier anchored to request allowances, then paid tiers that meter overage in dollars per million requests.
Deno Deploy's free plan allows 1 million requests per month, with Pro at $20 per month and Builder at $200 per month. Vercel is a different animal: Hobby is free and Pro is $20 per month with $20 of included usage credit, but it targets full-stack framework deploys such as Next.js rather than isolated edge functions. If your workload is a handful of API endpoints and scheduled tasks, Workers' $5 minimum is the cheaper paid starting point; if it is a full framework app with build pipelines and image optimization, Vercel's bundled credit can net out lower.
For steady, compute-heavy workloads that do not need edge latency, a cheap VPS still undercuts per-request edge pricing at high volume, at the cost of managing the machine yourself.
Who should use Cloudflare Workers, and who shouldn't
The Free plan is a genuine fit for personal projects, prototypes, low-traffic APIs, and internal tools that stay under 100,000 requests a day. The 10 ms CPU ceiling is comfortable for routing, auth checks, and light JSON work.
The Paid plan suits production APIs and full-stack apps that need Durable Objects, more subrequests, or headroom past the daily cap. It is a poor fit for long-running background jobs, heavy media processing, or anything needing a persistent, stateful process: Workers is designed for short, stateless request handling, and the 5-minute CPU ceiling on Paid reflects that.
Limits to check before you commit
- Free plan: 100,000 requests per day, 10 ms CPU per invocation, 128 MB memory, 50 subrequests per request, 64 environment variables per Worker.
- Paid plan: no request limit, but a 5-minute CPU cap per invocation, 128 MB memory, 10,000 subrequests per request, and 128 environment variables per Worker.
- No renewal cliff: Cloudflare's page shows a flat $5 per month minimum rather than a first-year promotional rate, so the number you sign up at is the number you keep paying.
At a glance
| Workers Free | Workers Paid | |
|---|---|---|
| Monthly cost | $0 | $5 minimum per account |
| Requests included | 100,000 per day | 10 million per month |
| Request overage | None (hard daily cap) | $0.30 per additional million |
| CPU time | 10 ms per invocation | 30 million CPU ms per month |
| CPU overage | Not billed (capped) | $0.02 per additional million CPU ms |
| Memory / subrequests | 128 MB / 50 per request | 128 MB / 10,000 per request |
| Environment variables | 64 per Worker | 128 per Worker |
FAQ
Is Cloudflare Workers free?
Yes, up to 100,000 requests per day on the Free plan, with 10 ms of CPU time per invocation and no charge for duration. The Paid plan starts at a $5 per month minimum per account and adds 10 million requests plus 30 million CPU milliseconds.
How much does Cloudflare Workers cost per million requests?
Nothing until you pass 10 million requests in a month on the Paid plan. Beyond that Cloudflare charges $0.30 per additional million requests, plus $0.02 per additional million CPU milliseconds.
What happens to Deno Deploy now that Cloudflare owns Deno?
Deno Deploy continues running for six months from the October 2026 announcement, then shuts down. Cloudflare says it will provide migration support for paying Deno Deploy customers moving to Cloudflare Workers. The Deno runtime itself gets one more year of support before Cloudflare ends development.
Related reading
Cloudflare alternatives in Europe, Cloudflare Web Analytics, Vercel vs Netlify: which serverless platform should you deploy on in 2026?, What Are Cloudflare Containers and What Do They Cost?