Cloudflare Workers Pricing: Free vs Paid, and What 10 Million Requests Cost

Cloudflare Workers is priced on two meters, requests and CPU time, and the free plan gives you a generous amount of the first and a tight amount of the second. Free allows 100,000 requests a day at 10 ms of CPU per invocation; Paid has a $5.00 monthly minimum that includes 10 million requests and 30 million CPU-ms. At 7 ms of CPU per request, 10 million requests a month costs $5.80 (calculated 2026-10-25). This page shows where the meters trip and what each volume band actually bills.

What each plan includes

What the meters actually charge

Request volume is the meter people watch and CPU time is the meter that decides the bill. A worker that answers from a cache in 2 ms costs almost nothing in CPU and almost everything in requests; a worker that fetches three APIs and renders HTML costs the reverse.

The 100 million row is Cloudflare's own worked example, which is useful because it removes any argument about method: $5.00 minimum, $27.00 of request overage at $0.30 per million beyond the included 10 million, and $13.40 of CPU overage at $0.02 per million CPU-ms. The same page shows a caching variant — 100 million requests with an 80% cache hit rate, so only 20 million invoke the worker — costing $34.20, because the request charge stays the same and the CPU charge collapses.

How we measured it

We loaded the Workers pricing documentation and the Workers limits page on 2026-10-25, took the published allowances and rates, and applied a 7 ms CPU figure per request because that is the number Cloudflare uses in its own examples. No worker was deployed and no traffic was generated; these are published rates multiplied out, with the arithmetic dated. The 7 ms assumption is the one variable that changes the CPU column, and it is stated rather than buried.

What changes in practice

The 10 ms CPU ceiling on Free is the real upgrade trigger, not the 100,000 requests. Three million requests a month is more than most small sites serve, but 10 ms is not enough to resize an image, parse a large JSON payload and re-serialise it, or talk to two services in sequence. The moment a worker needs 20 ms, Paid is the only option and the bill starts at $5.

Cache hit rate is the lever that keeps the bill flat. Requests are charged whether or not they reach your code, so a worker sitting behind a cache still pays $0.30 per million for the privilege of being skipped. Cloudflare's 80% example is the proof: 100 million requests cost $45.40 cold and $34.20 warm, and the $11.20 difference is entirely CPU time that never happened.

There is no bandwidth line at all, which is why the plan suits media-heavy sites. Static asset requests are free and unlimited, egress is free, and subrequests a worker makes downstream are not billed. A site serving 1 TB of images through Workers pays for invocations only.

Bottom line

Below roughly 3 million requests a month and 10 ms of CPU per request, Free costs $0 and does the job. Above that, budget the $5.00 minimum plus $0.30 per million requests and $0.02 per million CPU-ms: 10 million requests lands at $5.80, and the bill only becomes a real line item past 50 million requests, where it reaches $23.40.