Your website is a set of files — text, photos, maybe a script or two. Those files have to sit on a computer that's switched on all the time and connected to the internet, so that when someone types your address, something answers.

That computer is the host. Hosting is renting space on it.

The house analogy, briefly

Three separate things, and people mix them up constantly:

• The domain is the address — davesplowing.com. Rented yearly from a registrar.
• The hosting is the land and the building — the place the files live. Paid monthly, or free.
• The website is what's inside — your words and photos, arranged how you want.

You can move house without changing your address. You can rebuild the inside without moving. And if the landlord sells the building, your address is still yours.

What a host actually does

More than just storing files:

• Serves the pages — answers requests, quickly, to phones on bad connections.
• Provides the security certificate — the padlock in the address bar, so the site loads over HTTPS. Free now, from Let's Encrypt, but somebody has to install and renew it.
• Keeps backups — ideally. Ask. Many cheap hosts don't, and you find out at the worst moment.
• Keeps the machine running — power, cooling, updates, replacing failed disks. That's most of what you're paying for.
• Handles email — sometimes, separately, or not at all.

Who provides it

Website builders (Squarespace, Wix) bundle hosting into their monthly fee. You never see it as a separate line item, and you can't host the site anywhere else.

Web hosts (the traditional kind) sell space directly — you upload files or install WordPress. Cheaper, more control, more work.

Free services host your page at no cost, usually on a sub-address, in exchange for keeping it simple and standard. Fastpages works this way, and so do free tiers of several builders, with their own limits.

You — a computer in your basement. Possible. Not recommended. See can I host a website myself.

What you're really paying for

Reliability and speed, mostly. A $5-a-month shared host and a $200-a-month dedicated server run the same HTML identically; the differences are how many other sites share the machine, how fast it responds, how often it goes down, and how much support you get when it does.

For a one-page business site with a few hundred visitors a month, almost any host is fast enough. The realistic reasons to pay more are: you're running an online shop, you get thousands of visitors a day, or you need someone to answer the phone at 9pm when something breaks.

What hosting is not

It's not the design. It's not the domain. It's not "the website" in the sense of what a customer sees. If your site looks wrong, that's a design or content problem; if it's down, it's hosting; if it doesn't load at all and the domain works, it's usually DNS — the pointer between the two.

Knowing which of those three is broken will save you an hour on hold with support.

Do you need to think about it at all?

If you're using a builder or a free service: no. It's handled. You may never read the word "hosting" again after this page, which is the correct outcome.

If you're running WordPress or a site someone set up for you: yes — find out who's paying for the hosting, when it renews, and what happens if it lapses. That's the same conversation as whose name is on the domain, and it matters just as much when the invoice stops.