Cloudflare Workers Pricing Calculator

This Cloudflare Workers Pricing Calculator helps you estimate your monthly bill based on the Workers Paid plan. Input your expected usage to see a breakdown of costs for requests and CPU duration. Discover how your application’s architecture impacts your serverless spending.

Base Fee

$5.00

Request Overage Cost

$0.00

CPU Overage Cost

$0.00

Formula: Total Cost = Base Fee + (Overage Requests × $0.30/million) + (Overage CPU ms × $0.02/million).

Metric	Your Usage	Included in Plan	Overage
Requests	12,000,000	10,000,000	2,000,000
CPU Duration (ms)	96,000,000	30,000,000	66,000,000

Table 1: Breakdown of usage vs. included monthly quota.

What is the Cloudflare Workers Pricing Calculator?

The cloudflare workers pricing calculator is a specialized tool designed to provide a clear cost estimate for applications deployed on Cloudflare’s serverless platform. Unlike generic cloud cost estimators, this calculator is tailored specifically to the Workers Bundled pricing model, which bills based on two primary metrics: the number of requests and the CPU time consumed. It helps developers, architects, and financial planners forecast expenses, avoid unexpected bills, and understand the financial implications of their code’s performance. Anyone considering a serverless architecture on the edge can benefit from using a precise cloudflare workers pricing calculator. A common misconception is that serverless is always cheaper; while it can be, inefficient code can lead to high CPU costs, a factor this calculator highlights.

Cloudflare Workers Pricing Formula and Mathematical Explanation

The cost calculation for the Workers Paid plan is straightforward. It begins with a fixed monthly subscription fee, which includes a generous allotment of requests and CPU time. Costs are only incurred for usage that exceeds these included amounts. Our cloudflare workers pricing calculator automates this formula for you.

The core formula is:

Total Monthly Cost = Base Fee + Request Overage Cost + CPU Overage Cost

Where:

• Request Overage Cost = (Total Requests – Included Requests) / 1,000,000 * $0.30
• CPU Overage Cost = (Total CPU ms – Included CPU ms) / 1,000,000 * $0.02

Variable	Meaning	Unit	Typical Range
Base Fee	Fixed monthly subscription cost.	USD	$5
Total Requests	Number of incoming requests to your Worker.	Count	100k – 1B+
Avg. CPU Time	Compute time used by the code per request.	Milliseconds (ms)	1 – 50+
Request Overage Rate	Cost per million requests over the included amount.	USD / 1M Requests	$0.30
CPU Overage Rate	Cost per million CPU milliseconds over the included amount.	USD / 1M ms	$0.02

Practical Examples (Real-World Use Cases)

Example 1: Low-Traffic API Endpoint

Imagine a backend API for a company blog that handles comments and contact form submissions. It’s not heavily used but needs to be reliable.

• Inputs:
  • Monthly Requests: 1,500,000
  • Average CPU Time: 4 ms
• Calculation:
  • Total CPU ms: 1,500,000 * 4 = 6,000,000 ms
  • Request Overage: 0 (since 1.5M is less than 10M included)
  • CPU Overage: 0 (since 6M is less than 30M included)
• Result: The total cost would be just the $5.00 base fee. The usage fits entirely within the included quota, making it extremely cost-effective. The cloudflare workers pricing calculator confirms this.

Example 2: High-Traffic Image Resizing Service

Consider a Worker that intercepts image requests, resizes them on the fly based on query parameters, and then serves them. This is a more CPU-intensive task with high volume.

• Inputs:
  • Monthly Requests: 25,000,000
  • Average CPU Time: 20 ms
• Calculation using the cloudflare workers pricing calculator:
  • Total CPU ms: 25,000,000 * 20 = 500,000,000 ms
  • Request Overage: 25M – 10M = 15,000,000 requests. Cost: (15M / 1M) * $0.30 = $4.50
  • CPU Overage: 500M – 30M = 470,000,000 ms. Cost: (470M / 1M) * $0.02 = $9.40
• Result: Total Cost = $5.00 (Base) + $4.50 (Requests) + $9.40 (CPU) = $18.90. Even with significant traffic and computation, the cost remains predictable and low.

How to Use This Cloudflare Workers Pricing Calculator

Using this calculator is simple and provides instant insights. Follow these steps to estimate your costs:

