Cloudflare Workers Pricing Calculator

Estimate Your Cloudflare Workers Monthly Costs

Use this Cloudflare Workers Pricing Calculator to get a detailed breakdown of your potential monthly expenses for Cloudflare Workers, Workers KV, Durable Objects, R2 storage, and egress bandwidth. Input your estimated usage to see a comprehensive cost projection.

Detailed Cloudflare Workers Pricing Assumptions

Service Component	Free Tier	Paid Tier 1 Rate	Paid Tier 2 Rate	Unit
Workers Requests	1,000,000	$0.30 / 1M (first 50M)	$0.15 / 1M (over 50M)	Requests
Workers CPU Time	1,000,000 ms	$0.000015 / 1M ms	N/A	Milliseconds
Workers KV Reads	10,000,000	$0.0000003 / read (first 10M)	$0.00000015 / read (over 10M)	Reads
Workers KV Writes	1,000,000	$0.0000005 / write (first 1M)	$0.00000025 / write (over 1M)	Writes
Workers KV Stored Data	1 GB	$0.03 / GB	N/A	GB
Durable Objects Active Objects	50	$0.000005 / object	N/A	Objects
Durable Objects Requests	1,000,000	$0.50 / 1M requests	N/A	Requests
Durable Objects Stored Data	1 GB	$0.03 / GB	N/A	GB
R2 Class A Operations	1,000,000	$4.50 / 1M ops	N/A	Operations
R2 Class B Operations	10,000,000	$0.36 / 1M ops	N/A	Operations
R2 Stored Data	10 GB	$0.015 / GB	N/A	GB
Egress Bandwidth	10 GB	$0.045 / GB	N/A	GB

Caption: This table outlines the specific pricing tiers and free allowances used in the Cloudflare Workers Pricing Calculator.

What is Cloudflare Workers Pricing Calculator?

The Cloudflare Workers Pricing Calculator is an essential online tool designed to help developers, businesses, and IT professionals estimate the monthly costs associated with using Cloudflare’s serverless platform, Cloudflare Workers. This powerful platform allows you to deploy JavaScript, WebAssembly, or other languages to Cloudflare’s global network, running code at the edge—closer to your users—for enhanced performance and reduced latency.

Understanding the cost structure of a serverless platform like Cloudflare Workers can be complex due to its usage-based billing model, which includes various components like requests, CPU time, storage (Workers KV, Durable Objects, R2), and egress bandwidth. A dedicated Cloudflare Workers Pricing Calculator simplifies this by allowing users to input their projected usage metrics and receive an immediate, transparent cost estimate.

Who Should Use the Cloudflare Workers Pricing Calculator?

• Developers: To budget for personal projects or new application deployments.
• Startups & SMBs: To forecast infrastructure costs and manage financial planning.
• Enterprises: For cost optimization, comparing Cloudflare Workers against other serverless providers, and scaling strategies.
• Solution Architects: To design cost-effective edge computing solutions.
• Anyone evaluating Cloudflare Workers: To understand the financial implications before committing to the platform.

Common Misconceptions About Cloudflare Workers Pricing

Many users have misconceptions about Cloudflare Workers pricing. A common one is underestimating the impact of CPU time, especially for complex or long-running Workers. Another is overlooking the costs associated with data storage services like Workers KV, Durable Objects, and R2, assuming they are always negligible. Furthermore, while Cloudflare is known for its generous free tier, exceeding these limits can quickly lead to unexpected costs if not properly monitored. The Cloudflare Workers Pricing Calculator helps demystify these aspects by providing a clear breakdown.

Cloudflare Workers Pricing Formula and Mathematical Explanation

The Cloudflare Workers Pricing Calculator uses a combination of tiered pricing and per-unit rates across various services. The core principle is that a certain amount of usage is free, and beyond that, charges apply based on predefined rates. Here’s a step-by-step derivation and explanation of the formulas used:

Step-by-Step Derivation:

1. Workers Compute Cost:
   • Requests: `PaidRequests = MAX(0, MonthlyRequests – FreeRequests)`. Cost is tiered: `(PaidRequests <= 50M) ? (PaidRequests / 1M * Rate1) : (50M / 1M * Rate1 + (PaidRequests - 50M) / 1M * Rate2)`.
   • CPU Time: `PaidCpuTime = MAX(0, MonthlyCpuTimeMs – FreeCpuTimeMs)`. Cost = `PaidCpuTime / 1M * CpuRate`.
   • `WorkersComputeCost = RequestsCost + CpuTimeCost`.
