Cloudflare Workers and developer platform pricing covers how Cloudflare charges for its serverless platform: Workers and Pages Functions for compute, Workers KV, D1, Durable Objects, Queues and Workflows for state and messaging, R2 for object storage, and Containers, Workers AI and related products.[1][3] Nothing is licensed per user or per server. An account is on either the Workers Free plan or the Workers Paid plan, and metered usage above the included amounts is billed per unit.[1] The Workers Paid plan “is separate from any other Cloudflare plan (Free, Professional, Business) you may have”, so a domain on Pro does not include paid Workers usage.[1]
Editions
| Plan | Price | What it includes |
|---|---|---|
| Workers Free | $0 | Default for every account. Limited usage of Workers, Pages Functions, Workers KV and Hyperdrive, with daily limits.[1] |
| Workers Paid | $5 per month per account minimum | Workers, Pages Functions, Workers KV, Hyperdrive and Durable Objects usage with larger monthly allotments, then per-unit charges.[1] |
| Workers Enterprise | Contract | “Workers Enterprise accounts are billed based on the usage model specified in their contract.”[1] |
Workers Paid uses the Standard usage model. Earlier usage models, Workers Bundled and Workers Unbound, are legacy, and Cloudflare advises users to move to Standard. Changing the usage model “only affects billable usage, and has no technical implications”. Workers that were on Bundled before the migration to Standard pricing on 2024-03-01 were given an automatic 50 ms CPU limit.[1]
Metrics
The Units of Measurement define a Request for the developer platform as “a single HTTP/S or similar request that hits or otherwise invokes a Worker or Durable Object on Cloudflare’s edge”. They also define Read, Write, List and Delete for KV, Durable Objects, D1 and Workers Analytics Engine, and Storage as the average hourly amount stored during a monthly billing period.[8] The product price pages use these units:
- Workers: requests and CPU milliseconds.[1]
- Workers KV: keys read, written, deleted and listed, plus stored GB.[1]
- D1: rows read, rows written and GB stored.[1]
- Durable Objects: requests and compute duration in GB-seconds, plus storage.[1]
- Queues: operations, one per 64 KB written, read or deleted.[1]
- R2: GB-months, Class A and Class B operations, and data retrieval for Infrequent Access.[2]
- Workers AI: Neurons, “a measure of compute capacity used for machine learning model workloads”.[8]
Counting / floors
Workers
| Usage | Workers Free | Workers Paid (Standard) |
|---|---|---|
| Requests | 100,000 per day | 10 million per month included, then $0.30 per additional million |
| CPU time | 10 ms per invocation | 30 million CPU ms per month included, then $0.02 per additional million CPU ms |
| Duration (wall-clock) | No charge | No charge or limit |
Source: Workers pricing.[1] On Workers Paid, CPU time is capped at 5 minutes per invocation (30 seconds by default) and 15 minutes per Cron Trigger or Queue Consumer invocation. Customers can set their own CPU limits per Worker “to prevent accidental runaway bills or denial-of-wallet attacks”.[1]
Only inbound requests count. “Cloudflare does not bill for subrequests you make from your Worker”, and “Requests to static assets are free and unlimited.” A WebSocket connection counts as one request; messages routed through it do not.[1] Calls from one Worker to another through a Service Binding do not incur additional request fees on the Standard model; on the deprecated Bundled or Unbound models they are charged as separate requests.[1] Workers run before the Cloudflare cache, so cached requests that hit a Worker still count. With Workers Caching on, cache hits are billed at the request rate but use no CPU time.[1] Catalog proof: Subrequests and static asset requests are not billed; Subrequests and static asset requests are not billed.
Cloudflare’s own worked example: a Worker serving 15 million requests a month at an average of 7 ms of CPU time costs $5.00 for the subscription, $1.50 for the 5 million requests above the allotment and $1.50 for the CPU time above 30 million ms, a total of $8.00.[1] The $5 is a floor: an account on Workers Paid pays it even with no usage. Catalog proof: Workers Paid has a $5 monthly minimum per account.
Storage and data products
On Workers Paid, Workers KV includes 10 million reads and 1 million each of writes, deletes and lists per month, then charges $0.50 per million reads and $5.00 per million for the others, with stored data at $0.50 per GB-month above 1 GB. KV operations are billed per key, and bulk reads are billed by the number of keys read.[1] D1 includes 25 billion rows read and 50 million rows written per month, then charges $0.001 per million rows read and $1.00 per million rows written; storage above 5 GB is $0.75 per GB-month. A row counts once regardless of its size, and a full table scan of 5,000 rows counts as 5,000 rows read.[1]
Durable Objects are billed for requests and for compute duration while an object is active and cannot hibernate. Billable usage above the monthly allocation is rounded up to the next billable unit; for example, 500,000 GB-s of billable duration is billed as 1,000,000 GB-s.[1] Queues charge per operation, and a message usually takes three operations (write, read, delete); messages over 64 KB count as several.[1]
R2 lists Standard storage at $0.015 per GB-month, Class A operations at $4.50 per million and Class B operations at $0.36 per million. Infrequent Access storage is $0.01 per GB-month plus $0.01 per GB retrieved, with higher operation prices. Egress to the Internet is free for both classes.[2] The free tier of 10 GB-month, 1 million Class A and 10 million Class B operations per month applies only to Standard storage.[2] “Cloudflare rounds up your usage to the next billing unit”, so one million and one operations bill as two million, and “A GB-month is calculated by averaging the peak storage per day over a billing period (30 days).”[2] Catalog proof: R2 usage is rounded up to the next billing unit; R2 storage is the average of daily peak storage.
Compute and AI products
Containers are billed for every 10 ms they run. Workers Paid includes 25 GiB-hours of memory, 375 vCPU-minutes and 200 GB-hours of disk per month, with additional usage at $0.0000025 per GiB-second, $0.000020 per vCPU-second and $0.00000007 per GB-second. Container egress is charged by region, from $0.025 per GB in North America and Europe after 1 TB included.[1] Workers AI is listed at $0.011 per thousand Neurons on the paid plan, with 10,000 Neurons per day on the free plan.[3]
Workers Logs is included in both plans: 200,000 log events per day on Free, and 20 million per month on Paid, then $0.60 per additional million. Beginning on 2026-12-01, Workers Logs moves to Cloudflare Observability pricing.[1]
What happens at a limit
The two plans behave differently at their limits. On Workers Free, limits reset daily at 00:00 UTC, and “If you exceed any one of these limits, further operations of that type will fail with an error.” On Workers Paid, monthly allotments are followed by per-unit charges.[1] The Developer Platform terms also let Cloudflare temporarily limit storage or requests if processing them would put an undue burden on its network.[7] Catalog proof: Workers Free limits stop operations instead of billing.
Virtualization & partitioning
There is no processor, core or host metric. Compute is measured in CPU milliseconds per invocation for Workers, and in vCPU-seconds, memory and disk for Containers.[1] Placement on Cloudflare’s network is not a licensing question.
Cloud / BYOL
The developer platform runs only on Cloudflare’s network, so there is no bring-your-own-licence model. Workers Paid has “no additional charges for data transfer (egress) or throughput (bandwidth)”, and R2 does not charge egress for any storage class.[1][2]
Workers for Platforms is the sanctioned way to let a customer’s own End Users run Workers functionality on its Internet Properties, provided that use complies with the Agreement.[7] The plans page lists it at $0.30 per million requests, $0.02 per million CPU ms and $0.02 per script deployed, with no free tier.[3] After a trial or subscription ends, the customer “may be permitted” to access uploaded content for up to 30 days, and Cloudflare has no obligation to keep it afterwards.[7] For R2, if a payment method fails preauthorization, buckets become inaccessible, and data may be deleted if the payment method is not updated within 30 days.[9] Catalog proof: Workers for Platforms may expose Workers functionality to end users; Developer Platform content is accessible for up to 30 days after termination.
Programs
- Workers Free plan and Workers Paid plan. The two self-serve plans described above.[1]
- Enterprise Subscription. Enterprise customers should confirm pricing with their account team, and their usage model is set in the contract.[1]
- Preview services. Contracted customers can enable Workers as a 30-day preview.[10]
Billing and monitoring
Usage-based products are billed in arrears: Cloudflare “charges you based on how much you used a feature during your previous billing period”, while plans are prepaid flat fees.[4] If Workers is turned on partway through a billing period, the next invoice covers usage from that day to the billing date.[4] Every billable dimension appears as its own invoice line, even at $0.00 within the free tier; a single R2 subscription can produce six or more lines.[6] Catalog proof: Usage-based products are billed in arrears.
For self-serve accounts, when combined usage charges across all usage-based products reach a level set by Cloudflare during a billing cycle, Cloudflare raises a mid-cycle threshold invoice. It fires once per account, the threshold cannot be changed, and “Enterprise accounts and startup program participants are not subject to threshold billing”.[5] Cloudflare may also preauthorize the card on file during a period for services with usage-based billing.[9] The billable usage dashboard shows daily costs per product, and budget alerts can email when account-wide usage spend crosses a dollar threshold.[4] Catalog proof: Self-serve usage can trigger a one-time mid-cycle threshold invoice; Self-serve usage can trigger a one-time mid-cycle threshold invoice.
Out of scope
This page does not cover Pages build limits, Stream, Images, Vectorize, Hyperdrive, AI Gateway or Browser Rendering pricing in detail, the application services plans (see Cloudflare application services plans), or open-source components that Cloudflare publishes under their own licences.