Cloudflare's own example: an hourly cron that uses 3 minutes of CPU
Scenario · workers
Example 3 runs 720 times a month and spends 180,000 CPU milliseconds on each run. The published CPU line is $1.99.
On the Paid plan this model comes to $6.99. The other plan, with the same inputs, comes to $0.00. The 30-day month is the same length R2 uses in its storage example. Daily free caps are not monthly pools.
CPU is active time, not wall time
Waiting on the network, KV, or D1 does not count as CPU. Paid usage includes 30 million CPU milliseconds and then charges $0.02 per million, prorated. The Free plan allows 10 ms per invocation and fails with error 1102 past that. It is not a monthly pool.
Read this before you trust the total
Free plan lines at $0 can still be an outage: error 1027, error 1102, or a D1 quota error. R2 above its monthly free tier is billed on both plans. Durable Object requests round up to the next million, as in Cloudflare's own Example 1, which bills 500,000 requests as 1 million.
This model
$6.99 · Paid
The $5 is an account minimum for Workers Paid, not a per-product fee. Included usage sits inside it.
129,600,000 used, 30,000,000 included. Billable: 99,600,000. Exact charge $1.992, shown as $1.99. CPU time is active execution only. Waiting on fetch, KV, or D1 does not count. Paid CPU is prorated at $0.02 per million milliseconds after 30 million.
Assumptions
- A 30-day month and steady traffic across it.
- Rates as published on 2026-10-25; taxes excluded.
- The Workers Paid plan has a $5 monthly minimum. It is charged even if you use nothing, and it covers the included allowances.
- Worker CPU time adds $1.99 (28% of the bill): you used more than the 30,000,000 included.
Sources
- Workers pricingOfficial