How to choose
For a purely static site, start with the workflow rather than the brand name:
- Content-heavy docs or marketing site: Cloudflare Pages is a strong first choice because static delivery is where it shines.
- Jamstack site with previews and platform add-ons: Netlify is still one of the smoothest options.
- Frontend app that may become a framework app: Vercel keeps the upgrade path simple if the site grows into Next.js or a richer frontend.
- GitLab-hosted project docs: GitLab Pages keeps source, CI and publishing inside the same product.
The main free-tier risks for static sites are not cold starts. They are build minutes, monthly credits, file count, site size, custom-domain limits and bandwidth.
Practical recommendation
If you are launching an Astro, Hugo, Vite or documentation site and do not already have a strong platform preference, try Cloudflare Pages first. It has a generous free static-hosting profile and a clear CDN-first model. Choose Netlify when editorial workflow, deploy previews and Jamstack integrations matter. Choose Vercel when the static site is part of a React or Next.js path. Choose GitLab Pages when the repository already lives in GitLab and CI/CD is the center of the workflow.
Static hosting catches to watch
Free static hosting feels unlimited until the project grows in one of these directions:
- frequent content updates that trigger many builds
- large media libraries
- tens of thousands of generated files
- many preview deployments
- serverless or edge functions attached to the site
- commercial projects that need support, compliance or predictable limits
If the site is mostly HTML, CSS, JavaScript and images, a free static host can be a long-term home. If the site starts needing authentication, background jobs, database writes or private APIs, pair it with a backend or move to a platform designed for full-stack workloads.