Netlify vs traditional hosting: a static site that costs $0 a month to run

Most beginners assume a website needs a monthly hosting bill. For many sites, it does not. If your site is a set of pages that rarely change — guides, a portfolio, a landing page, a small business site — you can run it on static hosting, and the free tier of a static host can genuinely cost $0 a month. This guide explains when that works, when it does not, and how it compares with traditional hosting.

First, what "static" means

A static site is a collection of files: pages, styles, and images. When a visitor opens a page, the server hands over the files. Nothing is computed on the spot, no database is queried, and no login session is managed.

A dynamic site, by contrast, builds each page when it is requested — pulling content from a database, checking who is logged in, processing a form or a payment. That is what platforms like WordPress do, and it needs a server that runs software around the clock.

The distinction matters because static files are cheap to serve and hard to break, while dynamic sites need more server power, more updates, and more maintenance.

What Netlify-style static hosting does

A static host takes your files and publishes them on a fast global network. The usual workflow:

  1. You prepare your files (pages, styles, images).
  2. You upload them through the host's web dashboard, or connect a code repository if you use one.
  3. The host publishes them and gives you an address. You can then connect your own domain.
  4. HTTPS (the padlock) is normally included, and updating the site means uploading new files.

The free tier of a static host typically covers a small or medium site comfortably. Limits exist — on bandwidth, on build time, on the number of sites — so check the current limits on the provider's site before you rely on them. For a personal site or a small guide site, the free tier is usually more than enough; for a high-traffic site, it is not.

Static hosting provider homepage

What traditional hosting does differently

Traditional (shared) hosting gives you a server that runs software: a database, a scripting language, email, and a control panel. That is what you need when:

You pay a monthly or yearly fee for that server, and you take on updates and security for the software running on it. Check the current price on the provider's site, and remember to check the renewal price, not just the first term.

The comparison, side by side

QuestionStatic hosting (free tier)Traditional shared hosting
Monthly cost for a small site$0 on the free tier, within its limitsA hosting fee
What it runsFixed pages, files, imagesWordPress, shops, logins, databases
Setup effortLow — upload files, connect domainMedium — install and maintain software
Security updatesMostly the host's jobMostly your job
What breaks most oftenAlmost nothingPlugins, updates, logins
When it stops fittingHigh traffic, or features needing a serverRarely — it scales by upgrading plans

When static hosting is the wrong choice

Be honest about these cases, because picking wrong costs time:

A contact form deserves a note: a purely static site has no server to receive form submissions. The usual solutions are a third-party form service or a small serverless function, both of which are separate services with their own terms. If a working contact form is essential on day one, factor that in before choosing.

Domain, DNS, and HTTPS in plain language

Whatever host you choose, three pieces connect your domain to your site:

None of this requires a computer. It is all done in web dashboards, which is why the whole workflow can run from a tablet.

The bottom line

If your site is pages, not an app — guides, a portfolio, a business page — static hosting on a free tier is the cheapest honest option, and $0 a month is real for a small site within the tier's limits. If your site needs logins, a shop, or a database, pay for traditional hosting and pick it for the software you actually run. Match the hosting to the site, not the other way around.

← All guides