Vercel vs Netlify vs Cloudflare Pages in 2026: The Hosting Showdown

At 10K monthly visits, all three are free. At 100K visits with moderate serverless usage, the costs diverge significantly — and by 1M visits, Cloudflare Pages is meaningfully cheaper than Vercel, while Netlify lands in the middle. The honest 2026 answer: Vercel wins on Next.js developer experience, Cloudflare Pages wins on cost at scale, and Netlify wins when you need form handling, split testing, and CMS integrations without writing infrastructure. At WebVerse Arena, we use all three depending on the project — Next.js on Vercel for application-heavy projects, Astro on Cloudflare Pages for marketing sites with high traffic, and Netlify for JAMstack projects with content teams who use Netlify CMS or Decap CMS. Understanding when each wins requires looking at actual pricing numbers, not marketing page comparisons.

Free tier comparison (2026): Vercel Free includes 100GB bandwidth/month, 100 serverless function invocations/day (Hobby tier limit — this is extremely restrictive for any real application), 6,000 build minutes/month, and Next.js Edge Middleware. Netlify Free includes 100GB bandwidth/month, 125,000 serverless function invocations/month (far more generous than Vercel Hobby), 300 build minutes/month, 1 concurrent build, and 100 form submissions/month. Cloudflare Pages Free includes unlimited bandwidth (this is not a typo — Cloudflare does not charge for bandwidth), 500 builds/month, 100,000 Workers requests/day, and unlimited sites. For a marketing site or low-traffic application, Cloudflare Pages' unlimited bandwidth and generous Workers quota make it the obvious free-tier winner. Netlify's 125K function invocations on the free tier beat Vercel's 100/day by orders of magnitude.

Pricing at 100K monthly visits: assuming a typical Next.js or Astro site with moderate serverless function usage (50,000 function invocations/month, 50GB bandwidth beyond free), the costs break down as follows. Vercel Pro ($20/month per member): includes 1TB bandwidth and 1,000,000 function invocations, making 100K visit usage essentially free within the Pro plan — the $20 is the floor. Netlify Pro ($19/month): includes 400GB bandwidth and 125,000 function invocations/month; 100K visits with moderate API routes fits well within this tier. Cloudflare Pages (Workers Paid at $5/month): includes 10M Workers requests/month and 10ms CPU time per request; 100K visits sits comfortably in the $5 plan. The winner at 100K visits: Cloudflare at $5/month if your functions are edge-compatible. Vercel and Netlify are comparable at $19–20/month for the base Pro plan, but Vercel's per-member pricing becomes relevant for teams.

Pricing at 1M monthly visits: this is where the cost curves separate decisively. Vercel: the Pro plan covers 1TB bandwidth; at 1M visits with an average page size of 200KB, you're using ~200GB — within the plan. Function invocations at 1M visits with a 20% API call rate = 200,000 invocations — within Pro's 1M included. Total: ~$20/month per member (plus team seat costs if 3+ members). However, Vercel's Edge Function execution time and Image Optimization requests are billed separately — a site serving 1M visitors with significant image optimisation usage can hit $50–200/month in overages. Netlify: 1M visits at 200KB average = 200GB bandwidth — within the $19 Pro plan's 400GB. But function compute time: Netlify charges $25/125K invocations beyond the included quota; at 200K invocations you're $25 over. Total: ~$44/month. Cloudflare Pages (Workers Paid $5/month): 1M visits = ~1M Workers requests; the $5 plan includes 10M, so 1M visits is within the base plan. Bandwidth: unlimited and free. Total: $5/month. The gap at 1M visits is stark — Cloudflare Pages is 4–9x cheaper.

Edge runtime comparison: all three platforms offer edge compute, but with different runtimes and trade-offs. Vercel Edge Runtime uses the V8 Isolates model and supports a subset of Node.js APIs — no Node file system, no native modules, limited crypto. It integrates natively with Next.js Middleware and Edge Functions. Cold starts: near-zero (< 1ms) because V8 Isolates don't cold-start like Lambda functions. Netlify Edge Functions use Deno on Deno Deploy infrastructure — full Deno APIs, npm package compatibility via Deno's npm specifier, near-zero cold starts. More flexible than Vercel's edge runtime but less integrated with Next.js specifically. Cloudflare Workers (the runtime under Cloudflare Pages) is the most mature edge runtime — 7 years old, battle-tested at Cloudflare's scale, with the Workers platform offering KV storage, Durable Objects, D1 (SQLite at the edge), R2 (S3-compatible object storage), and Queues as companion primitives that Vercel and Netlify don't match. For edge-native architecture, Cloudflare's ecosystem is significantly deeper.

Developer experience: Vercel's CLI (`vercel dev`, `vercel deploy`) is the most polished, with direct Git integration, automatic preview URLs, comment-on-PR deploy previews, and Vercel Analytics (Web Vitals monitoring) built in. The Vercel Dashboard is the most intuitive of the three, and the integration between Vercel and Next.js is unsurprisingly seamless — features like ISR revalidation on-demand, Middleware config, and Image Optimisation are designed to work together. Netlify's CLI is strong, its CMS integrations (Decap CMS, Sanity, Contentful) and form handling (no backend code needed for contact forms) are unique advantages, and its split testing (A/B testing via URL-based traffic splitting) works out of the box. Cloudflare's DX has improved substantially — Wrangler CLI, the Pages dashboard, and the Workers+Pages integration are now solid — but the learning curve for Cloudflare-specific primitives (KV, D1, Durable Objects) is steeper than Vercel or Netlify for developers new to the platform.

Our recommendation: Next.js projects default to Vercel — the DX advantage and tight framework integration justify the cost at typical agency project scale (under 500K visits/month). Astro, Remix, or SvelteKit marketing sites for high-traffic clients go to Cloudflare Pages — the cost savings at scale are too significant to ignore, and the Cloudflare Workers ecosystem is mature enough to meet any requirement. Netlify remains our choice for content-team-managed sites that use Decap CMS or need Netlify's built-in form handling, split testing, and identity features without building infrastructure. One tactical note: Vercel's per-seat pricing ($20/seat/month on Pro) penalises large teams — a 5-person team pays $100/month before any usage, versus Netlify's flat $19/month or Cloudflare's $5/month. For agency setups managing multiple client projects, Cloudflare Pages' pricing model scales the most favourably. We're happy to audit your hosting costs and recommend a migration path.