Vercel vs Cloudflare Pages 2026: full deployment comparison

Cloudflare Pages wins for most teams in 2026. It is dramatically cheaper — free unlimited bandwidth versus Vercel’s 100GB free cap, and $5/month flat for a team of five versus Vercel’s $80/month minimum — and faster at the edge globally, with a 99.99% warm rate and 300+ PoPs. The OpenNext adapter now covers the full Next.js feature set for the majority of apps.

Vercel is still the right call for teams tracking the latest Next.js features closely — Node Middleware 15.2+, ML workloads that hit Cloudflare’s 128MB memory ceiling, or RSC-heavy apps with bundles over 10MB compressed. It is also the right call if you want observability, preview URLs, and analytics without assembling them yourself.

Who this is for

Developers choosing a deployment platform for a Next.js, Remix, Astro, or static site and wondering whether to pay Vercel or move to Cloudflare. If you are running a non-JavaScript backend or need Docker containers as the primary runtime, neither platform solves that problem — though Cloudflare Containers (launched in 2026) is a sign of where that is heading.

If your use case is a purely static site, the best deploy platforms for static sites in 2026 guide covers a wider shortlist.

What we tested

No proprietary benchmarking. The performance figures in this article come from three public primary sources:

OpenStatus latency study (2025) — p50 and p95 cold starts for Vercel Edge Functions and Vercel Node.js (Serverless)
Cloudflare blog post on Shard & Conquer (October 2025) — Cloudflare Workers warm start rate and cold start measurements post-optimization
Bejamas benchmark (January 2025) — static TTFB and edge function latency across 15 global regions, comparing Cloudflare Pages and Vercel

Pricing figures are from each platform’s published pricing pages, current as of June 2026.

Findings

Pricing: not even close for most teams

Vercel’s free Hobby tier looks reasonable until you look at what it omits. You get 100GB bandwidth, 1M edge requests per month, and 1M function invocations — but no build machine budget is included. The Pro plan is $20 per user per month: $80/month minimum for a five-person team, plus overage charges of $0.15/GB bandwidth, $2 per additional million edge requests, and $0.60 per additional million invocations.

Cloudflare Pages’ free tier gives you unlimited static bandwidth, 100,000 dynamic requests per day (roughly 3M per month), and 500 builds per month. The Workers Paid plan is $5/month flat, not per seat: 10M requests included, $0.30 per additional million.

Scenario	Vercel	Cloudflare Pages
Static site, solo dev	Free (100GB BW)	Free (unlimited BW)
SSR/dynamic, solo dev	Free (1M req/mo)	Free (3M req/mo equiv)
Team of 5, 10M req/mo	$80/mo + usage	$5/mo
Team of 5, 100M req/mo	$80/mo + ~$36 overage	$5/mo + ~$27 overage

At scale, the gap closes slightly — Vercel’s overage rates are competitive per million requests once you are already on Pro. But the $75/month fixed difference does not go away until you are in the hundreds of millions of requests per month.

Sources: Vercel pricing | Cloudflare Workers pricing | Cloudflare Pages limits

Cold starts and edge performance: Cloudflare wins by an order of magnitude

This is the technical gap that matters most if you are serving a global audience with server-side rendering.

Platform	Cold start p50	Cold start p95	Warm rate
Cloudflare Workers	—¹	—¹	99.99%
Vercel Edge Functions	~106ms	~178ms	—
Vercel Node.js (Serverless)	~859ms	~1,046ms	—

¹ The Cloudflare Shard & Conquer blog post reports warm rate (99.99%) and cold start rate (0.01%), not p50/p95 latency figures. Millisecond-level percentiles for Cloudflare Workers cold starts are not available from this source.

Cloudflare’s October 2025 Shard & Conquer update achieved a 10× reduction in cold starts (cold start rate now 0.01%) and a 99.99% warm rate. That is a fundamentally different operational profile from Vercel’s Node.js runtime.

Vercel’s Fluid Compute (GA April 2025) introduced in-function concurrency with billing paused during I/O wait, and Vercel states it reduces the frequency of cold starts — no specific percentage is published in the official announcement. That helps with cost efficiency and with bursty traffic, but the absolute cold start numbers remain in the hundreds of milliseconds for Node.js. The OpenStatus study measured Vercel Serverless functions; Fluid Compute-specific benchmarks have not been independently published.

Sources: Cloudflare Shard & Conquer | OpenStatus Vercel latency study

For a deeper runtime-level comparison of Workers versus Vercel Functions, see Cloudflare Workers vs Vercel Functions: 2026 comparison.

Network coverage: Cloudflare dominates outside US/EU

Cloudflare operates 300+ PoPs with consistent sub-50ms delivery worldwide. Vercel operates roughly 50–100 PoPs, concentrated in the US, EU, and Japan.

