Cloudflare Pages vs Netlify: which should you deploy to?

This site runs on Cloudflare Pages. I have shipped client work on both platforms, and the honest answer is that for a plain static site they are close enough that the decision rarely turns on performance. It turns on how each one meters you, and on what happens when your site stops being plain.

Every limit below was checked against the vendors’ own documentation on 31 August 2026. Both platforms change their commercial terms often — verify before you commit a client to one.

What Is Actually Different Between Them?

Netlify created this category: connect a git repository, run a build, publish the output to a CDN, attach serverless functions. Cloudflare Pages does the same job, but it is a product built on top of a global network that Cloudflare already ran for other reasons.

That origin shows up everywhere. Netlify is a developer-experience company that had to acquire a delivery network. Cloudflare is a network company that added a developer experience. Neither is better in the abstract, but it explains why Netlify’s dashboard, build plugins, form handling and deploy previews feel more finished, and why Cloudflare’s bandwidth and edge compute feel like infrastructure rather than a product tier.

How Do the Free Tiers Compare?

They are no longer comparable in shape, and that is the most important thing to understand before you pick one.

Cloudflare Pages meters builds. The free plan allows 500 builds per month, one build at a time, with a 20-minute build timeout. A site can hold up to 20,000 files, and no single asset may exceed 25 MiB. Bandwidth and requests to static assets are not the counted dimension.

Netlify meters credits. Rather than a flat bandwidth allowance, usage across deploys, compute, form submissions, bandwidth and web requests draws down a monthly credit balance, with bandwidth priced at 20 credits per GB and additional credits sold in blocks. Most comparison articles still describe an older flat free tier. That model has changed, and an article still quoting it will mis-price your project.

The practical consequence: Cloudflare Pages penalises you for building often, and Netlify penalises you for being popular. A documentation site rebuilt on every commit will hit Cloudflare’s build ceiling long before it troubles any bandwidth figure. A marketing site that rebuilds weekly but attracts traffic will draw down Netlify credits while barely touching Cloudflare’s counters.

Which One Is Faster?

For static assets, not different enough to choose on. Both serve pre-built files from a CDN close to the visitor, and the numbers in benchmark posts are usually one test location on one day.

The difference that does matter is cold-start behaviour on dynamic code, and it comes from the runtimes rather than the networks.

How Do Serverless Functions Differ?

This is the real fork in the road, and it is architectural rather than commercial.

Cloudflare Pages Functions run on the Workers runtime: V8 isolates rather than containers, which is why they start effectively instantly, and why they do not hand you the full Node API surface by default. Node compatibility arrives through a flag, and packages that assume a complete Node runtime, native modules or a filesystem will need replacing.

Netlify Functions run on AWS Lambda with a real Node runtime, so the ecosystem mostly just works, at the cost of container cold starts. Netlify Edge Functions run on Deno at the edge for cases where latency matters more than compatibility.

So: if your dynamic code is small, latency-sensitive and you control its dependencies, the Workers model wins. If you are lifting existing Node code with real dependencies, Lambda will fight you less.

Is Migrating From Netlify to Cloudflare Pages Hard?

The static half is close to trivial — same repository, same build command, same output directory. The work is in everything that was not static.

Netlify-specific features do not travel. Form handling, Identity, split testing and build plugins have to be replaced rather than moved. Redirect and header syntax converts reasonably cleanly. Forms and Identity do not; those become a Worker, a third-party service, or a rethink. Budget the migration around those, not around the build.

So Which Should You Choose?

Choose Cloudflare Pages when traffic is the thing you expect to grow, when your dynamic code is small and latency matters, when you already use Cloudflare for DNS and WAF, or when you want one vendor holding the network, the compute and the storage.

Choose Netlify when build ergonomics and team workflow matter more than infrastructure economics, when you want forms, identity and split testing without building them, when your functions are lifted Node code with real dependencies, or when the people maintaining the site are not infrastructure people.

And the answer nobody selling either platform will give you: for a brochure site that changes monthly and gets modest traffic, both are free, both are fast, and the decision does not deserve a week of research. Pick the dashboard you can stand, and spend the saved week on the content, which is what actually decides whether the site works.

Working With Me

I build on both. If you are choosing a platform for a project rather than a hobby, the useful conversation is about what the site has to do in two years — who edits it, what it integrates with, and what happens when it succeeds. Book a 30-minute call and we will work out which one fits.