Free calculator
Cloudflare Workers pricing calculator
A monthly Workers bill split into the $5 plan, requests, CPU time, KV and D1, plus a check on whether the Free plan would still do.
What does a Worker with 15 million requests a month at 7 ms of CPU each cost? (prices checked 2026-10-29)
$8.00 a month: the $5 Paid plan, $1.50 for the 5 million requests over the 10 million included, and $1.50 for the 75 million CPU milliseconds over the 30 million included. Cloudflare's own pricing page works out the same example to the same $8.00. Bandwidth and time spent waiting on other services cost nothing.
Estimated monthly bill, Workers Paid
$0
Prices from developers.cloudflare.com/workers/platform/pricing (Standard usage model), checked 2026-10-29: $5 a month per account with 10 million requests and 30 million CPU milliseconds included, then $0.30 per million requests and $0.02 per million CPU milliseconds. KV: 10 million reads and 1 million writes included, then $0.50 and $5.00 per million, 1 GB stored, then $0.50 per GB-month. D1: 25 billion rows read and 50 million rows written included, then $0.001 and $1.00 per million, 5 GB stored, then $0.75 per GB-month. Requests to static assets are free. Durable Objects, R2, Queues, Workers Logs past the included amount and Images are separate and not included here.
Why the CPU line grows
Workers bills CPU time, not wall-clock time. A request that waits 900 ms for a database and spends 4 ms running your code is billed for 4 ms. That's the opposite of AWS Lambda, where the meter runs while you wait, and it's why an API that mostly calls other services is cheap on Workers.
What does run up CPU: parsing and rendering big pages on every request (server-side rendering a heavy React tree), resizing images or building PDFs in the Worker, crypto, and JSON bodies of a few megabytes. If your average CPU time is in the double digits, the fix is usually caching the rendered result or moving that one job somewhere else, not a different plan.
Caching helps twice. A request answered from the Workers cache still counts as a request, but it uses no CPU time, so a page with a high hit rate costs almost nothing past the request fee. Static files served as Workers static assets don't count at all.
The requests line is the one that surprises people on busy sites: every dynamic request past 10 million is $0.30 per million, even a 1 ms one. A bot hammering an uncached route is a real cost, so put rate limiting or a cache in front of anything public.
Comparing Workers with a platform that charges for bandwidth? We priced the same app on both in Vercel vs Cloudflare pricing. And if your Cloudflare or Vercel bill doesn't look like what this page says it should, send us the bill.