Free Static Site Hosting Compared (2026): Cloudflare Pages vs Netlify vs Vercel vs GitHub Pages
Free-tier limits for Cloudflare Pages, Netlify, Vercel Hobby and GitHub Pages: bandwidth, builds, projects, file limits, custom domains, commercial-use rules and what happens when you go over.
If you build a blog, portfolio or documentation site with a static site generator such as Hugo, Astro, Jekyll or Eleventy, you don't need to rent a server. You can deploy to a free static host, and the shortlist usually comes down to four: Cloudflare Pages, Netlify, Vercel and GitHub Pages. All four say "free," but what you actually get for free, whether you can run ads, and what happens to your site when you hit a limit differ a lot.
Netlify now charges bandwidth and deploys against a pool of credits, and Cloudflare documents serving static assets from Workers as well as from Pages. Limits quoted in older comparison posts may no longer be accurate. This article compares the four services using only conditions confirmed on November 10, 2026 from each company's official docs, pricing pages and terms. If your site needs a server (WordPress, for example), see our separate breakdown of web hosting renewal prices.
At a glance
| Cloudflare Pages Free | Netlify Free | Vercel Hobby | GitHub Pages (GitHub Free) | |
|---|---|---|---|---|
| Price | $0 | $0 | $0 | $0 |
| Data transfer | Static asset requests free and unlimited | Deducted from 300 credits/mo (1 GB = 20 credits) | 100 GB/mo included | 100 GB/mo soft limit |
| Builds/deploys | 500/mo, 1 concurrent, 20 min each | 1 production deploy = 15 credits | 100 deploys/day, 1 concurrent, 45 min each | 10 builds/hour soft limit, 10 min deploy |
| Projects | 100 per account | 500 | 200 | 1 user/org site per account + 1 per repository |
| File limits | 20,000 files per site, 25 MiB per file | Not confirmed | 100 MB CLI upload, 15,000 source files | 1 GB site, files over 100 MiB blocked |
| Custom domains | 100 per project | Included (with SSL) | 50 per project | Supported |
| HTTPS | Certificates for custom domains | Included | Automatic Let's Encrypt | Supported and enforceable on all sites |
| Commercial use | No restriction found in pages reviewed | No restriction found in pages reviewed | Terms: personal or non-commercial use | No online business or e-commerce |
| Over the limit | Only Functions requests have a daily cap | All projects paused | Sustained overuse can pause deployments | Site may not be served, HTTP 429 |
Basis: official docs, pricing pages and terms checked November 10, 2026 (Vercel commercial-use terms rechecked November 14, 2026). Prices in USD. "No restriction found in pages reviewed" means we did not find language restricting commercial use of the free plan on the pages listed under "How we compared." It does not mean we confirmed language that permits it.
- Vercel Hobby100 GB
- GitHub Pages (soft limit)100 GB
- Netlify Free (maximum)15 GB
How we compared
We looked at seven things that directly affect running a static site: data transfer, build count and duration, number of projects, file count and size limits, custom domains and HTTPS, commercial-use terms, and what happens when you exceed a limit.
- Cloudflare: Pages limits, Pages Functions pricing, Workers limits, Workers static assets billing
- Netlify: pricing page, credit-based plans, how credits work
- Vercel: limits, Fair Use Guidelines, paused deployments
- GitHub: Pages limits, Pages terms
We did not compare speed, uptime or regional response times. Published terms can't support a fair comparison of those, and this article contains no performance measurements. Netlify's free-plan build time and file size limits, and the commercial-use clauses in Cloudflare's and Netlify's full account terms, were not confirmed from primary sources this time, so those cells are left blank or qualified.
Data transfer: "unlimited" vs. "credits"
For a static site, the biggest cost variable is how much data you send to visitors.
| Service | Free transfer | What the official docs say |
|---|---|---|
| Cloudflare Pages | Static asset requests free and unlimited | "Requests to static assets are free and unlimited" on free and paid plans |
| Cloudflare Workers static assets | Static asset requests free and unlimited, no storage charge | Only requests that invoke the Worker script are billed under Workers pricing |
| Netlify Free | 300 credits/mo, hard limit | 1 GB bandwidth = 20 credits; 10,000 web requests = 2 credits |
| Vercel Hobby | 100 GB Fast Data Transfer/mo | Also 1,000,000 function invocations and 10 GB Fast Origin Transfer |
| GitHub Pages | 100 GB/mo soft limit | GitHub Support may email you if you go over |
Basis: official docs, checked November 10, 2026.
With Netlify you have to do the math yourself, because bandwidth, requests and deploys all draw from the same credits:
- Deploys only: 300 ÷ 15 = 20 production deploys a month uses up every credit.
- A blog that deploys 8 times a month: 8 × 15 = 120 credits. The remaining 180 credits buy 180 ÷ 20 = 9 GB of bandwidth.
- The same blog with 100,000 requests a month: 100,000 ÷ 10,000 × 2 = 20 more credits, which cuts bandwidth headroom to 160 ÷ 20 = 8 GB.
On the other hand, Netlify's docs say deploy previews, branch deploys and failed deploys don't consume credits. If you edit often, batching changes on a preview branch and shipping fewer production deploys stretches your credits.
Build and deploy limits
| Cloudflare Pages | Cloudflare Workers Builds | Netlify Free | Vercel Hobby | GitHub Pages | |
|---|---|---|---|---|---|
| Build allowance | 500 builds/mo | 3,000 build minutes/mo | 15 credits per production deploy | 100 deploys/day, 100 builds/hour | 10 builds/hour (soft) |
| Concurrent builds | 1 | 1 | Not confirmed | 1 | Not confirmed |
| Max time per build | 20 min | 20 min | Not confirmed | 45 min | 10 min deploy |
Basis: official docs, checked November 10, 2026. GitHub says its 10-builds-per-hour soft limit does not apply if you build and publish with a custom GitHub Actions workflow.
- Vercel Hobby45 min
- Cloudflare Pages20 min
- Cloudflare Workers Builds20 min
- GitHub Pages10 min
For a documentation site with thousands of pages, build time is usually the first wall you hit. GitHub Pages deployments time out after 10 minutes, Cloudflare stops at 20, and Vercel's build step stops at 45. Vercel puts no cap on the number of output files, but warns that many thousands of files mean longer builds, and a build over 45 minutes fails.
Vercel Hobby has one more catch: a project on a Hobby team can't connect to Git repositories owned by a Git organization. If you want to deploy straight from a company or club organization repo, you need a different plan.
Projects, file limits and domains
| Cloudflare Pages | Netlify Free | Vercel Hobby | GitHub Pages | |
|---|---|---|---|---|
| Projects (sites) | 100 per account | 500 | 200 | 1 user/org site per account, 1 project site per repository |
| File count | 20,000 per site | Not confirmed | 15,000 source files via CLI | Not confirmed |
| Size limits | 25 MiB per file | Not confirmed | 100 MB CLI upload | 1 GB published site, 1 GB recommended repo, files over 100 MiB blocked |
| Custom domains | 100 per project | Included | 50 per project | Supported |
Basis: official docs, checked November 10, 2026. Cloudflare Workers static assets allow 20,000 files per Worker version, 25 MiB per file and 100 Workers per account.
Connecting a domain works differently on each. On Cloudflare Pages, an apex domain (example.com) must be added as a Cloudflare zone on the same account with nameservers pointed to Cloudflare, while a subdomain (blog.example.com) only needs a CNAME record. Vercel automatically requests a Let's Encrypt certificate when you add a domain and renews it 14 to 30 days before expiry. GitHub supports HTTPS, and HTTPS enforcement, on every Pages site, including ones with custom domains.
On GitHub, account type decides which repositories can publish. GitHub's plans page lists GitHub Free as including "GitHub Pages in public repositories," with Pages in private repositories available on paid plans such as GitHub Pro. If drafts or private notes live in the same repo, sort out what's public before you turn Pages on.
Commercial use: what the terms actually say
If you plan to earn money from ads or affiliate links, this is the section that matters most.
Vercel Hobby. Section 4 of Vercel's Terms of Service (last updated October 19, 2026) says: "You shall only use the Services under a Hobby plan for your personal or non-commercial use." The terms do not define commercial use.
When we first checked on November 10, 2026, the Fair Use Guidelines defined commercial usage and listed examples (ads such as Google AdSense, sites whose primary purpose is affiliate linking; donations not counting). The guidelines were updated on November 12, 2026 and that section is gone, and the pricing page no longer carried its "personal, non-commercial use" line when we checked on November 14. The one sentence in the terms is now the only primary-source rule.
That sentence alone doesn't settle whether an ad- or affiliate-supported site may run on Hobby. If the site earns money, the safe choices are Pro ($20/mo) or asking Vercel first.
GitHub Pages. GitHub's terms say Pages is "not intended for or allowed to be used as a free web hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS)." Some monetization is allowed, "such as donation buttons and crowdfunding links." We didn't find language addressing display ads specifically in the section reviewed.
Cloudflare Pages and Netlify. The pricing and limits pages reviewed for this article contain no language restricting commercial use of the free plan. We did not review either company's full account terms or acceptable use policy, so if you're running a revenue site, read those directly before you commit.
What happens when you go over
| Service | Behavior stated in official docs |
|---|---|
| Cloudflare Pages | Static assets are unlimited. Functions requests count toward the Workers free quota (100,000/day, resets at midnight UTC) |
| Cloudflare Workers | Over the daily limit returns Error 1027. Depending on the route, the Worker is skipped (fail open) or an error page is shown (fail closed). Requests matching run_worker_first get a 429 |
| Netlify Free | When credits run out, all web projects are paused and visitors see "Site not available." No extra credits or auto recharge; the balance resets next cycle |
| Vercel Hobby | Sustained usage past limits can pause a deployment (visitors see 503 DEPLOYMENT_PAUSED). Vercel reaches out first where it can; upgrading or reducing usage resolves it |
| GitHub Pages | Over quota, the site may not be served. Rate-limited requests get HTTP 429. GitHub Support may email you |
Basis: official docs, checked November 10, 2026.
Netlify Free never bills overages, but sites stop together, account-wide. A traffic spike on one project takes your other sites on the same account offline too. Vercel doesn't state how long a usage pause lasts, and its FAQ says paused projects are resumed manually rather than automatically.
Which one fits your situation
A blog that earns from ads or affiliates. GitHub Pages doesn't fit its terms, and Vercel Hobby's terms ("personal or non-commercial use") don't clearly allow it. Among the pages reviewed, Cloudflare Pages has no commercial-use restriction and doesn't meter static asset transfer, so it carries the lowest cost risk. If you want an apex domain, you'll need to move your nameservers to Cloudflare.
A personal portfolio. Without a revenue goal, all four work. If a public code repo is fine, GitHub Pages works with no extra signup. If you want framework features like Next.js, Vercel Hobby is a natural fit. If the portfolio exists to win client work, Vercel's docs suggest contacting its support team to check whether that counts as "advertising the sale of a product or service."
An open-source docs site. With many pages, check build time and file counts first: Cloudflare Pages allows 20,000 files and 20 minutes per build, GitHub Pages 1 GB and a 10-minute deploy, Vercel a 45-minute build. Remember that Vercel Hobby can't connect to organization-owned repos.
A site you deploy constantly. On Netlify Free, 20 production deploys exhaust 300 credits. If you ship several times a day, Cloudflare Pages (500 builds/mo) or Vercel Hobby (100 deploys/day, within its terms) leaves far more room.
Watch out for
- Large images and video. Cloudflare caps files at 25 MiB, and GitHub blocks files over 100 MiB (Git warns above 50 MiB). Large video belongs in separate storage, not on a static host.
- Server functions have their own limits. Cloudflare's "unlimited" applies only to static asset requests. Pages Functions and Worker script requests draw on the 100,000-per-day free quota.
- Soft limits are not guarantees. GitHub Pages' 100 GB and 10 builds per hour are soft limits, and GitHub says your site may stop being served if you exceed them.
- Terms change often. Netlify has moved to credits, and Vercel's limits page was last updated in September 2026. Recheck the linked originals right before you pick a plan.
Static hosts can't run a site that needs PHP or a database, such as WordPress. For that case, see how intro prices and renewals stack up in our web hosting renewal price comparison.
Related reading
FAQ
Can I run a blog with Google AdSense ads on Vercel's free Hobby plan?
Vercel's Terms of Service (Section 4) limit Hobby to "personal or non-commercial use" but don't define commercial use. The Fair Use Guidelines used to list AdSense and affiliate sites as commercial examples; that section was removed in the November 12, 2026 update. The current wording doesn't settle it either way, so for a revenue site the safe options are Pro ($20/mo) or confirming with Vercel first.
How much traffic does Netlify's free plan allow per month?
The Free plan has 300 credits a month with a hard limit. Bandwidth costs 20 credits per GB, each production deploy 15 credits, and every 10,000 web requests 2 credits. Spent only on bandwidth, that's a maximum of 300 ÷ 20 = 15 GB. When credits run out, all your projects are paused and visitors see a 'Site not available' page.
Can I host an online store or business website on GitHub Pages?
GitHub's terms say Pages is not intended for or allowed to be used as free hosting to run an online business, an e-commerce site, or a site primarily aimed at commercial transactions or commercial SaaS. Some monetization, like donation buttons and crowdfunding links, is allowed. On GitHub Free, Pages is available only for public repositories.