If you've ever tried to set up a website, someone probably mentioned "web hosting" and then assumed you knew what that meant. This is my attempt to explain it in a way that actually makes sense, including whether you need to pay for it at all.
The simple version
Your website is made of files — HTML, CSS, images, maybe some JavaScript. Those files have to live somewhere so that anyone in the world can load them in a browser. Web hosting is just that: a computer (called a server) that stores your files and serves them up when someone visits your URL.
When someone types your web address into a browser, their device sends a request to that server, and the server sends back the files that make up your page. That's it. Web hosting is the place where your files live.
Why it sounds more complicated than it is
The hosting industry has done a good job of making this seem technical and expensive. Terms like "bandwidth," "uptime SLA," "shared vs. dedicated," and "cPanel" get thrown around to justify monthly fees. For a large website with heavy traffic, user logins, or a database, some of those things matter. For a small business brochure site or a nonprofit page, most of them don't.
The vast majority of small business websites are simple static files — a few HTML pages, some CSS, maybe a contact form. Those files are tiny. They don't need a dedicated server. They don't need much bandwidth. They need a place to live that stays online reliably.
Free hosting exists and it's actually good
This is where I push back on the conventional advice. Platforms like GitHub Pages and Netlify offer free hosting for static websites, and the quality is genuinely excellent. Both are used by millions of developers. Both have solid uptime. Both support custom domain names. Neither puts ads on your site.
I host every Webspansion project on one of these two platforms. Every site I've built — for nonprofits, for small businesses, for community groups — runs on free hosting. In over 19 projects, I've never had a hosting-related issue that affected a client's site.
The trade-off is that free hosting on these platforms works best for static sites — no database, no backend, no WordPress. If your site needs user logins, a shopping cart, or dynamic content generated server-side, you'll probably need paid hosting or a platform like Squarespace that handles all of it. But if your site is informational — which describes most small business and nonprofit sites — free hosting works fine.
What you do need to pay for: the domain name
The hosting can be free, but the domain name — the custom address like yourbusiness.com — typically costs money. Domain names usually run $10–$20 per year, depending on the extension (.com, .org, .net) and the registrar you use.
Some hosting packages bundle the domain name in the price for the first year, then charge separately after. That's one reason people conflate hosting and domain costs. They're separate things: hosting is where the files live, the domain is the address people type to get there.
For context: every Webspansion client either already has a domain name or gets one registered as part of their free project. The hosting is always free.
So do you need to pay for hosting?
For most small businesses and nonprofits: no. If your site is informational and doesn't need a database or user accounts, you can run it for free on GitHub Pages or Netlify with a custom domain name that costs about $12 a year.
If you're using WordPress, Squarespace, Wix, or Shopify, those platforms bundle hosting into their subscription fees and you don't control it separately. That's fine, just know you're paying for hosting as part of the package.
The short answer is: the internet has changed. You don't need a $30/month shared hosting plan just to have a basic website for your business. What matters is that the site loads fast, stays online, and has your real domain name on it.