Publishing a static site for free — and what "free" actually covers

A static site is just files: HTML, CSS, images. No database, no PHP, nothing to keep patched. That makes it the cheapest kind of website to run, and the easiest to move. It also makes "free hosting" genuinely free rather than a trial that expires.

Here is how to put one online, and — more usefully — where the limits actually are.

Why static hosting is free at all

Serving a fixed file is close to costless. There is no server work per visitor: the host copies your files to machines around the world and hands them out. Bandwidth is the only real expense, and for a brochure site, a menu, a portfolio, that number is tiny.

WordPress hosting costs money because something has to run — PHP executes, a database answers queries, and both need patching. A static site removes that entire category of expense, and with it a category of maintenance.

The process, start to finish

1. Get your files. A zip with index.html at the top level, plus a folder of assets. That is the whole site.

2. Make a free account at Netlify, Cloudflare Pages, or GitHub Pages. Netlify is the friendliest for people who do not use Git.

3. Drag the unzipped folder onto the deploy area. You get a working address within a minute — something like your-site.netlify.app. It is live, on HTTPS, worldwide.

4. Point your own domain at it. In the host's dashboard, add your domain. It gives you either a set of nameservers or a CNAME record. You paste that into whichever registrar you bought the domain from. Propagation takes anywhere from minutes to a few hours.

5. HTTPS is automatic. Every host above issues a free certificate and renews it. This used to be a paid annual chore; it is now a non-event.

What "free" covers, and what it does not

Covered: hosting, global delivery, HTTPS, and generous bandwidth. For a small business site you will not approach the limits.

Not covered — and this is the part people meet later:

• Your domain still costs money. Ten to fifteen dollars a year, paid to a registrar. Free hosting does not include a free domain.
• Forms need a service. A static host cannot process a form submission, because nothing runs on the server. Either the form opens the visitor's email app, or you point it at a form service — Formspree, Basin, or the host's own forms feature. Most have a free tier covering a modest number of submissions.
• No admin panel. There is no dashboard to log into and edit text. Changing a headline means editing the HTML file and re-uploading. That is the honest trade for the simplicity and the zero cost.
• Uptime is the host's. Their track records are strong, but if the site is down at 3am, it is their status page you are reading, not your developer's phone you are calling.

When static is the right answer

It fits when your content changes rarely and you value not maintaining anything: restaurants, tradespeople, portfolios, single-product sites, brochure sites for established businesses.

It fits badly when you need to publish frequently without touching code, when you need accounts and logins, or when you are running a shop. A blog you update weekly will frustrate you inside a month. A store needs a store platform.

The part worth keeping in mind

The reason to choose static is not only that hosting is free. It is that the files are ordinary and portable. Any developer can read them, any host can serve them, and moving between hosts is a drag-and-drop away. There is no platform to be locked into, no plugin ecosystem to maintain, no renewal to forget.

That is a smaller website in the best sense: fewer moving parts, fewer things that can break, and nothing between you and the files you own.