GitHub Pages limits: storage, bandwidth, builds. What happens when you pass them?
Quick answer
GitHub Pages sites may be “no larger than 1 GB,” with a soft limit of 100 GB of bandwidth a month and 10 builds an hour, per the limits doc GitHub's terms (effective August 27, 2026) point to. Past them, GitHub “may not be able to serve your site,” or emails you suggestions such as a CDN. Rate limits answer HTTP 429.
Free plan: no credit card, 1 published page, 10,000 page views a month.
On this page
- Every GitHub Pages limit, and what happens past it
- What happens when a site passes a limit
- What a 429 rate-limit error means on a Pages site
- Builds: the 10-an-hour limit and GitHub Actions
- Size: the site, the repository, and single files
- Free hosts compared on the same limits
- If your site is one HTML page: Convika
- Which one to pick
- Frequently asked questions
- Sources
GitHub Pages sites may be “no larger than 1 GB,” with a “soft bandwidth limit of 100 GB per month” and a “soft limit of 10 builds per hour,” per the GitHub Pages limits doc that GitHub's Additional Product Terms, effective August 27, 2026, point to. Past them, the doc says, “we may not be able to serve your site, or you may receive a polite email from GitHub Support.”
GitHub's terms and docs were read on October 23, 2026. The GitHub Pages limits page carries no date; its file in GitHub's public docs repository last changed on July 24, 2026. The Additional Product Terms say Pages “may not be appropriate for some high-bandwidth uses” and send you to that page for the numbers. Limits change, so check them before you launch.
The same doc and the terms also rule out using Pages “to run your online business, e-commerce site,” or SaaS. The page Can you use GitHub Pages for a commercial or business site? covers that rule case by case. This page covers the numbers.
Every GitHub Pages limit, and what happens past it
The table lists each limit in GitHub's docs, whether GitHub calls it soft, and what the docs say happens past it. Where a doc gives a limit but not what happens at it, the table says so.
| Limit | What GitHub's docs say | A hard limit? | What happens past it |
|---|---|---|---|
| Size of the published site | “Published GitHub Pages sites may be no larger than 1 GB.” | GitHub doesn't say | GitHub's general rule: it “may not be able to serve your site” |
| Bandwidth | “GitHub Pages sites have a soft bandwidth limit of 100 GB per month.” | No, soft | GitHub “may not be able to serve your site,” or emails you suggestions, such as a CDN in front of the site |
| Builds | “a soft limit of 10 builds per hour. This limit does not apply if you build and publish your site with a custom GitHub Actions workflow.” | No, soft | GitHub's general rule; no more detail |
| Deployment time | “GitHub Pages deployments will timeout if they take longer than 10 minutes.” | Yes | The deployment times out |
| Requests | “rate limits may apply,” with no number given | GitHub doesn't say | “you will receive an appropriate response with an HTTP status code of 429, along with an informative HTML body” |
| Size of the source repository | “a recommended limit of 1 GB”; the large-files doc: “ideally less than 1 GB, and less than 5 GB is strongly recommended” | No, a recommendation | “you might receive an email from GitHub Support asking you to take corrective action” |
| One file in the repository | “GitHub blocks files larger than 100 MiB.” A file over 50 MiB gets a warning | Yes | GitHub blocks the file; past 100 MiB, Git LFS is required |
| User or organization sites | “You can only create one user or organization site for each account on GitHub.” | Yes | Project sites are separate: one per repository |
What happens when a site passes a limit
GitHub's limits doc says it in 1 sentence: “If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from GitHub Support suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other GitHub features such as releases, or moving to a different hosting service that might better fit your needs.”
GitHub doesn't say how far past a soft limit a site can go, how long a site stays unserved, or which of those 2 outcomes comes first. The Pages docs name no charge for traffic past 100 GB. The terms add that Pages may not be used in violation of “the GitHub Pages service limitations set forth in the Pages documentation.”
What a 429 rate-limit error means on a Pages site
A Pages site answers with HTTP status 429 when GitHub rate-limits a request to it. The limits doc: “In order to provide consistent quality of service for all GitHub Pages sites, rate limits may apply. These rate limits are not intended to interfere with legitimate uses of GitHub Pages. If your request triggers rate limiting, you will receive an appropriate response with an HTTP status code of 429, along with an informative HTML body.”
The doc gives no number of requests and no wait time. The fix GitHub's own email suggests for a busy site is a CDN in front of it, or another host.
Builds: the 10-an-hour limit and GitHub Actions
Every Pages site deploys through GitHub Actions. The publishing-source doc says “Your GitHub Pages site will always be deployed with a GitHub Actions workflow run, even if you've configured your GitHub Pages site to be built using a different CI tool.”
- Deploying from a branch: Each push to the source branch publishes the site, and the soft limit of 10 builds an hour applies.
- A custom Actions workflow: The limit of 10 builds an hour “does not apply.” The workflow uploads the site as one archive, and “The
tarfile must be under 10GB in size.” The published site still has the 1 GB limit. - Actions minutes: The Pages docs say “GitHub Actions is free for public repositories. Usage charges apply for private and internal repositories that go beyond the monthly allotment of free minutes.” On GitHub Free, a Pages repository must be public anyway.
- Pushes from a workflow: “Commits pushed by a GitHub Actions workflow that uses the
GITHUB_TOKENdo not trigger a GitHub Pages build.”
Size: the site, the repository, and single files
The published site may be up to 1 GB. The source repository has “a recommended limit of 1 GB,” and GitHub's large-files doc goes further: “We recommend repositories remain small, ideally less than 1 GB, and less than 5 GB is strongly recommended.”
Single files have firmer limits. Git warns about a file over 50 MiB, and “GitHub blocks files larger than 100 MiB.” A larger file needs Git Large File Storage. The Pages docs read for this page don't say whether a Pages site serves files stored in Git LFS.
Free hosts compared on the same limits
| Host and free plan | Site or file size | Traffic included | Builds or deploys | Past a limit |
|---|---|---|---|---|
| GitHub Pages | Published site up to 1 GB; files over 100 MiB blocked | A soft limit of 100 GB of bandwidth a month | A soft limit of 10 builds an hour, none with a custom Actions workflow | GitHub “may not be able to serve your site,” or emails you suggestions; rate limits answer HTTP 429 |
| Netlify Free | Netlify doesn't say | 300 credits a month; bandwidth costs 20 per GB | 15 credits per production deploy | Every project on the account pauses until the next billing cycle; Free can't buy credits |
| Cloudflare Pages Free | Up to 20,000 files, 25 MiB each | Static asset requests are “free and unlimited” | 500 builds a month, 1 at a time, 20 minutes each | No limit to pass for static files |
| Vercel Hobby | 100 MB of source files per CLI upload | 100 GB of data transfer and 1,000,000 CDN requests a month | 100 deployments a day, 100 builds an hour | In most cases, you wait 30 days to use the feature again |
| Convika Free | One HTML file up to 2 MB | 10,000 page views a month, all pages together | Up to 30 publishes a day, no build step | Editing and analytics pause, and 7 days later the pages stop until the month ends or you upgrade |
Convika's page-view limit counts from sign-up for workspaces created on or after October 23, 2026 (Japan time), and from November 1, 2026 (UTC) for earlier ones.
If your site is one HTML page: Convika
Convika hosts landing pages, one HTML page each, with a form that keeps entries and stats on who visited. There is no repository, build, or bandwidth meter: you upload the page's HTML file, up to 2 MB, or paste its code, and Convika counts page views. Claude, Claude Code, or Codex can also save the page through Convika's MCP server. Free allows up to 30 publishes a day.
Section 7 of Convika's terms allows commercial use on every plan, Free included: a page that sells or advertises a product or service, a startup or waitlist page, or a client's page you build, host, and bill the client for. It bars reselling Convika itself without permission.
Free includes 1 published page, 10,000 page views a month, 50 form entries a month with CSV export and an email for each, 90 days of visit stats, and 1 custom subdomain such as www.yourbrand.com, with a small Convika badge. At 10,000 page views in a month, editing and analytics pause, and 7 days later the pages stop until the month ends or you upgrade. Pro monthly costs $12 a month, includes 100,000 page views, and never stops for traffic: each 10,000 views past that cost $0.10. Pricing lists each plan.
Not a fit for: a Jekyll site, documentation, or a site with several routes. Convika hosts a single HTML document per page, and the page's scripts can only fetch data from its own address. To see your page on Convika first, the free HTML publishing tool gives you a preview link with no account.
Which one to pick
- An open-source project's site, docs, or a personal blog under 1 GB: Stay on GitHub Pages. If traffic nears 100 GB a month, put a CDN in front, as GitHub suggests.
- A site that rebuilds often: Publish with a custom Actions workflow, which lifts the limit of 10 builds an hour.
- A static site that might get a traffic spike: Pick Cloudflare Pages, where static asset requests are free and unlimited.
- A single landing page that sells or collects signups: Pick Convika Free, with the form and stats included. GitHub's terms rule out running a business on Pages.
Frequently asked questions
Does GitHub Pages have a bandwidth limit?
Yes, a soft one. GitHub's limits doc says “GitHub Pages sites have a soft bandwidth limit of 100 GB per month.” Past it, GitHub “may not be able to serve your site,” or may email you suggestions such as putting a CDN in front of the site.
Will GitHub take my Pages site down if it goes over 100 GB?
Yes, it may. The doc says that if a site exceeds the usage quotas, “we may not be able to serve your site, or you may receive a polite email from GitHub Support.” GitHub doesn't say how far past 100 GB that happens or for how long.
Is GitHub Pages storage limited to 1 GB?
Yes, for the published site. “Published GitHub Pages sites may be no larger than 1 GB.” The source repository has a recommended limit of 1 GB too, and GitHub's large-files doc strongly recommends keeping a repository under 5 GB.
Does a 429 error mean GitHub Pages rate-limited my site?
Yes. GitHub's limits doc says “If your request triggers rate limiting, you will receive an appropriate response with an HTTP status code of 429, along with an informative HTML body.” It gives no number of requests that triggers it.
Is the 10 builds per hour limit on GitHub Pages a hard limit?
No. GitHub calls it “a soft limit of 10 builds per hour,” and says “This limit does not apply if you build and publish your site with a custom GitHub Actions workflow.”
Does GitHub charge for GitHub Pages bandwidth?
No, GitHub's Pages docs name no charge for traffic. Past the soft limit of 100 GB a month, they describe GitHub not serving the site or emailing you suggestions. Builds run on GitHub Actions, which is free for public repositories; a private repository's minutes past its plan's allowance are billed.
Can I have more than one GitHub Pages site?
Yes. You get 1 user or organization site per account, at <owner>.github.io, and 1 project site per repository. “You can only create one user or organization site for each account on GitHub.”
Can a file in a GitHub Pages repository be bigger than 100 MiB?
No, not in the repository itself. “GitHub blocks files larger than 100 MiB.” A larger file needs Git Large File Storage, and the Pages docs read for this page don't say whether a Pages site serves files stored that way.
Can I use GitHub Pages for a business site?
No, not one that runs your business. 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).” The page Can you use GitHub Pages for a commercial or business site? covers the cases GitHub hasn't ruled on.
Is there a free host without a bandwidth limit?
Yes, for static files. Cloudflare's Pages docs say “On both free and paid plans, requests to static assets are free and unlimited.” Convika counts page views instead of bandwidth: 10,000 a month on Free, whatever the file weighs.
Sources
- GitHub Pages limits (GitHub Docs) (checked October 23, 2026)
- GitHub Terms for Additional Products and Features (GitHub Docs) (checked October 23, 2026)
- What is GitHub Pages? (GitHub Docs) (checked October 23, 2026)
- Configuring a publishing source for your GitHub Pages site (GitHub Docs) (checked October 23, 2026)
- Using custom workflows with GitHub Pages (GitHub Docs) (checked October 23, 2026)
- Creating a GitHub Pages site (GitHub Docs) (checked October 23, 2026)
- About large files on GitHub (GitHub Docs) (checked October 23, 2026)
- Credit usage and pricing for GitHub Actions (GitHub Docs) (checked October 23, 2026)
- How credits work (Netlify Docs) (checked October 23, 2026)
- Resume paused projects (Netlify Docs) (checked October 23, 2026)
- Cloudflare Pages limits (Cloudflare Docs) (checked October 23, 2026)
- Pages Functions pricing (Cloudflare Docs) (checked October 23, 2026)
- Vercel Hobby Plan (Vercel Docs) (checked October 23, 2026)
- Limits (Vercel Docs) (checked October 23, 2026)
Next step
How to share an HTML file as a link that opens on any phone
Email and Google Drive open HTML files on a phone without scripts. Compare 5 hosts (Netlify Drop, Tiiny Host, GitHub Pages, Convika) and follow 4 steps.
Related articles
- Can you use GitHub Pages for a commercial or business site?GitHub Pages bans e-commerce and SaaS, and business landing pages are a gray area. See what the 2026 terms allow and free hosts without a business rule.
- Vercel Hobby plan limits: bandwidth, deployments, and what happens when you pass themVercel Hobby includes 100 GB of data transfer and 100 deployments a day. Past a limit, you wait 30 days in most cases. Every limit, quoted from Vercel's docs.
- What happens to a free website when it gets too much traffic? Limits comparedTraffic limits of 8 free hosts, GitHub Pages, Netlify, and Vercel included: whether a viral page stops, slows, or gets billed, and how to keep it up.
- GitHub Pages alternatives for a one-page site (no git needed)Netlify, Cloudflare Pages, Vercel, Tiiny Host, Carrd, and Convika compared with GitHub Pages on git, forms, passwords, custom domains, and commercial use.
- Can I use a website made with ChatGPT or Claude for my business? Who owns it?Yes: OpenAI says you “own the Output,” Anthropic assigns its rights “if any,” and Google “won't claim ownership.” What each AI's terms say on business use.
- Is Netlify free? What the Free plan's 300 credits cover in 2026Netlify's $0 plan gives 300 credits a month (15 per deploy, 20 per GB) and allows commercial projects. See how long 300 credits last for 1 HTML page.