Workers pricing and limits: how CPU-time billing works and how to estimate your bill
BenZ explains, in Traditional Chinese, the two dimensions of a Workers bill — requests and CPU time — the Free and Paid limits, a step-by-step way to estimate a monthly bill, and the limit errors people hit most.
- Products
- Workers
- Source
- Author experienceBenzHub
- Author
- BenZ
Key points
- The author says a Workers bill has two parts, requests and CPU time, with no egress charge; Free allows 100,000 requests a day and 10 ms of CPU per request, while Paid includes 10 million requests and 30 million CPU ms a month, then $0.30 per extra million requests and $0.02 per extra million CPU ms, with a default 30-second CPU limit that can be raised to 5 minutes. He labels his figures approximate and points to the official page. Cloudflare’s current Workers pricing and limits pages list the same included amounts, overage prices and CPU limits.
- He stresses that CPU time only counts computation, not time spent waiting on databases or external APIs, so a request that takes 400 ms may bill only around 10 ms of CPU; for real numbers, enable observability in wrangler.jsonc and read per-request CPU time in the Workers dashboard or with wrangler tail rather than guessing.
- His estimation steps: check whether daily requests fit the Free plan’s 100,000; if not, compare monthly requests and monthly CPU ms (requests × average CPU ms) with the Paid allowances — if both are under, the bill is the $5 minimum. In his example, 200,000 requests a day at 3 ms each exceeds Free, but about 6 million requests and 18 million CPU ms a month stay inside Paid’s allowances.
- His three pitfalls: assuming wall-clock billing; hitting the per-request CPU limit with image conversion, heavy cryptography or tight loops, which he says should move to Queues, Workflows or Containers rather than being solved with money; and bundles over the 3 MB (Free) or 10 MB (Paid) limit failing to deploy. He also flags the per-request subrequest cap (50 external fetches on Free, 10,000 on Paid) and suggests batching calls.
Original sources
Published
Workers pricing and limits: how CPU-time billing works and how to estimate your bill
Open original sourceBenZ explains, in Traditional Chinese, the two dimensions of a Workers bill — requests and CPU time — the Free and Paid limits, a step-by-step way to estimate a monthly bill, and the limit errors people hit most.
More to read
How I keep Cloudflare under $5: where surprise bills come from
Ashish Sharma (@sarmaasis) runs several sites on the $5 Workers Paid plan and lists, product by product, the usage patterns he says quietly run up a Cloudflare bill, ending with a 12-item checklist.
shmily7: a Durable Object alarm loop and a reported US$10,811.41 bill.
@shmily7 reports a Durable Object alarm loop in an unused test project, then says he paid the full US$10,811.41 bill to avoid service suspension. Cloudflare’s Ashley Peacock publicly says he is looking into it internally and will follow up. Cloudflare’s Dane Knecht later replies that he escalated it too. On October 9 the author declares the case closed: he reports that, with Ashley Peacock’s help, Cloudflare decided to refund the charges incurred during the bug in full, with the money still to arrive, and posts the support ticket reply he received.
Containers: an author asks Cloudflare to void a $161.11 memory charge.
Hacker News user alexander2002 asks Cloudflare support to void a $161.11 Container Memory charge, saying he usually pays Cloudflare around $30 and this was a sudden jump. He later says he already tried the official support route and X.