The Bejamas (January 2025) benchmark captures this well. For static files from eu-west-3, Vercel was faster — 41ms TTFB versus Cloudflare’s 53ms. That flips dramatically for dynamic edge functions: in af-south-1 (South Africa), Cloudflare TTFB was 41ms while Vercel’s was 1,203ms — a 29× difference. Across all 15 tested global regions, Cloudflare’s edge functions were faster.

If your audience is in Africa, LATAM, or Southeast Asia, this is a hard constraint, not a soft preference.

Source: Bejamas Cloudflare Pages vs Vercel

Next.js support: Vercel is canonical, Cloudflare is close

Vercel is the company behind Next.js, so “canonical host” is not marketing — it means zero-config support for every feature on release day: App Router, RSC, PPR, Server Actions, ISR, Image Optimization, and Node Middleware including the 15.2+ additions.

Cloudflare Pages runs Next.js through the OpenNext adapter. As of mid-2026, OpenNext covers:

App Router, SSR, SSG, ISR
Server Actions, PPR
Middleware (but not Node Middleware from Next.js 15.2+)
Image optimization

What it does not cover:

Node Middleware 15.2+ — this requires a Node.js runtime; Cloudflare Workers run V8 isolates, not Node.js
Workloads needing >128MB memory — Workers are capped at 128MB versus Vercel’s 4GB
Bundles over 10MB compressed — Workers enforce a 10MB compressed bundle limit versus Vercel’s 250MB

The next-on-pages adapter is now deprecated. If you are on Cloudflare and still using it, migrate to OpenNext.

For most Next.js apps — especially those built on the stable App Router feature set — OpenNext works. For teams tracking next/canary or using ML inference in route handlers, Vercel is still the correct host.

Sources: OpenNext Cloudflare docs | next-on-pages deprecation

Build times: no primary-source data

No independent benchmark for build times exists that covers both platforms on comparable workloads. Do not let anyone sell you a number here without a citation.

What is documented: Vercel offers a 45-minute build timeout with three machine tiers — Standard ($0.014/min), Enhanced ($0.028/min), and Turbo ($0.105/min). Cloudflare enforces a 20-minute build timeout with no tiering.

The shorter timeout is a real constraint if you have a monorepo or a large Astro site with thousands of static paths. For a typical Next.js app, 20 minutes is sufficient.

Observability: Vercel is the clear winner

Vercel ships a built-in observability dashboard on all plans, Web Analytics (50K events/month free), Speed Insights, and — as of October 2025 — Vercel Drains for exporting logs and metrics to Datadog, New Relic, and other third-party tools.

Cloudflare Pages has no analytics in the Pages dashboard itself. Cloudflare Web Analytics exists as a separate product — it is free, privacy-first, and requires no cookies — but it is less rich than Vercel’s offering and not integrated into the deployment view. If you need traces, errors, and performance data in one place without external tooling, Vercel wins this category outright.

Sources: Vercel observability docs | Vercel Drains announcement

2026 platform updates worth knowing

Vercel

Fluid Compute GA (April 2025): in-function concurrency, billing pauses on I/O wait, reduced cold start frequency for Node.js workloads (no specific percentage published)
Next.js 16: Cache Components and the use cache directive for fine-grained caching control
AI SDK 6: agents and MCP (Model Context Protocol) support

Cloudflare

Shard & Conquer (October 2025): 10× cold start reduction, 99.99% warm rate
OpenNext adapter maturation: the majority of Next.js App Router features now work on Workers; next-on-pages deprecated
Cloudflare Containers: run Docker containers co-located with Workers on paid plans — pricing details not yet publicly available

Verdict

Pick Cloudflare Pages if:

You care about price — the $5/month flat rate for teams is hard to argue against
Your users are distributed globally, especially in Africa, LATAM, or Southeast Asia
Your Next.js app stays within the mainstream App Router feature set
You do not need integrated observability out of the box

Pick Vercel if:

You are tracking the Next.js release cycle closely and depend on features like Node Middleware 15.2+ before they land in OpenNext
Your server-side code needs more than 128MB memory or a bundle over 10MB compressed
You want a single dashboard for deployments, analytics, and performance data with no assembly required
Cold starts in the 100ms range are acceptable for your use case

The question is not which platform is better in the abstract. It is whether you need what Vercel’s DX premium buys you. For most teams, the answer in 2026 is no.

For a full cost-benefit breakdown of Vercel specifically — including the exact thresholds where the math breaks — see Vercel in 2026: is it still worth it?.

Caveats

Build times: no primary-source benchmark was found for either platform. The section above documents timeouts and billing, not measured build durations.
OpenNext coverage: the adapter covers most Next.js features but not all. Verify the specific features your app relies on against the OpenNext Cloudflare compatibility page before migrating.
Cloudflare Containers pricing: the product launched in 2026 but detailed pricing is not yet public. Check Cloudflare Containers docs before factoring it into a cost model.
No affiliate relationships: toolchew has no affiliate arrangement with Vercel or Cloudflare. All URLs in this article are direct links.