Cloudflare Pages, Netlify, Vercel and GitHub Pages, compared on free tier limits, build behaviour, and what actually breaks when a site gets traffic.
The Infrastructure Desk · Cloud platforms · Published 2026-08-17 · Updated 2026-08-17
What actually differentiates these
Every host here will take a Git repository, run a build command, and serve the output from a global edge network with free TLS. That is the commodity part, and it is genuinely commoditised. Performance differences between them for a static file are small enough that you will not measure them without instrumentation.
What differs is the failure modes. How the free tier ends. What happens when traffic arrives unexpectedly. How long a build takes and how often it breaks. Whether the platform’s own features quietly make you dependent on it. Those are the things you will care about in six months, and none of them appear in a feature comparison.
Cloudflare Pages
The distinguishing feature is that bandwidth is not metered. Not generous, not high-limit: not metered. For a content site, that removes the single most common way a hobby project turns into an unexpected invoice, and it removes the incentive to worry about traffic at all.
The tradeoffs are real but narrow. The free tier limits how many builds you run per month, which matters if you push constantly and does not matter otherwise. The number of files in a single deployment is capped, which only becomes an issue for very large generated sites. Build environments are somewhat less forgiving than Vercel’s, so an unusual toolchain occasionally needs a nudge. And Cloudflare’s product surface is enormous, which means the documentation you land on is sometimes for a neighbouring product.
For a publication, a documentation site, or a marketing site, this is the safe answer.
Vercel
Vercel builds Next.js, and Next.js on Vercel is the only place where every Next.js feature works with no configuration and no caveats. If that is your framework, the argument for going elsewhere has to overcome real convenience.
The developer experience is the best of the four. Preview deployments per branch are excellent, build logs are readable, the dashboard tells you what you need without hunting, and framework detection almost always guesses right.
The cost model is where care is required. Bandwidth and function execution are metered, and the free tier is scoped to non-commercial use. A traffic spike on a metered plan produces a bill, and the platform’s most pleasant features are the ones that most tightly couple you to it. Set spending limits deliberately rather than discovering them.
Netlify
Netlify invented much of this category and remains a solid, well-documented choice. Its build plugin ecosystem is the most mature, its forms and identity add-ons are genuinely useful for small sites that need one dynamic feature, and the redirect and header configuration is the clearest of the four to reason about.
It is also the one with the least distinctive argument in 2026. It is not the cheapest at scale, not the fastest to adopt for Next.js, and not the one with unmetered bandwidth. It is competent everywhere and first nowhere, which is a reasonable place to be if you value stability over any single advantage.
GitHub Pages
Free, permanent-feeling, and already wherever your code is. For documentation attached to a repository, a personal site, or anything where the content and the code live together, it is hard to argue against.
The limits are soft rather than billed, which is the right shape for a hobby project: exceed them and you get a polite email, not a charge. What you give up is control. Build customisation is limited unless you drive it yourself through Actions, redirect support is minimal, and there is no preview deployment story worth using. It is the right answer for a narrow set of sites and the wrong answer as soon as you want a build pipeline.
Side by side
| Cloudflare Pages | Vercel | Netlify | GitHub Pages | |
|---|---|---|---|---|
| Bandwidth model | Unmetered | Metered | Metered | Soft limits |
| Overage risk | None | Real | Real | None |
| Free tier ceiling | Build count | Bandwidth and usage | Bandwidth and build minutes | Soft usage limits |
| Next.js support | Good | Best available | Good | Not practical |
| Preview deploys | Yes | Best in class | Yes | No |
| Edge network size | Largest | Large | Large | Adequate |
| Best for | Content sites | Next.js apps | General purpose | Repo-attached docs |
Which should you pick
Pick Cloudflare Pages if the site is content and you want to stop thinking about hosting. Unmetered bandwidth is the single most valuable property on this list for anything that might get popular.
Pick Vercel if you are building a Next.js application rather than a site, and the framework features are the point. Configure spend limits on day one.
Pick Netlify if you want one mature platform for many small sites and value predictable, well-documented behaviour over any individual advantage.
Pick GitHub Pages if the site is documentation living beside the code it documents, and you will never need a build step more complicated than the one you have today.
Verdict
For a content site, Cloudflare Pages is the default: the bandwidth is unmetered, the network is the largest of the four, and there is no traffic spike that turns into a bill. Choose Vercel instead if you are running Next.js and want its framework features to work without configuration, and accept that you are trading cost predictability for that convenience.
Frequently asked questions
Is a static host really enough for a real website?
For anything that is mostly reading, yes. Blogs, documentation, marketing sites, directories and publications are all better served static. You need a server when users write data, log in, or need something computed per request.
What happens if my site suddenly goes viral?
On Cloudflare Pages and GitHub Pages, nothing financial. On Vercel and Netlify, metered bandwidth means a large enough spike produces a bill or throttling, depending on your plan and settings. Set a spend cap if the platform offers one.
Can I move between these later?
Easily, if your site is genuinely static. The build command and output directory are all any of them need. The lock-in risk comes from platform-specific features like edge functions, image optimisation and redirects, not from the static files.
Do I need a separate CDN?
No. All four serve from a global edge network already. Adding another CDN in front usually makes things slower and harder to debug.
Sources
- Cloudflare Pages limits documentation
- Netlify pricing and usage
- Vercel limits documentation
- GitHub Pages usage limits
Written with AI assistance and reviewed against our editorial standards.
