Web hosting is the service of providing the server resources, network connectivity and operational management that make a website or web application reachable on the internet. In hosting, the provider supplies compute, storage, bandwidth and usually a web server stack, while the customer supplies the site, its code and its content. Within the subject of servers, web hosting is the commercial layer that turns raw infrastructure into a place where sites can live.
Hosting ranges from a few dollars a month for a shared account to dedicated clusters costing thousands. The models differ in isolation, control, scalability and who is responsible for patching, security and backups, and choosing among them is one of the first technical decisions for any web project.
What a web hosting service provides
A hosting service bundles several layers that a site needs in order to run. At its core are server resources: CPU time, memory and disk space. Around them the provider adds a network uplink with bandwidth, a data center with power and cooling, and a software environment.
| Component | What it supplies | Typical specification |
|---|---|---|
| Compute | CPU and memory for applications | Shared cores to dedicated servers |
| Storage | Space for files and databases | SSD or NVMe, a few GB to many TB |
| Network | Connectivity and traffic | Metered or unmetered bandwidth |
| Software stack | Web server, PHP, databases | Nginx or Apache, MySQL or MariaDB |
| Control panel | Self-service management | cPanel, Plesk, DirectAdmin, CloudPanel |
| Supporting services | Email, DNS, TLS, backups | Included or sold as add-ons |
A domain name is usually registered separately and pointed to the hosting server with DNS records. Many providers sell both, but they remain distinct services, and keeping them independent makes a later migration to another host much easier.
Types of web hosting
Hosting models are distinguished mainly by how resources are shared and how much control the customer has. The table compares the most common types.
| Type | Isolation | Customer control | Typical fit |
|---|---|---|---|
| Shared hosting | Accounts share one server | Files and panel only | Small sites and blogs |
| VPS hosting | Virtual machine with guaranteed resources | Full root access | Growing sites, custom stacks |
| Dedicated server | Whole physical machine | Full hardware and OS control | Heavy or regulated workloads |
| Cloud hosting | Elastic virtual resources | API-driven, pay per use | Variable or scaling traffic |
| Managed WordPress hosting | Tuned platform for one CMS | Application level only | Business WordPress sites |
| Colocation | Customer hardware in provider rack | Complete, including hardware | Organizations owning servers |
Two further variants are common. Reseller hosting lets agencies resell shared accounts under their own brand, and platform hosting such as Vercel or Netlify deploys static and serverless front ends directly from a Git repository, without a traditional server to manage.
Managed and unmanaged hosting
Independent of the type, a hosting plan is either managed or unmanaged, and this decides who carries the operational burden. Under managed hosting, the provider patches the operating system, monitors services, maintains backups and responds to incidents. Under unmanaged hosting, the provider only keeps the hardware and network running.
| Task | Unmanaged | Managed |
|---|---|---|
| Hardware and network | Provider | Provider |
| Operating system updates | Customer | Provider |
| Web server and PHP tuning | Customer | Provider |
| Backups and restores | Customer | Provider, often with retention limits |
| Application code and content | Customer | Customer |
| Security monitoring | Customer | Provider, scope varies |
Unmanaged plans are cheaper but require real system administration skills. A neglected unmanaged VPS is a common source of compromised servers, so the lower price must be weighed against staff time and risk.
How to choose a web hosting plan
The right plan follows from workload, traffic profile, skills and compliance needs, not from headline storage numbers. Advertised “unlimited” disk or bandwidth is usually bounded by fair-use policies and by CPU and process limits that matter far more.
| Situation | Suggested choice | Reason |
|---|---|---|
| Personal site or small blog | Shared hosting | Lowest cost, no administration |
| Business WordPress site | Managed WordPress hosting | Caching, updates and staging included |
| Custom application stack | VPS or cloud instance | Root access and chosen software |
| Strong seasonal peaks | Cloud hosting with autoscaling | Capacity follows demand |
| Static front end | Platform hosting or CDN | Global delivery, minimal operations |
| Data residency rules | Provider with suitable regions | Legal location of stored data |
Important criteria include data center location relative to visitors, guaranteed resources, backup frequency and retention, support response times, the uptime commitment in the service level agreement and the ease of exporting data when leaving.
Common hosting risks and mistakes
Hosting problems usually surface only under stress, which is why they are worth anticipating. The following mistakes recur across all hosting types:
- Relying solely on provider backups, which may be infrequent, short-lived or stored on the same infrastructure.
- Noisy neighbors on shared or oversold plans that slow every site on the server.
- Ignoring resource limits such as entry processes, inodes or PHP workers until the site starts failing.
- Choosing a distant region, adding latency for most visitors.
- Leaving software unpatched on unmanaged servers.
- No exit plan, making migration slow when prices or service quality change.
Keeping independent off-site backups, monitoring uptime from outside the provider and documenting the stack reduces the impact of almost every hosting failure.
The idea in brief
A website needs a computer that is always switched on, always connected to the internet and looked after. Most people and companies do not want to run that computer themselves, so they rent space on one. That rental is web hosting.
It works much like renting a place to live. A shared plan is like a room in a shared apartment: cheap, but you share the kitchen. A dedicated server is like a whole house. The more space and privacy you rent, the more it costs and the more you may have to maintain yourself.
A practical scenario
A regional bakery chain runs its WordPress site with an online ordering form on a shared hosting plan costing a few dollars a month. Before holidays, orders spike, the site hits the plan’s process limit and visitors see errors exactly when demand is highest.
The owner moves the site to a managed WordPress hosting plan with server-side page caching, a staging copy for testing updates and daily backups kept for 30 days. A separate weekly backup is copied to independent cloud storage. During the next holiday season, the site handles several times its normal traffic without errors, and a faulty plugin update is rolled back from staging in minutes instead of hours.