Cloudflare Pages vs Vercel vs Netlify — free tier comparison 2026

Three platforms dominate free static site hosting in 2026: Cloudflare Pages, Vercel, and Netlify. All three offer generous free tiers. The right choice depends on specific project needs.

Here is a practical comparison based on real usage.

The 30-second summary

• Cloudflare Pages — best for unlimited bandwidth, fastest global CDN
• Vercel — best for Next.js and full-stack apps, excellent developer experience
• Netlify — best for JAMstack conventions, mature form and function support

Feature-by-feature comparison

Feature	Cloudflare Pages	Vercel	Netlify
Bandwidth	Unlimited (unmetered)	100 GB/month	Legacy: 100 GB/month • New: ~15 GB (credit-metered)
Requests	Unlimited static	1M edge requests/month	Credit-metered on new plan
Build minutes / deploys	500 builds/month	6,000 build minutes/month	Legacy: 300 min • New: ~20 deploys from credits
Concurrent builds	1	1	1
Sites per account	100	Effectively unlimited	Unlimited
Custom domain	Free	Free	Free
SSL	Free (auto)	Free (auto)	Free (auto)
Serverless functions	Billed via Workers plan (100K req/day)	1M invocations, 4 CPU hours, 300s timeout	Legacy: 125K invocations, 100 hrs • New: credit-metered, 10s timeout
Team collab (free)	Limited	Free with limits	Free with limits
Analytics	Free (Web Analytics)	Basic free	Paid

When each wins

Cloudflare Pages — best for scale

Unlimited bandwidth is the killer feature. No other free tier matches this.

If a site suddenly hits 10 TB traffic:

• Cloudflare: $0
• Vercel: charged for overage
• Netlify: charged for overage

Also excellent at:

• Sites with lots of images/videos
• Content that could go viral (no bandwidth panic)
• Global performance (largest edge network)
• Free Web Analytics without cookies

Weaker at:

• Server-side rendering (Workers work but different mental model)
• Framework-specific integrations (less polished than Vercel’s Next.js support)

Vercel — best developer experience

Fastest way to deploy any framework. Next.js is first-class. Astro, Nuxt, SvelteKit, Remix all work out-of-box.

Excellent at:

• Framework-heavy sites (Next.js especially)
• Serverless functions (integrated deeply)
• Preview deployments on every PR
• Team collaboration
• Documentation and support

Weaker at:

• Bandwidth-heavy sites (100 GB cap)
• Cost predictability at scale (bills can grow fast on Pro tier)

Netlify — best JAMstack conventions

Pioneered many JAMstack patterns. Forms, redirects, and split testing built-in.

Excellent at:

• Forms (native, no external service)
• Redirects and rewrites (simple config file)
• Split testing / A/B testing
• Long-standing plugin ecosystem
• Mature CMS integrations

Weaker at:

• Build minutes (only 300/month — tight for large sites)
• Framework-specific optimizations (Vercel edges out)
• Serverless function limits

Real-world scenarios

Blog with 10,000 monthly visitors

All three handle this trivially on free tier. Pick based on preference.

Winner: any of the three. Cloudflare Pages if bandwidth might spike.

Small SaaS marketing site + docs

Vercel or Netlify. Both handle framework integrations best. Vercel’s Next.js support wins if using Next.js.

Portfolio / personal site with rich media

Cloudflare Pages. Unlimited bandwidth means embedded videos and high-res images don’t push into paid tier.

E-commerce demo / product showcase

Vercel or Netlify. Both handle Shopify/Snipcart/checkout integrations well.

Documentation site for open-source project

Cloudflare Pages. Bandwidth cost matters when popular OSS gets thousands of daily visits.

Serverless API + static frontend

Vercel. Serverless functions are most polished. Cloudflare Workers are competitive but different paradigm.

Migration cost

Moving between the three is straightforward — all three support:

• Direct Git integration
• Standard build systems
• Same-day domain migration

Realistic migration: 1-2 hours for a small site. All three deploy the same static output.

The catch on each

Cloudflare Pages

• Workers (serverless) have their own pricing after 100K requests/day
• Some routing patterns require Cloudflare Workers, not just Pages
• Analytics is free but requires enabling the Cloudflare Web Analytics beacon
• Rate limiting available but requires Cloudflare Pro ($20/month) for full control

Vercel

• 100 GB bandwidth is enough for ~500K-1M monthly page views typically
• Hobby has no pay-per-GB overage — you must upgrade to Pro ($20/user/month) once you hit the limit
• Serverless function execution time is 300 seconds (5 min) default on Hobby, individual function build has 45 min max
• Commercial use of Hobby tier is technically not allowed (must upgrade to Pro)

Netlify

• Netlify restructured its free plan on September 4, 2025. Accounts created before that date stay on the legacy plan (100 GB bandwidth + 300 build minutes + 125K function invocations). New accounts use a credit system: 300 credits/month shared across bandwidth (20 credits/GB), deploys (15 credits each), and functions (10 credits/GB-hour).
• On the credit plan, 300 credits translates to roughly 15 GB bandwidth OR 20 production deploys — not both
• Forms: 100 submissions/site/month on free plan; edge functions get 1M invocations/month separately from the credit pool
• Commercial use of the free tier is allowed but hard-capped (no auto-recharge on free)

Pricing when you outgrow free

Platform	Next tier	Cost
Cloudflare Pages	Workers Paid	$5/month + usage
Vercel	Pro	$20/user/month
Netlify	Pro	$19/user/month

Cloudflare’s paid tier is cheaper per feature. Vercel and Netlify get expensive quickly for teams.

Reproduce this yourself

All three offer free signup with no credit card required for the free tier.

• Cloudflare Pages: https://pages.cloudflare.com
• Vercel: https://vercel.com
• Netlify: https://netlify.com

Deploy the same test repo on all three. Compare:

• Build time
• Deploy speed
• Custom domain setup difficulty
• Analytics quality
• Support responsiveness

Typical result: all three deploy in under a minute for a small site.

Combined strategy — using multiple

Serious projects sometimes use multiple:

• Primary hosting: Cloudflare Pages (bandwidth-safe)
• Preview deployments: Vercel (better PR previews)
• Forms and CMS: Netlify (mature integrations)

This adds complexity but leverages best-of-breed.

For most solo developers and small teams, pick ONE and stick with it. Migration cost is low if requirements change later.

Recommendation by profile

• Blog / personal site: Cloudflare Pages (bandwidth peace of mind)
• Next.js app: Vercel (first-class support)
• JAMstack with forms: Netlify (built-in forms)
• Open-source docs: Cloudflare Pages (bandwidth)
• E-commerce: Vercel or Netlify (framework integrations)
• Anything might go viral: Cloudflare Pages (unlimited bandwidth)

Bottom line

For 2026, all three free tiers are excellent. There is no bad choice.

If uncertain, pick Cloudflare Pages first. Unlimited bandwidth means no surprise bills, no scaling anxiety, no complexity if traffic grows.

Switch to Vercel if using Next.js and want smoothest DX.

Choose Netlify if JAMstack conventions (forms, redirects, A/B tests) match your needs.

Deploy time is under a minute on all three. Try them.