Cloudflare Workers Cost Calculator
Price Cloudflare Workers on requests plus CPU milliseconds and check whether the free daily allowance still covers you.
About Cloudflare Workers Cost Calculator
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
Worked example
With the default values below, Cloudflare Workers Cost Calculator returns Monthly Cost of $54.20. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Requests per monthaccepts 0–1,000,000 million
- 120 million
- CPU time per requestaccepts 0–30,000 ms
- 7 ms
- Workers plan feeaccepts 0–100,000 USD/month
- 5 USD/month
- Requests included in the planaccepts 0–100,000 million
- 10 million
- CPU-milliseconds includedaccepts 0–1,000,000 million
- 30 million
- Price per million requests above the allowanceaccepts 0–100 USD
- 0.3 USD
- Price per million CPU-milliseconds above the allowanceaccepts 0–100 USD
- 0.02 USD
- Free-plan daily request allowanceaccepts 0–100,000 thousand/day
- 100 thousand/day
Results
- Monthly Cost
- $54.20
- Plan Fee
- $5.00
- Request Overage
- $33.00
- CPU Time Overage
- $16.20
- Average Daily Requests
- 4,000.0 thousand/day
- CPU Time Consumed
- 840.0 million ms
- Free Plan Verdict
- Paid plan needed — daily volume is above the free allowance
- Effective Cost per Million Requests
- $0.4517
Step by step
- 1Values used
- 2Cloudflare Workers Cost
- 3Monthly Cost= 54.20
- 4Plan Fee= 5.00
- 5Request Overage= 33.00
- 6CPU Time Overage= 16.20
- 7Average Daily Requests= 4,000.0 thousand/day
- 8CPU Time Consumed= 840.0 million ms
Assumptions and limits
- The result is derived only from the 8 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax or compounding frequency into account.
- Figures are rounded for display to 4 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
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.
Related Calculators
You might also need
- Cloudflare CDN Cost CalculatorCommonly used together
- Edge Compute Cost CalculatorCommonly used together
- Cloudflare R2 Storage CalculatorCommonly used together
- CDN Cache Hit Ratio CalculatorAlso in CDN, Edge & DNS
- Global Latency CalculatorAlso in CDN, Edge & DNS
- Anycast Coverage CalculatorAlso in CDN, Edge & DNS
