The $0 Hosting Tier Is the New Default

Five years ago, free hosting meant a GitHub Pages site with no build pipeline, a CNAME file, and a prayer that Jekyll wouldn’t choke on your Markdown. It worked, barely, for personal blogs and project documentation. Anything beyond that required a paid plan somewhere.

That world is gone.

In 2026, the free tier on any of the four major static hosting platforms — Render, Vercel, Cloudflare Pages, and Netlify — gives you a global CDN, automatic SSL, custom domains, deploy previews, git-push deploys, and build pipelines that handle modern frameworks out of the box. For most static sites, paying for hosting is a choice you make for specific features, not a requirement to ship production work.

This isn’t a theoretical observation. I deploy client sites across all four platforms. The free tier is where most of those sites live, and they serve real traffic with zero issues. Here’s how the platforms actually compare when you’re spending nothing.

What You Get for Free

The broad strokes are remarkably similar across all four platforms. Every free tier includes HTTPS, custom domains, git-based deploys, and a CDN. The differences are in the limits and the details around those limits.

Render gives you 100 GB of bandwidth per month, automatic deploys from GitHub or GitLab, and a straightforward static site setup. You get custom domains with automatic SSL via Let’s Encrypt. Build minutes are limited to 750 per month across all free services on your account. No deploy previews on the free tier — this is Render’s biggest gap compared to the others.

Vercel is the most generous on the surface. 100 GB bandwidth, 6,000 build minutes per month, and deploy previews for every pull request. You get their edge network, serverless functions (with limits), and analytics. The catch is their fair-use policy and the per-seat pricing model that kicks in the moment you add a team member. Solo developers and personal projects get a luxury experience. Agencies managing client sites hit the paywall fast.

Cloudflare Pages offers unlimited bandwidth on the free tier. Read that again. Unlimited. You get 500 builds per month, deploy previews, and access to Cloudflare’s massive global network — over 300 edge locations. You also get Cloudflare Workers integration, which means edge functions are part of your free tier. The 20,000 files per project limit is the constraint you’ll hit first on large sites.

Netlify provides 100 GB bandwidth, 300 build minutes per month, deploy previews, form handling (100 submissions/month), and serverless functions (125,000 invocations/month). The deploy previews are excellent — every branch and PR gets its own URL with the same production CDN behavior. The build minutes limit is the tightest of the four, and it adds up fast if you’re deploying frequently.

Here’s the side-by-side:

Feature	Render	Vercel	Cloudflare Pages	Netlify
Bandwidth	100 GB/mo	100 GB/mo	Unlimited	100 GB/mo
Build minutes	750/mo (shared)	6,000/mo	500 builds/mo	300 min/mo
Deploy previews	No	Yes	Yes	Yes
Custom domains	Yes	Yes	Yes	Yes
SSL	Auto	Auto	Auto	Auto
Edge network	Global CDN	Global edge	300+ locations	Global CDN
Serverless functions	No (free tier)	Yes (limited)	Workers (limited)	Yes (limited)

The Real Limitations

The comparison table tells you what each platform advertises. The actual experience of living on the free tier is more nuanced.

Build minutes are the universal bottleneck. A Next.js static export with 50 pages takes 1–3 minutes to build depending on your dependencies and asset pipeline. If you’re deploying 5 times a day on Netlify’s 300-minute plan, that’s roughly two months of headroom. On Render, those 750 minutes are shared across all your free services — so a background job or a cron service running on the same account eats into your static site’s build budget.

Vercel’s free tier is personal-only. Their terms explicitly restrict the free Hobby plan to personal, non-commercial projects. If you’re deploying a client’s marketing site on the free tier, you’re technically in violation. Whether Vercel enforces this aggressively is debatable, but it’s a real constraint for agencies and freelancers. The moment you add a second team member, you’re on Pro at $20/seat/month.

Netlify’s form handling sounds generous until it isn’t. 100 form submissions per month is fine for a portfolio site’s contact form. A client’s service business getting 10 leads a day will blow through it in 10 days. At that point you’re either upgrading or routing forms through your own edge function — which is what you should be doing anyway.

Cloudflare’s developer experience has rough edges. The platform is technically excellent, but the dashboard is dense and the documentation assumes more infrastructure knowledge than the others. Setting up a custom domain on Cloudflare Pages is straightforward if you’re already using Cloudflare for DNS. If you’re not, you’re migrating your nameservers first, which is a bigger commitment than just adding a CNAME record.

