Free Cloudflare Workers Cost Calculator

• The free tier includes 100K requests/day (~3M/month) with 10ms CPU limit — enough for most hobby projects and MVPs
• Workers Paid plan at $5/month includes 10M requests — most startups stay under $10/month total
• R2 has zero egress fees, making it dramatically cheaper than S3 for read-heavy workloads
• CPU time (not wall-clock time) is what's billed — a Worker waiting on fetch() doesn't consume CPU
• At scale (1B requests/month), Workers costs ~$0.30/million requests — cheaper than Lambda, Vercel, and most alternatives

Use Cases

Frequently Asked Questions

How much does Cloudflare Workers cost?

Workers has a free tier (100K requests/day, 10ms CPU limit) and a paid plan at $5/month that includes 10M requests and $0.30 per additional million. CPU time costs $0.02 per million milliseconds. For most startups serving under 10M requests/month with simple Workers, the total cost is just $5/month. At 100M requests/month with 5ms avg CPU, expect ~$32/month.

Is Cloudflare Workers free?

Yes, there's a generous free tier: 100,000 requests per day (~3M/month), 10ms CPU time limit per invocation, and 100K KV reads per day. This is enough for most personal projects, MVPs, and low-traffic sites. You only need the $5/month paid plan when you need more than 10ms CPU time, higher request limits, or access to Durable Objects.

What is the difference between CPU time and wall-clock time?

CPU time is the time your Worker actively uses the CPU (computation). Wall-clock time includes waiting for external I/O (fetch requests, KV reads, database queries). Workers bills on CPU time, not wall-clock time. So a Worker that takes 200ms wall-clock (190ms waiting for an API + 10ms CPU) only bills for 10ms. This makes Workers very cost-effective for I/O-heavy workloads.

How does R2 pricing compare to S3?

R2 is significantly cheaper than S3 for most workloads because of zero egress fees. S3 charges $0.09/GB for data transfer out — for a site serving 1TB/month, that's $90 in egress alone. R2: $0. Storage is also cheaper: R2 at $0.015/GB vs S3 Standard at $0.023/GB. The only area where S3 wins is ecosystem breadth and advanced features like S3 Object Lambda.

When should I use KV vs D1 vs Durable Objects?

KV: Read-heavy, eventually consistent data (config, feature flags, cached content). D1: Relational data with SQL queries (user profiles, products, analytics). Durable Objects: Stateful, strongly consistent, real-time (WebSocket rooms, counters, rate limiters, collaborative editing). Rule of thumb: if you need SQL, use D1. If you need real-time state, use Durable Objects. For everything else, start with KV.

How does Workers compare to AWS Lambda?

Workers is cheaper (10M requests for $5 vs Lambda's ~$18-30), has zero cold starts (Lambda can take 100-500ms), deploys globally by default (Lambda is single-region), and has zero egress fees with R2. Lambda advantages: longer execution time (15 min vs 30s), more memory options, larger ecosystem, and direct integration with AWS services. For edge/API workloads, Workers wins on cost and latency.

What is the CPU time limit on Workers?

Free plan: 10ms CPU time per invocation. Paid plan: 30 seconds (Standard) or 15 minutes (Unbound, now deprecated in favour of Standard). Note: this is CPU time, not wall-clock time. A Worker can run for minutes of wall-clock time (waiting for fetch responses) while only using milliseconds of CPU. Most API Workers use 1-10ms CPU time.

How do Durable Objects pricing work?

Durable Objects have three billing dimensions: Requests ($0.15/million after 1M included), Wall-clock duration ($12.50/million seconds after 400K seconds included), and Storage ($0.20/GB after 1GB included). They're priced higher than stateless Workers because they maintain state and provide strong consistency. Best for: WebSocket servers, collaborative apps, rate limiters, and any use case requiring coordinated state.

Can I use this calculator for Cloudflare Pages Functions?

Partially. Pages Functions run on the Workers runtime with the same pricing model for the paid plan. Free tier for Pages is different (limited by builds and bandwidth rather than requests). For the request/CPU pricing portion, this calculator applies directly to Pages Functions. The KV, R2, and DO pricing is identical.

What happens if I exceed the free tier?

On the free plan, requests beyond 100K/day are dropped (return errors). Your Worker doesn't automatically upgrade or incur charges. On the paid plan, you're billed for usage beyond included allowances at the per-unit rates. There are no surprise bills on the free plan — but your users will see errors. Set up usage notifications in the Cloudflare dashboard to monitor approach to limits.

How accurate is this calculator?

This calculator uses Cloudflare's published 2026 pricing and provides estimates accurate to ±10% for standard workloads. Actual costs may vary due to: rounding in Cloudflare's billing, sub-request costs (subrequests to other Workers), Cron Triggers billing, and any custom enterprise pricing. For production budgeting, use this as a starting estimate and compare against your first month's actual bill.

Is Workers good for full-stack applications?

Yes. Cloudflare's stack covers full-stack: Workers (compute), D1 (SQL database), KV (key-value store), R2 (object storage), Durable Objects (stateful compute), Queues (async jobs), and Pages (static hosting). Frameworks like Hono, Remix, and Astro have first-class Workers support. The main limitation is the 128MB memory limit and 30s CPU time — not suitable for heavy computation or ML inference.