Vercel vs Netlify vs Cloudflare Pages: Compared

Updated September 2026 · Written and maintained by the Progression Agency strategy team

Vercel and Netlify are the two platforms most front-end teams deploy to, and Cloudflare Pages is the third option that keeps coming up. This comparison covers frameworks, rendering support, edge and serverless functions, build minutes, bandwidth, pricing models, limits, team features and where each one is the right choice for a business website, a Next.js application or a static Astro site.

On this page · 12 sections

Vercel vs Netlify at a glance
What Vercel is
What Netlify is
What Cloudflare Pages is
Framework support compared
Pricing models and where costs appear
Vercel vs Netlify for a business website
Vercel vs Netlify for a Next.js app
Cloudflare Pages vs Vercel
AWS vs Vercel
Which should you choose?
How Progression Agency deploys

The short answerChoose Vercel for Next.js applications: it is built by the Next.js team, supports every rendering feature first and needs no configuration. Choose Netlify for framework-agnostic sites, forms, identity and a mature build platform, especially Astro, Nuxt, SvelteKit and static sites. Choose Cloudflare Pages when bandwidth cost is the worry, when you already use Cloudflare for DNS and security, or for static sites and Workers-based apps. All three have free tiers that cover small sites; the differences appear at scale, in usage-based pricing and in framework support.

Comparisons are based on each project’s official documentation as linked in the text. Progression Agency builds with all of the technologies compared and has no affiliate relationship with any of them.

Vercel vs Netlify at a glance

Vercel vs Netlify vs Cloudflare Pages
	Vercel	Netlify	Cloudflare Pages
Best for	Next.js and React apps	Any framework; static and SSR sites	Static sites, Workers apps, bandwidth-heavy sites
Owner of a framework	Next.js	No (created the JAMstack term)	No (Workers platform)
Serverless functions	Vercel Functions (Node, Edge)	Netlify Functions, Edge Functions	Workers (V8 isolates)
Next.js support	Complete, first	Good, via Netlify runtime adapter	Via OpenNext adapter
Static sites	Yes	Yes	Yes
Forms / identity built in	No (third party)	Netlify Forms, Identity	No (Workers + third party)
Preview deployments	Per branch and PR	Per branch and PR (Deploy Previews)	Per branch
Bandwidth pricing	Included allowance, then usage	Included allowance, then usage	Static assets free; Workers usage
Pricing pages	vercel.com/pricing	netlify.com/pricing	developers.cloudflare.com/pages

Fit by use case (1-5, editorial) — Vercel leads for Next.js; Netlify and Cloudflare lead for static sites and cost.

What Vercel is

Vercel is the company behind Next.js and a hosting platform tuned for it: push to Git, get a build, preview URLs for every pull request, a global CDN, serverless and edge functions, image optimization, analytics and observability. It hosts other frameworks too (Astro, Nuxt, SvelteKit, Remix, plain static sites), but Next.js features such as Incremental Static Regeneration, streaming, middleware and Partial Prerendering work without setup only on Vercel. Documentation: vercel.com/docs.

What Netlify is

Netlify popularized the JAMstack approach: static sites built from Git and served from a CDN, with serverless functions for the dynamic parts. It supports every major framework through build plugins and runtime adapters, includes Netlify Forms, Identity and split testing, and has a long record with agencies and marketing teams. Its Next.js runtime supports server rendering, ISR and middleware. Documentation: docs.netlify.com.

What Cloudflare Pages is

Cloudflare Pages is the static and full-stack hosting product on Cloudflare’s network, backed by Workers for server logic, KV, D1 (SQL), R2 (object storage with no egress fees) and Durable Objects. Static asset delivery is free with no bandwidth cap on the free plan, which makes it the cheapest option for media-heavy static sites. Next.js runs through the OpenNext adapter; Astro, SvelteKit, Nuxt and Remix have first-party adapters. Documentation: developers.cloudflare.com/pages. See also Cloudflare vs AWS.

Framework support compared

Framework fit
Framework	Vercel	Netlify	Cloudflare Pages
Next.js (App Router, ISR, streaming)	Native	Adapter, most features	OpenNext adapter
Astro	Adapter	Adapter	Adapter
Nuxt	Adapter	Adapter	Adapter
SvelteKit	Adapter	Adapter	Adapter
React Router / Remix	Adapter	Adapter	Adapter
Plain static HTML	Yes	Yes	Yes
Angular SSR	Yes	Yes	Community

Pricing models and where costs appear

All three offer free tiers for personal and small projects and per-seat paid plans for teams. Costs grow with three things: bandwidth, serverless or edge function execution, and build minutes. Vercel and Netlify include allowances and bill overages; Cloudflare does not charge for static bandwidth and bills Workers requests and CPU time. A commercial site should be on a paid team plan on any of them, because free tiers exclude commercial use or SLAs. Check the linked pricing pages before committing; figures change several times a year.

Vercel vs Netlify for a business website

