Cloudflare Workers
Cost Calculator

Cloudflare Workers uses a pay-as-you-go model. The Free plan includes 100K requests/day with 10ms CPU per request. The Paid plan costs $5/month and includes 10M requests and 10M CPU-ms per month. Beyond the included allowances, you pay $0.30 per million requests and $12.50 per million CPU-ms. KV, R2, D1, and Queues are billed separately based on operations performed.

No. Memory is fixed at 128MB per Worker invocation and is not a billing dimension. You are billed on CPU time (CPU-ms), not wall-clock time or memory usage. A request that waits 5 seconds on a fetch() call consumes zero billable CPU time during that wait — only the actual compute work counts.

The most common cause of surprise bills is a misconfigured loop that generates millions of KV writes or requests per day. To avoid bill shock: (1) monitor your usage in real time with a tool like FlareLog, (2) set spending caps in the Cloudflare dashboard, (3) use KV reads ($0.50/M) instead of writes ($5/M) wherever possible, and (4) cache aggressively to reduce repeat operations.

A CPU-millisecond (CPU-ms) is one millisecond of actual CPU compute time consumed by your Worker. It is not wall-clock time — time spent waiting for I/O (fetch calls, KV operations, subrequests) does not count. The Paid plan includes 10M CPU-ms per month, after which you pay $12.50 per million CPU-ms. A typical lightweight Worker uses 1-5 CPU-ms per request.

It depends on your access pattern. KV writes cost $5 per million (16x more than reads at $0.50/M), while D1 rows written cost $1 per million and D1 rows read cost $0.001 per million. If your workload is read-heavy, D1 is dramatically cheaper. If you need sub-millisecond key-value lookups, KV reads are cost-effective — but avoid using KV as a write-heavy cache, as write costs compound fast.