All guides
Next.js is a React framework that can render pages at build time, on the server or at the edge. Where you host it changes cost, speed and how much work you take on. Both Vercel and Cloudflare are strong choices; they differ in how closely they track the framework.
| Question | Vercel | Cloudflare |
|---|---|---|
| Framework support | Built by the Next.js team, so new features land first | Supported through the OpenNext adapter on Workers; check feature coverage for your version |
| Setup effort | Connect a repository and deploy | Slightly more configuration |
| Strengths | Previews on every pull request, simple operations | Global network, strong security tooling, generous static asset delivery |
| Watch for | Usage-based pricing as traffic grows | Edge runtime limits for some Node.js libraries |
How to decide
- Mostly static pages with a contact form: either works, so pick on price and who will operate it.
- Server rendering, image optimization and incremental regeneration with full Node.js APIs: Vercel is the lowest-friction option.
- You already run DNS, WAF and Zero Trust on Cloudflare and want one vendor: Cloudflare is attractive.
- Avoid lock-in by keeping business logic out of host-specific APIs and by documenting the deploy.
Habits that matter more than the host
- Render on the server by default and send as little client JavaScript as you can.
- Use next/image and next/font so images and fonts do not shift the layout or slow loading.
- Keep Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 ms and layout shift under 0.1.
- Set a canonical URL, a unique title and description per page, and structured data for your business.
- Add security headers and a Content-Security-Policy, and re-run an audit before each release.