Cloudflare review 2026: Free vs Pro, Workers and when to pay
A desk review of Cloudflare's Free, Pro and Business plans and its Workers pricing: what the free plan covers, when Pro is worth $20, and edge compute costs.
7 min read

In this article
The short verdict: for most small websites, Cloudflare's free plan already covers the essentials: CDN, unmetered DDoS protection, Universal SSL and a free managed WAF ruleset. Upgrade to Pro when you want image optimisation, more rules and ticket support; move to Business only if you need an uptime SLA or chat support. For code at the edge, the free Workers plan suits prototypes and low-traffic tools, and the $5 Workers Paid plan is inexpensive once a project has real traffic.
This is a desk review based on Cloudflare's plans page and its developer documentation, checked on 9 October 2026. We did not run speed tests or load tests for this article, and no performance figures below were measured by us. Prices are in US dollars, exclude tax and are quoted at the time of writing (October 2026); see the Cloudflare plans page before you decide.
Two products under one account
Cloudflare sells two things that small teams often confuse:
- Application services plans (Free, Pro, Business and an Enterprise contract) that sit in front of a website you host elsewhere. You point your domain's DNS at Cloudflare and it proxies, caches and filters traffic.
- Developer platform products such as Workers, Pages, KV, D1 and R2, which run your code and store data on Cloudflare's network. These are billed separately, mostly by usage.
You can use either without the other. A WordPress site on a shared host may only need the Free application plan; a static site or API can live entirely on Workers.
Application plans at a glance (October 2026)
| Plan | Annual billing | Monthly billing | Intended for (Cloudflare's wording) |
|---|---|---|---|
| Free | $0 | $0 | Personal or hobby projects |
| Pro | $20 per month | $25 per month | Professional websites |
| Business | $200 per month | $250 per month | Small businesses |
| Enterprise (listed as "Contract") | Custom, billed annually | Custom | Mission-critical applications |
These prices are per domain, not per user, which makes Cloudflare's cost easy to predict: it does not change with team size.
What each plan includes
| Feature | Free | Pro | Business |
|---|---|---|---|
| CDN, unmetered DDoS protection, Universal SSL | Yes | Yes | Yes |
| WAF with the free managed ruleset | Yes | Yes | Yes |
| Cloudflare Rules | 70 rules and 10,000 bulk redirects | 225 rules and 25,000 bulk redirects | 450 rules and 50,000 bulk redirects |
| Image optimisation | None | Lossless image optimisation | Lossless image optimisation |
| Bot mitigation | Simple bots | Easy-to-detect bots | Sophisticated bots and basic bot analytics |
| Uptime SLA | None | None | 100%, with 1x service credits |
| Support | Community forums and docs | Tickets and forums | Tickets, chat and forums |
Is the free plan really enough?
For a blog, a brochure site or a small online shop, often yes. The parts that protect a site from being knocked offline or served without HTTPS are on every plan, including Free. The free plan's 70 rules are enough for common redirects, cache settings and a handful of security rules. What Free lacks is mainly convenience and assurance: image optimisation, more nuanced bot handling and someone to open a ticket with.
When Pro earns its $20
Pro is worth considering when images are a large share of your page weight and you do not already optimise them at build time, when you need more than 70 rules, or when a business owner wants a support channel other than a community forum. If your framework or host already optimises images, Pro's main benefit shrinks.
When Business makes sense
Business costs ten times Pro. The clearest reasons to pay it are the 100% uptime SLA with service credits, chat support and stronger bot mitigation. A small business that loses real revenue during an outage, or that faces persistent scraping or credential-stuffing bots, can justify it; most small sites cannot.

Workers: pricing for code at the edge
Workers runs JavaScript, TypeScript and other languages compiled to WebAssembly on Cloudflare's network. The pricing is short enough to quote in full.
| Workers Free | Workers Paid | |
|---|---|---|
| Base charge | None | $5 per month minimum per account |
| Requests | 100,000 per day | 10 million per month included, then $0.30 per additional million |
| CPU time | 10 ms per invocation | 30 million CPU milliseconds per month included, then $0.02 per additional million |
| Static asset requests | Free and unlimited | Free and unlimited |
Cloudflare bills CPU time rather than wall-clock duration, and the pricing page says there is no charge or limit for duration. A Worker that spends most of its time waiting for a database or a third-party API therefore costs less than its response time suggests. The paid plan allows up to five minutes of CPU time per invocation, with a 30-second default.
Getting started takes three commands, according to Cloudflare's guide:
npm create cloudflare@latest -- my-first-worker
npx wrangler dev # run locally
npx wrangler deploy # publish to Cloudflare
The generated Worker is a single exported handler:
export default {
async fetch(request, env, ctx) {
return new Response("Hello World!");
},
};
Storage: KV, D1 and R2 free allowances
| Product | Free allowance | Paid pricing highlights |
|---|---|---|
| KV (key-value) | 100,000 reads and 1,000 writes per day, 1 GB stored | 10 million reads and 1 million writes per month included; $0.50 per extra million reads |
| D1 (SQLite database) | 5 million rows read and 100,000 rows written per day, 5 GB total | 25 billion rows read and 50 million rows written per month included |
| R2 (object storage) | 10 GB-month of storage, 1 million Class A and 10 million Class B operations per month | $0.015 per GB-month; no egress charges |
R2's lack of egress fees is the line most worth noticing. For media-heavy sites, outbound bandwidth is often the largest storage cost elsewhere.
Pages limits for static sites
Cloudflare Pages remains available for Git-connected static sites. Its documented limits on the Free plan are 500 builds per month, one concurrent build, a 20-minute build timeout, 20,000 files per site and 25 MiB per file. Pro raises builds to 5,000 per month and Business to 20,000. Pages Functions are billed as Workers.

Strengths
- A strong free tier. DDoS protection, SSL, a CDN and a managed WAF ruleset cost nothing.
- Predictable pricing. Application plans are per domain, and Workers pricing is a short list of published unit prices.
- Cheap edge compute. The $5 Workers Paid plan includes 10 million requests, and static asset requests are free.
- No egress fees on R2. Useful for downloads, images and backups.
Weaknesses and things to watch
- DNS change required. Application plans typically mean moving your domain's DNS to Cloudflare, which some organisations need to approve.
- Big jump to Business. There is nothing between $20 and $200 per month for teams that want an SLA.
- Edge runtime constraints. Workers is not a full Node.js server; check the runtime's compatibility with any library you depend on before you migrate.
- Configuration depth. Rules, caching and security settings are powerful, and a mistaken rule can break a site; changes deserve the same review as code.
Who should choose which
- Personal sites, blogs and small business websites: Free.
- Image-heavy sites, agencies managing client sites, or anyone who wants ticket support: Pro.
- Revenue-critical sites that need an SLA or face serious bot traffic: Business.
- Developers building APIs, webhooks or small full-stack apps: Workers Free to start, Workers Paid once daily requests or CPU limits bite.
Alternatives
For a CDN in front of an existing site, Fastly, Akamai and Amazon CloudFront are the established alternatives, the latter fitting best when you already host on AWS. For deploying front-end frameworks with Git-based previews, Vercel and Netlify are the obvious comparisons, and DigitalOcean App Platform suits teams that want conventional servers and managed databases. Bunny.net is a lower-cost CDN option that many small sites consider.
Summary
Cloudflare is one of the few infrastructure services where the free plan is a serious product. Start there, add Pro when image optimisation, rules or support justify $20 a month, and treat Business as an SLA purchase. On the developer side, Workers' published prices make it easy to estimate costs before you commit, and R2's free egress is a real differentiator for storage-heavy projects.
Frequently asked questions
Is Cloudflare's free plan good enough for a business website?
For many small sites, yes. The Free plan includes the CDN, unmetered DDoS protection, Universal SSL, the free managed WAF ruleset and 70 rules. It lacks image optimisation, an uptime SLA and ticket support.
How much does Cloudflare Pro cost?
At the time of writing (October 2026), Cloudflare lists Pro at $20 per month billed annually or $25 billed monthly, per domain.
What does Cloudflare Workers cost?
Workers Free allows 100,000 requests per day. Workers Paid has a $5 monthly minimum and includes 10 million requests and 30 million CPU milliseconds per month, then $0.30 per additional million requests and $0.02 per additional million CPU milliseconds.
Are static assets on Workers billed?
No. Cloudflare's Workers pricing page says requests to static assets are free and unlimited on both the Free and Paid plans.
Which Cloudflare plan includes an uptime SLA?
Business and Enterprise. Business lists a 100% uptime SLA with 1x service credits; Free and Pro have no SLA.
Does Cloudflare R2 charge for egress?
No. Cloudflare's pricing documentation states that R2 has no egress charges. Storage is $0.015 per GB-month beyond the free 10 GB-month.
Your next customer could start right here.
Introduce your tool, product or business to readers exploring technology.
Explore placements and request a private quote
Sources
- Cloudflare plans — Cloudflare
- Network and CDN plans (Markdown version of the plans page) — Cloudflare
- Workers pricing — Cloudflare Docs
- Pages limits — Cloudflare Docs
- Get started with Workers (CLI) — Cloudflare Docs
Written with substantial AI assistance. Facts checked against cited sources. Editorial policy.
Comments
No comments yet. Be the first to join the conversation.
Leave a comment
Every comment is read by a moderator before it appears. Your email address is never published; it is used only to contact you about this comment.
More from Cloudsoft Zone

Product reviewReviews
Postman review 2026: plans, AI credits, and running collection tests in CI
A documentation-based review of Postman in October 2026: what each plan includes, how AI credits are metered, single-user limits, and a hands-on example that adds tests to a collection and runs them in GitHub Actions.
By Cloudsoft Zone

ComparisonReviews
Cursor vs GitHub Copilot in 2026: plans, usage limits and project rules
Cursor and GitHub Copilot compared from their published plans and documentation: prices, how AI usage is metered, privacy controls, editor support, and how to give both tools the same repository rules.
By Cloudsoft Zone

ComparisonReviews
Vercel vs DigitalOcean App Platform: pricing, limits and which apps suit each
Vercel and DigitalOcean App Platform compared from their pricing pages and documentation: free-tier rules, usage-based versus per-container billing, function limits, workers and a decision checklist for October 2026.
By Cloudsoft Zone
