ToolScore

GitHub Pages

GitHub · website builders · reviewed by Stan K. · Source: data snapshot · data as of 2026-11-13

Static hosting served straight from the repo — a "soft limit of 100 GB per month" bandwidth, everything leaves, and commerce sits in a documented gray zone.

#5 of 11 in Website Builders

Try GitHub Pages for $0
Real price
Free tier
freemium
Free tier
Yes
$0. Bandwidth carries a "soft limit of 100 GB per month"; the published site is capped at 1 GB; builds at 10/h
Limits
8.0/10
$0 · 100 GB/mo soft bandwidth · 1 GB published site
Verdict
GOOD
"Soft limit of 100 GB per month" bandwidth · 1 GB published site · 10 builds/hour (soft, waived with your own

ToolScore breakdown — why 78/100

Price / Value
9.0
Token & Rate Limits
8.0
Speed / Latency
8.5
Privacy & Retention
5.0
BYOK (Own API Key)
10.0
Output Quality
7.0
Stability
8.5
Ease of Setup
6.0
Billing Transparency
9.0
Support & Community
7.0

10 criteria × 10 points. Low pillars are visible on purpose — that's the point of a score you can audit. Methodology →

What it does well

  • ▸"Soft limit of 100 GB per month" bandwidth — soft, not a meter that pauses you
  • ▸Everything leaves: static output served straight from the repo; Actions workflows are portable YAML
  • ▸10 builds/hour is soft too — waived with your own Actions workflow
  • ▸The gray zones are documented rather than discovered: the AUP spells out what commercial use means

Where it costs you

  • ▸Commercial use is a gray zone, not a ban — the AUP says advertising is "not generally prohibited", but the site's primary purpose shouldn't be promotional
  • ▸1 GB max published site — heavier asset libraries need an external CDN
  • ▸Git + CLI instead of a browser editor — the static trade-off

Hidden traps — the stuff the pricing page doesn't say

medium riskCommerce is a gray zone, not a ban

GitHub Pages' acceptable-use policy says advertising is "not generally prohibited", but the site's primary purpose shouldn't be promotional. A project page that links a store is fine; a store that squats on Pages is not the documented intent. Selling directly here means reading the AUP yourself.

low risk1 GB max published site

The published site is capped at 1 GB — heavier asset libraries (video, large image sets) need an external CDN. The bandwidth soft limit forgives traffic; the size cap does not forgive assets.

Try GitHub Pages

Know the limits before you pay: read the traps above, then decide with eyes open.

Visit official site

Affiliate link where available — never affects the score.

What the advertised price hides
$0. Bandwidth carries a "soft limit of 100 GB per month"; the published site is capped at 1 GB; builds at 10/hour (soft, waived with your own Actions workflow).
Sources & freshness

Data as of 2026-11-13. Prices and limits change monthly — report anything stale. How we verify: methodology.

Closest alternatives

GitHub Pages review

In-depth analysis · last updated 2026-11-13

The repo is the site

GitHub Pages lands at 78 in our export/lock-in table — the "generous, gray-zone commerce" row, two slots under Cloudflare Pages. The model is the purest in this hub: static output served straight from the repo, Actions workflows as portable YAML, everything leaves. Like every static host here, the trade-off is Git + CLI instead of a browser editor, and the prize is an exit that consists of moving the same files somewhere else.

The soft limits

The published numbers: a "soft limit of 100 GB per month" of bandwidth, a 1 GB published site, and 10 builds/hour — soft as well, waived with your own Actions workflow. Note the shape: these are soft limits, not meters — nothing pauses when you cross them (contrast Netlify, where hard credits pause every project). The one hard-ish ceiling is the 1 GB published site: heavier asset libraries need an external CDN.

The gray zone

Commercial use is a gray zone, not a ban — the AUP says advertising is "not generally prohibited", but the site's primary purpose shouldn't be promotional. That wording leaves room for a project site that links a store, and none for a store that squats on Pages. It is to GitHub's credit that the gray zone is documented policy rather than a surprise; it is still a gray zone, and selling directly here means reading the AUP yourself.

How the pillars land

Price/Value 9: $0 with soft limits is real value — docked a point against Cloudflare's unlimited everything. Site & commerce limits 8: 100 GB soft bandwidth, 1 GB site cap, documented. Editor & publishing 8.5: git push to publish, static ships fast out of the box. Export & ownership 10: everything leaves, workflows are portable YAML. Feature set 7: static only — no Functions layer on the free tier's terms like Cloudflare's Workers quota. Track record 8.5: the limits pages are stable, documented policy. Ease 6: Git + CLI instead of a browser editor — the steepest skills bill in the static trio. Pricing transparency 9: limits and AUP both published; the gray zone is at least written down. Support & docs 7: the official limits and policy docs are the verified record. Privacy isn't on this category's scorecard — this hub researches price, limits and exit, not data practices.

Verdict — GOOD, 78/100

For docs, project sites and portfolios, GitHub Pages is the zero-friction answer — the repo you already have becomes the site. If traffic grows unbounded or commerce becomes the primary purpose, that's the moment to move to Cloudflare Pages' unlimited free tier; thanks to the portable-static shape, the move is a DNS change, not a migration.

From the insights