Cloudflare Workers / R2 spending cap: Partial
Does Cloudflare Workers / R2 have a hard spending cap?
Partial Per the docs as of Oct 14, 2026: The Workers Free plan has hard daily limits that fail with errors instead of billing. On Paid, Cloudflare's billing docs say budget alerts are informational only and do not pause or cap usage, and we found no dollar spend cap in the official docs. The documented guard on Paid is a per-invocation CPU time limit.
How do I turn on a spending limit in Cloudflare Workers / R2?
- Staying on the Workers Free plan is the documented way to avoid usage charges for Workers.
- On Paid, set a CPU time limit per Worker (Wrangler file, or dashboard: Workers & Pages > your Worker > Settings > CPU Limits). Cloudflare's pricing page recommends this to prevent runaway bills.
- Set a budget alert at Billing > Billable Usage. Since mid-2026 eligible Pay-as-you-go accounts get a default $10 alert.
What happens when the Cloudflare Workers / R2 limit is hit?
Free plan: 100,000 requests/day, then Cloudflare returns Error 1027; other Free limits fail with an error. Paid: usage keeps running and is billed; a budget alert only sends one email.
Gotchas
- Budget alerts fire the day after the threshold is crossed, because usage is processed once per day.
- Budget alerts ignore subscription fees such as the $5/month Workers Paid fee.
- CPU limits cap cost per request, not total requests, so a traffic flood can still add up.
- R2: per the R2 pricing FAQ, you are not charged for operations that fail as unauthorized (HTTP 401).