Skip to content
Calcrivo

Cloudflare Workers Cost Calculator

Price Cloudflare Workers on requests plus CPU milliseconds and check whether the free daily allowance still covers you.

Inputs

million
ms

Workers bill CPU time only — time awaiting a fetch subrequest is not billed.

USD/month
million
million
USD
USD
thousand/day

Monthly Cost

$54.20

Plan Fee

$5.00

Request Overage

$33.00

CPU Time Overage

$16.20

Average Daily Requests

4,000.0thousand/day

CPU Time Consumed

840.0million ms

Free Plan Verdict

Paid plan needed — daily volume is above the free allowance

Effective Cost per Million Requests

$0.4517

Step by step

  1. Values used

    Requests per month = 120 million; CPU time per request = 7 ms; Workers plan fee = 5 USD/month; Requests included in the plan = 10 million; CPU-milliseconds included = 30 million; Price per million requests above the allowance = 0.3000 USD; Price per million CPU-milliseconds above the allowance = 0.0200 USD; Free-plan daily request allowance = 100 thousand/day

  2. Cloudflare Workers Cost

    cost = plan fee + max(0, requests − included requests) × request price + max(0, requests × CPU ms − included CPU ms) × CPU price.

  3. Monthly Cost

    = 54.20

  4. Plan Fee

    = 5.00

  5. Request Overage

    = 33.00

  6. CPU Time Overage

    = 16.20

  7. Average Daily Requests

    = 4,000.0 thousand/day

  8. CPU Time Consumed

    = 840.0 million ms

How it works

The paid plan is a small flat fee that includes a block of requests and a block of CPU milliseconds; only usage beyond those blocks is metered. Because CPU time is billed separately from invocations, a Worker that does heavy JSON or crypto work can cost more in milliseconds than in requests even at modest traffic. Workers execute at whichever of Cloudflare's 300+ locations is nearest the user, so the same code replaces both a regional function and a CDN rule — but the CPU meter punishes slow code globally. Confirm the current plan fee, allowances and unit rates with Cloudflare before budgeting.

Formula

Cloudflare Workers Cost

cost = plan fee + max(0, requests − included requests) × request price + max(0, requests × CPU ms − included CPU ms) × CPU price.

included requests
Requests the plan fee already covers each month
CPU ms
Processor time per invocation, excluding time awaiting subrequests
free allowance
Daily request budget on the free plan

Frequently Asked Questions

How is Cloudflare Workers Cost calculated?

cost = plan fee + max(0, requests − included requests) × request price + max(0, requests × CPU ms − included CPU ms) × CPU price. The paid plan is a small flat fee that includes a block of requests and a block of CPU milliseconds; only usage beyond those blocks is metered. Because CPU time is billed separately from invocations, a Worker that does heavy JSON or crypto work can cost more in milliseconds than in requests even at modest traffic.

Why does Cloudflare Workers Cost matter?

Workers execute at whichever of Cloudflare's 300+ locations is nearest the user, so the same code replaces both a regional function and a CDN rule — but the CPU meter punishes slow code globally. Confirm the current plan fee, allowances and unit rates with Cloudflare before budgeting.

What values do I need to enter?

This calculator takes 8 inputs: Requests per month, CPU time per request, Workers plan fee, Requests included in the plan, CPU-milliseconds included, Price per million requests above the allowance, Price per million CPU-milliseconds above the allowance, Free-plan daily request allowance. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Does waiting on a fetch inside a Worker cost money?

No. Only CPU time is billed, so a Worker that spends 200 ms waiting on an origin fetch but 3 ms computing is billed for roughly 3 ms. That is why the CPU-per-request input here is much smaller than observed response time.

You might also need