Cloudflare Pages review

Cloudflare Pages is Cloudflare’s option for serving prebuilt websites, especially static sites. A Reddit commenter describes the split this way: Pages serves static content, while Workers runs code when a request comes in. Pages can also use Functions, which that commenter says run on Workers, for server-side behavior.

Pages sits inside a larger Cloudflare platform, not a standalone website builder. Cloudflare’s homepage describes a global network for running applications and code, securing traffic, and connecting users, devices, and data. It lists developer tools, compute and storage, CDN, and security services, including Workers, Durable Objects, Workers KV, R2, and SQL storage. The homepage also lists Zero Trust and AI services.

That breadth matters if you want to add backend services over time. But for a simple portfolio or blog, the practical question is narrower: can you host the static output affordably, and what will server-side features cost?

The clearest case for Pages is a static site that needs inexpensive hosting and a global delivery network. Cloudflare’s homepage says its network spans 335+ cities and lists CDN, DDoS mitigation, SSL, WAF, and bot protection. Its Free option lists unmetered DDoS protection, CDN, Universal SSL, a free managed ruleset, and a web application firewall.

Cost is attractive at the entry level. The published product information lists a free tier, with paid compute starting at $5 per month. A Reddit commenter describes Pages as including unlimited sites, bandwidth, and requests; treat that as a user report, not a published limit we can verify from the published pricing. Another commenter recommends pairing Pages with Workers for backend functions and other Cloudflare storage products as needs grow.

That can keep a static site simple while leaving room for APIs, data storage, or AI services on the same platform. Cloudflare lists Workers, Durable Objects, Workers KV, R2, and SQL storage, plus AI inference and secure MCP portals. The trade-off is that these broader platform features are separate from the basic static-hosting case.

Pages is easiest to evaluate when the site is static. Once you need request-time code, user-specific pages, or database calls, you are evaluating Workers and related services too. Reddit commenters disagree on how to describe the free boundary: one says dynamic work is not unlimited, while another cites 100,000 free Worker requests per day. That request figure is a Reddit report, not a limit confirmed by the published pricing. Check current product documentation before planning around it.

Price labels also need care. The published pricing lists Free at $0, Pro at $20 per month billed annually or $25 monthly, and Business at $200 annually billed monthly or $250 monthly, but those plans list website security and uptime features; the material does not establish that they are Pages hosting tiers. Compute is separately described as starting at $5 per month, and Workers Builds are listed at $0.005 per build minute. Budget for the actual services you use rather than assuming a free static-site price covers server-side workloads. The sources do not publish Pages-specific caps for build minutes, files, or bandwidth.

The published pricing lists a free tier, but it does not give a Pages-specific price or clearly separate Pages hosting from Cloudflare’s other products. For websites, the listed Free plan is $0; Pro is $20 per month billed annually or $25 month to month; Business is $200 annually billed or $250 monthly. That is a substantial jump from Free to Pro, and another tenfold jump from Pro to Business at annual rates. Contract pricing is custom and billed annually.

Cloudflare’s product details also say paid compute starts at $5 per month, but don’t explain how that relates to these website plans. Workers Builds are listed separately at $0.005 per build minute. Check which charges apply to your Pages setup before budgeting: the published details don’t publish Pages limits or explain when server-side compute adds cost. Pro and Business also cost more if paid monthly; the listed annual rates require annual billing.

For a marketing site already built from static files, the move may be simpler than switching an app with server-side requirements. But the published information doesn’t document Pages’ deployment process, runtime compatibility, or migration tooling, so verify those against your app before moving. Cloudflare’s broader platform includes Workers and storage products, but that alone doesn’t confirm your existing code or data will transfer unchanged.

Before leaving, identify what needs to move: site files, code, storage, and any services tied to Cloudflare. The published material doesn’t describe data-export options or Pages-specific caps, so ask how to export your data and confirm limits in writing. That matters if you add server-side code after starting with a static site. The product notes say Pages limits aren’t clearly published; runtime needs and unclear caps are reasons to check before switching in either direction. We can’t substantiate a Reddit-driven reason people leave from the published published material.