What Do Hosting Plan Specs Mean?

How to read a hosting plan

Two hosting plans. Similar prices. One lists “10GB NVMe SSD storage” and the other offers “unlimited storage and bandwidth.” Neither tells you how your site will actually perform, how many visitors it can handle, or whether you’ll hit a wall six months in.

In this article
  1. Storage: How Much You Need (and What Type Matters)
  2. Bandwidth: The Spec That Catches People Out
  3. Uptime Guarantees: What the Percentage Means in Real Time
  4. RAM and CPU: When These Numbers Matter to You
  5. The Hidden Specs: Inodes, PHP Workers, and Backup Terms
  6. Specs That Hosts Leave Off the Page
  7. Questions About Hosting Specs

Hosting plans are full of numbers and terms that look informative but rarely explain themselves. This guide breaks down what each spec actually means, which ones matter for your situation, and a few that hosts quietly leave off the page altogether.

Storage: How Much You Need (and What Type Matters)

Storage is the space your site’s files occupy on the server. That includes your pages, images, videos, databases, email, theme files, and any backups stored on the same account. For most small to medium sites, the raw amount of storage is rarely the limiting factor. A typical business website or blog sits comfortably under 2GB. Where storage becomes important is the type.

Most hosts now advertise SSD storage as standard. SSDs are significantly faster than the older spinning hard drives (HDDs) that budget hosts still quietly use on some plans. A step up from SSD is NVMe storage, which uses a faster connection between the drive and the server’s processor. The practical difference: pages load faster, your database responds quicker, and the site handles traffic spikes better. If two plans are otherwise identical and one specifies NVMe, it’s the better pick.

When a plan advertises “unlimited storage,” treat that with some scepticism. There’s always a practical ceiling, and it’s usually enforced through other limits rather than a hard storage cap. More on that in the hidden specs section below.

Bandwidth: The Spec That Catches People Out

Bandwidth is the amount of data transferred between your server and your visitors each month. Every page view, image load, file download, and form submission uses a slice of it. A simple page might transfer 1–2MB per visit. A site with large images or downloadable files will use considerably more.

For most new or small sites, bandwidth isn’t something you’ll think about. The average blog or business website uses well under 5GB per month. Problems tend to arrive when traffic spikes: a product launch, a post that gets shared widely, a mention in the press. Or when your site grows faster than expected.

“Unlimited bandwidth” is one of the most common claims in shared hosting. The honest answer is that it’s never truly unlimited. Hosts set boundaries through acceptable use policies and CPU resource caps rather than a hard bandwidth number. If your site consistently pushes a lot of traffic, you may find yourself being asked to upgrade regardless of what the plan says.

Uptime Guarantees: What the Percentage Means in Real Time

Uptime is the percentage of time your site is online and accessible. It sounds like a single number, but the difference between 99.9% and 99.99% is significant in practice.

Uptime % Downtime per month Downtime per year
99.9% ~43 minutes ~8.7 hours
99.95% ~22 minutes ~4.4 hours
99.99% ~4 minutes ~52 minutes
99.5% ~3.6 hours ~43 hours

The guarantee itself is worth scrutinising. Most hosts back their uptime promise with a service level agreement (SLA), but the compensation offered when they fall short is usually account credits that rarely reflect the actual cost of downtime to your business. The guarantee is a signal of confidence, not a safety net.

What matters more than the headline number is consistent real-world performance. Check independent monitoring data when you can, and read recent reviews that reference actual downtime incidents. Our uptime explained guide goes deeper on what the guarantee does and doesn’t cover.

RAM and CPU: When These Numbers Matter to You

On shared hosting plans, RAM and CPU are rarely listed as fixed allocations. You’re sharing a server with other sites, and the host manages resource distribution. That’s fine for most small sites, but it means your performance can be affected by what your neighbours on that server are doing.

RAM and CPU become explicit and important when you move to a VPS or cloud plan. At that point, you’re getting a guaranteed slice of the server’s resources. A VPS with 2GB RAM and 2 CPU cores has those resources reserved for you alone.

