Cloudflare Workers Pricing in 2026: Full Breakdown

At 10 million requests per month on Cloudflare Workers, you pay $5. The same volume on AWS Lambda — even after its 2024 price cut — runs roughly $2.00 in invocations alone, but add API Gateway and you are looking at $35+. That delta is why Cloudflare Workers pricing remains a recurring discussion in architecture reviews, especially for teams shipping latency-sensitive workloads at the edge. This article gives you the exact 2026 plan structures, a line-item comparison against Lambda, Vercel, and Netlify, a workload-profile decision matrix you will not find elsewhere, and a clear read on where Cloudflare's developer platform actually falls short.

Cloudflare Workers Pricing as of Q2 2026

Cloudflare consolidated its billing model in late 2025, retiring the legacy "Bundled" and "Unbound" naming. As of May 2026 the structure is straightforward:

Free Plan

100,000 requests per day. 10 ms CPU time per invocation. No charge. Workers KV includes 100,000 reads/day and 1,000 writes/day. For side projects and low-traffic APIs, this is still the most generous serverless free tier available.

Workers Paid ($5/month, billed to your account)

The $5/month baseline includes 10 million requests and 30 million CPU-milliseconds. Beyond that, additional requests cost $0.30 per million and additional CPU time costs $0.02 per million CPU-ms. Workers KV, R2, D1, and Durable Objects each carry their own metering, but the $5 covers the compute layer. Duration-based billing means you pay for actual CPU work, not wall-clock time — a meaningful distinction when your worker awaits upstream fetches.

Enterprise

Custom contracts. The notable difference: SLA-backed latency percentiles, dedicated support, and negotiable request pricing at volumes above 1 billion/month. Cloudflare does not publish these rates, but practitioners report $0.15–$0.20/million at scale as of early 2026.

Cloudflare Pages Pricing in 2026

Pages remains tightly coupled to Workers under the hood — every Pages Function is a Worker. The hosting-specific pricing:

• Free: 500 builds/month, 1 concurrent build, unlimited sites, unlimited bandwidth.
• Pro ($20/month): 5,000 builds/month, 20 concurrent builds. Includes Pages Functions at the Workers Paid rate.
• Business ($200/month): 20,000 builds/month, 20 concurrent builds, plus WAF and custom cache rules.

Unlimited bandwidth on every tier is the headline. Netlify caps its free tier at 100 GB/month and charges $55/100 GB after that. Vercel caps at 100 GB on Pro. If your static assets move serious volume, Pages pricing alone can justify the migration.

Cloudflare Workers vs AWS Lambda: 2026 Cost Comparison

The comparison only makes sense when you normalize for the same workload profile. Below is a realistic mid-scale API scenario: 50 million requests/month, average 5 ms CPU time per invocation, 128 MB memory on Lambda.

Lambda's raw compute is competitive, but API Gateway is the tax. If you can use Lambda Function URLs and skip API Gateway entirely, Lambda closes the gap to about $14/month — cheaper than Workers at this volume. The tradeoff: you lose request transformation, auth integration, and throttling controls at the gateway layer.

Cloudflare Pages vs Netlify vs Vercel for Frontend Teams

All three platforms deploy from Git, run serverless functions, and offer preview environments. The 2026 pricing differentiators that actually matter:

• Bandwidth: Cloudflare Pages unlimited on every tier. Netlify 100 GB free, then $55/100 GB. Vercel 100 GB on Pro ($20/month), then $40/100 GB.
• Build minutes: Netlify free tier gives 300 minutes/month. Pages gives 500 builds (no per-minute metering). Vercel gives 6,000 minutes on Pro.
• Edge functions: Pages Functions are Workers — same runtime, same pricing. Netlify Edge Functions run on Deno Deploy. Vercel Edge Functions run on V8 isolates but with a 30s streaming limit on Hobby.
• Framework lock-in: Vercel owns Next.js and consistently ships features that work best — or only — on their platform. If you run Next.js, Vercel gives you the smoothest path. If you do not want that coupling, Pages or Netlify keeps your options open.

Where Cloudflare Workers Falls Short

No honest review skips this part.

• CPU ceiling: 30 seconds on paid, 10 ms on free. Anything compute-heavy — image transcoding, PDF generation, ML inference — hits the wall fast. Lambda gives you 15 minutes.
• Cold-start consistency: Workers generally start in under 5 ms, but Durable Objects and D1 can add 50–200 ms on first access depending on the colo.
• Ecosystem maturity: D1 is still in open beta as of May 2026. R2 lacks lifecycle policies comparable to S3. If your stack needs transactional guarantees or cross-region replication, you are patching around gaps.
• Debugging and observability: Wrangler tail and Workers Logpush improved in 2025, but structured tracing still requires third-party collectors. Lambda's integration with CloudWatch, X-Ray, and Powertools remains deeper.

Workload-Profile Decision Matrix

This matrix maps workload characteristics to the platform that minimizes total cost of ownership, not just unit compute price.

That last row deserves expansion. When your delivery volume exceeds 25 TB/month, general-purpose serverless platforms stop being cost-efficient for asset delivery. This is where a dedicated CDN layer makes sense alongside your compute layer. BlazingCDN provides volume-based pricing starting at $4/TB ($0.004/GB) for up to 25 TB, scaling down to $2/TB at 2 PB+ — delivering fault tolerance and uptime comparable to CloudFront at a fraction of the cost. Teams like Sony use it for large-scale delivery. If your Workers handle API logic while a separate CDN handles heavy asset egress, you keep both bills lean.

FAQ

How much does Cloudflare Workers cost in 2026?

The paid plan is $5/month, which includes 10 million requests and 30 million CPU-milliseconds. Beyond that, you pay $0.30 per million requests and $0.02 per million CPU-ms. The free tier still provides 100,000 requests per day at no charge.

Is Cloudflare Workers worth it for startups?

For latency-sensitive, high-fan-out workloads with lightweight compute, yes. The included routing layer alone saves $30–50/month versus Lambda + API Gateway at moderate volumes. If your workloads are CPU-heavy or you need deep AWS ecosystem integration, Lambda remains the stronger choice.

Cloudflare Workers vs AWS Lambda — which is cheaper?

Workers is cheaper at the total-bill level for most API workloads under 100 million requests/month, primarily because Cloudflare bundles routing at no additional cost. Lambda's raw compute pricing is competitive and sometimes lower, but API Gateway adds $1.00–$1.40 per million requests on top.

Should I use Cloudflare Pages instead of Vercel in 2026?

If you run Next.js and depend on ISR, image optimization, and middleware, Vercel offers the smoothest experience. For non-Next.js frameworks (Astro, SvelteKit, Remix), Pages provides unlimited bandwidth, lower cost, and no framework lock-in. Evaluate your framework dependency first.

Does Cloudflare Pages really have unlimited bandwidth?

Yes, as of May 2026, all tiers — including free — include unlimited bandwidth for static assets served from Pages. There is no published fair-use cap, though Cloudflare reserves the right to throttle abusive patterns under their ToS section 2.8.

What to Do This Week

Pick your highest-traffic Worker or Pages project and run a cost audit. Pull your actual request count and CPU-ms from the Workers Analytics API, map it against the tables above, and compare line by line with what you are currently paying on Lambda, Vercel, or Netlify. If the delta exceeds $20/month on a single project, the migration math is already clear. If your bandwidth line item alone exceeds 25 TB, split your architecture: keep compute on Workers, move heavy delivery to a dedicated CDN, and stop subsidizing egress at serverless rates. Post your numbers — the comparison only gets useful when it is grounded in real workloads.