2. Workers KV Cost:
   • Reads: `PaidKvReads = MAX(0, KvReads – FreeKvReads)`. Cost is tiered: `(PaidKvReads <= 10M) ? (PaidKvReads * ReadRate1) : (10M * ReadRate1 + (PaidKvReads - 10M) * ReadRate2)`.
   • Writes: `PaidKvWrites = MAX(0, KvWrites – FreeKvWrites)`. Cost is tiered: `(PaidKvWrites <= 1M) ? (PaidKvWrites * WriteRate1) : (1M * WriteRate1 + (PaidKvWrites - 1M) * WriteRate2)`.
   • Storage: `PaidKvStorage = MAX(0, KvStorageGb – FreeKvStorageGb)`. Cost = `PaidKvStorage * StorageRate`.
   • `KvCost = KvReadsCost + KvWritesCost + KvStorageCost`.
3. Durable Objects Cost:
   • Active Objects: `PaidDoActiveObjects = MAX(0, DoActiveObjects – FreeDoActiveObjects)`. Cost = `PaidDoActiveObjects * ActiveObjectRate`.
   • Requests: `PaidDoRequests = MAX(0, DoRequests – FreeDoRequests)`. Cost = `PaidDoRequests / 1M * RequestRate`.
   • Storage: `PaidDoStorage = MAX(0, DoStorageGb – FreeDoStorageGb)`. Cost = `PaidDoStorage * StorageRate`.
   • `DoCost = DoActiveObjectsCost + DoRequestsCost + DoStorageCost`.
4. R2 Storage & Operations Cost:
   • Class A Ops: `PaidR2ClassA = MAX(0, R2ClassAOps – FreeR2ClassAOps)`. Cost = `PaidR2ClassA / 1M * ClassARate`.
   • Class B Ops: `PaidR2ClassB = MAX(0, R2ClassBOps – FreeR2ClassBOps)`. Cost = `PaidR2ClassB / 1M * ClassBRate`.
   • Storage: `PaidR2Storage = MAX(0, R2StorageGb – FreeR2StorageGb)`. Cost = `PaidR2Storage * StorageRate`.
   • `R2Cost = R2ClassACost + R2ClassBCost + R2StorageCost`.
5. Egress Bandwidth Cost:
   • `PaidEgress = MAX(0, EgressGb – FreeEgressGb)`. Cost = `PaidEgress * EgressRate`.
6. Total Cost: `TotalCost = WorkersComputeCost + KvCost + DoCost + R2Cost + EgressCost`.
7. Free Tier Savings: This is calculated by summing up the costs if there were no free tiers, then subtracting the `TotalCost`.

Variable Explanations and Table:

The Cloudflare Workers Pricing Calculator relies on several key variables, each representing a specific aspect of your usage on the Cloudflare platform.

Key Variables for Cloudflare Workers Pricing Calculation

Variable	Meaning	Unit	Typical Range
Monthly Workers Requests	Number of invocations for your Workers scripts.	Requests	1,000 to 1,000,000,000+
Monthly Workers CPU Time	Total processing time consumed by Workers.	Milliseconds (ms)	1,000 to 10,000,000,000+
Monthly Workers KV Reads	Data read operations from Workers KV.	Reads	1,000 to 100,000,000+
Monthly Workers KV Writes	Data write operations to Workers KV.	Writes	100 to 10,000,000+
Monthly Workers KV Stored Data	Total data size stored in Workers KV.	Gigabytes (GB)	0.1 to 100+
Monthly Durable Objects Active Objects	Number of concurrently active Durable Objects.	Objects	1 to 1,000+
Monthly Durable Objects Requests	Requests made to Durable Objects.	Requests	1,000 to 100,000,000+
Monthly Durable Objects Stored Data	Total data size stored by Durable Objects.	Gigabytes (GB)	0.1 to 100+
Monthly R2 Class A Operations	Write and list operations for R2 storage.	Operations	1,000 to 10,000,000+
Monthly R2 Class B Operations	Read operations for R2 storage.	Operations	1,000 to 100,000,000+
Monthly R2 Stored Data	Total data size stored in R2 buckets.	Gigabytes (GB)	1 to 1,000+
Monthly Egress Bandwidth	Data transferred out from Cloudflare (excluding R2).	Gigabytes (GB)	1 to 1,000+

