Cloudflare Workers Free plan limits (2026)
Every daily limit on Workers Free: requests, Durable Objects, KV, D1 and Workers AI, when they reset, and what happens when you hit one.
Last updated October 10, 2026
Every daily limit on Workers Free
These are the allowances FlareMeter measures against on the Free plan. All are per account, per day.
| Product | Metric | Free, per day |
|---|---|---|
| Workers | Requests | 100,000 |
| Workers | CPU time (ms) | 10 ms per request |
| Durable Objects | Requests | 100,000 |
| Durable Objects | Rows read (SQLite) | 5 million |
| Durable Objects | Rows written (SQLite) | 100,000 |
| Durable Objects | Stored data | 5 GB (total) |
| Workers KV | Reads | 100,000 |
| Workers KV | Writes, deletes and lists | 1,000 |
| D1 | Rows read | 5 million |
| D1 | Rows written | 100,000 |
| Workers AI | Neurons | 10,000 |
Two limits work per request rather than per day: each request gets 10 ms of CPU time, and a Worker can make up to 50 subrequests per request.
When the limits reset
Daily limits reset at 00:00 UTC. If you’re in India (UTC+5:30) that’s 5:30 in the morning; on the US West Coast it’s 4 or 5 in the afternoon, depending on daylight saving. A traffic spike in your evening can exhaust the next UTC day’s allowance early.
What happens when you hit a limit
- Worker requests: requests return error 1027 until the reset. On routes you can set the failure mode to “fail open”, so requests go to your origin without the Worker.
- KV, D1 and Durable Objects: operations past the cap fail with an error, which your Worker sees as an exception.
- Workers AI: inference requests are refused until the neuron allowance resets.
Nothing is billed: the Free plan only stops. That makes it safe for side projects, and risky for anything people rely on, because a launch or a crawler can take your app down for the rest of the UTC day.
The limits people hit first
- KV writes (1,000 a day). The smallest allowance by far. Writing a counter or a session per request runs out within minutes of real traffic.
- Worker requests (100,000 a day). About 70 requests a minute averaged over the day, less at your peak.
- Durable Object and D1 rows written (100,000 a day). A chatty app that writes on every message gets here fast.
How to see how close you are
The Cloudflare dashboard shows each product’s usage on its own page. The monitoring guide covers the dashboard, the GraphQL Analytics API, and how to watch everything in one place.
When to move to Workers Paid
If you’re regularly above half of any daily cap, or an outage until midnight UTC would hurt, Workers Paid ($5 a month) replaces the daily caps with much larger monthly included amounts and bills past them instead of failing. See Workers Paid pricing explained.
Frequently asked questions
Is the Workers Free request limit per Worker or per account?
Per account. The 100,000 requests a day are shared by every Worker on the account, so one busy Worker can use up the allowance for all of them.
When do Cloudflare Workers Free limits reset?
Every day at 00:00 UTC. Usage counts from midnight UTC, not from your local midnight or from your first request.
Will Cloudflare charge me if I go over the free limits?
No. Workers Free never bills you. Past a daily limit, the affected requests or operations fail until the reset. To keep serving past the limits, upgrade to Workers Paid ($5 a month).
What error do I get when a Worker exceeds the free daily request limit?
Requests to the Worker return Cloudflare error 1027 until 00:00 UTC. For Workers on routes, you can instead choose to let requests bypass the Worker and go to your origin (fail open).
How much CPU time does a Worker get on the free plan?
10 milliseconds of CPU time per request on Workers Free. Time spent waiting on network requests doesn't count toward it.
Sources
Figures as of October 2026, from Cloudflare’s documentation. Cloudflare changes pricing from time to time, so check the current pages before relying on them: