Vercel vs Netlify vs Cloudflare Pages — the real pick
The three deploy platforms every frontend dev compares. DX, pricing, edge runtimes, bandwidth traps, and which you should actually push your site to in 2026.
The contenders
Vercel
The Next.js mothership. Best DX, priciest bandwidth.
- Best developer experience — preview URLs, logs, analytics just work
- First-class Next.js support (they build Next.js)
- Edge network + AI-era features (AI SDK, v0, Fluid Compute)
- Bandwidth and function execution get expensive fast at scale
- Vendor lock-in creeps in if you use Vercel-specific APIs
- Hobby plan has strict commercial-use restrictions
Netlify
The original Jamstack host. Solid, mature, a bit quieter.
- Framework-agnostic — Astro, SvelteKit, Remix, Next all first-class
- Build plugins ecosystem is mature and useful
- Forms, Identity, edge functions out of the box
- Lost mindshare to Vercel for Next.js specifically
- Function limits tighter than competitors at paid tier
- Pricing less predictable than Cloudflare for high traffic
Cloudflare Pages
The price killer. Unlimited bandwidth, global edge.
- Unlimited bandwidth on the free tier — nothing else offers this
- Global edge from day one (Cloudflare's whole network)
- Workers + D1 + R2 + KV for full-stack at tiny cost
- DX still trails Vercel — dashboard & logs less polished
- Build times capped, slower on large sites
- Some frameworks need adapter config to run on Workers runtime
Spec by spec
| Spec | Vercel | Netlify | Cloudflare Pages |
|---|---|---|---|
| Pricing | |||
| Free tier bandwidth | 100 GB | 100 GB | Unlimited |
| Free tier builds | 100 hrs build time | 300 build min | 500 builds/mo |
| Paid starter | $20/user/mo | $19/user/mo | $5/mo (via Workers) |
| Bandwidth overage cost | $0.15/GB (above 1TB Pro) | $55 per 100GB | No overage |
| Frameworks | |||
| Next.js support | First-class (they build it) | Supported via adapter | Supported via OpenNext |
| Astro / SvelteKit / Remix | Full | Full | Full |
| DX | |||
| Preview deploys | Yes, polished | Yes | Yes |
| Analytics | Built-in (paid) | Built-in (paid) | Web Analytics free |
| Runtime | |||
| Edge/serverless functions | Edge + Node Functions + Fluid | Edge + background + scheduled | Workers (V8 isolates) |
| Included database | Postgres/Redis via marketplace | Via partners | D1 (SQLite) built-in |
| Business | |||
| Enterprise posture | Strong | Strong | Strongest (CF Enterprise) |
The TL;DR before you scroll
Three deploy platforms. Three totally different pricing philosophies. Three sweet spots.
Vercel wins on DX and Next.js — best developer experience, best AI tooling, most expensive bandwidth.
Cloudflare Pages wins on price and scale — unlimited bandwidth free, global edge built-in, cheapest full-stack.
Netlify wins on framework-agnostic maturity — still a clean pick, just not dominating any single category.
In 2026 the common pattern is Vercel for the app, Cloudflare for everything else — static sites, assets, storage, R2 for file uploads.
Vercel: still the best DX, at a price
Vercel is what most frontend developers instinctively reach for in 2026, and there are real reasons why. Preview deploys on every PR work flawlessly. Logs are actually readable. Built-in analytics, Speed Insights, and the AI SDK are polished. Next.js support is first-class — Vercel builds Next.js, so every feature ships on Vercel first.
The new-in-2026 features are legitimate too: Fluid Compute (a serverless runtime that keeps connections warm between invocations), better pricing for AI workloads, and the v0 integration for generating UI.
The catch: bandwidth is expensive. Pro plan includes 1 TB, then $0.15/GB. Function execution time adds up. A surprise viral moment or a mis-configured image can cost four figures. This is the single most common complaint.
Who it’s for: Next.js teams, AI-first apps, anyone who values DX over cost predictability.
Cloudflare Pages: the grown-up answer for high traffic
Cloudflare Pages is the boring, obvious choice that most developers still underrate. Free tier: unlimited bandwidth. Paid ($5/mo via Workers): a full-stack platform with a SQLite database (D1), object storage (R2, S3-compatible with no egress fees), KV, queues, and AI — all at prices that look like rounding errors.
The tradeoff is DX. The dashboard is less polished than Vercel. Build times are capped and slower on big sites. Some framework adapters need config. It rewards developers who know what they’re doing more than it hand-holds newbies.
In 2026, Cloudflare Pages + Workers + D1 + R2 is the cheapest way to run a real full-stack app at serious scale. Full stop. If you’re running anything that gets real traffic, this platform deserves a hard look.
Who it’s for: high-traffic sites, cost-sensitive teams, edge-first apps, anyone who’s been bitten by a surprise Vercel bill.
Netlify: still solid, just quieter
Netlify invented this category. Jamstack, instant previews, the whole deployment-as-git-push workflow — Netlify shipped it first. In 2026 it’s still a very good product: framework-agnostic (Astro, SvelteKit, Remix, Next all first-class), great build plugins, Forms and Identity built-in, solid enterprise story.
It just doesn’t win a specific category anymore. Vercel owns Next.js and DX. Cloudflare owns price and edge. Netlify is the “nothing’s wrong with it” option, which is underselling how polished and reliable it is.
Who it’s for: multi-framework teams, anyone who needs Forms/Identity out of the box, teams that want a mature, no-drama Jamstack host.
Pricing: the honest breakdown
| Cost | Vercel | Netlify | Cloudflare Pages |
|---|---|---|---|
| Free tier | Hobby (100 GB, no commercial) | Starter (100 GB) | Unlimited bandwidth |
| Paid starter | $20/user/mo | $19/user/mo | $5/mo |
| Overage | $0.15/GB | ~$55/100 GB | None |
| Ops cost at 1 TB/mo | ~$20 + overages | ~$550 overages | $0–5 |
That last row is the whole argument for Cloudflare for high-traffic sites.
Frameworks: all three cover 95% of what you’d want
In 2026, all three support Next.js, Astro, SvelteKit, Remix, Nuxt, Gatsby, React Router — you name it. The nuances:
- Vercel: Next.js is seamless. Everything else is well-supported, but Next gets new features first.
- Netlify: Truly framework-agnostic. No framework gets special treatment; all work equally well.
- Cloudflare Pages: Uses Workers runtime (V8 isolates, not Node.js). Adapters exist for every major framework via OpenNext, Wrangler, etc. Next.js via OpenNext is now genuinely solid.
If your framework is Next.js and you want zero friction, Vercel. Otherwise, all three are fine on frameworks.
The 2026 power combo: Vercel + Cloudflare
The split a lot of serious teams run in 2026:
- Vercel hosts the main Next.js app (SSR, API routes, AI features)
- Cloudflare R2 stores user uploads and static assets (no egress fees!)
- Cloudflare Workers handles any high-frequency edge logic
- Cloudflare Pages hosts the marketing site, blog, docs separately
You get Vercel’s DX on the product, Cloudflare’s pricing on everything bandwidth-heavy. A lot of the “Vercel is expensive” complaints disappear once you offload asset storage to R2.
Edge functions vs serverless vs “fluid compute”
- Vercel Edge (Edge Runtime) + Fluid Compute (warm Node functions): broadest runtime flexibility
- Netlify Edge Functions (Deno-based) + background/scheduled functions: solid, simpler
- Cloudflare Workers (V8 isolates): fastest cold start, most global, some Node compat caveats
For AI streaming apps specifically, Vercel’s AI SDK + Edge is the smoothest path. For raw edge performance at scale, Workers wins.
So, who actually wins?
Vercel for Next.js teams and AI-first apps where DX > price.
Cloudflare Pages for everyone else — especially anyone who cares about bandwidth, price, or global performance.
Netlify if you need Forms/Identity built-in or you’re framework-agnostic and want a no-drama host.
If you’re starting a new site in 2026 and have no strong tie to a stack: Cloudflare Pages free tier is the correct answer. If you’re shipping a Next.js SaaS with a design team and don’t want to fight tooling: Vercel Pro. Both can be right.
Winner: Vercel
Vercel is still the pick if you're shipping a Next.js app and you want the best DX money can buy — preview URLs, logs, analytics, and AI tooling that just work. But in 2026 Cloudflare Pages is the grown-up answer for anything high-traffic or cost-sensitive: free unlimited bandwidth, global edge, D1 + R2 + Workers for basically pennies. Netlify is still a clean, mature option especially if you're framework-agnostic — it just doesn't win a specific category anymore. Many teams use Vercel for the main app and Cloudflare for everything else.
Pick by use case
FAQ
Is Vercel worth it in 2026 given Cloudflare is free? +
For Next.js apps where DX matters, yes. Vercel's preview deploys, logs, analytics, AI SDK, and Fluid Compute integration are worth the price for production teams. For static sites, marketing pages, or high-traffic apps where bandwidth is the bottleneck, Cloudflare Pages' free unlimited bandwidth wins outright. Match the tool to the workload.
Does Cloudflare Pages really have unlimited bandwidth? +
Yes, on the free tier — and it's not a gotcha. Cloudflare's whole business is bandwidth, so they treat Pages traffic as rounding error. You do hit limits on builds (500/month) and Workers requests (100K/day free), but the bandwidth itself is genuinely uncapped. This is the single biggest reason to pick Pages for high-traffic sites.
Will I get a huge Vercel bill if my site goes viral? +
Possibly. Vercel's Hobby plan has a 100 GB soft limit and strict commercial-use rules; Pro is pay-as-you-go above included amounts. A truly viral moment (millions of views, heavy function calls) can produce four-figure bills. Set spend caps, use edge caching, and consider moving static assets to Cloudflare R2 + CDN if this worries you.
Is Netlify falling behind? +
Not exactly falling behind — just not winning a specific category anymore. Vercel owns Next.js. Cloudflare owns price and edge. Netlify is a solid, mature, framework-agnostic pick with a great build plugin ecosystem and good enterprise features. If you don't have a strong reason to pick Vercel or Cloudflare, Netlify is totally fine — and Forms + Identity are still great built-ins.
Can I use Cloudflare Pages with Next.js? +
Yes, via OpenNext or the Next-on-Pages adapter. Most features work, some (ISR, specific edge APIs) need workarounds. In 2026 the ergonomics are much better than a couple years ago, but Vercel still has the smoothest Next.js experience. If Next.js is your stack and budget isn't your top concern, Vercel is less friction.
What about self-hosting on a VPS? +
A DigitalOcean or Hetzner VPS plus Coolify/Dokploy can host many Next.js/Astro sites for $5-10/month total, and you avoid all per-service pricing games. But you own the operational cost — patches, backups, SSL, scaling. For a small team, Pages/Vercel/Netlify is almost always the better time-vs-money trade. For a side project with predictable traffic, self-hosting is very real.
More cloud & infra picks
Found this useful? Share it.
Good picks spread faster than bad ones.