Quick answer
Cloudflare Workers is free for up to 100,000 requests a day. The Workers Paid plan costs $5 a month and includes 10 million requests and 30 million CPU milliseconds, then $0.30 per million requests and $0.02 per million CPU ms; Cloudflare R2 storage costs $0.015 per GB-month with free egress. Playxoft's free Cloudflare cost calculator adds R2, D1, KV and the CDN from official prices checked October 14, 2026: 50 million requests at 10 ms of CPU each cost $26.40 a month.
- Workers CPU-time billing
- R2, D1 and KV
- $5 plan included usage
- Free plan check
- Compare with Lambda
- Every line explained
How to use the Cloudflare Cost Calculator
- 1Start from the Static site + API preset, or Start empty and add Workers, R2, D1 and KV one by one.
- 2Enter requests per month and the CPU time per request: the time your code computes, not the time it waits on databases or APIs.
- 3Add R2 storage and operations, D1 rows read and written, and KV reads and writes.
- 4Read the Cloudflare total first, with AWS, Google Cloud and Azure priced for the same workload below.
- 5Open Cost breakdown to see what the $5 plan already covers and what you pay beyond it.
How much does Cloudflare Workers cost per month?
The Workers Paid plan costs $5 a month per account and includes 10 million requests and 30 million CPU milliseconds. Beyond that, you pay $0.30 per million requests and $0.02 per million CPU milliseconds.
Two things make Workers billing different from every other serverless platform:
- Only CPU time is billed. Time spent waiting on a database, an API or a fetch is free. Memory is not billed either; every Worker gets 128 MB.
- Egress is free. Data sent from Workers and R2 to users costs nothing, on every plan.
So 50 million requests a month at 10 ms of CPU each cost $26.40: the $5 plan, 40 million extra requests and 470 million extra CPU milliseconds. Requests for static assets are free and do not count.
When do Workers cost less than Lambda, Cloud Run or Azure Functions?
It depends on how much of each request is spent waiting. For a light endpoint (100 ms per request, 128 MB, 10 ms of CPU), the always-free allowances of Lambda, Cloud Run and Azure Functions win at low volume, and Lambda's lower per-request price keeps it ahead at high volume:
| Requests a month | AWS | Google Cloud | Azure | Cloudflare |
|---|---|---|---|---|
| 1 million | $0.00 | $0.00 | $0.00 | $5.00 |
| 10 million | $1.80 | $3.20 | $1.80 | $6.40 |
| 100 million | $33.97 | $57.03 | $33.40 | $51.40 |
Now take an API that waits on a database: 300 ms per request at 512 MB, still with 10 ms of CPU. At 100 million requests a month, Lambda bills the full duration and comes to $263.13, while Workers bill only the CPU and cost $51.40. Google Cloud Run comes to $311.24 and Azure Functions to $253.40.
The rule of thumb: the more time your code spends waiting on I/O, the more Workers save. For the full head-to-head, with break-even points, see AWS Lambda vs Cloudflare Workers and Cloud Run vs Cloudflare Workers.
What do Cloudflare R2, D1 and Workers KV cost?
One $5 plan covers Workers, Workers KV and Cloudflare D1 up to their included amounts. Cloudflare R2 object storage is billed separately, with its own monthly free allowance:
| Product | Included with the $5/month Workers Paid plan | Beyond that |
|---|---|---|
| Workers requests | 10 million a month | $0.30 per million |
| Workers CPU time | 30 million ms a month | $0.02 per million ms |
| D1 rows read | 25 billion a month | $0.001 per million |
| D1 rows written | 50 million a month | $1.00 per million |
| D1 storage | 5 GB | $0.75 per GB-month |
| KV reads | 10 million a month | $0.50 per million |
| KV writes | 1 million a month | $5.00 per million |
| KV storage | 1 GB | $0.50 per GB-month |
| R2 storage (billed separately) | 10 GB free | $0.015 per GB-month |
| R2 writes / reads (billed separately) | 1M / 10M free | $4.50 / $0.36 per million |
| Egress from Workers and R2 | Unlimited | $0 |
R2 rounds usage up to the next whole unit (GB-month or million operations). D1 bills the rows a query scans, not the rows it returns, so a query that scans 1,000 rows to return 10 counts 1,000; indexes keep that number down.
What are the Cloudflare Workers free tier limits?
The free plan allows 100,000 requests a day with up to 10 ms of CPU per request. It is a hard cap, not a bill: over the limit, requests fail with an error until the next day. Workers KV on the free plan allows 100,000 reads and 1,000 writes a day, and Cloudflare D1 allows 5 million rows read and 100,000 rows written a day with 5 GB of storage.
That makes the free plan ideal for side projects and prototypes. For production traffic that must never be cut off, the $5 plan is the safer choice; the calculator tells you when your usage would also fit the free plan.
When is Cloudflare not the right fit?
Cloudflare is often the cheapest option for APIs and anything bandwidth-heavy, but it is not a drop-in replacement for a full cloud:
- No virtual machines. Long-running servers, background workers with large memory needs and most off-the-shelf software need Containers or another cloud.
- 128 MB of memory per Worker. Heavy image processing or large in-memory datasets will not fit.
- D1 databases hold up to 10 GB each. Larger datasets must be split across databases, or kept in an external PostgreSQL reached through Hyperdrive.
- KV is eventually consistent. A write can take 60 seconds or more to reach other locations, so it suits configuration and caching, not balances or inventory.
- Large media on the CDN. Under Cloudflare's terms, video and other large files must be served through paid products such as R2, Stream or Images.
Many teams get the best of both: Workers and R2 at the edge, with a database or long-running jobs on AWS, Google Cloud or Azure.
How does Cloudflare compare with AWS, Google Cloud and Azure?
Each comparison prices both clouds at three usage levels in all 12 regions and compares their features from official documentation.
- [AWS vs Cloudflare](/tools/cloud-pricing/aws-vs-cloudflare): Cloudflare charges no egress fees and bills Workers for CPU time only, while AWS offers a far wider range of services, including servers.
- [Google Cloud vs Cloudflare](/tools/cloud-pricing/google-cloud-vs-cloudflare): Cloudflare charges no egress fees and bills Workers for CPU time only, while Google Cloud runs larger, longer workloads in a single region.
- [Azure vs Cloudflare](/tools/cloud-pricing/azure-vs-cloudflare): Cloudflare charges no egress fees and no base fee for its CDN, while Azure offers servers and a broad catalog billed per region.
Service by service: AWS Lambda vs Cloudflare Workers · Google Cloud Run vs Cloudflare Workers · Amazon S3 vs Cloudflare R2 · Google Cloud Storage vs Cloudflare R2 · Amazon CloudFront vs Cloudflare CDN.
Where do these prices come from?
Every number comes from the provider's own published price list, read on October 14, 2026: the AWS Price List files, the Azure Retail Prices API, Google Cloud's pricing pages and Cloudflare's pricing documentation. Nothing is scraped from third-party sites, and each value was checked against a second official source where one exists.
- AWS: Amazon EC2 On-Demand pricing · AWS Lambda pricing · Amazon S3 pricing · Amazon RDS for PostgreSQL pricing · Amazon DynamoDB pricing · EC2 data transfer pricing · Amazon CloudFront pricing
- Google Cloud: Compute Engine VM pricing · Cloud Run pricing · Cloud Storage pricing · Cloud SQL pricing · Firestore pricing · Network (egress) pricing · Cloud CDN pricing
- Azure: Linux Virtual Machines pricing · Azure Functions pricing · Blob Storage pricing · Azure Database for PostgreSQL pricing · Cosmos DB serverless pricing · Bandwidth pricing · Azure Front Door pricing
- Cloudflare: Containers pricing · Workers pricing · R2 pricing · D1 pricing · Workers KV pricing · Cloudflare plans
Prices are in US dollars, on-demand, for Linux, with no commitments. Every figure on this page is generated from the same price snapshot as the calculator, and automated tests check each claim whenever the prices change. A month is 730 hours and 1 TB is 1,024 GB. Providers change prices from time to time, so for a purchase decision confirm the final figure in the provider's console.
Want an engineer to check your real cloud bill?
A calculator shows list prices. A real bill also carries the costs nobody planned for: servers sized for a launch that never came, test environments left running, services that talk across zones, logs nobody reads. Finding those is our day job.
Playxoft designs, builds and runs production backends on Cloudflare: real-time game services and messaging platforms on Google Cloud Run, player systems on AWS EC2 and Lambda, and edge services on Cloudflare Workers. We help teams:
- Choose the right cloud and architecture before the first bill, not after
- Cut an existing bill by rightsizing, committing where it pays and removing waste
- Migrate between clouds with a tested plan and no surprise downtime
- Deliver white-label cloud work for agencies and software studios, under your brand
Send us your architecture or last month's invoice and we will tell you, free and honestly, where the money goes and what we would change. Get a free cloud cost review or see our backend and cloud services.
Frequently asked questions
Last updated by the Playxoft engineering team.