Cloudflare prices Workers by request and CPU time, not bandwidth

The workload

Cloudflare documents its Workers platform across two pages a founder must read together: the pricing page states what each plan costs and includes, and the limits page states hard technical ceilings that apply regardless of plan. The task before deploying anything is to check both: whether the code's per-invocation CPU time fits the plan's cap, and whether expected traffic fits the included request allotment before overage applies. Cloudflare states plainly on the pricing page that it charges nothing for data transfer or bandwidth on either plan, removing one variable a founder would otherwise model.

What the documents show

Verified: the Free plan, as retrieved 16 September 2026, includes 100,000 requests per day and 10 milliseconds of CPU time per invocation, at no charge, per the pricing page. Verified: the Paid plan costs $5 per month minimum and includes 10 million requests per month, billed at $0.30 per additional million; it also includes 30 million CPU milliseconds per month, billed at $0.02 per additional million CPU milliseconds. The limits page adds detail the pricing page omits: the default CPU-time cap per request on Paid is 30 seconds, configurable up to 5 minutes, and both plans share a 128 MB per-isolate memory limit. The two documents agree where both mention a figure; the limits page alone states the configurable maximum duration.

The operating cost

Verified: a Worker that never exceeds 100,000 requests a day and 10 ms of CPU time per invocation costs $0 per month, per the pricing page. Above that, the minimum paid cost is $5 per month, which already includes 10 million requests and 30 million CPU milliseconds; the page's own worked example states that a Worker serving 15 million monthly requests at roughly 7 ms average CPU time costs approximately $8.00 total once the subscription and overage are added. Estimated: any other workload's total depends on its own request volume and average CPU time, neither of which the page can supply in advance.

The stop condition

The vendor states one stop condition directly: on the Free plan, the 100,000-requests-per-day and 10 ms CPU-time-per-invocation ceilings are hard limits with no overage price, so a Worker needing more of either must move to Paid or stop, per the limits page. Editorially, a second point is worth naming: since Cloudflare charges nothing for bandwidth, the remaining variable cost is almost entirely CPU time, so the moment to reconsider the code is when CPU-time overage, not request-count overage, is the larger line item.

• Does the code's typical CPU time per request stay under the Free plan's 10 ms ceiling, or does it already require Paid?
• Is the workload request-heavy or compute-heavy, since Cloudflare prices those two dimensions separately?
• Would raising the per-request CPU-time limit fix a timeout problem, or does the code need rewriting instead?

Both documents are living pages the company can revise without notice; the entry states only what each page said on the date it was retrieved.