Practical Examples: Real-World Cloudflare Workers Cost Scenarios

To illustrate how the Cloudflare Workers Pricing Calculator works, let’s consider a couple of practical scenarios with realistic numbers.

Example 1: Small Blog with Dynamic Content and Edge Caching

Imagine a small blog that uses Cloudflare Workers to serve dynamic content, cache API responses, and handle some authentication logic. It also uses Workers KV for configuration and R2 for media storage.

• Monthly Workers Requests: 5,000,000
• Monthly Workers CPU Time: 50,000,000 ms (average 10ms per request)
• Monthly Workers KV Reads: 15,000,000
• Monthly Workers KV Writes: 500,000
• Monthly Workers KV Stored Data: 2 GB
• Monthly Durable Objects Active Objects: 0 (not used)
• Monthly Durable Objects Requests: 0 (not used)
• Monthly Durable Objects Stored Data: 0 GB (not used)
• Monthly R2 Class A Operations: 200,000
• Monthly R2 Class B Operations: 15,000,000
• Monthly R2 Stored Data: 50 GB
• Monthly Egress Bandwidth: 20 GB

Calculator Output Interpretation:

Using the Cloudflare Workers Pricing Calculator with these inputs, the estimated costs would be:

• Workers Compute Cost: ~$1.50 (4M paid requests @ $0.30/M, 49M paid CPU ms @ $0.000015/M ms)
• Workers KV Cost: ~$4.50 (5M paid reads @ $0.0000003/read, 0 paid writes, 1GB paid storage @ $0.03/GB)
• Durable Objects Cost: $0.00
• R2 Storage & Ops Cost: ~$0.69 (0 paid Class A, 5M paid Class B @ $0.36/M, 40GB paid storage @ $0.015/GB)
• Egress Bandwidth Cost: ~$0.45 (10GB paid @ $0.045/GB)
• Total Estimated Monthly Cost: ~$7.14
• Estimated Free Tier Savings: ~$10.00+

This example shows how a moderately active application can still maintain very low costs on Cloudflare Workers, leveraging the generous free tiers.

Example 2: High-Traffic API Backend with Durable Objects and R2

Consider a high-traffic API backend that uses Workers for routing and business logic, Durable Objects for stateful coordination, and R2 for large asset storage, with significant data transfer.

• Monthly Workers Requests: 75,000,000
• Monthly Workers CPU Time: 750,000,000 ms (average 10ms per request)
• Monthly Workers KV Reads: 20,000,000
• Monthly Workers KV Writes: 2,000,000
• Monthly Workers KV Stored Data: 10 GB
• Monthly Durable Objects Active Objects: 200
• Monthly Durable Objects Requests: 10,000,000
• Monthly Durable Objects Stored Data: 5 GB
• Monthly R2 Class A Operations: 5,000,000
• Monthly R2 Class B Operations: 50,000,000
• Monthly R2 Stored Data: 500 GB
• Monthly Egress Bandwidth: 200 GB

Calculator Output Interpretation:

Inputting these values into the Cloudflare Workers Pricing Calculator would yield:

• Workers Compute Cost: ~$16.50 (50M paid requests @ $0.30/M + 24M paid requests @ $0.15/M, 749M paid CPU ms @ $0.000015/M ms)
• Workers KV Cost: ~$1.50 (10M paid reads @ $0.00000015/read, 1M paid writes @ $0.00000025/write, 9GB paid storage @ $0.03/GB)
• Durable Objects Cost: ~$10.00 (150 paid active objects @ $0.000005/object, 9M paid requests @ $0.50/M, 4GB paid storage @ $0.03/GB)
• R2 Storage & Ops Cost: ~$10.05 (4M paid Class A @ $4.50/M, 40M paid Class B @ $0.36/M, 490GB paid storage @ $0.015/GB)
• Egress Bandwidth Cost: ~$8.55 (190GB paid @ $0.045/GB)
• Total Estimated Monthly Cost: ~$46.60
• Estimated Free Tier Savings: ~$20.00+

