GitHub Pages is genuinely good hosting. It is free, it has been running for over a decade, and it gives you a custom domain and an SSL certificate at no cost. The problem is not quality. The problem is that everything about it assumes you already work in Git — and if you built your site in Claude or ChatGPT and have a folder on your desktop, that assumption is the whole obstacle.
What GitHub Pages actually asks of you
To publish with GitHub Pages you need a GitHub account, a repository, and your files committed into it. There is no upload button and no drag-and-drop. That is not an oversight — GitHub Pages is a feature of a version-control system, and the repository is the interface.
For a developer this is free infrastructure attached to a tool they already use. For a designer holding a folder called my-site, it means learning Git first, then publishing. Most people who ask for a GitHub Pages alternative are really asking for a way to skip that first step.
One more constraint catches people out. On the free plan, Pages works from public repositories. Publishing from a private repository requires GitHub Pro, Team or Enterprise. Your source files are visible to anyone unless you pay.
The limits worth knowing first
GitHub publishes its limits openly, which is more than most hosts do. Four of them matter for a normal site:
1 GB for the repository, and 1 GB for the published site. Comfortable for a portfolio, tight if you have uncompressed photography or video.
100 GB of bandwidth per month. GitHub calls this a soft limit, meaning it is a guideline they enforce by getting in touch rather than a switch that flips. Do not read it as a hard cap in either direction.
10 builds per hour, also soft, and not applied if you build through your own GitHub Actions workflow.
Ten minutes maximum for a deployment to complete before it times out.
Custom domains are free on GitHub Pages, including on the free plan, and the SSL certificate is issued automatically through Let’s Encrypt. Plenty of paid hosts charge for exactly that combination. If Git is not an obstacle for you, this is a real argument for staying.
Six alternatives, side by side
Every host below can put a finished folder online. They differ on what they ask for first, and on what happens when you exceed the free allowance. Figures checked on 8 September 2026 against each provider’s own pricing and documentation pages.
| Publish without Git | Free tier | Custom domain when free | Paid from | |
|---|---|---|---|---|
| GitHub Pages | No — repository required | Yes, public repos | Yes, SSL included | GitHub Pro for private repos |
| Netlify | Yes — Netlify Drop | 300 credits per month | Yes | $9 / month |
| Vercel | Yes — Vercel Drop | Yes, non-commercial only | Yes | $20 per user / month |
| Cloudflare Pages | Yes — Direct Upload | 500 builds per month | Yes | $5 / month for Workers Paid |
| Static.app | Yes | 50 MB, one site | No | $5 / month |
| Neocities | Yes — browser editor | 1 GB, 200 GB bandwidth | No | $5 / month |
| sofast | Yes — drag a folder | None | — | $5 / month |
Two entries in that table need a sentence of context, because the headline number is misleading in both cases.
Netlify’s free tier is now measured in credits, not gigabytes. You get 300 credits a month. A production deploy costs 15 credits and bandwidth costs 20 credits per gigabyte, from the same pot. So 300 credits is roughly twenty deploys or fifteen gigabytes of traffic — not both. When they run out on the free plan, your sites are paused and visitors see a “Site not available” page. Any article still telling you Netlify gives away 100 GB is describing a plan that no longer exists.
Vercel’s free Hobby plan is for non-commercial, personal use only. That is an explicit rule, not a grey area. A business brochure site, a client landing page or a portfolio that sells something does not qualify. The next step up is $20 per user per month.
Which one fits which situation
You already use Git and your site is public. Stay on GitHub Pages. Nothing here beats free, indefinite hosting with a custom domain when the workflow already suits you.
You want the fastest possible one-off publish. Netlify Drop or Vercel Drop. Both take a folder in the browser. Note that each Vercel Drop upload creates a new project, so it is a way to publish once, not a way to update a site.
Your DNS already lives at Cloudflare. Cloudflare Pages Direct Upload, and static requests are free with no bandwidth cap. Two catches: the browser uploader takes up to 1,000 files at 25 MiB each, and a project created by Direct Upload cannot be switched to Git later without recreating it.
You want a personal page and do not need your own domain. Neocities gives you 1 GB free and an editor in the browser. A custom domain requires the $5 Supporter plan.
You want updating a live site to stay as easy as publishing it. That is what sofast is for. You drag the folder in and the site is live in about fifteen seconds, with your own domain and SSL on every plan. There is no free tier — plans start at $5 a month for two sites and 500 MB. We would rather charge a small amount and keep your site online than run a free tier we would have to take away later.
Moving an existing GitHub Pages site somewhere else
Moving is easier than people expect, because a GitHub Pages site is already a folder of static files.
Download the repository. On GitHub, use Code, then Download ZIP. Unzip it. If your site is built by a generator such as Jekyll, you want the built output instead, not the source.
Check that index.html sits at the top of the folder. Not inside a subfolder. This one detail causes most failed first uploads anywhere.
Upload the folder to the new host, then confirm the site looks right on its temporary address before touching any DNS.
Move the domain last. Point the DNS records at the new host, and keep the GitHub repository until the new address has been serving correctly for a few days. Nothing is lost by waiting.
Common questions
The answers below cover cost, private repositories, custom domains, bandwidth, and what happens to your address if you move.
For public repositories, yes — it is free indefinitely within its usage limits, with no trial period and no card required. The cost appears in a different place: publishing from a private repository requires a paid GitHub plan, so keeping your source files out of public view is the part you pay for.
In practice, no. You can upload files through the GitHub web interface, which avoids the command line, but you still need an account, a repository, and an understanding of commits and branches to publish and update reliably. If that is the part you want to avoid, a drag-and-drop host is the honest answer.
Yes, both, on the free plan. You add the domain in the repository settings, point your DNS at GitHub, and a Let’s Encrypt certificate is issued automatically. It occasionally needs a nudge — removing and re-entering the domain forces the certificate request again.
GitHub describes the 100 GB monthly figure as a soft limit. In practice that means they may contact you about the usage rather than switch the site off without warning. Treat it as a guideline for what the service is designed for, not as a hard ceiling you can rely on either way.
Yes. Unlike Vercel’s free Hobby plan, GitHub Pages has no non-commercial restriction. The practical obstacles are different: the repository must be public unless you pay, and handing a client a workflow that requires Git usually means you stay responsible for every future text change.
Not if you use your own domain. The domain is yours and points wherever you tell it to, so moving hosts is a DNS change your visitors never notice. You only lose an address if you were using the free username.github.io subdomain, which is why a custom domain is worth setting up early.
If your site came out of an AI tool and you want it online without a repository, these guides show the export and upload step by step.
