What is Cloudflare Pages in October 2026?
Cloudflare Pages is Cloudflare’s Git-connected hosting for static sites and full-stack apps. Static files are served from Cloudflare’s network, and server code runs as Pages Functions, which are Workers underneath. Their usage counts against your Workers plan quota.
One fact changes how we plan new projects. Cloudflare’s own migration guide describes Workers as having a “distinctly broader set of features” than Pages and documents how to move a Pages project to Workers with static assets. Pages still works and is still the simplest route for a plain static site. For anything that will grow server logic, we check whether to start on Workers instead.
What do we deploy there?
- Astro and other static sites with a headless CMS, where speed and low running cost matter more than platform features. See our Astro services.
- High-traffic content sites, such as documentation and media, where almost every request is cacheable.
- Small full-stack apps that use Functions with KV, D1 or R2 bindings: forms, lightweight APIs, auth callbacks.
- Next.js on Workers, when the team accepts the adapter route and wants Cloudflare pricing. We test this per project because the Next.js feature surface matters. Compare with our Next.js work.
How do builds and previews work?
Pushing to the production branch deploys it, and every other branch and pull request gets a preview URL. Cloudflare’s limits page lists builds per month by plan: 500 on Free, 5,000 on Pro and 20,000 on Business. A site is limited to 20,000 files on Free, and a single asset can be at most 25 MiB. Larger files go to R2.
Configuration lives in wrangler.toml or wrangler.jsonc, with bindings for KV, D1, R2 and secrets declared in code. We keep tests in GitHub Actions and let Cloudflare build only after checks pass. Preview environments use separate bindings, so a test branch never writes to production data.
Edge and serverless functions
Pages Functions use file-based routing under a functions/ folder, and Workers run on V8 isolates, so there is no container cold start. The limits differ from Node-based hosts: you work with web-standard APIs, not the full Node ecosystem, though many Node modules now run through compatibility flags.
According to Cloudflare’s pricing page, the Workers Free plan allows 100,000 requests per day and 10 ms of CPU time per invocation. Workers Paid starts at $5 per month and includes 10 million requests and 30 million CPU milliseconds per month, with overage at $0.30 per million requests. Requests for static assets are free and unlimited on both plans, and the paid plan has no egress or bandwidth charges.
We use Functions for form handling, redirects with logic, geo or header-based rewrites, and API routes that read from KV or D1.
Cost at scale
Cost on Cloudflare tracks CPU time and request count for dynamic routes, not bandwidth. A site that is 95% static assets costs close to nothing as traffic grows. A site that renders every page in a Worker pays per request and per CPU millisecond, so we cache rendered output and keep database calls short. This is the opposite of metering on bandwidth, where heavy media pages cost most.
Usage-based bills still need alerts. We set budgets, review analytics monthly and track which routes consume CPU.
When do we pick another host?
- Next.js with ISR, image optimisation and middleware on the framework’s fastest path: Vercel. Our Vercel vs Netlify comparison sets out what that integration buys.
- Forms, identity add-ons and many frameworks under one UI: Netlify.
- Heavy Node dependencies, long jobs, relational databases with many connections: containers or a managed cluster from our DevOps support team.
How do we migrate?
From Vercel or Netlify, we translate redirects and headers into _redirects and _headers files, rewrite functions to the Workers API, recreate secrets and bindings, and test every route on a preview domain. DNS is easiest when the zone is already on Cloudflare. Pages can serve custom domains outside Cloudflare zones and Workers cannot, so check that before moving a project to Workers.
From Pages to Workers, we follow Cloudflare’s guide: replace the output setting with an assets directory, set 404 handling explicitly, compile functions/ and move CI to Workers Builds. If you need an engineer for this, hire a DevOps engineer or start at Cloud and DevOps.