For reference: a standard business website or blog needs very little. A site running a large product catalogue, membership features, or heavy custom functionality needs more. The key question isn’t “is this enough RAM?” It’s “does this plan give me dedicated resources or shared ones?” Shared resources on a well-managed server can outperform poorly allocated dedicated resources, so the hosting provider’s infrastructure matters as much as the numbers on the page.

The Hidden Specs: Inodes, PHP Workers, and Backup Terms

These are the specs that cause the most frustration. They rarely appear in plan headlines and only become visible in the fine print, or when you’ve already hit a wall.

Inodes are the total number of files and folders your hosting account can hold, counted individually. Every image, script, theme file, database entry, and email message uses one. Shared hosting plans commonly cap this at 100,000 to 250,000 inodes. That sounds like a lot, but a standard site with a few months of backups, a sizeable plugin library, and email stored on the server can get there faster than expected. When you hit the limit, you can’t add new files, even if you have storage space remaining.

PHP workers control how many requests your site can process at the same time. On a shared plan, this is typically set between 2 and 6. If more simultaneous visitors than that try to load your site at once, the extra requests queue up and wait. For low-traffic sites this is invisible. For sites that get bursts of traffic, it’s the reason pages suddenly slow to a crawl even though the rest of the spec sheet looks fine.

Backup terms are another area where the headline rarely matches reality. “Free daily backups” can mean the host keeps one day of backups or thirty. It might mean you can restore with one click, or it might mean you need to raise a support ticket and wait. Check how many restore points are kept, how long they’re retained, and whether restores are free or charged per incident.

Specs That Hosts Leave Off the Page

Some of the most useful information about a hosting plan doesn’t appear in the comparison table at all. Before committing, it’s worth digging into these directly.

  • PHP version support. Older PHP versions have known security vulnerabilities and run slower. Check that the host supports current PHP versions and lets you switch between them.
  • Number of websites allowed. Some entry-level plans restrict you to a single site. If you might add a second site later, confirm this before you’re locked in.
  • Email hosting. Not all hosting plans include email accounts. Some charge separately or route you to a third-party service. If you need professional email, confirm it’s included.
  • Server location. Where the server is physically located affects how fast your site loads for visitors in that region. If your audience is primarily in one country or region, choose a host with a data centre close to them.
  • Resource throttling policy. What happens when you exceed CPU or bandwidth limits? Some hosts throttle your site silently. Others send a warning. A small number suspend accounts without notice. The acceptable use policy usually covers this, but it’s rarely easy reading.

A host that publishes this information clearly is usually a better bet than one that doesn’t. InMotion Hosting is a good example of a provider that surfaces resource allocation and backup terms prominently rather than burying them in small print. Worth using as a benchmark when comparing plans.

Questions About Hosting Specs

How much storage does a typical website need?

Most small to medium websites use under 2GB of storage. A business site, portfolio, or blog with standard images and a reasonable number of pages sits well within that. Storage becomes a consideration if you’re hosting large video files, running a large product catalogue, or storing email and backups on the same account. For most sites starting out, the storage type matters more than the raw amount.

Is unlimited bandwidth really unlimited?

Not quite. Hosts that advertise unlimited bandwidth apply limits through other means: CPU usage caps, acceptable use policies, or resource throttling. If your site consistently drives very high traffic, you may be asked to upgrade regardless of what the plan says. For the vast majority of small sites, bandwidth won’t be an issue. The caveat matters most if you’re expecting sudden or sustained traffic spikes.

What uptime guarantee should I look for?

99.9% is the minimum to accept from any paid host. That’s roughly 43 minutes of potential downtime per month. Many reputable hosts now offer 99.99%, which brings monthly downtime under five minutes. The guarantee matters less than the host’s actual track record, so look for reviews and monitoring data alongside the headline number.

What is NVMe storage and does it affect speed?

NVMe is a type of solid-state storage that connects directly to the server’s processor via a faster interface than standard SSD. In practice, it means faster file access, quicker database responses, and better handling of traffic spikes. If two plans are otherwise comparable and one specifies NVMe, it will generally perform better.

What specs should I check that aren’t always listed?

PHP version support, inode limits, PHP worker count, server location, email hosting inclusion, and the host’s throttling or suspension policy are all worth checking before you commit. These rarely appear in headline comparisons and are often buried in support documentation or acceptable use policies. If you can’t find them, ask support before signing up.