Vercel vs Netlify vs Cloudflare Pages: where to host your site
Vercel fits Next.js with server features, Cloudflare is cheapest for static sites, and Netlify suits mixed frameworks. Prices, limits and fit.
By Sohail Hussain21 November 20266 min read
Choose Vercel if your site is built in Next.js and uses its server features, and you want them to work with no configuration. Choose Cloudflare if the site is static or mostly static and you want the lowest cost at any traffic level, including commercial use on the free plan. Choose Netlify if you build with a mix of frameworks, want built-in extras such as form handling, and prefer one flat price for the whole team.
All three deploy from a Git repository, give you preview links for every change, serve pages from a global network, and handle SSL. For a small static company site, any of them works. They differ in billing model, in how fully they support Next.js, and in what happens when traffic grows. For the Next.js sites we build as part of our website design and development work, the deciding question is which Next.js features the site uses.
How do the three compare?
| Vercel | Netlify | Cloudflare Pages / Workers | |
|---|---|---|---|
| Free plan (as of October 2026) | Hobby: personal, non-commercial use only | Free: 300 credits a month, hard limit | Free: commercial use allowed |
| First paid plan (as of October 2026) | Pro: $20 per developer seat a month | Personal $9; Pro $20 a month with unlimited members | Workers Paid: from $5 a month per account |
| Billing model | Seats plus metered usage over an included allowance | Credits for deploys, bandwidth, requests and compute | Requests and compute; static assets free |
| Bandwidth | Hobby 100 GB; Pro 1 TB, then from $0.15 per GB | 20 credits per GB | Static asset requests free and unlimited |
| Next.js support | Built by the Next.js team; verified adapter | Own integration; verified adapter in progress | Own integration on Workers; verified adapter in progress |
| Best for | Next.js sites using server features | Mixed frameworks, small teams, built-in forms | Static and mostly static sites, cost-sensitive traffic |
Plans change often. Check Vercel's pricing, Netlify's pricing and Cloudflare Workers pricing before you commit. To estimate your own traffic and bandwidth, use our website hosting cost calculator.
When is Vercel the right choice?
Your site is Next.js and uses what Next.js does on a server. Incremental regeneration when content changes, Draft Mode previews for editors, Server Actions for forms, image optimisation, Proxy for redirects by country. Vercel builds Next.js, and the Next.js deployment documentation lists Vercel among its verified adapters. Everything works on the first deploy.
You want the least setup. Connect the repository, add environment variables, deploy. Preview deployments for every branch are useful for client and editor review.
You are a small team. Pro is priced per developer seat, and viewers are free. A company with one or two developers and editors who only use the CMS pays for one or two seats.
The catch is the free plan. As of October 2026, Vercel describes Hobby as for personal, non-commercial use. A company site on Hobby is outside the terms, however small it is. Budget for Pro, at $20 a seat a month, which includes $20 of usage credit and 1 TB of data transfer. Most company sites never go beyond that.
When is Cloudflare the right choice?
The site is static, or close to it. A static export, a documentation site, a marketing site with forms handled elsewhere. As of October 2026, Cloudflare states that requests to static assets on Workers are free and unlimited. Cloudflare Pages, the older product for static sites, allows 500 builds a month on the free plan, 20,000 files per site and files up to 25 MiB each.
Traffic is high or unpredictable. Because static asset requests are free, a spike from a campaign or a viral post does not produce a bill. On metered hosts the same spike costs money.
You want a commercial site on a free plan. Cloudflare's free plan has no non-commercial restriction.
For Next.js sites using server features, Cloudflare runs them on Workers through its own integration. The Next.js documentation lists Cloudflare as working on a verified adapter, with its own integration available in the meantime. Most features work; test the ones you rely on, such as image optimisation and on-demand revalidation, before committing. Cloudflare's paid Workers plan starts at $5 a month per account, as of October 2026.
When is Netlify the right choice?
You build with more than one framework. Netlify has supported static site generators, Astro, Nuxt, SvelteKit and Next.js for years. An agency or team with sites in several frameworks gets one dashboard for all of them.
You want simple built-in extras. Form handling without a server, split testing between branches, and a plugin ecosystem for builds.
You want a flat team price. As of October 2026, Netlify Pro is $20 a month with unlimited team members and 3,000 credits. For a team with several developers, that can be cheaper than per-seat pricing.
Watch the credits. Netlify bills deploys, bandwidth, requests and compute from one pool: 15 credits per production deploy, 20 credits per GB of bandwidth and 2 credits per 10,000 requests, as of October 2026. On the free plan's 300 credits, ten production deploys (150 credits) and 7.5 GB of bandwidth (150 credits) use the whole month. When a free account runs out, Netlify pauses its sites until the next cycle. Preview and branch deploys do not use credits. For a business site that publishes often, plan on a paid plan from the start.
Next.js runs on Netlify through its own integration, and like Cloudflare, Netlify is working on a verified adapter.
Does a static site even need one of these?
Not necessarily. A fully static site, including a Next.js static export, is a folder of HTML, CSS and JavaScript files. It runs on any web host, an object storage bucket behind a CDN, or a plain VPS. The three platforms add convenience: Git-based deploys, previews, automatic SSL and a global CDN. For most teams that convenience is worth far more than its cost, which is often zero. Our guide to static vs dynamic websites explains which kind your site is.
If you are hosting WordPress, none of these three is the right home, because they do not run PHP. See where to host a WordPress site, and shared vs VPS vs managed hosting for the server-based options.
How should you decide?
- Is the site static or does it use Next.js server features? Static: Cloudflare or any of the three. Server features: Vercel first, then test on the others.
- Is it a commercial site? Then Vercel Hobby is out. Cloudflare's free plan is in.
- How many people deploy? One or two: Vercel's per-seat pricing is fine. Several: compare with Netlify's flat Pro price.
- Could traffic spike? Cloudflare's free static assets remove that risk.
- Who owns the account? Your company, on its own card, with your developer added as a member. The same rule applies to the domain.
For why we build company sites in Next.js in the first place, read why we build company websites with Next.js. For the larger platform decision, WordPress vs custom website covers both sides.
Was this guide useful?