What "Unlimited" Hosting Actually Limits
“Unlimited storage, unlimited bandwidth, unlimited domains” is standard language on shared hosting pricing pages, and it’s true in the narrowest technical sense while being genuinely misleading about what actually happens once a site grows. The real limits are inode counts, CPU throttling thresholds, and I/O caps, figures rarely mentioned on the pricing page but written into every provider’s acceptable use policy. Here’s what those limits actually mean, in real numbers, and how a normal, non-abusive website hits them.
Key takeaways
- Inode limits, not storage space, are what most WordPress sites actually hit first A typical shared hosting cap sits around 150,000-250,000 inodes; a fully built-out WordPress site with WooCommerce can consume roughly 50,000 of those on its own.
- CPU throttling kicks in around 100% of a single core, not when you 'use too much' vaguely Shared hosts commonly run CloudLinux with LVE (Lightweight Virtual Environment) to enforce this per-account, and exceeding it produces slow response or a 508 error, not a warning email first.
- The business model depends on most accounts staying well under their limits Providers routinely oversell shared servers 10-20x their real capacity on the assumption most sites stay quiet, which is also exactly why a suddenly successful site (a viral post, a sale) is the moment limits get hit.
What an Inode Actually Is, and Why It Matters More Than Storage Space
An inode is a filesystem record for a single file, every image, every plugin file, every cached page fragment, every email in your inbox counts as one, regardless of its size. That's the specific reason inode limits catch people off guard: your site can be using a small fraction of its advertised storage space in gigabytes while still being close to its inode ceiling, because the limit is counting files, not the bytes those files contain. A typical mid-range shared hosting plan caps inodes somewhere between 150,000 and 250,000; free hosting tiers are often far tighter, commonly around 30,000.
A real WordPress installation with a popular theme and a normal plugin set can consume 15,000-20,000 inodes before you've uploaded a single piece of content. Add a few years of blog posts with multiple image sizes (WordPress generates several resized versions of every uploaded image automatically), a caching plugin writing cache files, and a WooCommerce product catalog, and a genuinely modest small-business site can reach 50,000 inodes without anything resembling abuse, on a 200,000-inode plan, that's a meaningful chunk of your ceiling from one ordinary WordPress install, before you've added the addon domains many 'unlimited' plans also market.
Most cPanel-based hosting shows current inode usage under Statistics or a dedicated Resource Usage panel. Check it now, before a launch or a sale, not after you start seeing failed uploads or bounced email.
CPU Throttling: How It Actually Works, Not Just That It Exists
Most shared hosting in 2026 runs on CloudLinux, an operating system layer built specifically to isolate and enforce per-account resource limits through something called LVE (Lightweight Virtual Environment), effectively a container around your account that caps how much CPU, memory, and I/O it can consume regardless of what's happening on the rest of the physical server. CPU throttling commonly kicks in around 100% utilization of a single CPU core; I/O operations are commonly restricted to roughly 1024 IOPS. Cross either threshold and the practical result is your site becoming slow or unresponsive, sometimes returning an explicit '508 Resource Limit Reached' error, not a graceful degradation or an advance warning.
This isn't arbitrary punishment, it's the direct mechanism that makes shared hosting's business model work at all. Providers routinely oversell a physical server's real capacity by a factor of 10-20x, betting that the large majority of accounts on it will stay quiet most of the time. That bet is usually correct, which is exactly why the moment your traffic spikes, a successful marketing campaign, a product going viral, a Black Friday sale, is precisely the moment you're most likely to get throttled, since that's when your resource usage stops looking like the 'average' dormant account the pricing was built around.
What to Actually Check Before Choosing a Shared Plan
Real numbers to look for, not just the word "unlimited"
A transparent provider states an exact number; a provider that only says ‘unlimited’ with no figure is hiding the real constraint.
This tells you whether throttling is enforced predictably per-account or more loosely.
Some providers throttle gracefully and notify you; others suspend the account outright.
A full WordPress/WooCommerce build uses meaningfully more inodes than a handful of static HTML pages.
You will eventually need this if the site succeeds, so the upgrade path matters as much as the entry price.
Who Should Weight This Most Heavily
- Checking real inode/CPU numbers costs nothing and takes a few minutes per provider
- Understanding LVE/CloudLinux explains why throttling happens instead of it feeling random
- Knowing your own site’s inode usage lets you compare plans honestly against your actual needs
- Most pricing pages simply don’t publish these numbers prominently, if at all
- A growing WordPress/WooCommerce site can hit inode limits well before disk space becomes an issue
- Throttling commonly happens at the exact moment a site is succeeding, not failing
Comparing hosting providers directly
See our full hosting guide for shared, VPS, cloud and WordPress-specific hosting comparisons.
Our Sources
Where this comes from
The specific inode ranges, CPU threshold figures, and I/O cap numbers here are drawn from published 2026 technical explainers and hosting providers’ own acceptable use policies, cross-checked across multiple independent sources given how much specific numbers vary by provider and plan tier.
-
Technical resource-limit explainers reviewed
Multiple independent 2026 sources explaining inode, CPU and I/O limit mechanics on shared hosting, cross-checked for consistent figures.
-
Provider acceptable use policies referenced
Real published inode and CPU limit ranges checked against provider terms-of-service documentation, not just marketing pages.
-
No claims of our own load testing
This article explains published limit mechanics; it does not present our own live throttling tests against specific providers.
Frequently Asked Questions
Frequently asked questions
What's a typical inode limit on shared hosting?
Most mid-range shared hosting plans cap inodes somewhere between 150,000 and 250,000, while free hosting tiers are often much tighter, commonly around 30,000, always check the specific number for your plan rather than assuming.
Why does a small WordPress site use so many inodes?
Every file counts as one inode regardless of size, a normal WordPress install with a theme and plugins can use 15,000-20,000 inodes before any content is added, and WordPress automatically generates multiple resized versions of every uploaded image, adding up quickly.
What happens when I hit a CPU or I/O limit?
Commonly your site becomes slow or unresponsive, sometimes returning an explicit ‘508 Resource Limit Reached’ error, this typically happens automatically via the hosting platform’s resource-isolation system (often CloudLinux/LVE), not as a manual action after a warning.
Is 'unlimited bandwidth' actually unlimited?
Technically it usually means unmetered rather than truly unlimited, subject to a fair use policy that allows the provider to throttle or restrict an account whose usage negatively affects other customers on the same shared server, the threshold for that is rarely clearly published.
How do I check my current resource usage on shared hosting?
Most cPanel-based hosting accounts show current inode usage and other resource statistics under a Statistics or Resource Usage section, check this proactively, especially before a planned traffic increase, rather than discovering limits after something breaks.
Final take
- Inode limits (150,000-250,000 typical) are usually hit before raw storage space
- CPU/I/O throttling via CloudLinux LVE triggers around 100% of one core, ~1024 IOPS
- Success (a traffic spike) is exactly when throttling is most likely to hit
“Unlimited” hosting is technically accurate in the narrowest sense and genuinely misleading in practice, the real constraints are inode counts, CPU thresholds, and I/O caps that rarely appear on the pricing page but govern exactly when a growing site starts breaking. None of this makes shared hosting a bad choice; it makes checking the actual published numbers, and your own site’s real usage, worth the ten minutes it takes before you build something that outgrows its plan at the worst possible moment.
