Estimate your monthly bill before Cloudflare's 15-minute lag catches up. Workers, KV, R2, D1, and Queues — all in one place.
We'll email you the moment your real usage crosses this estimate
At this usage, a single misconfigured KV loop adding 50M writes/day would add $250/week to your bill before Cloudflare's metrics catch up.
See how FlareLog catches this in real time →Base price. Everything below is included — you only pay overage when you exceed these allowances.
// Memory is fixed at 128MB per Worker invocation and is not a billing dimension. // You are billed on CPU time, not wall-clock time — I/O wait time is free.
Select Free or Paid ($5/mo), enter monthly requests, average CPU-ms, KV reads/writes, R2 Class A/B ops, D1 rows read/written and Queues ops. The live estimate applies official 2026 included allowances first, then $0.30/M requests, $0.02/M CPU-ms, $0.50/M KV reads, $5/M KV writes, R2 $4.50/M Class A / $0.36/M Class B, D1 $1/M writes and Queues $0.40/M ops. Save your estimate by email to get burn alerts.
Math matches Cloudflare's official 2026 rates (Workers docs Jul 2026, KV/D1/Queues Apr 2026, R2 Aug 2026): $5 base, 10M requests and 30M CPU-ms included. It models the five bill drivers — Workers, KV, R2, D1, Queues — but not zone plans, Workers AI neurons, or subrequest edge cases. Use it for budgeting, then monitor real usage because dashboards lag 15-60 minutes.
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 30M CPU-ms per month. Beyond the included allowances, you pay $0.30 per million requests and $0.02 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 30M CPU-ms per month, after which you pay $0.02 per million CPU-ms. A typical lightweight Worker uses 1-5 CPU-ms per request, so the included 30M covers roughly 6-30 million such requests per month.
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.
Official 2026 rates, free-tier limits, and the traps that inflate bills — verified against Cloudflare's docs.
The same dashboard captures errors, traces, and AI costs wherever your code runs — not just Workers.
Get real-time cost burn alerts. FlareLog watches your Workers, KV, R2, and D1 usage — and emails you the moment it spikes.
Start free — 10,000 logs/mo