How to Host a Simple Website for Free (2026)

Next to it, create styles.css in the same folder:

body { font-family: system-ui, sans-serif; max-width: 40rem; margin: 3rem auto; padding: 0 1rem; }
h1 { font-size: 2rem; }
nav a { margin-right: 1rem; }

Two details do most of the work here. First, the href="styles.css" in the HTML points at the stylesheet with a relative path, meaning from this folder. Write the same thing without the folder and the browser looks for the file in the wrong place. Second, keep images in a subfolder such as images/ and reference them as images/portrait.jpg, never as a full path from your computer's drive.

Add more pages any time you want by creating work.html and contact.html beside index.html and linking to them the same way.

Test the Website Before Upload

Open index.html by double-clicking it. It should render in your browser exactly as it will online, minus the address bar.

Then click every link and every image. A link that jumps nowhere usually means the file name does not match, or the file is in a subfolder you forgot about. Missing styling almost always means the stylesheet is named slightly differently, such as Styles.css or styles.css.txt after a save that added an extension.

Two habits worth forming now. Type file names in lowercase with hyphens, so about-me.html instead of About Me.html, and check the browser console for errors. It takes ten seconds and it points straight at the line that broke. Testing locally also keeps broken paths from becoming a public embarrassment once the site is live.

How to Host a Simple Website for Free With GitHub Pages or Netlify

Netlify is the shortest route. Sign up, open the dashboard, choose to add a new site from a folder, and drag the whole my-site folder onto the upload area. The site is live within seconds on an address like my-site.netlify.app. Rename the project in site settings afterwards if you want a cleaner address; the random suffix is the part people complain about most.

GitHub Pages takes four more minutes and gives you a proper editing workflow afterwards.

1. Create a GitHub account, then create a new repository. Name it username.github.io, where username is your actual GitHub handle. That exact naming rule is what turns the repository into a site address rather than a project page. If you already have a repository under another name, the site still works at username.github.io/repository-name/.
2. On the repository, choose Settings, then Pages in the sidebar. Under Build and deployment, set the source to Deploy from a branch, pick main, and the root folder. Save.
3. Upload your files with the Add file button: index.html and styles.css in the root of the repository. Make sure they are not sitting inside an extra folder that got created by mistake.
4. Wait a minute or two for the build to finish. The Pages tab then shows a green confirmation and a Visit site link.

Whichever host you pick, the uploaded site is the same folder you tested locally. That is the nice part: if it worked on your machine, it works here.

Publish and Verify the Site

Your live address is either username.github.io or your-site.netlify.app. Open it in a private browser window so you are not looking at a cached version, then walk through it as a visitor would: every link, every image, and the page on a phone-sized screen.

HTTPS is on by default on all of these platforms, so visitors see the padlock without any setup. Nothing to configure, nothing to pay for a certificate.

Updating later is the part that gets easier. On Netlify, drop the folder in again and the site updates. On GitHub Pages, edit index.html in the repository, type a short commit message, and commit to main; the site rebuilds and republishes itself, usually within a minute. Learn how GitHub Pages publishes your site before you change the branch or folder settings, since those are the controls that decide what gets published.

Common Mistakes and How to Fix Them

Nearly every problem people hit is one of these, and every one has a two-minute fix.

• The site shows a 404. On GitHub Pages, the repository name is not username.github.io, or Pages is set to a branch and folder that hold no files. Check the Pages tab for the URL it reports and compare it with your repository name.
• Styling disappears after upload. The stylesheet was not uploaded, or the link is an absolute path from your computer such as C:/Users/you/Documents/styles.css. Relative paths only, always.
• Images are missing but the page loads. The image file is in a subfolder that the HTML does not reference, or the file name differs by a capital letter. Match them character for character.
• Links work on your computer and not online. You linked to C:/Users/... or to a file that never made it into the folder you uploaded.
• Refreshing a page gives you a 404. This one is specific to single-page applications built with React or Vue. Those apps need a redirect rule that sends every path back to index.html. Providers document it as a rewrite or fallback rule, and without one the first visit works while every refresh fails. A plain HTML site never hits this.
• You worry about publishing keys. A public repository shows its entire history to everyone, including anything you committed early on. Keep API keys out of the site folder, store secrets in the host's environment variable settings, and rotate anything that was already committed.
• The free plan stops being enough. Watch bandwidth and storage rather than guessing. Once you approach the published limits, you are close to a paid tier or a CDN, and it is better to find out deliberately than to have the site vanish one day.

Two maintenance habits go a long way. Keep a copy of your folder somewhere outside the hosting account, because a deleted repository takes the site with it, and re-upload after any change so the local copy and the live copy never drift apart. Add a simple title, a description and an image preview to each page while you are there; it costs nothing and it is what people see when they share your link.

Frequently Asked Questions

Conclusion

The quickest route is short: write index.html and styles.css in one folder, open the file in your browser to check it, then drag the folder into Netlify or push it to a repository and switch on GitHub Pages. You will have a public HTTPS address the same afternoon.

Start with a single static page and add features only when something actually needs them. A link hub today can become a small multi-page site later, and every step up from there is a deliberate choice rather than a rewrite.