We hosted the same three apps on Vercel, Netlify, and Cloudflare Pages for a full month. A Next.js application with API routes. An Astro marketing blog. A Svelte dashboard with WebSocket realtime updates.
Then we tracked everything. Deploy times across thirty pushes. Time to first byte from five regions. And the invoice at 100GB, 500GB, and 1TB of monthly egress. The gap is wider than the marketing pages suggest.
The Three Frontend Hosts Worth Considering In 2026
The frontend hosting market is mostly a three-horse race in 2026. Render and Fly.io exist for fullstack workloads. Cloudways and Hostinger exist for traditional shared hosting. But for static-plus-edge-functions frontend hosting, you're picking one of Vercel, Netlify, or Cloudflare Pages.
What's interesting is how differently they make money. Vercel charges for everything past a tight free tier and sells the Next.js native experience as the moat. Netlify charges for compute and bandwidth and sells the build pipeline plus team features. Cloudflare sells security and DNS to enterprise customers and lets bandwidth be loss-leading infrastructure on Pages.
That last point is the entire game. Cloudflare offers unlimited bandwidth on every paid tier of Pages. Vercel and Netlify charge per gigabyte past their free allotment. At low traffic the gap is invisible. At high traffic the gap is brutal.
Where Each Platform Started And Where It Ended Up
Vercel started as the Next.js company. They built the framework, they own the hosting, and the integration is the deepest in the market. If you want zero-config Next.js with image optimization, edge middleware, and incremental static regeneration, Vercel is the path of least resistance. Everything else they offer (other frameworks, serverless functions, edge config) is real, but Next.js is where they win on quality.
Netlify started as the JAMstack pioneer. They invented the deploy-from-git workflow most platforms now copy. The build pipeline is still the most flexible. The form handling, the redirects, the build plugins (which they invented) remain best in class. But they made some pricing decisions in 2024 that pushed users away, and they've been recovering since.
Cloudflare Pages started as a side bet. Cloudflare's main business is the CDN and security stack. Pages was launched in 2021 as a way to keep developers inside the Cloudflare ecosystem long enough to upsell them on Workers, R2, and the rest. The unlimited bandwidth was the loss leader. In 2026 it works. Pages has matured fast and the Workers integration story is now the cleanest for full-stack edge applications.
The platforms aren't really competing on the same axis. Vercel sells Next.js performance. Netlify sells build pipeline flexibility. Cloudflare sells unlimited bandwidth at network-edge scale. Pick the one whose business model isn't punishing the thing you do most of.
Deploy Times Measured On Three Identical Projects
We pushed thirty commits to each platform across the three test apps. The Next.js application had a roughly 90-second build. The Astro blog took 35 seconds. The Svelte dashboard took 22 seconds.
Vercel was fastest on Next.js (no surprise). Average deploy time including the cold container start was 1 minute 48 seconds for the Next app, 52 seconds for Astro, and 38 seconds for Svelte. The Next.js advantage came from cached dependencies and the optimized build pipeline.
Netlify came second on Next.js but first on Astro. The build pipeline is slightly faster for static generators. Average times were 2 minutes 14 seconds for Next, 47 seconds for Astro, and 41 seconds for Svelte. The Astro advantage came from how Netlify caches the build output between deploys.
Cloudflare Pages came third on every project but was the most consistent. Average times were 2 minutes 38 seconds for Next, 1 minute 8 seconds for Astro, and 56 seconds for Svelte. Pages spends more time on the global propagation step because it's pushing to 300+ edge locations, not just a CDN cache.
If deploy time is your bottleneck, Vercel wins. If it's not, the gap of 30 to 50 seconds per deploy doesn't matter at the volume most teams ship at.
TTFB From Five Regions On The Same Page
We measured time to first byte from five regions on the same statically generated page hosted on each platform. The regions were Virginia, Frankfurt, Singapore, São Paulo, and Tokyo.
Cloudflare came in first on every region. The 300+ edge locations mean every request is being served from a colocation point within 50ms of the user. Virginia averaged 19ms, Frankfurt 22ms, Singapore 28ms, São Paulo 41ms, Tokyo 31ms.
Vercel came in second on most regions. The Vercel Edge Network is real but smaller than Cloudflare's. Virginia 31ms, Frankfurt 43ms, Singapore 58ms, São Paulo 89ms, Tokyo 67ms.
Netlify came in third. The CDN is decent but they don't have the global footprint of either competitor. Virginia 42ms, Frankfurt 67ms, Singapore 124ms, São Paulo 156ms, Tokyo 113ms.
For static content, Cloudflare wins TTFB outright. For Next.js routes that need edge runtime, Vercel's middleware layer is closer in latency but Cloudflare's Workers still beat it for cold-start performance.
The Next.js Adapter Story On Cloudflare Pages Now
This is the section that should kill some of the Vercel-Next.js mythology. In 2026 the OpenNext adapter is mature enough that you can deploy a non-trivial Next.js application on Cloudflare Pages and have most features just work. ISR, dynamic routes, server components, edge middleware.
What still has friction. Image optimization. Cloudflare uses Cloudflare Images, which works but requires a separate integration. Vercel ships image optimization built in. The Next.js cache layer is more opinionated on Vercel and the OpenNext adapter has to bridge it to Cloudflare KV. Most teams don't notice but heavy ISR users will.
What works well. The edge runtime is now a first-class citizen on Pages. The Workers integration means you can mix Pages routes with Workers without separate deploys. The Cloudflare ecosystem (D1, R2, KV, Durable Objects) is a real production stack that Vercel doesn't quite match outside Next.js.
For the serverless function comparison underneath this, see our Workers vs Lambda deep dive. The hosting platform decision and the serverless platform decision are related but separable.
Bandwidth Math At 100GB, 500GB, And 1TB Per Month
This is where the conversation gets honest.
At 100GB egress per month, all three platforms cost roughly the same. Vercel Pro at $20 per month gives you 1TB of bandwidth included. Netlify Pro at $19 per month gives you 400GB. Cloudflare Pages Pro at $5 per month gives you unlimited. At low traffic the marginal cost is the platform fee, not the bandwidth.
At 500GB per month, the gap opens up. Vercel still includes you on the 1TB allowance. Netlify charges roughly $55 in overages on top of the $19 base. Cloudflare stays at $5 base, unlimited bandwidth.
At 1TB per month, Vercel hits its included cap and overage starts at $0.15 per GB above the cap (so still $20 if you stay exactly at 1TB, but each additional 100GB is $15). Netlify charges roughly $90 plus the $19 base. Cloudflare stays at $5 base.
The dramatic version is at 10TB per month. Vercel lands around $1,500 with overages. Netlify lands around $2,600 with credits and overages. Cloudflare lands at $5 plus the function invocation costs, which for static content is essentially zero. That's not a typo. Real-world Cloudflare Pages bills at high traffic are routinely under $50 per month.
Hidden Cost Watch: Build Minutes And Edge Function Invocations
Bandwidth isn't the only cost vector. Watch the build minutes and edge function invocations because they're where the bill creeps.
Vercel includes 6,000 build minutes per month on Pro and charges per additional thousand. For a team doing CI on every PR with preview deploys, you can burn that allowance fast. Each preview deploy is a full build. Our test team running 80 PRs a month was at 4,200 build minutes before the production deploys, leaving very little headroom.
Netlify charges similarly per build minute and the per-minute rate is comparable. The difference is Netlify gives you 300 build minutes free on the starter tier and 25,000 on the Pro tier. Pro tier has more headroom but you pay more upfront.
Cloudflare Pages doesn't charge for build minutes on the Pages product. It does charge for Workers invocations if you're using them, at $0.30 per million requests on the Paid plan. For a frontend application that's basically free. For an API-heavy application, it's still under $5 per month at hundreds of millions of requests.
Where Netlify Still Wins And Where It Genuinely Lost
Netlify wins on three specific things. The build pipeline is still the most flexible. If you have a weird build process (legacy Hugo plus webpack plus a Python script that processes Markdown), Netlify's build plugins handle it cleaner than Vercel or Cloudflare. The form handling is built in and works at zero config. Submit forms get emailed to you with no API to write. And the team-edit collaboration features (Drawer, Visual Editor) are a real moat for marketing teams.
Where it lost. The bandwidth pricing is the worst of the three for high-traffic sites. The Next.js story is solid but not as deep as Vercel's. And the edge function story trails both Vercel's middleware and Cloudflare's Workers. If you're building a static site with light dynamic content and a marketing team that wants to edit visually, Netlify still wins. For everything else, it's harder to justify.
Our Pick By Stack And By Stage
For a Next.js app with high traffic and ISR, we'd still pick Vercel for the path of least resistance, then watch the bill carefully. Once you hit 5TB per month, the Cloudflare migration pencils out.
For a static marketing site, an Astro blog, or anything else heavy on outgoing bandwidth, Cloudflare Pages, every time. The 95% cost savings at scale isn't a margin you ignore.
For a marketing team that lives in the Netlify drawer-and-form-handling world, Netlify, and just plan the migration when you cross 1TB egress.
For a team that's standardizing on the Cloudflare ecosystem (D1 for SQL, R2 for storage, Workers for everything), Pages is the natural landing. The integrated stack is denser than Vercel's and more cost-effective than Netlify's. For indie hackers who watch bills like hawks, this is the route we'd recommend.
FAQ
Is Vercel Still The Best For Next.js In 2026?
Yes, for the path of least resistance. The OpenNext adapter on Cloudflare Pages is mature but still requires more setup. If you want zero-config Next.js with all features working out of the box, Vercel. If you want to control your bill, Cloudflare with the OpenNext adapter.
What's The Cheapest Tier That Includes Custom Domains?
Cloudflare Pages Free includes custom domains. Vercel Hobby includes custom domains for personal projects but no commercial use. Netlify Free includes custom domains. All three are free for static sites, but Cloudflare wins on bandwidth.
Can I Use Cloudflare Pages For An API-Heavy App?
Yes, through the Workers integration. Pages handles the static assets, Workers handle the API routes. The combined Pages-plus-Workers bill is usually under $20 per month for traffic that would cost $500-$2,000 on Vercel.
Does Netlify Still Have The Best Build Plugins?
For flexibility, yes. The plugin ecosystem is the deepest of the three. If you have a weird build process, Netlify handles it. For standard frameworks, the difference doesn't matter.
Are Cloudflare Pages Build Times Going To Improve?
They've already improved twice in 2026. The current 30-second penalty versus Vercel on Next.js builds is closing. If deploy time is your priority, watch this gap. If it's not, the cost savings overwhelm the build-time delta.
What About Vercel's Image Optimization?
It's the best in the market. Cloudflare Images works but it's a separate product with its own pricing. Netlify Image CDN is a third option. For Next.js image-heavy sites, Vercel's built-in is the smoothest experience.
Where Does Render Or Fly.io Fit?
Different category. Render and Fly.io are full-stack hosts that include databases and long-running processes. Vercel, Netlify, and Cloudflare Pages are frontend-plus-functions hosts. The categories overlap on edge functions but the use cases diverge fast. See our serverless comparison for adjacent context.
The Closing Take
The lazy framing of this comparison is that Vercel is for serious teams, Netlify is for marketers, and Cloudflare is for the budget-conscious. That framing is wrong in 2026.
Vercel is for Next.js teams that want the deepest framework integration and don't mind paying for it. Netlify is for teams that need build-pipeline flexibility and have a marketing-team editing component. Cloudflare Pages is the default choice for everyone else, especially anyone running a content site with non-trivial bandwidth.
Run the math on your actual traffic before you pick. The 10x cost gap between Cloudflare and Vercel at high traffic isn't theoretical. It's the difference between a sustainable business model and a hosting bill that grows linearly with your audience.
Whatever you pick, deploy on Friday and ship before midnight. The hosting platform isn't the bottleneck. Your shipping discipline is. Our version-control comparison covers the next layer of that stack.
