Pricing (30)

Last updated Oct 2, 2026 By default, users have access to the Workers Free plan. The Workers Free plan includes limited usage of Workers, Pages Functions, Workers KV and Hyperdrive. Read more about the Free plan limits.

The Workers Paid plan includes Workers, Pages Functions, Workers KV, Hyperdrive, and Durable Objects usage for a minimum charge of $5 USD per month for an account. The plan includes increased initial usage allotments, with clear charges for usage that exceeds the base plan. There are no additional charges for data transfer (egress) or throughput (bandwidth).

All included usage is on a monthly basis.

Pages Functions billing

All Pages Functions are billed as Workers. All pricing and inclusions in this document apply to Pages Functions. Refer to Functions Pricing for more information on Pages Functions pricing.

Workers

Users on the Workers Paid plan have access to the Standard usage model. Workers Enterprise accounts are billed based on the usage model specified in their contract. To switch to the Standard usage model, contact your Account Manager.

¹ Inbound requests to your Worker. Cloudflare does not bill for subrequests you make from your Worker.

² WebSocket connections made to a Worker are charged as a request, representing the initial Upgrade connection made to establish the WebSocket. WebSocket messages routed through a Worker do not count as requests.

³ Requests to static assets are free and unlimited.

⁴ When Workers Caching is enabled, requests served from the Worker's cache are billed at the same per-request rate as requests that invoke the Worker. This includes requests to static assets and worker-to-worker invocations. CPU time is only billed when the Worker runs (on a cache miss or bypass).

Example pricing

Example 1

A Worker that serves 15 million requests per month, and uses an average of 7 milliseconds (ms) of CPU time per request, would have the following estimated costs:

Example 2

A project that serves 15 million requests per month, with 80% (12 million) requests serving static assets and the remaining invoking dynamic Worker code. The Worker uses an average of 7 milliseconds (ms) of time per request.

Requests to static assets are free and unlimited. This project would have the following estimated costs:

Example 3

A Worker that runs on a Cron Trigger once an hour to collect data from multiple APIs, process the data and create a report.

• 720 requests/month
• 3 minutes (180,000ms) of CPU time per request

In this scenario, the estimated monthly cost would be calculated as:

Example 4

A high traffic Worker that serves 100 million requests per month, and uses an average of 7 milliseconds (ms) of CPU time per request, would have the following estimated costs:

Example 5: Worker with caching

The same Worker as Example 4, but with Workers Caching enabled and an 80% cache hit rate. 80 million requests are served from cache and 20 million invoke the Worker. Cache hits count as requests but do not consume CPU time.

For details on what is cached and how to enable caching, refer to Cache.

Custom limits

To prevent accidental runaway bills or denial-of-wallet attacks, configure the maximum amount of CPU time that can be used per invocation by defining limits in your Worker's Wrangler file, or via the Cloudflare dashboard (Workers & Pages > Select your Worker > Settings > CPU Limits).

If you had a Worker on the Bundled usage model prior to the migration to Standard pricing on March 1, 2024, Cloudflare has automatically added a 50 ms CPU limit on your Worker.

How to switch usage models

Note

Some Workers Enterprise customers maintain the ability to change usage models.

Users on the Workers Paid plan have access to the Standard usage model. However, some users may still have a legacy usage model configured. Legacy usage models include Workers Unbound and Workers Bundled. Users are advised to move to the Workers Standard usage model. Changing the usage model only affects billable usage, and has no technical implications.

To change your default account-wide usage model:

1. In the Cloudflare dashboard, go to the Workers & Pages page. Go to Workers & Pages ↗
2. Find Usage Model on the right-side menu > Change.

Usage models may be changed at the individual Worker level:

1. In the Cloudflare dashboard, go to the Workers & Pages page. Go to Workers & Pages ↗
2. In Overview, select your Worker > Settings > Usage Model.

Existing Workers will not be impacted when changing the default usage model. You may change the usage model for individual Workers without affecting your account-wide default usage model.

Workers Logs

Workers Logs is included in both the Free and Paid Workers plans.

Pricing change

Beginning December 1, 2026, Workers Logs will use Cloudflare Observability pricing. Until then, the Workers Logs pricing in this table applies.

Workers Logs documentation

For more information and examples of Workers Logs billing, refer to the Workers Logs documentation.

Workers Trace Events Logpush

Workers Logpush is only available on the Workers Paid plan.

¹ Workers Logpush charges for request logs that reach your end destination after applying filtering or sampling.

Workers KV

Workers KV is included in both the Free and Paid Workers plans.

¹ The Workers Free plan includes limited Workers KV usage. All limits reset daily at 00:00 UTC. If you exceed any one of these limits, further operations of that type will fail with an error.

Note

Workers KV pricing for read, write and delete operations is on a per-key basis. Bulk read operations are billed by the amount of keys read in a bulk read operation.

KV documentation

To learn more about KV, refer to the KV documentation.

Hyperdrive

Hyperdrive is included in both the Free and Paid Workers plans.

<details>

<summary>

Footnotes

</summary>

1: The Workers Free plan includes limited Hyperdrive usage. All limits reset daily at 00:00 UTC. If you exceed any one of these limits, further operations of that type will fail with an error.

2: Database queries refers to any database statement made via Hyperdrive, whether a query (<code>SELECT</code>), a modification (<code>INSERT</code>,<code>UPDATE</code>, or <code>DELETE</code>) or a schema change (<code>CREATE</code>, <code>ALTER</code>, <code>DROP</code>).

</details>

Footnotes

1. The Workers Free plan includes limited Hyperdrive usage. All limits reset daily at 00:00 UTC. If you exceed any one of these limits, further operations of that type will fail with an error. ↩
2. Database queries refers to any database statement made via Hyperdrive, whether a query ( SELECT), a modification ( INSERT, UPDATE, or DELETE) or a schema change ( CREATE, ALTER, DROP). ↩

Hyperdrive documentation

To learn more about Hyperdrive, refer to the Hyperdrive documentation.

Queues

Cloudflare Queues charges for the total number of operations against each of your queues during a given month.

• An operation is counted for each 64 KB of data that is written, read, or deleted.
• Messages larger than 64 KB are charged as if they were multiple messages: for example, a 65 KB message and a 127 KB message would both incur two operation charges when written, read, or deleted.
• A KB is defined as 1,000 bytes, and each message includes approximately 100 bytes of internal metadata.
• Operations are per message, not per batch. A batch of 10 messages (the default batch size), if processed, would incur 10x write, 10x read, and 10x delete operations: one for each message in the batch.
• There are no data transfer (egress) or throughput (bandwidth) charges.