Beginner guide

What is web hosting?

A plain explanation of what a web host does, what the different types are, and how to work out which one you actually need.

Ben Johnson · last checked 2026-08-03 · 6 min read

Say you build a website on your laptop. It looks great. You show a friend, and they ask for the link. You don’t have one. The site only exists on your machine, and your laptop is closed and in a bag.

That’s the problem web hosting solves. A web host is a computer that never turns off, sitting in a building with fast internet, holding a copy of your files. When someone types your address, that computer sends them the site.

That’s the whole idea. Everything else is detail.

The three parts of a live website

People mix these up all the time, and it causes most of the confusion. A working website needs three separate things:

Your files. The HTML, images, styles, and any code you wrote. This is the website itself.

A host. The always-on computer that stores those files and hands them out. This is what you rent.

A domain name. The address people type, like example.com. You rent this separately, usually from a different company.

Here’s the part that trips people up: buying a domain does not give you hosting, and buying hosting does not give you a domain. They’re two purchases. You then have to connect them, which means pointing your domain at your host.

Think of it like a shop. The host is the unit you rent. The domain is the street address on the sign. Neither one is much use without the other.

What the host is actually doing

When someone visits your site, a lot happens in under a second:

1. Their browser asks the internet where example.com lives. It gets back a number, like 203.0.113.10.
2. The browser sends a request to that number.
3. A program on the host computer catches the request. This program is called a web server.
4. It finds the right file. If the file has code in it, the server runs the code first.
5. It sends the finished page back.

Step 4 is where the two big categories split apart.

If your site is just HTML and images, the server only has to find a file and send it. That’s fast and almost nothing can break.

If your site runs code — WordPress, or anything in PHP — the server has to build the page fresh every time someone asks. That’s slower, and it’s the reason busy sites slow down.

The types of hosting, without the sales talk

Two honest notes about this table.

A VPS is not “better” hosting. It’s less hosting. You get an empty computer and you become the person who has to set it up, patch it, and fix it at 2am. That’s a fine trade if you want the control. It’s a bad trade if you just want a website.

Static hosting is better than most people think. If your site has no code in it, you don’t need a server that runs code. Static hosts are faster, harder to break, and often free.

For most people reading this, the answer is shared hosting.

What you’re really paying for

Hosting companies advertise storage space because it sounds generous. Storage is almost never the thing that runs out.

What runs out is how many pages your site can build at once. Every hosting plan caps this. On a free plan it’s usually around ten at a time.

Here’s what that means in practice. Say each page takes two seconds to build. With ten slots, you can serve about five people per second. Visitor number eleven, arriving at the same moment, gets an error instead of a page — usually a 508 resource limit message.

The fix is rarely a bigger plan. It’s caching. Caching saves a finished copy of each page, so the server hands out the saved copy instead of building it again. Most requests then skip the code entirely. It’s free, it takes about ten minutes to switch on, and it moves that ceiling further than any upgrade will.

The other thing you’re paying for is email. Nearly every free host blocks outgoing mail. That’s not stinginess — free hosting attracts spammers, and one bad user can get the whole server’s mail blocked everywhere. If your contact form has to work, check this before you sign up.

Free or paid?

Free hosting is real, and it works. It’s the right choice for a portfolio, a school project, a hobby site, or anything you’re still figuring out. We wrote a full breakdown of where free hosting stops if you want the specifics.

Paid hosting is worth it once one of these is true:

• The site makes money, so downtime costs you something.
• You need email that actually sends.
• You need scheduled tasks, or a language other than PHP.
• You’re spending more time working around limits than building.

That last one is the honest signal. Free hosting is a good deal while you don’t notice it. Once you’re fighting it, your time costs more than the upgrade.

How to pick without overthinking it

Ask four questions:

1. Does my site run code? No means static hosting. Yes means shared.
2. Do I want to be a server administrator? No means avoid a VPS.
3. Does this site need to send email? Yes means check that before anything else.
4. What happens if it goes down for a day? Nothing means free is fine.

Start small. Moving to a bigger plan later is easy, and every host makes it easy on purpose. Starting with more than you need just costs money while you find out what you actually wanted.

So, what is web hosting?

It’s renting space on a computer that stays on, so other people can reach your files.

The rest — the plan names, the storage numbers, the feature lists — is a company’s way of describing how big a slice you get and what it’s allowed to do. Once you know that a slice is what you’re buying, the plans stop being confusing and start being comparable.

When you’re ready to put something live, the step-by-step guide walks through uploading files, setting up a database, and getting your domain connected. And if the domain part is what’s giving you trouble, our DNS checker will tell you whether the problem is your settings or just the internet catching up.