Back in early 2023 a client of mine, a mid-sized e-commerce brand based in Manchester, was paying £180 a month on bandwidth overages with their existing host. I moved them to Cloudflare Pages in an afternoon. Their next invoice: £0 in hosting costs. That kind of result sticks with you.
I've spent the better part of nine years at Seahawk Media building and deploying static sites. Over 12,000 of them. And the Cloudflare Pages vs Netlify question comes up constantly from agency owners, freelancers, people who just want a fast, affordable place to ship their Next.js or Astro projects without drama. So I'm going to give you my honest take, not a feature table copied from a marketing page.
---
The Free Tier Reality Check
Everyone leads with the free tier comparison. Fair enough, it's where most people start.
Netlify's free tier gives you 100GB of bandwidth per month and 300 build minutes. Sounds fine until your site gets a Reddit hug of death or you're running CI on a monorepo with five packages. I've watched 300 build minutes evaporate in three days on a modestly active project. After that you're looking at Netlify's Pro plan at $19/month per member, which adds up fast if you're running a small team.
Cloudflare Pages, on the other hand, offers unlimited bandwidth on the free tier. Unlimited. I know that sounds like marketing copy but it's genuinely true and it genuinely matters. Build minutes are capped at 500 per month (slightly better than Netlify), and you get unlimited sites. That Manchester client I mentioned? Unlimited bandwidth was the entire point.
The catch with Cloudflare Pages free tier: you get 1 concurrent build. If you're deploying multiple branches simultaneously, you'll queue. Netlify free gives you 1 concurrent build too, so that's a wash.
---
Build Performance and Deploy Speed
This is where things get interesting.
Netlify has had years to refine its build system. Their build plugins ecosystem is genuinely impressive. Things like the Essential Next.js plugin, the Gatsby cache plugin, the image optimisation pipeline, Netlify has tooling that Cloudflare Pages simply doesn't match yet. If you're running a complex Gatsby v5 site with tens of thousands of pages, Netlify's incremental builds and caching behaviour will save you real time.
Cloudflare Pages builds, honestly, can feel a bit raw. The build environment is solid and they've improved it dramatically since the 2021 beta days, but the plugin ecosystem isn't there. You're working with a leaner toolchain.
That said, for the majority of what I ship, which is Next.js on the App Router, Astro, or straight SvelteKit, Cloudflare Pages builds are fast enough that the difference is negligible. A typical Astro blog build on Cloudflare Pages takes under 45 seconds for me. On Netlify, similar project, similar result. You're not picking a winner here on raw build speed for most projects.
The Edge Network Difference
This is where Cloudflare Pages genuinely pulls away. Cloudflare operates one of the largest edge networks on the planet, with 300+ PoPs globally. Your static assets are served from wherever your user is, with latency numbers that are hard to argue with.
Netlify's CDN is solid. It's not slow. But it's not Cloudflare's network. I ran informal Pingdom tests on identical sites (same Astro build, same content) deployed to both platforms earlier this year. London to Sydney: Cloudflare Pages was consistently 18-25% faster on TTFB. London to São Paulo: similar story. For most UK or US clients the gap is smaller, but it's real.
---
Serverless Functions: Where Netlify Still Has an Edge
Netlify Functions (built on AWS Lambda) have been around since roughly 2018. They're mature, well-documented, and the Netlify Functions docs cover enough edge cases that I rarely need to Google beyond them. You write a file in netlify/functions/, deploy, done. Background functions, scheduled functions, streaming responses, it's all there.
Cloudflare Workers (which back Pages Functions) are architecturally different. They run on Cloudflare's V8 isolate runtime, not Node.js. That's a big deal. You don't get the full Node.js API surface. Things like fs, certain npm packages that assume a Node environment, libraries that use native bindings, they won't work without a polyfill or a rewrite.
I had a Seahawk project last year, a fintech dashboard with a serverless function that used node-postgres to connect to a Neon database. Dropped it into Cloudflare Pages Functions, spent 90 minutes debugging why it wouldn't connect, then realised the TCP socket handling was the issue in the Workers runtime. Moved it to Netlify Functions, worked in 10 minutes.
So: if your functions are simple (form handling, API proxying, basic auth), Cloudflare Pages Functions are fast and free and plenty capable. If they're doing anything Node-specific, Netlify is the safer bet.
---
Pricing at Scale
Here's the thing. Free tier comparisons are only half the story. What happens when you actually grow?
Netlify's pricing beyond the free tier:
- Starter (free): 100GB bandwidth, 300 build minutes
- Pro ($19/member/month): 400GB bandwidth, 25,000 build minutes, background functions
- Business ($99/member/month): 600GB bandwidth, SSO, advanced analytics
- Enterprise: custom pricing, custom everything
Cloudflare Pages pricing beyond the free tier:
- Free: unlimited bandwidth, 500 build minutes, 1 concurrent build
- Pro ($20/month for the Cloudflare account): unlimited bandwidth, 5,000 build minutes, 5 concurrent builds
- Business ($200/month): more Workers KV storage, more advanced features
The maths here isn't subtle. For a small agency running 20 client sites, Cloudflare's $20/month Cloudflare Pro plan covers all of them with unlimited bandwidth. On Netlify, 20 sites across multiple team members gets expensive fast.
I ran the numbers for our internal Seahawk tooling back in Q1 this year. We were spending around $140/month on Netlify across team seats and bandwidth. Moved the simpler sites (mostly marketing pages, documentation sites, portfolio builds) to Cloudflare Pages. Monthly cost dropped to $20 flat. The savings were embarrassing.
---
Developer Experience
Both platforms have good DX. Both have GitHub/GitLab/Bitbucket integrations that work reliably. Both give you preview deploys on branches and PRs, which is non-negotiable for me.
Netlify's dashboard is more polished. The form handling, the identity service, the split testing feature, Netlify has spent years building a product around the developer workflow and it shows. If you're handing login access to a less technical client, Netlify's UI will confuse them less.
Cloudflare Pages dashboard has improved but still feels like a Cloudflare product, which is to say: functional, not pretty, and buried inside the larger Cloudflare dashboard where your DNS, WAF, Workers, R2 buckets, and seventeen other things live. It's a lot. New users sometimes take 10 minutes to find where their build logs are.
Local Development
Netlify CLI (netlify dev ) is genuinely good. It proxies your functions locally, handles redirects from your netlify.toml, and mostly behaves like production. I've used it on every Netlify project for the past four years.
Cloudflare's wrangler CLI does the same for Pages Functions and Workers. It's solid too, though the local simulation of KV storage and D1 (their SQLite database) can behave slightly differently from production in ways that catch you out. Minor gripe, but worth knowing.
---
When to Pick Each One
Let me just be direct about this.
Pick Cloudflare Pages if:
- You're running marketing sites, blogs, documentation, or portfolios
- Bandwidth cost is a concern (i.e., always)
- Your serverless needs are simple
- You're already using Cloudflare for DNS (the integration is smoother)
- You want the fastest possible global TTFB
Pick Netlify if:
- Your serverless functions rely on Node.js-specific APIs
- You need Netlify's form handling or identity features without rolling your own
- Your team is less technical and the cleaner UI matters
- You're building something with complex build pipelines and need the plugin ecosystem
Honestly, for about 80% of what I build at Seahawk, Cloudflare Pages wins. The remaining 20%, mostly anything with complex backend function logic or specific client requirements around Netlify's integrated features, stays on Netlify.
---
The Stuff Nobody Talks About
A few things that don't make it into most comparisons:
- Cloudflare's R2 storage integrates natively with Pages for things like large file hosting, and R2's egress fees are zero. If you're serving assets from S3 and paying AWS data transfer fees, this alone might be worth the switch.
- Netlify's analytics (available on Pro and above) are privacy-friendly, server-side, and surprisingly useful. Cloudflare has Web Analytics too, also privacy-friendly, also free. Both are worth enabling.
- Redirects: Both platforms handle
_redirectsfiles or config-based redirects. I've had fewer weird edge cases with Cloudflare's implementation, specifically around query string passthrough, but this might just be my projects. - Custom headers: Both support them. Cloudflare's
_headersfile approach is straightforward.
One more thing. Netlify got acquired by Automattic in late 2023. It's been... fine, mostly, but there's been some churn in leadership and product direction since. Nothing catastrophic, but it's worth paying attention to. Cloudflare, as a public company with a clear product roadmap, feels more stable to me right now as a long-term bet.
---
FAQ
Is Cloudflare Pages actually free for unlimited bandwidth?
Yes, and I was sceptical too. Cloudflare's business model is built on selling network and security products, not on charging for bandwidth at the edge. Serving static files from their CDN is effectively a loss-leader for them. The unlimited bandwidth on the free tier is real and has been consistent since they launched Pages.
Can I use Next.js on Cloudflare Pages?
You can, with some caveats. Cloudflare supports Next.js via their OpenNext adapter, which translates Next.js server features into Workers-compatible code. It works well for most App Router projects but some features (particularly anything relying on Node.js APIs in server components) need attention. I'd test your specific feature set before committing a complex Next.js app to Cloudflare Pages.
Which platform has better uptime?
Both are excellent. I've been running production sites on both for years and I can count meaningful downtime incidents on one hand across the board. Cloudflare's infrastructure is arguably more resilient purely because of its scale, but Netlify's uptime track record is also very strong. This isn't a meaningful differentiator.
Does Netlify still make sense in 2026?
Yes, for the right project. It's not dead, it's not declining into irrelevance. The product is still actively developed and the developer experience around complex build pipelines and serverless functions is genuinely better than Cloudflare Pages in specific scenarios. I still deploy things to Netlify every week.
What about Vercel?
Vercel is the obvious third option and deserves its own post. Short answer: Vercel is the best platform for Next.js specifically, but the pricing at scale is significantly higher than both Cloudflare Pages and Netlify. I use it for client projects where Next.js performance is non-negotiable and budget allows for it.
---
Neither platform is going anywhere. Both are good. But if I had to give one recommendation to a freelancer or small agency owner starting fresh in 2026, I'd say: start on Cloudflare Pages, stay there unless something specific pushes you to Netlify. The bandwidth economics alone make it the sensible default.