FlareCostUsage costs, in the open
EN, EnglishES, Español

Cloudflare's own example: 15 million requests at 7 ms

Scenario · workers

Reviewed 2026-10-25 · against the official Cloudflare pricing pages listed under Sources

Try this scenarioLoads these inputs into the calculator so you can change them.

This is example 1 on the Workers pricing page, copied into the calculator so the line items can be checked against the docs.

On the Paid plan this model comes to $8.00. 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.

Requests are the first Paid meter

Workers Paid includes 10 million requests a month and then charges $0.30 per million, prorated. Subrequests are not extra requests on Standard pricing. Cache hits still count as requests when Workers Caching is enabled; they usually add no CPU.

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

$8.00 · Paid

Workers Paid minimum
$5.00

The $5 is an account minimum for Workers Paid, not a per-product fee. Included usage sits inside it.

Worker requests
$1.50

15,000,000 used, 10,000,000 included. Billable: 5,000,000. Exact charge $1.50, shown as $1.50. Paid requests are prorated at $0.30 per million after the included 10 million. They are not rounded up to the next million. Requests served as static assets are free and unlimited, so they should not be included in this request count. On Standard pricing, subrequests and service-binding calls are not extra requests. CPU used by both Workers still counts.

Worker CPU time
$1.50

105,000,000 used, 30,000,000 included. Billable: 75,000,000. Exact charge $1.50, shown as $1.50. 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 requests adds $1.50 (19% of the bill): you used more than the 10,000,000 included.
  • Worker CPU time adds $1.50 (19% of the bill): you used more than the 30,000,000 included.

Try this scenario

Sources