Vercel vs Netlify vs Cloudflare Pages: Deployment Platforms Ranked

Runtime Performance

This is where Cloudflare Pages distinguishes itself. Cloudflare's edge network is the largest of the three, with over 300 points of presence worldwide. This translates to consistently lower Time to First Byte (TTFB) for users in regions far from the US.

We measured TTFB from five global locations:

Cloudflare's numbers are remarkable. The consistency across regions — all under 60ms — reflects the advantage of running code on Workers, which execute at the edge globally rather than in a specific region. Vercel's edge functions provide similar global distribution, but their serverless functions default to a single region unless you configure otherwise. Netlify's edge performance is the weakest of the three.

Edge Functions and Serverless

Vercel offers two runtimes: Edge Functions (V8 isolates, globally distributed) and Serverless Functions (Node.js, regional). You choose per-route. Edge Functions have API limitations (no filesystem access, limited Node.js APIs) but are fast. Serverless Functions support the full Node.js API but are regional.

Netlify's Edge Functions run on Deno. Netlify Functions run on AWS Lambda. The Deno-based edge functions are fast but have a limited API surface. Lambda functions have cold start latency that can add 200-500ms to the first request after idle.

Cloudflare Workers are V8 isolates at every edge location. There are no cold starts — Workers are always warm at the edge. The tradeoff is that Workers have a different runtime than Node.js. Some Node.js APIs are not available, though compatibility has improved significantly with the nodejs_compat flag.

// Cloudflare Worker (Pages Function)
export async function onRequest(context) {
  const { searchParams } = new URL(context.request.url);
  const query = searchParams.get('q');
  
  // Access Cloudflare KV, D1, R2 directly
  const cached = await context.env.CACHE.get(query);
  if (cached) return new Response(cached, {
    headers: { 'Content-Type': 'application/json' }
  });
  
  const result = await context.env.DB
    .prepare('SELECT * FROM products WHERE name LIKE ?')
    .bind(`%${query}%`)
    .all();
  
  await context.env.CACHE.put(query, JSON.stringify(result), {
    expirationTtl: 3600
  });
  
  return Response.json(result);
}

Additional Services

The platforms differ significantly in what else they offer beyond deployment:

Vercel: Analytics (web vitals), Speed Insights, KV storage, Postgres (via Neon), Blob storage, Cron jobs, Firewall. Vercel's additional services are tightly integrated with the deployment platform.

Netlify: Forms, Identity (auth), Large Media, Split Testing. Netlify's extras are practical but feel less modern than the competition.

Cloudflare: Workers KV, D1 (SQLite at the edge), R2 (S3-compatible storage), Queues, Durable Objects, AI inference, Images, Stream. Cloudflare's ecosystem is the broadest by far. If you build on Cloudflare Pages, you have access to an entire platform of services that can replace dedicated providers.

Pricing

Cloudflare's free tier is the most generous. Unlimited bandwidth alone makes it attractive for content-heavy sites. Vercel's free tier is good for development and small projects but gets expensive as you scale.

On paid plans (Vercel Pro at $20/user/month, Netlify Pro at $19/user/month, Cloudflare Pro at $5/month), the cost difference is significant. Cloudflare is by far the cheapest, and the gap widens at scale. A site handling 1TB of bandwidth per month would cost roughly $150 on Vercel, $110 on Netlify, and $0 extra on Cloudflare (bandwidth is always free).

Developer Experience

Vercel has the best developer experience of the three. The dashboard is fast and well-designed. Preview deployments per PR are seamless. The CLI is excellent. Integration with Next.js means zero configuration for the most common framework.

Netlify's dashboard is functional but busier. There are more settings, more menus, and more concepts to understand. The CLI works well. Build plugins add flexibility but also complexity.

Cloudflare's dashboard has improved but still feels enterprise-oriented. The Pages interface is clean, but configuring Workers, KV, D1, and other services involves navigating a sprawling console. The Wrangler CLI is powerful but has a steeper learning curve.

Who Should Use What

Choose Vercel if:

• You use Next.js and want zero-configuration deployment
• Developer experience is a top priority
• You need preview deployments and team collaboration features
• You are willing to pay for premium deployment infrastructure

Choose Netlify if:

• You use Gatsby, Hugo, or Eleventy
• You need built-in forms or identity without external services
• You prefer a platform with a long track record

Choose Cloudflare Pages if:

• Global performance is critical
• You want the best pricing, especially at scale
• You plan to use edge storage (KV, D1, R2)
• You are comfortable with a non-Node.js runtime

FAQ: Vercel vs Netlify vs Cloudflare Pages

Which is better for Next.js: Vercel, Netlify, or Cloudflare Pages?

Vercel. The company builds Next.js, so App Router, Server Actions, Partial Prerendering, and ISR all work with no configuration. In our test Netlify did not support Partial Prerendering and needed extra setup for Image Optimization. Cloudflare Pages runs Next.js through the @opennextjs/cloudflare adapter, which handled static generation and basic server rendering but needed a polyfill for one API route that used Node.js streams.

Which platform has the fastest builds?

Vercel. Across 20 builds from the same commit, Vercel averaged 48 seconds, Cloudflare Pages 52 seconds, and Netlify 67 seconds. Vercel caches node_modules and .next between builds. Cloudflare Pages had the most consistent times, with the smallest spread between its fastest and slowest runs.

Which is fastest for users outside the US?

Cloudflare Pages. Its Time to First Byte stayed under 60ms in all five locations we tested, including 42ms in London, 55ms in Tokyo, 48ms in São Paulo, and 52ms in Sydney. Vercel measured 180ms in Tokyo and 195ms in Sydney, and Netlify measured 210ms and 230ms in the same cities.

Do Vercel, Netlify, or Cloudflare Pages have cold starts?

Cloudflare Workers run as V8 isolates at every edge location and have no cold starts. Netlify Functions run on AWS Lambda, where cold starts can add 200 to 500ms to the first request after idle. Vercel lets you choose per route between Edge Functions, which are globally distributed with limited Node.js APIs, and regional Serverless Functions with the full Node.js API.

Which has the best free tier?

Cloudflare Pages. Its free plan includes unlimited bandwidth, 500 builds per month, 100K Workers requests per day, and unlimited team members. Vercel and Netlify both cap free bandwidth at 100 GB and allow one team member. Vercel's free tier gives 6,000 build minutes a month versus 300 on Netlify.

How much does 1TB of bandwidth cost on each platform?

We estimate a site serving 1TB per month costs roughly $150 on Vercel and $110 on Netlify, and nothing extra on Cloudflare because bandwidth is always free there. Paid plans start at $20 per user per month for Vercel Pro, $19 per user per month for Netlify Pro, and $5 per month for Cloudflare Pro.

When should I pick Netlify?

Netlify fits sites built with Gatsby, Hugo, or Eleventy, where its native framework support is strongest, and teams that want built-in Forms and Identity without adding external services. It scored 7.9/10 in our review, behind Vercel at 8.7 and Cloudflare Pages at 8.4.

The Verdict

For Next.js projects, Vercel is the path of least resistance. Everything works, the DX is excellent, and the performance is strong. For projects where cost and global edge performance are priorities, Cloudflare Pages is the better choice — and its ecosystem of edge services (D1, R2, KV) makes it a compelling full-stack platform. Netlify remains a solid option, particularly for static-first sites, but it has lost ground to both competitors in the past two years.

Deploy on Vercel · Try Netlify · Start with Cloudflare Pages