Vercel vs Cloudflare Pages
Vercel gives you the best Next.js experience with excellent DX. Cloudflare Pages gives you unlimited bandwidth on a much larger edge network and a real backend via Workers. Pick Vercel for speed of shipping Next.js; pick Cloudflare Pages for cost efficiency, global reach, and full-stack on the edge.
Two products, side by side.
Best-in-class Next.js hosting with previews and edge functions
- Best Next.js DX
- Fast edge functions
- v0 + AI SDK integrated
- Preview per commit
- Bandwidth costs can spike
- Function bundle size caps at 250 MB
- Fewer regions than Cloudflare
Static + serverless on Cloudflare's global 300+ location network
- Unlimited free bandwidth
- 300+ edge locations
- Workers give you a full backend
- D1, R2, KV, Durable Objects integrated
- Cheapest at scale
- Next.js support is via next-on-pages adapter, some edge-cases missing
- Workers have a learning curve
- DX not as polished as Vercel
Vercel vs Cloudflare Pages on the specs.
| Feature | Vercel | Cloudflare Pages |
|---|---|---|
| Bandwidth (free) | 100 GB / mo | ✓Unlimited |
| Edge locations | 30+ | ✓300+ |
| Next.js support | ✓Native | via @cloudflare/next-on-pages |
| Backend runtime | Vercel Functions (Node + Edge) | Workers (V8 isolates) |
| Database options | Bring your own | ✓D1 (SQLite), Durable Objects, KV |
| Object storage | Bring your own | ✓R2 (S3-compatible, no egress fees) |
| DX | ✓Best in class | Good, improving fast |
| Preview URLs | Per commit | Per commit |
| AI tools | v0, AI SDK, AI Gateway | Workers AI (bind LLMs on the edge) |
| Function cold start | ~50-200 ms | ✓<5 ms (isolates) |
What you will actually pay.
| Tier | Vercel | Cloudflare Pages |
|---|---|---|
| Free | $0 (Hobby, 100 GB bandwidth) | $0 (unlimited bandwidth, 500 builds / mo) |
| Pro | $20 / user / mo + $40/100 GB overage | $5 / mo (Workers Paid) |
| Egress | Included, then $40 / 100 GB | R2: $0 egress |
Which one should you pick?
You are shipping a Next.js app, you want the best DX possible, and you are willing to trade some bandwidth cost for zero friction.
You care about global performance, want unlimited free bandwidth, are OK adopting Cloudflare Workers for backend logic, or you are shipping SvelteKit / Astro / Remix / static content.
For a static marketing site, either is fine. Cloudflare Pages is cheaper if you get any real traffic (Vercel bandwidth adds up fast).
Related matchups.
Common questions.
Can I run Next.js on Cloudflare Pages?
Yes via @cloudflare/next-on-pages. Most features work but you'll hit occasional adapter gaps on brand-new Next.js features. Vercel is safer for cutting-edge Next.js.
Which has faster cold starts?
Cloudflare, Workers use V8 isolates with sub-5ms cold starts. Vercel functions are Node-based and take 50-200ms.
Which is better for a static site?
Cloudflare Pages wins on cost (unlimited bandwidth) and global performance (300+ locations).
Can I switch later?
Yes if you keep your app framework-standard. Migration mostly means changing the adapter and env vars. Cloudflare-specific bindings (KV, D1, Durable Objects) are the lock-in points.
Is Cloudflare Pages good for indie hackers?
Yes, especially post-launch. The unlimited-bandwidth free tier means a Product Hunt spike will not blow your budget the way Vercel can.
Open the tool.
Once you have picked, grade your stack across 10 production categories in 3 minutes. Free, honest, prioritised fix plan.
Grade the Vercel or Cloudflare Pages setup you pick