Cloudflare Workers Pricing (2026) — Plans, CPU-ms & Real Examples
Workers pricing is a $5/month floor plus two usage meters: requests and CPU time. Both meters have generous included allowances, and overages are cheap — the bills that hurt come from the products around Workers (KV, R2, D1, Queues), not from Workers itself. Here are the exact numbers, with a calculator to model your own traffic.
Rates verified against Cloudflare's official docs · last checked July 2026
Cloudflare Workers pricing table
| Free plan | Paid plan ($5/mo) | |
|---|---|---|
| Requests | 100,000 / day | 10M / month included, then $0.30 per additional million |
| CPU time | 10 ms per invocation | 30M CPU-ms / month included, then $0.02 per additional million CPU-ms |
| CPU limit per request | 10 ms (hard) | 30 s default, configurable up to 5 min |
| CPU limit (Cron / Queue consumer) | 10 ms | up to 15 min |
| Duration (wall clock) | no charge | no charge, no limit |
| Memory | 128 MB | 128 MB (never billed) |
| Static asset requests | free & unlimited | free & unlimited |
// Subrequests you make from a Worker are never billed. WebSocket upgrades count as one request; messages over an established WebSocket are free.
What actually matters
$0.02 per million CPU-ms — not $12.50
CPU overage is one of the cheapest meters in serverless. Cloudflare's own example: 15M requests at 7ms average CPU costs $8/month total ($5 base + $1.50 requests + $1.50 CPU). If a calculator tells you otherwise, it's using pre-2024 rates.
CPU-ms ≠ milliseconds of latency
Only actual compute is billed. A request that spends 4 seconds waiting on a fetch() or KV call consumes zero billable CPU during the wait. Lightweight Workers use 1–5 CPU-ms per request.
The free tier dies at midnight UTC
100K requests/day is a hard cap — exceed it and every visitor gets Error 1027 until 00:00 UTC. Unlike paid-plan overage, there is no grace and no billing, just downtime.
Example: 15M requests/month at 7ms average CPU
What people miss
- ▸Cron Triggers and Queue consumers run even with zero user traffic — a Worker firing every minute burns 43,200 invocations/month on the free tier's daily budget.
- ▸Pages Functions are billed exactly as Workers — the limits in this article apply to them too.
- ▸With Workers Caching enabled, requests served from the Worker's cache are still billed as requests (CPU only billed on cache miss).
- ▸Your Cloudflare zone plan (Pro/Business) and your Workers plan are billed separately — a Pro zone does not include Workers Paid.
Model your own bill
Plug your monthly volumes into the free calculator and see the total across Workers, KV, R2, D1, and Queues. Then let FlareLog watch the real thing: real-time cost burn alerts fire the moment a loop or spike starts inflating your bill — hours before Cloudflare's 15–60 minute dashboards catch up.
FAQ
How much does Cloudflare Workers cost per month?
The Free plan is $0 with 100,000 requests/day and a 10ms CPU cap per request. The Paid plan is a $5/month minimum that includes 10M requests and 30M CPU-ms. Beyond that, requests cost $0.30 per million and CPU time $0.02 per million CPU-ms. Most indie apps that outgrow the free tier land between $5 and $20/month total.
What is a CPU-ms and how is it billed?
A CPU-millisecond is one millisecond of actual compute. Wall-clock time waiting on I/O (fetch, KV, R2, D1 calls) is free. The Paid plan includes 30M CPU-ms/month; after that you pay $0.02 per million CPU-ms. A typical CRUD Worker uses 1–5 CPU-ms per request, so the included allowance covers tens of millions of requests.
What happens if I exceed 100,000 requests on the Free plan?
Cloudflare stops invoking your Worker and serves an 'Error 1027' page to every visitor until the counter resets at 00:00 UTC. There is no automatic upgrade or grace period. If you're about to launch something viral, either upgrade to Workers Paid ($5/mo) beforehand or monitor your request rate in real time.
How do I estimate my Workers bill before deploying?
Multiply your monthly requests by average CPU-ms to get total CPU-ms, then apply the included allowances: $0.30 per million requests over 10M, $0.02 per million CPU-ms over 30M, plus the $5 base. Or use the free calculator below — it covers Workers, KV, R2, D1, and Queues in one estimate.