Render’s lack of deploy previews matters more than you’d think. When you’re building a client site and need to share a preview URL for review, having to push to production (or manage a separate staging branch manually) is friction the other platforms eliminated years ago. For solo projects where you are the reviewer, it’s less of an issue.

Performance: Edge Networks Aren’t Equal

All four platforms serve static files from a CDN. But CDN architectures differ, and those differences show up in real-world latency.

Cloudflare Pages wins on raw edge presence. Their network spans 300+ cities globally. A static file served from Cloudflare is almost certainly cached on a node close to the user, regardless of where that user is. First-byte times from Cloudflare are consistently under 30ms for cached assets in major metros.

Vercel’s edge network is optimized for Next.js. If your site is built with Next.js, Vercel’s edge behavior is tuned for that framework — intelligent caching of static pages, automatic ISR handling, and optimized asset serving. For a vanilla static export, the performance is competitive but not meaningfully better than Cloudflare or Netlify.

Netlify’s CDN is solid and well-understood. Cache invalidation is fast (typically under 30 seconds for a full deploy), and their edge nodes handle static assets efficiently. Performance is consistent across regions without significant cold-cache penalties on subsequent requests.

Render’s CDN is the smallest of the four. It performs well in North America and Europe but can show higher latency in Asia-Pacific and South America compared to Cloudflare or Vercel. For sites with a primarily US/EU audience, this is irrelevant. For a globally distributed audience, it’s a factor.

One thing every platform gets right: cache invalidation on deploy. When you push a new version, the old cached assets are purged and the new ones propagate across the CDN within seconds. You don’t need to append cache-busting query strings or wait for TTLs to expire. This was a genuine pain point with older CDN setups. On all four platforms, deploy means the new version is live globally within 30–60 seconds.

For the majority of static sites — the portfolio, the local business, the blog, the documentation site — the performance difference between these platforms is single-digit milliseconds. Users won’t notice. Lighthouse won’t notice. The difference matters at scale or for audiences in underserved regions.

Developer Experience: Where You’ll Spend Your Time

Performance parity means the real differentiator is how it feels to work with each platform day to day.

Vercel has the best DX of the four, and it’s not close. git push deploys just work. The dashboard is clean. Preview deployments generate automatically with comments on your pull request. The CLI is fast and useful for local testing. If you’re using Next.js, the integration is seamless to the point where the framework and the platform feel like one product.

# Vercel: deploy from CLI in seconds
npx vercel --prod

Netlify is a close second. The netlify.toml configuration file is well-documented and powerful. The CLI (netlify dev) gives you a local development server that accurately simulates the production environment, including serverless functions and edge functions. Build plugins extend the pipeline without custom scripts.

# netlify.toml — clean, declarative config
[build]
  command = "npm run build"
  publish = "out"

[[redirects]]
  from = "/*"
  to = "/index.html"
  status = 200

Cloudflare Pages is powerful but opinionated. The wrangler CLI is capable but has a steeper learning curve. Configuration lives in wrangler.toml, and the integration with Cloudflare’s broader ecosystem (Workers, KV, R2) is a strength if you need it and added complexity if you don’t. Deploy times are fast — Cloudflare consistently has the shortest build-to-live pipeline of the four.

# wrangler.toml — Cloudflare Pages config
name = "my-site"
compatibility_date = "2026-04-01"

[site]
  bucket = "./out"

Render keeps it simple. Point it at a repo, tell it the build command and the publish directory, and it deploys. There’s no CLI, no configuration file in your repo, no plugin ecosystem. Everything is configured in the dashboard. This is either refreshing simplicity or frustrating inflexibility depending on your workflow preferences.

The git integration story is worth calling out separately. All four platforms support GitHub and GitLab. Vercel and Netlify also support Bitbucket. On all of them, the flow is the same: connect a repo, configure a build command and output directory, and every push to your main branch triggers a production deploy. Branches trigger preview deploys (except on Render). This is table stakes now, but it’s worth remembering that five years ago you were writing custom CI pipelines to get this behavior.

The one DX differentiator that doesn’t show up in feature lists is error messaging during builds. Vercel and Netlify surface build errors clearly in the dashboard and in pull request comments. Cloudflare Pages shows build logs but they can be harder to parse, especially for framework-specific errors. Render’s build logs are straightforward but minimal — you get stdout and stderr, and that’s about it.

Which One for Which Use Case

This is where opinions matter more than benchmarks.