For a marketing site built in Astro or as static Next.js, Netlify and Cloudflare Pages are simpler and cheaper; Netlify’s forms and split testing help marketing teams. For a Next.js application with server rendering, authentication and API routes, Vercel removes the most friction. Either way, keep DNS and the domain in an account the business owns, not the agency’s.

Vercel vs Netlify for a Next.js app

Vercel supports every Next.js feature on release day and its Fluid compute and edge network are designed around it. Netlify’s Next.js runtime is solid for most apps and worth choosing when the team already runs Netlify or values its forms and identity. Heavy server rendering at scale can be cheaper on a container platform (AWS, Google Cloud Run) or a VPS; see hosting for React and Next.js apps.

Cloudflare Pages vs Vercel

Cloudflare wins on bandwidth cost, DDoS protection and the size of its edge network, and its Workers platform is excellent for small full-stack apps. Vercel wins on Next.js compatibility, developer experience and preview workflows. Many teams use both: Cloudflare for DNS, WAF and caching in front of a Vercel deployment.

AWS vs Vercel

AWS Amplify Hosting supports Next.js and static sites with a similar Git-based workflow, and running Next.js in containers on ECS or on a plain EC2 or Lightsail server gives full control and predictable cost at high traffic. The trade is setup and operations effort. Teams already on AWS with DevOps capacity often prefer it; teams without prefer Vercel. See AWS vs Azure vs Google Cloud and DevOps services.

Next — Next.js first. Vercel supports it natively..

Forms — Forms and identity. Netlify includes them..

BW — Bandwidth. Cloudflare static is free..

Fn — Functions. Serverless and edge on all three..

Own — Ownership. Deploy in the client's account..

Which should you choose?

Vercel, Netlify or Cloudflare Pages?
Situation	Recommendation
Next.js application with SSR and API routes	Vercel
Astro or static marketing site	Netlify or Cloudflare Pages
Site with heavy media and traffic, cost-sensitive	Cloudflare Pages
Marketing team needs forms, redirects and A/B tests without code	Netlify
Already on Cloudflare for DNS and security	Cloudflare Pages, or Cloudflare in front of Vercel
Enterprise on AWS with DevOps team	AWS Amplify or containers
Agency managing many client sites	Netlify or Vercel team plans

How Progression Agency deploys

We deploy Next.js products to Vercel, Astro and static sites to Cloudflare Pages or Netlify, and put Cloudflare in front for DNS and security where it helps. Hosting is set up in the client’s own accounts with the estimated monthly cost written into the proposal. See Next.js development and website migration services.

Deploying a site or app?

We will recommend Vercel, Netlify, Cloudflare or AWS for your stack and traffic, set it up in your accounts and document it.

Get a hosting recommendation

Getting found in search

AI, AEO and what is changing

Paid media and lead generation

Websites and design

Choosing and working with an agency

Software and app development

Web development, platforms and hosting

Social, content and brand

By industry and by situation

Frequently asked questions

Is Vercel better than Netlify?

For Next.js, yes. For other frameworks and static sites the two are close, and Netlify’s forms and identity can tip it.

Is Netlify free?

Netlify has a free tier for personal projects; commercial sites should use a paid plan. Check netlify.com/pricing.

Is Vercel free?

Vercel’s Hobby plan is free for non-commercial use; teams need the Pro plan or above. Check vercel.com/pricing.

Which is cheaper, Vercel or Netlify?

Similar at small scale; costs diverge with bandwidth and function usage. Cloudflare Pages is cheapest for static bandwidth.

Can Netlify host Next.js?

Yes, through its Next.js runtime, including server rendering and ISR.

Can Cloudflare Pages host Next.js?

Yes, through the OpenNext adapter; static-exported Next.js works directly.

Is Cloudflare Pages better than Vercel?

For static, bandwidth-heavy sites and Workers apps, often yes; for full Next.js feature support, no.

Do I need Vercel to use Next.js?

No. Next.js runs on Netlify, Cloudflare, AWS, Azure, Google Cloud or any Node.js server.

Which is best for SEO?

All three serve fast, cacheable pages; SEO depends on the site build, not the host.

What are preview deployments?

Temporary URLs for each branch or pull request so stakeholders can review changes before they go live; all three provide them.

Can I use Cloudflare in front of Vercel or Netlify?

Yes, for DNS, WAF and caching; follow each platform’s proxy guidance.

What is a serverless function?

Server code that runs on demand without a server you manage; used for APIs, forms and dynamic pages.

Which should an agency use for client sites?

Netlify or Vercel team plans for workflow, or Cloudflare Pages for cost; sites belong in the client’s account.

Which does Progression Agency use?

Vercel for Next.js products, Cloudflare Pages or Netlify for static and Astro sites, AWS when clients need it.

Can I migrate between them?

Yes; the code is portable. Framework adapters and DNS changes are most of the work.

Need help choosing or moving hosting?We recommend, set up, migrate and manage hosting for the sites and apps we build, and for sites built elsewhere.