Web hosting is the service that stores a website’s files, applications and data on an internet-connected server so visitors can access the site through a browser. When someone enters a domain name, DNS helps direct the request to the appropriate server, which then returns the website’s content over HTTP or HTTPS. In other words, a domain is the address people use, while hosting provides the infrastructure that actually delivers the website.
Choosing hosting is therefore less about finding the provider with the longest feature list and more about matching infrastructure, resources, security, support and management to the website you are building. A small portfolio site may need very little server capacity, while an online store, membership platform or busy web application may need substantially more predictable resources, scaling options and operational control.
That distinction explains much of the confusion surrounding web hosting. Providers use terms such as shared hosting, cloud hosting, VPS, dedicated servers, bandwidth, storage, caching and uptime, but those terms describe different parts of the same system.
This guide explains how hosting works, the major hosting models, which specifications actually matter, what you pay for, and what to check before choosing a plan.
What exactly is web hosting?
At its simplest, web hosting gives your website a place to live.
A website consists of files and, depending on how it is built, application code and databases. A web server stores those resources and software on infrastructure connected to the internet. When a visitor requests a page, the server processes the request and sends the necessary resources back to the browser.
A simple request can therefore involve several separate systems:
- You enter a domain such as
example.com. - DNS translates that domain into information that helps locate the relevant server.
- The browser sends an HTTP or HTTPS request.
- The hosting infrastructure receives and processes it.
- The server returns HTML, images, stylesheets, JavaScript and other resources.
- The browser assembles those resources into the page you see.
DNS is particularly important because the domain name and hosting account are not the same thing. ICANN describes DNS as the system that connects human-readable domain names with IP addresses, while web hosting provides the server resources from which a website can be delivered.
This also means you can change hosting without necessarily changing your domain name. The domain can remain registered with one company while the website is hosted somewhere else.
The main types of web hosting
There is no single hosting architecture that fits every website. The important question is how much infrastructure you need, how much control you require and how much server administration you want to handle yourself.
| Hosting type | How resources are provided | Typically suited to | Main trade-off |
|---|---|---|---|
| Shared hosting | Multiple websites share a hosting environment | Personal sites, blogs, small business websites | Lower cost and simpler management, but fewer resources and less isolation than higher-tier environments |
| VPS hosting | A virtual server provides more isolated and controllable resources | Growing sites, applications and users needing more control | More configuration and administration |
| Cloud hosting | Workloads run across cloud infrastructure with resources that can be provisioned or scaled | Resource-intensive or growing websites and applications | Greater flexibility can come with higher cost and complexity |
| Dedicated hosting | A physical server is allocated to one customer | Workloads requiring substantial control or dedicated infrastructure | Higher cost and greater responsibility |
| Managed hosting | The provider handles significant parts of server or application management | Users who want less infrastructure administration | Convenience often comes with restrictions or a higher price |
The boundaries are not always clean. “Cloud,” for example, describes an infrastructure model rather than a guarantee that a website will automatically scale without limits. “Managed hosting” describes how much operational work the provider takes responsibility for, not necessarily how powerful the underlying server is.
Shared hosting
Shared hosting places multiple websites within the same broader hosting environment.
The appeal is straightforward: the provider manages much of the infrastructure, while the cost is distributed across many customers. For a new blog, brochure website or small business site, this can be entirely adequate.
The important limitation is that resources are shared. The exact architecture varies by provider, so “shared” does not automatically mean poor performance. What matters is how the provider allocates CPU, memory, storage, processes and other resources, and how effectively the environment isolates accounts.
For many first websites, simplicity matters more than having access to a large amount of unused infrastructure.
VPS hosting
A virtual private server divides physical infrastructure into virtual machines or environments that provide greater isolation and control than conventional shared hosting.
A VPS can make sense when a website or application has outgrown basic hosting or requires software configuration that a shared environment does not permit.
The trade-off is administrative responsibility. Depending on whether the VPS is managed, you may need to handle operating-system updates, configuration, security hardening, backups and troubleshooting yourself.
A cheap VPS is therefore not automatically cheaper in practice if you have to spend substantial time administering it.
Cloud hosting
Cloud hosting uses cloud infrastructure rather than relying on the traditional idea of one website being tied to one physical server.
The practical advantage can be flexibility. Providers can offer configurable CPU, memory, storage and networking resources, while some architectures make it easier to scale or distribute workloads.
But “cloud” should not be interpreted as synonymous with unlimited performance. Every cloud plan still has defined resources, pricing and technical constraints.
For example, SiteGround currently describes its managed cloud offering as running on Google Cloud and offers configurations beginning at four CPU cores, 8 GB of memory and 40 GB of SSD storage, with higher configurations available.
Dedicated hosting
Dedicated hosting gives one customer an entire physical server rather than sharing the machine with unrelated websites.
That can provide greater control over hardware resources and configuration. It can also make sense where an organization has particular infrastructure, compliance or performance requirements.
The disadvantage is cost and responsibility. Paying for an entire server when a website uses only a fraction of its capacity is inefficient, and managing dedicated infrastructure requires more technical expertise unless the service is heavily managed.
Managed hosting
Managed hosting addresses a different question: who is responsible for operating the environment?
A managed service may handle tasks such as updates, monitoring, backups, security configuration or application-specific maintenance. The exact scope differs considerably between providers.
This can be valuable because server administration has an opportunity cost. A business owner or developer may prefer to spend time on the website rather than maintaining the underlying operating system.
Managed hosting does not eliminate the need for good security practices, however. Website owners still need to protect accounts, review access, keep applications current and maintain recovery plans.
What does hosting actually give you?
A hosting plan is more than disk space.
Depending on the service, it can include server resources, databases, email, SSL certificates, backups, caching, content delivery, security tools, migration assistance, technical support and management interfaces.
The challenge is determining which features materially affect your website.
Storage
Storage is the amount of server space available for website files, databases, email and other data, depending on the plan.
A text-heavy business website might use very little storage. A photography portfolio, video platform or large ecommerce catalogue can consume much more.
More storage is not automatically more useful. If your site uses 2 GB and your plan provides 100 GB, buying another plan because it offers 200 GB does not necessarily improve the website.
CPU and memory
CPU and memory become important when the server has to execute application code, generate pages dynamically, process database queries or handle many simultaneous requests.
This is why two plans with identical storage allowances can behave very differently.
A WordPress site with a small number of visitors may be perfectly comfortable with modest resources. A database-driven application with complex queries and many concurrent users can need substantially more CPU and memory.
Bandwidth and traffic
Bandwidth describes the amount of data that can be transferred over a period of time. It is different from storage.
A site with 10 GB of stored files can potentially transfer much more than 10 GB of data to visitors because those files may be downloaded repeatedly.
Conversely, a website with large video files can consume considerable bandwidth even if its total stored content is relatively modest.
When a provider advertises “unmetered” or “unlimited” traffic, read the terms and resource policies rather than interpreting the phrase as unlimited server capacity. SiteGround, for example, describes its current shared plans as having unlimited traffic while separately defining plan resource limits and approximate visit figures.
Databases
Dynamic websites commonly rely on databases to store information such as posts, products, accounts, orders and settings.
The relevant question is not simply how many databases a provider permits. It is whether the database technology, limits and available server resources are appropriate for the application.
A website that depends heavily on database queries can become constrained by CPU, memory, database configuration or application code long before it reaches a headline storage limit.
Performance: what actually makes a website fast?
Hosting performance is a system-level issue.
The physical or virtual resources matter, but so do server software, application code, database performance, caching, content delivery, image sizes and network distance.
A useful distinction is between server response time and the total time required to render a page.
A fast server cannot compensate indefinitely for a badly optimized website containing enormous images, inefficient JavaScript and unnecessary third-party services.
Server location
The physical location of infrastructure can influence network latency, particularly for visitors who are geographically distant from the server.
For an audience concentrated in one country or region, selecting an appropriate data-center location can therefore matter.
For a global audience, a content delivery network can help by serving cached resources from locations closer to visitors.
Caching
Caching stores reusable content so it does not have to be generated from scratch for every request.
For a content-heavy website, effective caching can reduce application and database work and improve response times.
Caching is not universally appropriate for every piece of content. Personalized account pages, shopping carts and frequently changing information may require different handling from a static blog post.
CDN
A content delivery network distributes or caches content across a network of locations.
This is particularly useful for static resources such as images, stylesheets and JavaScript files. It can reduce the physical distance between visitors and frequently requested content.
CDNs can also provide additional traffic-management and security capabilities, depending on the provider and configuration.
Security is part of hosting—but not all of security
A hosting company can provide important security controls, but hosting does not make a website secure by itself.
Useful capabilities can include:
- Automatic backups
- SSL/TLS certificates
- Malware detection
- Web application firewalls
- Account isolation
- Security monitoring
- Software updates
- Brute-force protection
- Access controls
The exact implementation matters more than the number of features listed on a sales page.
SSL/TLS, for example, protects data in transit between the browser and website when HTTPS is correctly configured. It does not automatically protect a compromised administrator account or vulnerable plugin.
Likewise, a backup is only genuinely useful if it can be restored successfully.
For important websites, understand how frequently backups are created, how long they are retained, where they are stored, whether restoration costs extra and whether you can create an additional independent backup.
Uptime: look beyond the percentage
Hosting companies often advertise uptime guarantees or targets.
A percentage can sound impressive without providing much practical information.
For example, 99.9% availability corresponds to roughly 8 hours and 46 minutes of downtime over a 365-day period if the entire allowance occurred continuously. Actual outages can be distributed across many incidents, and contractual uptime guarantees may define exclusions differently.
Therefore, ask:
- Is the figure a guarantee or a marketing target?
- What types of downtime are excluded?
- Are scheduled maintenance periods excluded?
- Are compensation mechanisms available?
- How is downtime measured?
- Does the guarantee apply to your particular hosting product?
Reliability also depends on your own website. A hosting provider can keep the server operational while a broken plugin, expired domain, bad DNS change or application error makes the website unavailable.
Managed WordPress hosting versus ordinary hosting
WordPress can run on many types of hosting, so “WordPress hosting” does not automatically describe a fundamentally different server architecture.
Managed WordPress services generally add application-specific tools and support.
These may include automatic WordPress updates, migration tools, performance plugins, staging environments, WordPress-specific security controls and specialized support.
SiteGround currently lists managed WordPress services such as free migrations, managed updates, a Speed Optimizer plugin, a Security Optimizer plugin and WP-CLI/SSH access on its WordPress plans. Higher tiers add features such as staging, on-demand backups and Git.
The important question is whether those services remove work that you would otherwise have to perform yourself.
If you are comfortable administering WordPress manually, some managed features may have limited value. If you are running a business website and want fewer infrastructure tasks, they may be more consequential.
Hosting price: the first-year number is not the whole cost
Hosting advertisements frequently emphasize introductory prices.
That can be useful for attracting new customers, but it is not the same as the long-term cost of ownership.
For example, SiteGround’s current shared hosting pages advertise introductory prices of $2.99 per month for StartUp, $4.99 for GrowBig and $7.99 for GoGeek when prepaid for 12 months, while displaying higher regular renewal prices.
Those figures also illustrate why the renewal price deserves attention. SiteGround’s current published pricing shows regular annual rates of $17.99, $29.99 and $44.99 per month respectively for those tiers.
The relevant calculation is therefore not simply:
“What does this hosting plan cost today?”
It is:
“What will this website cost over the period I realistically expect to operate it?”
Include:
- Renewal pricing
- Domain registration and renewal
- Premium themes or plugins
- Email services
- Backup services
- CDN or security services
- Migration costs
- Additional storage
- Premium support
- Taxes or regional charges
- Cancellation terms
SiteGround also states that its shared hosting plans are set to automatic annual renewal by default, although customers can change renewal settings.
For readers comparing current offers, the provider’s live pricing should take precedence over older articles or screenshots.
How to choose the right hosting
Start with the website rather than the hosting package.
For a personal website or portfolio
A basic shared plan is often sufficient.
Prioritize:
- Reliable availability
- SSL
- Backups
- Easy deployment
- Adequate storage
- Reasonable support
- A straightforward control panel
You generally do not need substantial dedicated resources for a small site that receives modest traffic.
For a small business website
Reliability and maintainability become more important.
A business site should have dependable backups, security controls, email arrangements, easy recovery and enough resources to handle normal traffic without constant intervention.
The cost of an outage can also be greater for a business than for a personal blog, so support quality and recovery procedures deserve more attention.
For an online store
Ecommerce sites introduce additional requirements.
You may need:
- More predictable application performance
- Reliable database resources
- Strong security practices
- Frequent backups
- Disaster recovery
- Payment-provider compatibility
- Monitoring
- Capacity for traffic spikes
The key metric is not how much storage the product catalogue consumes. It is whether the entire application remains responsive and reliable while customers browse, search, add products to carts and complete transactions.
For a high-traffic website
Traffic alone does not determine hosting requirements.
Two websites receiving the same number of visits can require radically different infrastructure depending on page complexity, caching, database activity, user sessions and traffic patterns.
Look at resource usage rather than visitor counts alone.
If the site consistently approaches CPU or memory limits, a larger or differently structured hosting environment may be appropriate. If the problem is inefficient code or database queries, upgrading the server may only conceal the underlying issue temporarily.
For developers and agencies
Control and workflow become more important.
Developers may care about:
- SSH access
- Git
- Staging environments
- Database access
- PHP or other runtime versions
- Automated deployment
- API access
- Multiple websites
- User permissions
- Site isolation
- Server configuration
Agencies may additionally need collaboration tools, client access and white-label capabilities.
SiteGround’s higher hosting tiers currently include features such as staging, Git, private DNS, collaborator access and white-label capabilities, although the exact availability depends on the plan.
Domain, DNS and hosting: three things people often confuse
A domain name is not hosting.
A useful mental model is:
Domain = address
DNS = routing instructions
Hosting = infrastructure
The domain identifies your website in a human-friendly way. DNS records tell internet systems where relevant services are located. Hosting provides the server environment that delivers the website.
These services can be purchased from the same company or from different companies.
Separating them can provide flexibility, but it also means you need to understand where DNS is managed and who controls the domain registration account. ICANN specifically distinguishes domain registration, DNS hosting and web hosting as separate functions, even though one provider may offer several of them.
What should you check before buying hosting?
Before committing to a plan, look beyond the promotional price.
Check the renewal price
Calculate the expected cost after the introductory period, not just the first invoice.
Check resource limits
Look for CPU, memory, storage, process limits and other restrictions that may affect your application.
Check backup and restoration policies
Determine how frequently backups run, how long they are retained and whether restoration is included.
Check migration support
If you already have a website, determine whether migration is included and what the provider actually transfers.
Check the support model
“24/7 support” can mean different things. Find out whether you receive live human assistance, ticket support, chat, phone support or primarily documentation.
Check the cancellation terms
Understand renewal, cancellation, refund and domain-registration rules before paying for a long period.
Check your market
Pricing, taxes, payment methods, data-center availability, domains, support and legal terms can vary by country or region.
Do not assume that a plan advertised in US dollars has identical availability or conditions everywhere.
When should you upgrade?
The right time to upgrade is usually determined by evidence rather than by a calendar.
Signs that a hosting environment may need more capacity include sustained resource exhaustion, consistently slow dynamic requests, database bottlenecks, repeated traffic-related failures or an application that has outgrown the configuration.
Before upgrading, identify the cause.
If the website is slow because oversized images consume bandwidth, more CPU may not solve the problem. If an inefficient database query consumes excessive resources, moving to a larger server may improve symptoms without fixing the underlying application.
A sensible progression is often:
Optimize → measure → identify the bottleneck → upgrade the relevant resource.
That approach can prevent unnecessary spending.
What matters more than the hosting company’s feature list?
A hosting plan can advertise dozens of features while only a handful matter to a particular website.
For most site owners, the durable questions are simpler:
Will the site have enough resources for its actual workload?
Can it be recovered quickly after a failure?
Is the infrastructure and application maintained securely?
Can the owner get useful support when something breaks?
What will the service cost after the promotional period?
Can the hosting environment grow with the website without forcing an unnecessarily complicated migration?
Those questions remain useful even as individual hosting technologies change.
The hosting decision that matters most in 2026
Web hosting is becoming less about buying a fixed amount of disk space and more about choosing an appropriate operating environment for a website or application.
Modern hosting can bundle CDN services, automated backups, security systems, application management, AI-assisted tools, staging, monitoring and increasingly sophisticated cloud infrastructure. Those additions can reduce the amount of technical work required from the site owner, but they also make plan comparisons more complicated.
The most useful approach is to work backwards from the website’s actual requirements. Estimate the workload, identify the applications that must run, determine the level of management you want, establish the recovery requirements and calculate the long-term cost. Then compare hosting environments on those dimensions rather than choosing the package with the largest collection of advertised features.
The hosting market will continue to change, but the fundamental test will remain remarkably stable: the right hosting service is the one whose resources, reliability, management model, security controls and long-term cost fit the website you actually need to operate—not the website a pricing page implies you might someday build.