Make software by describing it
BBuilt with Prompts

Make software by describing it

How to Host a Static Website for Free

You can host a static website for free with services such as GitHub Pages, Netlify, Cloudflare Pages and similar hosts. A static site is just files, such as HTML, CSS, JavaScript and images, so the host only has to store them and send them to visitors. For a personal tool or small project, the free plans are usually enough.

Plans and limits change, so treat the details below as a guide to what to look for, and confirm current terms on each service’s own site before you decide.

What a static host does

When someone visits your address, their browser asks a server for your files. A static host keeps your files on servers around the world and delivers them quickly. There is no database and no code running on the server, which is why the service can be offered cheaply or for free.

This fits tools made with an AI assistant very well. A tip calculator, a converter or a one-page site runs entirely in the visitor’s browser. It needs a place to live, not a server to compute anything.

What you need before you start

Prepare three things:

  1. A folder with your site files. The main page should be named index.html.
  2. Working links. Use relative paths such as images/photo.jpg, not paths from your own computer.
  3. A test. Open the page from your folder and click everything to confirm it works.

If your page loads files from the internet, such as a library from a CDN, keep that in mind. Visitors need a connection for those parts to load.

The main free options

GitHub Pages. Publishes files from a GitHub repository. It suits people who are happy to learn a little Git, and it gives you version history for free. The default address looks like yourname.github.io.

Netlify. Offers a drag-and-drop upload for a folder, so you can publish without learning Git. You can also connect a repository for automatic updates. The default address ends in netlify.app.

Cloudflare Pages. Publishes from a repository or by direct upload, with a wide network behind it. It works well if you plan to use Cloudflare for your domain.

Others. Similar services exist, and new ones appear. The same questions apply to each: how do I upload, what is the address, what are the limits?

How to choose

For your first project, pick the option with the fewest steps. If you have never used Git, a drag-and-drop upload gets you online in minutes. If you expect to update the site often, a repository-based host saves time later, because pushing a change updates the site.

Consider these points:

Our comparison of Cloudflare Pages, Netlify and GitHub Pages goes through these in more detail.

A basic publishing routine

Whichever host you choose, the routine looks similar:

  1. Create an account and verify your email.
  2. Create a new site or project.
  3. Upload your folder, or connect the repository that contains it.
  4. Wait for the host to report that the site is live.
  5. Open the address it gives you and test the page on your phone.

If something is missing, check that index.html is at the top level of the uploaded folder, not inside a subfolder. This is the most common first mistake. Another is a file name with different capitalization than your links use; many hosts treat Photo.jpg and photo.jpg as different files.

Free does not mean unlimited

Free plans have limits, for example on monthly bandwidth or on the number of sites. For a small personal tool, you are unlikely to hit them. Read the plan details so you know what happens if a page suddenly receives many visitors. Some hosts slow or pause a site, others ask you to upgrade.

Also remember that everything you publish is public. Do not upload files with passwords, private keys, personal data or anything you would not want strangers to read. If you are not sure whether a file is safe, leave it out.

Keep a backup

Your host is not a backup. Keep the original folder on your computer, and consider copying it to cloud storage or an external drive as well. If you lose your account or make a mistake, you can republish from your copy.

Check the result like a visitor

After you publish, step back and use the site as a stranger would. Open the address on a phone without being logged in to anything, over mobile data instead of your home network. Look at how long it takes to load, whether images appear, and whether the layout is readable. Click every link, including those that lead outside your site.

Ask a friend to try it, too. Differences between your computer and theirs are common: a missing font, a blocked script, a slower connection. Write down what you find and fix the most visible problems first. Then update the site and test again, so you practice the whole loop of publish, check, fix.

Finally, think about the long run. Services change their free plans from time to time, and a host you rely on today may alter its terms. Keep your files portable, avoid features that tie you to one provider unless they give you something you need, and note the address of your site and the host in your project log. If a change forces you to move, you will be glad the files were organized and the details were written down.

Next steps

Pick one host and publish the simplest page you have, even a single line of text. Open the address on your phone, then change the text and republish to learn how updates work. Once that routine feels comfortable, move a real tool onto the host and write its address in your notes file alongside the date you published it.