vercelvscloudflare pages
for: Vercel for Next.js teams who want the best developer experience and preview deployments — Cloudflare for cost-sensitive teams needing global edge performance without bandwidth bills
skip if: Vercel at high bandwidth scale where costs compound — Cloudflare for Next.js teams who don't want to deal with adapter quirks
the cost gap at scale is real: vercel's bandwidth pricing can become significant at high traffic, while cloudflare's network is included. but vercel's next.js DX is purpose-built and still meaningfully better. for next.js: vercel. for other frameworks: cloudflare is worth a serious look.
the honest framing: vercel owns the next.js deployment story and cloudflare owns the "I need global edge performance at minimal cost" story. these are different stories for different teams.
vercel built next.js and their deployment platform is deeply integrated with it. preview deployments are excellent. edge config and analytics are native. the CI/CD pipeline is seamless. if you're on next.js and not price-sensitive at scale, vercel is the better experience with less friction.
cloudflare's edge network is the world's largest by some measures, and their pricing model doesn't charge for bandwidth. at significant scale, a vercel bill can become painful in ways that cloudflare's doesn't. cloudflare's developer tools have caught up significantly — workers, KV, R2, D1 — and pages is a legitimate deployment platform. the friction for next.js-specific features is real but manageable.
what each one actually is
Vercel is the deployment platform built by the creators of Next.js. it pioneered the preview deployment model (every PR gets a URL) and the serverless function approach for frontend frameworks. vercel's business model is usage-based hosting — you pay for builds, bandwidth, function invocations, and add-on products (analytics, edge config). the developer experience for next.js apps is the best available anywhere, period.
Cloudflare Pages is Cloudflare's static site and JAMstack deployment platform, built on Cloudflare's edge network. it's a significantly younger product than vercel (launched 2021) but backed by Cloudflare's infrastructure advantage: a network in 300+ cities, unlimited bandwidth, and pricing that doesn't charge for traffic. cloudflare pages integrates with cloudflare workers for serverless functions and the broader cloudflare developer platform.
pricing, honestly
vercel hobby (free): 100GB bandwidth/month, 100GB-hours of function execution, 6,000 build minutes. vercel pro: $20/month per seat, 1TB bandwidth, more function capacity. overages on bandwidth and function execution are real and can surprise teams at scale. vercel enterprise pricing is custom and typically significant.
cloudflare pages free: unlimited bandwidth, 500 builds/month, 100,000 worker requests/day (via workers integration). cloudflare pages paid ($5/month through the workers paid plan): unlimited builds, higher worker limits. the price difference at scale is stark — a site doing 10TB of bandwidth per month costs nothing additional on cloudflare and hundreds of dollars on vercel's pro plan.
what it's actually like to use them
vercel's DX is the standard that other platforms are measured against. connect a github repo, pick your framework, deploy. preview URLs per branch work out of the box. environment variables, domain management, and analytics are in a clean dashboard. for a next.js project, the default experience requires zero configuration — vercel knows what to do.
cloudflare pages has improved dramatically and the experience for most frameworks is genuinely good. the main roughness is specifically for next.js: the @cloudflare/next-on-pages adapter works but requires configuration that vercel doesn't, and some next.js features require workarounds or are unsupported. for astro, nuxt, sveltekit, or other frameworks, cloudflare pages is quite smooth and the unlimited bandwidth is a meaningful advantage.
who vercel is for
- next.js teams who want the best deployment experience with zero configuration
- teams that value preview deployments heavily in their review workflow
- projects where DX time-savings outweigh the bandwidth cost differential
- early-stage startups where traffic is low and the free tier covers everything
who cloudflare pages is for
- teams on non-next.js frameworks (astro, sveltekit, nuxt, remix on edge) who want global edge performance
- cost-conscious teams at scale where bandwidth pricing is a real budget line
- teams building apps on the cloudflare developer platform (workers, KV, D1, R2)
- companies with compliance requirements that benefit from cloudflare's security and DDoS protection layer
when to avoid each
don't use vercel if you're consistently above 1TB bandwidth/month and price-sensitive. the overages add up. and don't use vercel as the long-term plan if your next.js app does lots of heavy static asset delivery — cloudflare's CDN performance is competitive and much cheaper for that pattern.
don't use cloudflare pages as your primary deployment target for a next.js app where you use every next.js feature. server actions, streaming, partial prerendering, and some advanced API patterns have incomplete support on cloudflare pages via the adapter. the friction is manageable for teams who know what they're trading off, but rough for teams who discover it in production.
stuff their landing pages won't tell you
- vercel's analytics product costs extra — the "included" web vitals are basic; vercel analytics is an additional $14/month per project on pro
- cloudflare pages builds can be slow relative to vercel — cloudflare is improving this but build times sometimes lag
- vercel has a "spend management" feature to cap usage; set it up early or risk surprise invoices
- cloudflare's DDoS protection and WAF are automatically included — vercel has no equivalent, you'd add cloudflare in front of vercel for this (which some teams do)
- vercel's free tier limits are for "hobby" use — their terms prohibit commercial projects on the hobby plan
- cloudflare pages supports git branches via preview deployments now (added 2023), matching vercel's original differentiator
the call
next.js: vercel. the DX advantage is real and the platform integration is deep. unless you're at a scale where the bandwidth bill is hurting.
not next.js: seriously evaluate cloudflare pages first. unlimited bandwidth, global edge, and the cloudflare developer platform are compelling. for astro, sveltekit, or nuxt, cloudflare pages is often the better deployment target in 2026.
you can also use both: vercel for staging and PR preview deployments (the DX there is unmatched), cloudflare pages for production (the scale economics are better). some teams run exactly this configuration.
frequently asked
how does bandwidth pricing compare?
can next.js run on cloudflare pages?
how do build minutes compare?
what about cloudflare workers vs vercel edge functions?
can i use a custom domain on both free plans?
what about netlify?
some links on this page are affiliate links. we earn a small commission if you sign up, at no extra cost to you. we don't change verdicts for affiliate money — see how this site makes money.
last updated: june 14, 2026
related
Vercel vs Netlify
Vercel wins for Next.js teams and modern frontend DX. Netlify still better for plain static sites and simple functions if you're not on Next.
PlanetScale vs Neon
planetscale for MySQL + schema branching at production scale. neon for serverless postgres with a genuinely useful free tier.