This example demonstrates that even with substantial usage across multiple services, Cloudflare Workers can remain highly cost-effective, especially compared to traditional server infrastructure. The Cloudflare Workers Pricing Calculator helps in understanding these cost drivers.

How to Use This Cloudflare Workers Pricing Calculator

Using the Cloudflare Workers Pricing Calculator is straightforward and designed for quick, accurate cost estimations. Follow these steps to get your personalized Cloudflare Workers cost projection:

Step-by-Step Instructions:

1. Identify Your Usage Metrics: Before you begin, gather your estimated monthly usage for each Cloudflare Workers component. This includes:
   • Monthly Workers Requests
   • Monthly Workers CPU Time (in milliseconds)
   • Monthly Workers KV Reads, Writes, and Stored Data (in GB)
   • Monthly Durable Objects Active Objects, Requests, and Stored Data (in GB)
   • Monthly R2 Class A Operations, Class B Operations, and Stored Data (in GB)
   • Monthly Egress Bandwidth (in GB)

   If you’re unsure, start with conservative estimates or use the default values provided by the Cloudflare Workers Pricing Calculator as a baseline.

2. Input Your Values: Enter your estimated numbers into the corresponding input fields in the calculator section. The calculator updates in real-time as you type.
3. Observe Real-time Results: As you adjust the inputs, the “Total Estimated Monthly Cost” and the breakdown of costs for each service (Workers Compute, KV, Durable Objects, R2, Egress) will update instantly.
4. Review the Cost Breakdown Chart: The dynamic bar chart provides a visual representation of how each service contributes to your total cost, helping you identify primary cost drivers.
5. Examine the Detailed Pricing Table: Below the calculator, a table outlines the specific free tiers and paid rates used in the calculations, offering full transparency.
6. Use the “Reset” Button: If you want to start over or return to the default values, click the “Reset” button.
7. Copy Results: Click the “Copy Results” button to easily copy the main results and key assumptions to your clipboard for sharing or record-keeping.

How to Read Results:

• Total Estimated Monthly Cost: This is your primary result, indicating the overall projected cost for your Cloudflare Workers usage.
• Intermediate Costs: Each service (Workers Compute, KV, Durable Objects, R2, Egress) has its own cost displayed. This helps you understand where your money is going.
• Estimated Free Tier Savings: This value shows how much you save by utilizing Cloudflare’s free tiers, highlighting the platform’s cost-effectiveness for smaller workloads.

Decision-Making Guidance:

The Cloudflare Workers Pricing Calculator is a powerful tool for informed decision-making. If your estimated costs are higher than expected, review the cost breakdown to pinpoint the most expensive components. You might then consider optimizing your code to reduce CPU time, implementing more aggressive caching to lower requests, or optimizing data storage strategies. Conversely, if costs are very low, it confirms Cloudflare Workers as a highly economical choice for your workload.

Key Factors That Affect Cloudflare Workers Pricing Results

Understanding the factors that influence your Cloudflare Workers costs is crucial for effective budget management and optimization. The Cloudflare Workers Pricing Calculator takes all these into account.

1. Monthly Workers Requests: The number of times your Workers scripts are invoked. High request volumes, especially beyond the free tier, directly increase costs. Optimizing caching strategies can significantly reduce this.
2. Monthly Workers CPU Time: This is the total time your Workers spend executing code. Complex computations, extensive data processing, or long-running tasks will consume more CPU time, leading to higher costs. Efficient code and offloading heavy tasks can help.
3. Workers KV Operations and Storage: For applications relying on key-value storage, the number of reads and writes, along with the total data stored, are significant cost drivers. Frequent updates or large datasets in KV can add up.
4. Durable Objects Usage: If your application uses Durable Objects for stateful logic, the number of active objects, requests to those objects, and their stored data contribute to the cost. Designing efficient Durable Objects that minimize active time and requests is key.
5. R2 Storage and Operations: Cloudflare R2, their S3-compatible object storage, charges for data stored and for Class A (writes, list) and Class B (reads) operations. Large files, frequent uploads, or high read volumes will impact this. R2 has no egress fees, which is a major cost-saving factor compared to other cloud storage.
6. Egress Bandwidth: While R2 has free egress, other services on Cloudflare Workers might incur egress charges for data transferred out of Cloudflare’s network. Applications serving large amounts of data directly from Workers or other Cloudflare services will see this cost.
7. Free Tier Utilization: Cloudflare offers generous free tiers for all its Workers-related services. Maximizing the use of these free allowances before incurring paid usage is the most effective way to keep costs down, especially for smaller projects. The Cloudflare Workers Pricing Calculator clearly shows your free tier savings.
8. Tiered Pricing Structure: Many Cloudflare services, like Workers requests and KV operations, have tiered pricing, meaning the cost per unit decreases as your usage scales up. This makes the platform more economical for high-volume applications.

