"Unlimited" Hosting, Explained
No hosting plan is unlimited. Here is why hosts use the word, where the caps hide, and how to find them before you buy.
No hosting plan is unlimited. Here is why hosts use the word, where the caps hide, and how to find them before you buy.
Shared, VPS, or cloud? How to pick the right hosting for a small site, what to evaluate, and the red flags experienced users warn about.
A deep, vendor-neutral checklist for evaluating any web host, with exactly how to test each criterion before you buy and the red flags to watch for.
Shared hosting vs VPS is a timing question. Here are the signs you have outgrown shared hosting, what changes on a VPS, and how to switch without downtime.
VPS, cloud, or dedicated? What each one is, what it costs in money and effort, and how to pick based on traffic, resilience, and budget.
Here is unlimited hosting explained in one line: no hosting plan is unlimited, and the word is a marketing choice, not a technical one. A plan that advertises unlimited storage and bandwidth almost always sits on top of hard caps you cannot see from the pricing page: how much CPU time you get, how much memory, how many files you can store, and how fast your disk can read and write. The acceptable-use policy, not the feature list, is the document that decides what you can really do. If you run a small, ordinary website, unlimited plans are often fine. If you push hard, the hidden caps are where you land first.
This article is a deep dive on the one word that confuses hosting buyers the most. For the broader buying decision, start with the pillar on which hosting type is best for small websites, and for the full evaluation framework see how to evaluate a web host. Below, we cover why "unlimited" exists, exactly where the limits hide, how to find them before you pay, and when the word is harmless anyway.
Hosts advertise "unlimited" because the economics let them, and because it sells. Most customer accounts use a tiny fraction of a server's capacity, so a provider can promise more than it physically has and bet that not everyone uses it at once. That bet is called overselling, and it works because the average site is small. The word reduces buyer anxiety: you stop doing math and just sign up.
Overselling is not a scandal, it is how the entire industry is priced. A host that genuinely reserved peak capacity for every customer would have to charge far more, and almost nobody would pay it. The practice is universal across providers. As one administrator put it on Hacker News, "there is no such thing as guaranteed performance in the cloud. Ever. Every provider oversubscribes ... they do not expect and cannot handle 100% utilization by their subscriber base" (Hacker News).
The honest reading of "unlimited" is this: unlimited up to the point where you would cost the host money. At that point, other rules quietly take over. The word describes the headline metrics (storage, bandwidth) and stays silent about the metrics that decide whether your site stays fast: compute, memory, file count, and disk speed.
A plain guide to cloud hosting: how your site runs across a pool of machines, how pooled resources and scaling work, and the honest pros and cons.
The caps live in the resources that are expensive to share, not the ones that are cheap to advertise. Storage and bandwidth are easy to oversell, so they get the "unlimited" label. CPU time, memory, disk operations, and file count are scarce and contended, so they get capped, usually in fine print rather than on the pricing page. A summary of those caps:
None of these are exotic. They are the normal levers every shared host pulls to keep one account from degrading the rest. The problem is not that they exist, it is that "unlimited" is printed in large type and the caps are not printed at all.
The acceptable-use policy (AUP) is the document that overrides the marketing, and it is where "unlimited" goes to die. It typically reserves the host's right to suspend or throttle any account that uses "excessive" resources, without defining "excessive" in numbers. That vagueness is the point: it lets the host advertise no limits while keeping the authority to enforce them whenever your usage becomes inconvenient.
Read the AUP and the terms of service before you read the feature list. Common clauses to expect:
This is the part that bites without warning. A site grows, its resource use climbs, and one day it gets throttled or suspended under a clause the owner never read. The plan did not change. The usage crossed an undocumented line. Keeping an independent, off-site backup matters here precisely because suspension can lock you out of your own data with no notice.
You find the limits by reading the boring documents and asking support direct questions, because the numbers are deliberately kept off the sales page. Treat "unlimited" as a prompt to investigate, not a feature. The caps almost always exist somewhere; your job is to surface them before you commit, not after your site is already on the platform.
Where to look:
If you cannot find the CPU, memory, and inode limits after all of that, treat the absence as the answer. A plan whose caps are unknowable is a plan you cannot size your site against.
For a small, ordinary website, an unlimited plan is often the right call, and you do not need to overthink it. The hidden caps are sized so that a normal brochure site, portfolio, or low-traffic blog never comes near them. The word "unlimited" is misleading, but the practical experience for a small site is usually fine. Overspending to escape a problem you do not have is the more common mistake.
Unlimited is fine when:
Unlimited bites when:
When you outgrow the hidden caps, the move is to a plan with stated, dedicated resources: a VPS or cloud plan where the limits are written down and reserved for you. Some providers, including the one I work on at Carpathian, publish flat resource limits up front rather than advertising "unlimited," which trades a smaller-sounding number for one you can plan against. That is a tradeoff, not a free win: a stated cap is only better if it is sized for what you need.
Run through this before you buy any plan that uses the word:
The useful way to read "unlimited" is as a claim about the cheap resources and a silence about the expensive ones. The plan is not lying about storage, it is leaving out compute, memory, file count, and disk speed, which are the things that decide whether your site stays fast. Find those numbers before you pay, size them against what your site does, and the word stops mattering. A limit you can see and plan around beats an "unlimited" you cannot.