Portfolio or personal site: Cloudflare Pages. Unlimited bandwidth means you never think about it, even if a project goes viral on Hacker News. The edge network is fast globally, and the free tier has no commercial-use restrictions.

Client site you’re handing off: Render. The simplicity is a feature when the person managing the site after you isn’t a developer. The dashboard is clean, the mental model is obvious, and there’s nothing to misconfigure. You’ll want to factor in the missing deploy previews during development, but post-handoff that’s irrelevant.

Blog or content site with frequent updates: Netlify. The build pipeline is mature, deploy previews are excellent for editorial review, and the form handling covers basic contact forms without additional infrastructure. The 300 build minutes limit is the thing to watch — set up build hooks carefully so you’re not triggering rebuilds on every content save.

Next.js project where you want zero friction: Vercel. Nothing else matches the integration depth. But be clear-eyed about the terms: it’s a personal-use free tier. If this is a commercial project, you need the Pro plan. Accept that and Vercel is a premium experience.

Documentation site or open-source project: Cloudflare Pages or Netlify. Both handle this well. Cloudflare’s unlimited bandwidth is ideal for popular open-source docs. Netlify’s deploy previews make it easy for contributors to see the rendered output of their documentation PRs.

When You Actually Need to Pay

The free tier covers more than most developers expect, but it has real boundaries. Here’s when upgrading becomes necessary rather than optional.

You need team collaboration. The moment a second developer needs deploy access on Vercel, you’re on Pro. Netlify’s Starter plan has a single-member limit. Render allows multiple users on the free tier but with limited role management. Cloudflare Pages is the most generous here with multi-user support on the free plan.

You need guaranteed uptime or SLAs. Free tiers don’t come with service-level agreements. For a client site where downtime has real business consequences, a paid plan with support and SLAs is the responsible choice. Not because the free tier is unreliable — it generally isn’t — but because you need the contractual guarantee.

Your traffic outgrows the bandwidth. 100 GB per month serves roughly 500,000–1,000,000 page views depending on your page weight. If you’re consistently above that, Cloudflare’s unlimited free tier is one answer; upgrading on the others is the other.

You need advanced build features. Monorepo support, build concurrency, longer build timeouts, and priority build queues all live behind paid plans across every platform. If your project is complex enough to need these, the free tier isn’t the bottleneck you should be optimizing around.

You need server-side rendering. The free tier on all four platforms is designed for static output. The moment your Next.js project needs getServerSideProps or API routes that persist beyond a simple edge function, you’re in a different hosting category entirely.

You want custom headers, redirects, or middleware beyond the basics. All four platforms support basic redirect rules on the free tier. But complex redirect patterns (regex-based, conditional on headers or geolocation), custom security headers across specific routes, and middleware chains are either limited or reserved for paid tiers depending on the platform. If your site needs more than a _redirects file or a simple netlify.toml rule, read the fine print on what’s included.

The Uncomfortable Truth for Hosting Companies

The competitive dynamics here are fascinating. Each platform is essentially giving away static hosting as a loss leader to upsell you on compute, serverless, databases, and enterprise features. Cloudflare wants you on Workers and R2. Vercel wants you on their serverless and edge middleware. Netlify wants you on their functions and forms. Render wants you on their managed services and databases.

This is great for developers. The free tiers are genuinely good because they’re not the product — you are the product, or more precisely, your future scaling needs are the product. The platforms are betting that the developer who deploys a portfolio site for free today will provision a database and serverless functions there tomorrow.

For most static sites, tomorrow never comes. The portfolio, the blog, the small business landing page — they’ll live on the free tier indefinitely, performing well, costing nothing, and requiring almost no maintenance. That’s not a hack or a workaround. It’s exactly how the platforms designed it.

The Default Changed

The question used to be “where should I host this and how much will it cost?” Now it’s “is there any reason I should pay for hosting?”

For a static site served from a CDN with a custom domain and automatic SSL, the answer is usually no. The free tier on any of these four platforms is production-ready, performant, and reliable enough for the vast majority of static sites in the wild.

Pick Cloudflare Pages if you want the most headroom. Pick Vercel if DX matters most and you’re okay with the commercial restrictions. Pick Netlify if you want the most complete free feature set. Pick Render if you value simplicity and plan to scale into their paid services later.

Or pick any of them. The gap between the best and worst free tier is smaller than the gap between any free tier and what you got for free five years ago.

Paying for hosting isn’t dead. But it’s no longer the starting point. Zero dollars is the default, and the burden of proof is on the paid tier to justify itself.

Static Signal is published by Neuron Web Development.