Frequently Asked Questions (FAQ) About Cloudflare Workers Pricing

Q: Is Cloudflare Workers truly free for small projects?

A: Yes, Cloudflare Workers offers a very generous free tier that includes 1 million requests and 1 million milliseconds of CPU time per month, along with free tiers for Workers KV, Durable Objects, R2, and egress bandwidth. Many small projects can operate entirely within these free limits. Our Cloudflare Workers Pricing Calculator helps you verify if your usage falls within the free tier.

Q: How does CPU time differ from requests in Cloudflare Workers pricing?

A: Requests count each time your Worker is invoked. CPU time measures the actual processing time your Worker spends executing code. A Worker might handle many requests but consume little CPU time if it’s mostly doing simple tasks or serving cached responses. Conversely, a complex Worker might consume significant CPU time per request. Both are billed separately after their respective free tiers.

Q: Are there hidden fees with Cloudflare Workers?

A: Cloudflare’s pricing is generally transparent. However, costs can seem “hidden” if users don’t account for all components, such as Workers KV operations, Durable Objects usage, or egress bandwidth from services other than R2. The Cloudflare Workers Pricing Calculator aims to make all these components explicit.

Q: How can I reduce my Cloudflare Workers costs?

A: Optimize your Worker code for efficiency to reduce CPU time, implement aggressive caching to minimize requests, use Workers KV and Durable Objects judiciously, and leverage R2 for object storage to benefit from its free egress. Regularly monitor your usage through the Cloudflare dashboard and use this Cloudflare Workers Pricing Calculator for forecasting.

Q: Does Cloudflare R2 have egress fees?

A: No, one of the significant advantages of Cloudflare R2 is that it has zero egress fees. This makes it a highly cost-effective solution for storing and serving large amounts of data, especially for applications with global users. This is factored into the Cloudflare Workers Pricing Calculator.

Q: What are Durable Objects, and how do they impact pricing?

A: Durable Objects provide strongly consistent, low-latency storage for individual objects or entities, enabling stateful serverless applications. Their pricing is based on the number of active objects, requests to those objects, and the data stored. They are ideal for managing unique, isolated state, but their usage should be optimized to control costs.

Q: Can I set spending limits for Cloudflare Workers?

A: Cloudflare provides billing alerts and usage monitoring tools in its dashboard, allowing you to track your consumption and set notifications for when you approach certain thresholds. While direct hard spending limits might not be available for every service, these tools help prevent unexpected overages.

Q: How accurate is this Cloudflare Workers Pricing Calculator?

A: This Cloudflare Workers Pricing Calculator is designed to be highly accurate based on Cloudflare’s publicly available pricing as of its last update. However, actual costs may vary slightly due to rounding, specific billing cycles, or future changes in Cloudflare’s pricing structure. It provides a strong estimate for planning purposes.

Related Tools and Internal Resources for Cloudflare Workers Cost Optimization

To further enhance your understanding and optimization of Cloudflare Workers costs, explore these related resources:

• Cloudflare Workers Getting Started Guide: A comprehensive guide to deploying your first serverless functions on Cloudflare’s edge network.
• Serverless Cost Optimization Strategies: Learn general best practices for reducing expenses across various serverless platforms, including Cloudflare Workers.
• Cloudflare R2 Pricing Explained: A deep dive into R2’s cost model, highlighting its advantages for object storage without egress fees.
• Durable Objects Deep Dive: Understand the architecture and use cases for Cloudflare Durable Objects, and how to manage their costs effectively.
• Workers KV Best Practices: Tips and tricks for efficient usage of Workers KV, minimizing reads, writes, and storage costs.
• Benefits of Edge Computing: Explore the performance, security, and cost advantages of running your applications at the edge with Cloudflare Workers.