Vercel vs Netlify vs Cloudflare: The Free Tier Showdown

Deploying a website in 2026 is almost embarrassingly easy: connect a Git repository to a platform, push, and seconds later your site is live on a global CDN with HTTPS, previews per pull request and rollbacks included. Free.

The interesting question is no longer whether the big three — Vercel, Netlify and Cloudflare (Pages/Workers) — can host your project for free, but which free tier fits your project’s shape, and where each one’s limits will eventually pinch. Having deployed production projects on all three, here’s the honest comparison.

The short version

If you just want a recommendation: personal/hobby projects → any of the three; Next.js apps → Vercel; content sites expecting traffic → Cloudflare; balanced team projects on a budget → Netlify or Cloudflare. Now the details that justify it.

Click to enlarge

Vercel: the framework company

Vercel builds Next.js, and it shows: zero-config deployments where Next’s hybrid rendering, image optimization and caching all work exactly as documented. The developer experience remains the segment’s gold standard — the dashboard, preview deployments with commenting, and instant rollbacks are genuinely polished. For non-Next frameworks (Astro, SvelteKit, Nuxt), support is also excellent.

The catches. First, and most important: the Hobby tier is licensed for non-commercial use only. A blog with ads, a client site, a startup landing page — technically all require Pro ($20/user/month). People ignore this until they can’t. Second, Vercel’s à-la-carte pricing after the free tier is famously easy to underestimate: functions, image optimization, and data transfer are each metered, and viral traffic on a misconfigured app has produced legendary surprise bills (spend caps now exist — set them). Third, the platform’s magic is Next-shaped; if you use its more proprietary conveniences, migrating later means unwinding them.

Choose Vercel when: it’s a Next.js project, it’s genuinely non-commercial (or you’ll pay Pro happily), and DX is the priority.

Netlify: the balanced veteran

Netlify essentially invented this category, and its free tier remains the best balanced package: 100 GB bandwidth, functions, redirects/headers config, split testing, and small conveniences the others make you assemble yourself — form handling with spam filtering (contact forms with zero backend), scheduled functions, and a mature plugin ecosystem. Framework support is deliberately neutral: Astro, Next, SvelteKit, Eleventy all first-class.

The catch is 300 build minutes per month — by far the lowest. A chunky site building on every push (and every PR preview) can burn through it; content-heavy sites with frequent deploys feel it first. Mitigations exist (build skipping, caching), but it’s the number to watch. Function limits (125k invocations, 100 hours) are fair but real; and like Vercel, overage means a $19/user/month step up rather than pay-per-use — though free-tier commercial use is allowed, which matters for small paid projects.

Choose Netlify when: you want the most well-rounded free package with allowed commercial use, you value forms/redirects/plugins out of the box, and your build frequency is moderate.

Cloudflare: the infrastructure giant

Cloudflare comes at hosting from the opposite direction — it runs a substantial fraction of the internet’s edge network, and Pages/Workers are that network productized. The free tier is structurally different: unlimited bandwidth for static assets. Not 100 GB — unlimited, free, on one of the fastest global networks. For a content site that might get popular (a blog that hits the front page of Hacker News, say), this single line eliminates the failure mode that costs money elsewhere.

Dynamic code runs on Workers: 100,000 requests per day free, with the whole ecosystem attached — KV storage, R2 (S3-compatible storage with zero egress fees), D1 (SQLite at the edge), queues, cron. The platform has consolidated Pages and Workers so a modern deployment gets static assets served free and unlimited, with server logic metered per request. Paid scaling is usage-based and famously cheap ($5/month baseline) rather than per-seat.

The honest cost: Workers are not Node.js. The runtime is V8-based with broad but not total Node compatibility; most frameworks deploy fine through adapters, but the occasional npm package assuming full Node internals will bite. Build tooling and dashboard polish, while much improved, still trail Vercel’s. It’s infrastructure-first, DX-second — the inverse of Vercel.

Choose Cloudflare when: traffic is unpredictable or growing, the project is static or mostly-static (blogs, docs, marketing), you want R2’s free egress, or long-term unit economics matter more than dashboard warmth.

The clauses everyone misses

Three fine-print items cause 90% of free-tier regret:

1. Commercial use — Vercel Hobby prohibits it; Netlify and Cloudflare allow it. If the site earns money (including ads — relevant to anyone building an AdSense-supported content site), check this first.
2. What “exceeding free” means — Vercel/Netlify push you to ~$20/user/month plans; Cloudflare meters usage from $5. Model your realistic overage before choosing.
3. Single-person vs team — per-seat pricing multiplies: three collaborators on Pro plans is $60/month versus Cloudflare’s usage math. Solo developers barely notice; teams should.

Portability: the quiet strategy

The good news: for a standard framework project, these platforms are largely interchangeable — build command in, static assets + functions out. Keep it that way deliberately: prefer your framework’s native primitives over platform-proprietary ones, keep redirects/headers in your repo, and abstract storage behind interfaces. A portable project migrates in a weekend when pricing or policy changes — and platforms know it, which keeps free tiers generous.

A static-first architecture maximizes this freedom: pure HTML/CSS/JS output (like the Astro blog we build in this tutorial) runs identically on all three, plus GitHub Pages, plus a $4 VPS. It’s also the architecture that makes Core Web Vitals nearly automatic — CDN-served static HTML is the fastest thing there is. The framework choices that enable it are covered in our State of JavaScript Frameworks overview.

Frequently Asked Questions

Can I really run a production site on a free tier forever? For a static or mostly-static site with moderate traffic — yes, legitimately. A blog doing tens of thousands of monthly visits fits comfortably inside every tier here (on Cloudflare, inside the unlimited static allowance). The realistic upgrade triggers are teams (collaborator seats), heavy serverless usage, or Vercel’s commercial clause. Plan for the possibility of paying, celebrate if you never do.

What happens if my site suddenly goes viral? Platform-dependent, and worth knowing in advance. Cloudflare: static assets keep serving — that’s the headline benefit. Netlify: historically pause-or-pay when the allowance runs out mid-cycle. Vercel: spend caps let you choose between a hard stop and a bill. Whichever you pick, set the notification thresholds the day you deploy, not the day the traffic arrives.

Do these platforms handle databases too? Increasingly, via first-party or partner offerings: Vercel and Netlify both market integrated Postgres/KV/blob storage (typically white-labeled partners like Neon or Upstash), and Cloudflare has native D1, KV, R2 and Durable Objects. The free allowances are genuinely usable for side projects. The strategic note from the portability section applies double to data: databases are where lock-in actually bites, so favor standard interfaces (Postgres, S3-compatible) over proprietary ones.

What about GitHub Pages? Still excellent for what it is: free static hosting for docs, portfolios and project sites with zero configuration. Its limits — no serverless functions, no preview deployments, softer traffic guidance, public repos on the free plan — are exactly the features the big three compete on. For a personal page or an open-source project’s docs, Pages is enough; for anything with previews, functions or a team, graduate to one of the three above.

Final Thoughts

There’s no wrong answer among the three — that’s the luxury of a fiercely competitive category. The decision compresses to: Vercel if you’re deep in Next.js and non-commercial (or funded); Netlify if you want the most complete allowed-commercial free package with the least assembly; Cloudflare if bandwidth, scale economics or edge performance top your list.

And the meta-advice: don’t over-deliberate a reversible decision. Keep the project portable, deploy on whichever fits today, and let real usage — not marketing pages — tell you if you ever need to move. The deploy button is free on all three; your time deciding isn’t.