Is free static hosting really free? Where the limits actually bite
For a large class of sites, free static hosting is genuinely free forever. For the rest, the bill arrives suddenly. The difference is predictable if you know which meter you are running against.
Key takeaways
- For a genuinely static site with modest traffic, free tiers are free indefinitely — not a trial.
- The meters that matter are bandwidth, build minutes, and serverless function invocations.
- Build minutes catch people out more often than bandwidth, especially on large sites that deploy frequently.
- Commercial use is permitted on some free tiers and prohibited on others. Check before relying on it.
- Overage behaviour differs fundamentally: some platforms bill you, others stop serving. Know which.
Static hosting free tiers are unusually generous, and the generosity is genuine rather than a lead-in to a subscription. A personal site, a documentation site or a portfolio can run on one for years without paying.
The economics work because serving pre-built files from a CDN is cheap, and the platforms are really selling team features, build infrastructure and serverless compute to companies. Individuals are a rounding error and good marketing.
But there are meters, and knowing which one you are running against is the difference between free forever and an unexpected bill.
The four meters
Bandwidth
Data transferred to visitors. The one everybody checks, and usually the least likely to bite — a text-and-CSS site serves an enormous number of page views within a typical free allowance.
It becomes a real constraint when you serve large files: video, high-resolution images, downloadable PDFs, podcast audio. A handful of large media files can consume in days what a text site would take a year to use.
The standard fix is to keep large media off the hosting platform entirely — a dedicated image or video service, or object storage with its own CDN. That is usually cheaper than upgrading the hosting tier, and generally faster.
Build minutes
Compute time spent building your site on each deploy. This is the meter that most often surprises people, because it has no relationship to traffic.
A site with thousands of pages and a slow static generator might take several minutes per build. Deploy ten times in an afternoon while fiddling with CSS and you have spent half an hour of the allowance on a site nobody has visited. Add a CI pipeline that rebuilds on every commit, or a preview deploy per pull request, and it accumulates quickly.
Mitigations: enable incremental builds or caching if the platform offers them, avoid rebuilding for content-only changes where the framework supports it, and turn off automatic preview deploys if you are not using them.
Serverless function invocations
If your "static" site has a contact form, a search endpoint, an API proxy or authentication, it is running serverless functions, and those are metered separately — usually by invocation count and execution duration.
Worth knowing: on several platforms, server-side rendering runs through the same function infrastructure. A Next.js or Nuxt site using SSR can consume function invocations on every page view rather than only on form submissions, which changes the arithmetic entirely. If you are using a framework in SSR mode, check whether your page views are hitting the function meter.
Team seats and features
Free tiers are typically single-user. Password protection, role-based access, analytics, longer log retention and priority support sit behind the paid tier.
For solo projects this is irrelevant. It is usually what actually triggers an upgrade for anyone working with someone else — not resource limits at all.
What happens when you exceed a limit
This is the most important difference between platforms and the least advertised.
Some platforms bill you. Overage is charged per unit and the site keeps serving. Good for anything you cannot afford to have go offline, and it means a traffic spike — or someone hotlinking your assets — produces an invoice rather than an outage.
Some platforms stop serving. You hit the cap and the site returns an error or is suspended until the period resets or you upgrade. Good for hobby projects where a surprise bill would be worse than downtime; bad for anything that matters.
Neither is wrong, but you should know which one you have chosen, and configure it if the platform allows. Where spend caps or alerts are available, set them on day one rather than after an incident.
Commercial use
Free tier terms vary meaningfully here, and it is worth reading rather than assuming.
Some platforms explicitly permit commercial sites on the free tier. Others restrict it to personal and non-commercial projects, meaning a client site or a business landing page technically requires a paid plan even if it uses trivial resources.
Enforcement tends to be light, but building a client's site on a plan whose terms prohibit it is a poor position to be in later. Check the acceptable use policy before deciding the hosting is free.
The platforms, in broad terms
Rather than quote allowances that change frequently, here is what each is generally best at. Confirm current limits on the platform's own pricing page.
| Platform | Generally strongest for | Watch |
|---|---|---|
| Netlify | General static sites, forms and edge functions built in | Build minutes on large sites |
| Vercel | Next.js and React frameworks, preview deploys | Function usage under SSR; commercial-use terms on the free tier |
| Cloudflare Pages | Bandwidth-heavy sites — unusually generous transfer | Build limits; Workers metered separately |
| GitHub Pages | Documentation and project sites, simplest setup | No serverless functions; soft limits; not for commercial sites per the terms |
| Render | Static plus real backend services in one place | Free services may sleep when idle |
When to leave the free tier
Upgrade when you need a collaborator, when the site earns money and the terms require it, when you need password protection or access control, or when overage charges consistently exceed the paid tier's price — at which point the paid tier is simply cheaper.
Do not upgrade merely because traffic grew. Static hosting scales extremely well, and a popular text site can sit on a free tier for a very long time. Check which meter you are actually near before assuming you have outgrown it.
The thing to remember
Free static hosting is genuinely free for genuinely static sites. The costs appear when a site stops being static — server-side rendering, API routes, authentication, heavy media — and starts using compute per request.
If your bill is climbing, the useful question is usually not "which platform is cheaper" but "which parts of this site actually need to run per request". Often the answer is fewer than you think.
The comparison table's static hosting category covers these platforms alongside paid alternatives. Answer "static site" in the finder and it will route you there directly.
Further reading
- Choosing a hosting type — whether static suits your site at all.
- What "unlimited" means — the equivalent fine print in shared hosting.
- What hosting is not for — including using a CDN as file storage.