The limit on a resource sold as "unlimited" is not on the front of the contract but hidden in the fair use policy. The problem is not that the clause exists — every shared system must have a limit. The problem is learning where that limit sits only by hitting it.
Short answer: is unlimited hosting really unlimited?
No. On shared hosting plans, "unlimited disk" or "unlimited traffic" is bounded by the fair use policy in the contract; the real limits are usually technical quotas such as processor usage, concurrent processes and file count (inodes) rather than disk size. The approach is not misleading in itself — server resources are finite and shared. What matters to the customer is whether the contract states which limit applies at which threshold. If it does, you can plan; if it does not, surprises are inevitable.
The real limits behind "unlimited"
| Limit | What it measures | What happens when exceeded | Who it affects |
|---|---|---|---|
| CPU quota | Processing power used generating pages | Pages slow down, requests queue | Dynamic sites, e-commerce |
| Memory (RAM) limit | Memory used by concurrent processes | Process terminated, error page returned | Plugin-heavy installations |
| Concurrent processes | How many requests may run at once | Extra visitors are made to wait | Sites with traffic spikes |
| Inodes (file count) | Total files and folders in the account | No new files created, mail cannot be received | Image-heavy sites, old backups |
| I/O throughput | Read and write speed to disk | Page generation slows severely | Database-intensive applications |
| E-mail sending quota | Messages sent per hour or day | Sending stops; notifications never arrive | Sites sending order notifications |
Notice what is absent: disk space. The "unlimited disk" promise is usually accurate, because disk is not what stops you. The first limit reached is almost always the CPU quota or the inode count.
Which limit hits you first?
- Corporate brochure site: Usually approaches none of them. A shared plan serves this profile well for a long time.
- Blog / content site: As traffic grows, the CPU quota is stressed first. Caching pushes that limit back significantly.
- E-commerce: Concurrent processes and I/O throughput decide. On campaign days the limit is tested with a load far above ordinary levels.
- Image-heavy catalogue or gallery: The inode count fills silently. Thousands of small files can lock the account while disk space remains largely free.
- Systems sending newsletters or notifications: The e-mail quota is the first limit, and when exceeded, critical messages such as order confirmations stop too.
Rather than guessing where your own limit sits, you can measure it; we described the method in our capacity testing article.
Contract clauses to look for
- Is the fair use policy a separate document or part of the contract? If separate, read it — most limits are defined there.
- Are numerical thresholds stated? Look for concrete figures rather than phrases like "excessive use". Without figures, interpretation belongs to the provider.
- What happens when a limit is exceeded? A warning, throttling, or suspension? Those are three very different outcomes.
- Can you see your resource usage? Without current and historical usage graphs in the panel, you cannot know how close you are.
- Is the upgrade path defined? Which plan you move to, and on what terms, should be clear from the start.
- Are backups included in the quota? Whether backups count towards the inode limit is an important detail.
- Is there a service level commitment? Availability rates and remedy terms should be in writing.
Netişlem expert view: what matters is not the limit but its visibility
A significant share of the "why did my site slow down" questions we receive turn out to be plans hitting their limits. The customer does not know, because no warning appears in the panel and no figure appears in the contract. Our view is clear: having a limit is not the problem — every shared system does. Hiding it from the customer is.
Our second observation is that inodes produce the most surprises. An account can lock while disk usage sits at 20%, because thousands of small files, cache entries and old backups have filled the count. Regular cleanup is often more effective than upgrading the plan.
Third, the right question is not "is it unlimited" but "can I measure it". A business that can see its usage acts before hitting the ceiling: enabling caching, optimising images, or upgrading on a plan. A business that cannot must decide during a crisis.
Plan selection checklist
- Read the fair use policy and note the numerical thresholds.
- Confirm the panel provides resource usage graphs.
- Compare the inode limit with your current file count.
- Check the e-mail quota against your workflow (orders, forms, notifications).
- Learn the over-limit procedure: warning, throttling, suspension.
- Ask upfront about upgrade pricing and terms.
- Clarify whether backups count towards the quota.
- Request the service level commitment in writing — see SLA guarantee.
Frequently asked questions
Is the word "unlimited" misleading?
Not where the fair use policy is stated clearly and is accessible; it is established industry usage. The problem arises when no policy exists or when it contains no numerical thresholds. That document is where the decision should be made.
What do I do if my inode limit fills?
Clean up unnecessary files first: old backups, cache folders, unused plugin and theme files, undeleted mail archives. That usually suffices. If your setup permanently generates a high file count, upgrading is the answer.
How do I know I have hit the CPU quota?
The symptom is usually this: the site slows at particular hours while nothing is wrong with the server. If the panel shows CPU usage graphs, confirming it is easy. Caching and reducing heavy plugins are the first remedies.
When should I leave a shared plan?
When you regularly approach the limits and optimisation no longer helps. We detailed the signals in our VPS migration article.
Are there no limits on a VPS?
There are, but the difference is this: on a VPS resources are allocated to you and the limits are numerically defined. On a shared plan the limit is also affected by other users' behaviour. That difference in predictability is the most concrete reason to move.
Conclusion
"Unlimited" is a marketing term; the technical reality lives in the fair use policy. The right question is not "is it unlimited" but "where is the limit and how close am I". A business that can answer both makes its plan decision on schedule rather than in a crisis.
If you would like us to assess the real limits of your current plan, get in touch. You can review our corporate hosting and SLA guarantee pages.