1. Enter Monthly Requests: Input the total number of requests you anticipate your Worker will process in a month. This is the primary driver of request-based costs.
2. Enter Average CPU Time: This is a crucial metric. Estimate the average time in milliseconds (ms) your code takes to execute for a single request. You can find this data in the Cloudflare dashboard for an existing Worker. For new projects, you might need to benchmark your code.
3. Review the Results: The calculator instantly updates the “Estimated Monthly Cost.” It also breaks down the cost into the base fee, request overage, and CPU overage.
4. Analyze the Breakdown Table: The table below the main result shows exactly how your usage compares to the free quota included in the paid plan. This helps you see which metric (requests or CPU) is contributing more to your overage costs. For a deeper analysis, consult a serverless pricing model guide.

Key Factors That Affect Cloudflare Workers Pricing Calculator Results

Several factors can influence your final bill. Understanding them is key to managing costs effectively. Using a cloudflare workers pricing calculator helps visualize their impact.

• Request Volume: The most direct factor. More traffic means more requests, which can push you into overage territory.
• Code Complexity & Efficiency: This directly impacts CPU time. A complex, unoptimized function will consume more CPU milliseconds per request than a lean, efficient one, leading to higher costs even with the same number of requests.
• External API Calls (I/O): While Cloudflare’s CPU time model means you don’t pay for time spent waiting for external network responses, a slow external API can hold a Worker active, and complex logic to handle its response can increase CPU usage before and after the call.
• Caching Strategy: Aggressive caching at the CDN level can significantly reduce the number of requests that hit your Worker in the first place, directly lowering both your request and CPU costs. An effective cache strategy is a core part of any how to optimize Cloudflare Workers cost plan.
• Use of Other Platform Services: This calculator focuses on Workers compute costs. If you use KV, R2, Durable Objects, or other services, they have their own pricing models that will be added to your total bill.
• Choice of Plan (Free vs. Paid): The Free plan has strict limits (e.g., 100k daily requests, 10ms CPU time limit). Exceeding these requires an upgrade. The Paid plan provides a much larger quota and is necessary for any production application, as reflected in our cloudflare workers pricing calculator.

Frequently Asked Questions (FAQ)

1. What is a “CPU millisecond”?

A CPU millisecond is a measure of computation. It represents the amount of work your code does, not the “wall-clock” time it takes to run. Cloudflare’s pricing model only charges for this active compute time, not for idle time spent waiting on network I/O, which is a major advantage over traditional serverless platforms. You can find more details in our Workers vs Lambda cost comparison.

2. Does this calculator include costs for KV, R2, or Durable Objects?

No, this cloudflare workers pricing calculator is specifically for the compute costs of Cloudflare Workers (requests and CPU time). Workers KV, R2 Storage, and Durable Objects have separate pricing metrics (e.g., per read/write, per GB stored) that are not included here.

3. How accurate is this cloudflare workers pricing calculator?

This calculator is based on the publicly available pricing for the Workers Paid (Bundled) plan as of early 2026. It provides a highly accurate estimate assuming you have correctly projected your monthly requests and average CPU time. For official pricing, always refer to the Cloudflare website.

4. What happens if I exceed the Free Plan limits?

If you exceed the Free Plan’s daily limits (e.g., 100,000 requests or 10ms CPU time per invocation), your Worker will be temporarily disabled and return errors. To handle production traffic, you must upgrade to the Workers Paid plan.

5. Are there any data transfer (egress) fees?

No, one of Cloudflare’s key benefits is the absence of egress fees for data transfer from Workers. This can lead to significant savings compared to other cloud providers, a key point in any edge computing cost comparison.

6. How can I find my “Average CPU Time”?

If you have an existing Worker, you can find detailed analytics, including quantiles for CPU time (p50, p95, p99), in your Cloudflare account dashboard under Workers & Pages > Your Worker > Analytics.

7. Does the $5 base fee cover my entire account?

Yes, the $5/month Workers Paid plan subscription covers all Workers within your account. The included monthly quotas for requests and CPU time are pooled across your account.

8. Can I set a budget or spending limit?

Currently, Cloudflare does not offer hard spending limits for Worker usage. However, you can set up notifications based on usage to monitor your costs proactively and avoid surprises. This is a common feature request for those looking into free serverless hosting and scaling up.