If you want a website to be accessible on the public internet, you need somewhere for its files and applications to run. In most cases, that means web hosting. Hosting provides the server infrastructure that stores website files and delivers them to visitors when they request your site. But you do not necessarily need to buy a traditional hosting plan: website builders, managed platforms and services such as GitHub Pages can provide hosting as part of a broader service.
The important distinction is between a domain name, a website and hosting. Your domain is the address people use to find you; your website is the content and software they access; hosting is the infrastructure that makes that content available online. Buying a domain alone does not automatically create a working website. ICANN explicitly notes that a domain must be connected to hosting or another service capable of making the website accessible.
What web hosting actually does
A website consists of files and, depending on the site, databases and server-side applications. When someone enters your web address, their browser uses the Domain Name System (DNS) to find the appropriate server and then requests the website’s content. The server sends the necessary files back to the browser, which assembles them into the page the visitor sees.
Web hosting is the service that provides the infrastructure for that process.
A typical hosting environment may provide:
- Storage for website files and databases
- Processing and memory resources
- Network connectivity and bandwidth
- Tools for deploying and managing a website
- Security features
- Backups
- Domain and DNS integration
- Email hosting on some plans
- Performance features such as caching or CDN integration
The exact package varies considerably between providers and types of hosting.
For a simple website, this infrastructure may be relatively modest. An online store, membership platform or web application can require substantially more resources and more sophisticated server management.
Domain name vs. hosting: the distinction that causes most confusion
A domain name and web hosting are related, but they are not the same service.
Think of the three pieces this way:
| Component | What it does | Example |
|---|---|---|
| Domain name | Provides the human-readable address | example.com |
| Hosting | Stores and serves the website | A web server or hosting platform |
| Website | The pages, content, code and functionality visitors use | HTML, images, database, applications |
A domain can exist without a website. You can register example.com and leave it unused.
Likewise, you can have website files without purchasing a conventional hosting plan. They can be deployed to a platform that provides hosting as part of its service.
The domain is therefore better understood as the address rather than the website itself. ICANN makes the same distinction and explains that registering a domain does not automatically provide a functional website.
Do you always have to pay for web hosting?
No.
You need hosting or an equivalent way of serving your website, but that does not necessarily mean paying a separate hosting company.
There are several ways to put a website online.
Traditional web hosting
You purchase a hosting plan and upload or install your website on the provider’s servers.
This is common for:
- Business websites
- Blogs
- WordPress sites
- Portfolio websites
- Online stores
- Websites that need more control over their server environment
Traditional hosting gives you a relatively clear separation between the domain and the infrastructure running the site.
For people who want conventional hosting with tools for building and managing a website, provide one example of this model.
Website builders
Some website builders bundle hosting into the service.
Instead of separately choosing a server, installing software and configuring it, you build the website within the provider’s platform. The provider handles the underlying hosting infrastructure.
This can simplify setup considerably, particularly for a small business, personal site or portfolio.
The trade-off is that you may have less control over the underlying environment than you would with independently managed hosting.
Managed platforms
Services can also combine hosting, deployment and application management.
For example, a developer might deploy a site to a platform that automatically builds and serves the application. In that situation, the user may never interact with a traditional hosting control panel, but the website is still being hosted somewhere.
Free hosting
Free services can also publish websites. MDN lists services such as GitHub Pages and other free publishing platforms among options for getting a site online.
Free hosting can be useful for experimentation, documentation, simple personal projects or static websites. The important question is not whether hosting is free; it is what limitations come with the service.
Those limitations can involve storage, bandwidth, custom domains, server-side programming, support, commercial use or control over the environment.
What happens when someone visits your website?
The process is easier to understand if you follow a visitor’s request.
Suppose someone enters your domain into a browser.
First, DNS helps translate the human-readable domain into information that tells the browser where the website is hosted. The browser then sends a request to the relevant server. The server responds with the requested website resources, and the browser processes those resources to display the page.
This is why simply owning a domain does not put a website online.
There needs to be an actual service on the other end of the address capable of responding to visitors.
Can you host a website yourself?
Technically, yes.
A web server can be operated on infrastructure you control rather than rented from a conventional hosting company. MDN notes that a web server is essentially a computer hosting one or more websites, although modern hosting can also involve virtualized infrastructure rather than a dedicated physical machine.
For a typical website owner, however, self-hosting introduces responsibilities that a hosting provider would otherwise handle.
You may need to deal with:
- Server configuration
- Operating-system updates
- Security
- Network connectivity
- Backups
- Monitoring
- Hardware failures
- Traffic management
- Software updates
- DNS configuration
- TLS/HTTPS configuration
That can make sense for developers, organizations with specific infrastructure requirements or people who want complete control. For a normal business or personal website, outsourcing the infrastructure is often considerably simpler.
Do you need hosting for WordPress?
If you use self-hosted WordPress, yes: the WordPress installation needs somewhere to run.
That does not necessarily mean you have to manage the server yourself. A hosting company can provide the server environment and tools needed to install, operate and maintain WordPress.
There is also a distinction between WordPress software that you host yourself and hosted WordPress services. With a hosted service, infrastructure is bundled into the platform, so you are not separately purchasing and configuring a conventional server.
The practical question is therefore not simply “Do I need hosting for WordPress?” but “Where will my WordPress installation be hosted?”
Do you need hosting for a simple business website?
Usually, you need some form of hosted publishing service.
A small business website might contain only a handful of pages: an introduction, services, contact information, location and perhaps a blog. It does not require the same infrastructure as a high-traffic application.
That makes a website builder or straightforward hosting plan potentially sufficient.
The important considerations are less about buying the most powerful server and more about whether the service provides the capabilities the business actually needs.
For example, check whether you can use:
- Your own domain
- HTTPS
- Business email if required
- Forms or other interactive features
- Analytics
- Backups
- Content-management tools
- Appropriate storage and traffic limits
- The integrations your business depends on
A technically impressive hosting package provides little benefit if the website never uses its additional capabilities.
What should you look for when choosing hosting?
The right hosting depends on the website rather than on a universal specification.
Reliability
If visitors cannot reach your site, the quality of the website itself becomes irrelevant.
Look at the provider’s infrastructure, uptime policies, monitoring and backup arrangements. Be cautious about treating an advertised uptime figure as a guarantee of your particular site’s availability.
Performance
Hosting can affect how quickly a site can respond, but server specifications are only one part of performance.
Your site’s code, images, database queries, caching, content-delivery network and third-party services can all affect loading times.
A hosting plan with more resources is not automatically a faster website.
Security
Find out what security controls are included and what remains your responsibility.
Depending on the service, this might include SSL/TLS certificates, firewalls, malware scanning, account protections, backups and automated updates. SiteGround, for example, describes security and backup features included with its hosting services, but those are provider-specific offerings rather than universal characteristics of web hosting.
Backups
Backups deserve particular attention because they affect what happens after something goes wrong.
Ask:
- How frequently are backups created?
- How long are they retained?
- Can you restore individual files or an entire site?
- Are backups stored separately from the primary website?
- Are backups included in the advertised price?
A backup is valuable only if it can actually be restored when needed.
Scalability
A small website may need very little infrastructure initially. Its requirements can change if traffic grows, an online store is added or the site becomes more application-heavy.
Consider whether you can upgrade resources without migrating the entire website.
Support
Technical support matters most when something breaks.
Check the support channels, hours, scope of support and whether assistance covers the application itself or only the underlying hosting environment.
Do you need both a domain and hosting?
For a conventional website using its own domain, yes, you generally need both a domain and some form of hosting or website platform.
But they do not have to come from the same company.
ICANN distinguishes domain registration from web hosting, while MDN explains that a domain can be registered with one provider and hosted elsewhere. When they are separate, the domain’s DNS settings need to be configured so that the domain points toward the service hosting the website.
This separation can actually be useful.
For example, you might register a domain with one registrar and later move your website to another hosting provider without changing the domain itself.
The key is maintaining control of the domain registration and understanding where its DNS is managed.
What if you only want a website temporarily?
You may not need to commit to a long-term conventional hosting arrangement.
For a prototype, school project, documentation site or experiment, a free publishing platform may be adequate.
For a business, however, temporary savings should be weighed against the inconvenience of migrating later. A website often accumulates content, customer links, search visibility, integrations and other dependencies that make changing platforms more consequential than it initially appears.
The hosting decision that matters most
The fundamental question is not whether you need a particular type of hosting. It is where your website will live and who will be responsible for keeping it available.
If you use a conventional hosting provider, that provider supplies the server infrastructure. If you use a website builder, the platform generally bundles hosting into the service. If you deploy to a specialized platform or free publishing service, that platform provides the hosting layer instead.
So, if you want your website publicly accessible, you need hosting in the broad sense—but you do not necessarily need to buy a traditional standalone hosting plan.
For most website owners, the sensible choice is to match the hosting arrangement to the site’s actual requirements: how much control you need, what software it runs, how important reliability is, whether you need databases or server-side applications, what support you expect, and how easily you can move if your needs change. The domain is simply the address; the hosting arrangement is what gives that address somewhere to lead.