"Unlimited" Hosting, Explained

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.

Why do hosts advertise "unlimited" at all?

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.

Where do the hidden limits hide?

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:

• CPU time and process limits. Shared plans cap how many seconds of processor time your scripts can use and how many processes you can run at once. A long-running task gets killed mid-execution. This is why a background worker, a video encode, or a heavy import that runs fine on your laptop fails silently on shared hosting.
• RAM (memory). Your account gets a memory ceiling, often modest. A traffic spike, a memory-hungry plugin, or a large database query trips it, and the host kills the offending process rather than letting it slow down its neighbors.
• Disk IO and IOPS. "Unlimited storage" says nothing about how fast you can read and write that storage. Hosts cap your input/output operations per second (IOPS) so one busy account cannot starve the disk for everyone. A database-heavy site can feel slow even when the page itself is small.
• Inodes (the file count). An inode is the filesystem's record for a single file or folder, so the inode limit is a cap on how many files you can store, regardless of their size. A WordPress install with many plugins, a big email account, or a cache folder full of tiny files can hit the inode cap long before it fills the "unlimited" disk. As one Hacker News commenter summarized the whole pattern, unlimited "claims are false because of other rules around inode limits and cpu limits" (Hacker News).
• "Unlimited bandwidth" with throttling. Transfer may be uncapped in total, but your connection speed, concurrent connections, or requests per second are not. A plan can offer unlimited bandwidth and still throttle you the moment you use a lot of it.

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.

What does the acceptable-use policy really limit?

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:

• A ban on using "unlimited" storage for anything other than your website's normal operation. Backups, media libraries, and file archives are frequently called out as prohibited, which means the unlimited disk is not a personal storage drive.
• A reservation of the right to limit CPU, memory, processes, or IO for accounts deemed to affect "server stability" or "other customers."
• A clause allowing suspension for "abuse" or "resource overuse," often with little or no notice. The same fine print that promised unlimited gives the host the power to cut you off for using it.

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.

How do you find the true limits before you buy?

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:

1. Read the terms of service and the acceptable-use policy, not the pricing page. Search those documents for "CPU," "inode," "process," "memory," "IO," "concurrent," and "excessive." The caps usually appear there, or are referenced as a separate resource-usage policy.
2. Find the knowledge-base article on resource limits. Many hosts publish the per-plan caps in their help docs, away from marketing. Search the host's name plus "inode limit" or "CPU limit."
3. Ask support in writing, before you pay. Send specific questions and keep the answers. Good ones to ask: What is the inode limit on this plan? What is the per-process CPU and memory cap? Do you throttle or kill long-running processes, and after how many seconds? Is there a concurrent-connection or entry-process limit? Can I store backups or media archives on the unlimited disk, or is that against the AUP?
4. Watch how support answers. A host that gives you the numbers plainly is telling you it competes on being good. A host that dodges, deflects, or insists "it's unlimited, don't worry" is telling you the limits exist and it would rather you not see them. That evasiveness is itself a result.

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.

When is "unlimited" fine anyway, and when does it bite?

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:

• Your site is a standard small website with modest traffic. Communities broadly agree that low-traffic sites, under roughly 100,000 unique visitors a month, run comfortably on shared hosting (Hacker News).
• You are running ordinary web software (a CMS, a small store, a few plugins) and not background jobs, heavy media processing, or large file storage.
• You keep your own off-site backups and do not rely on the host's disk as your archive.

Unlimited bites when:

• You run long processes or background workers. Shared plans kill them, and no amount of "unlimited" storage changes that.
• You store many small files. The inode cap, not the disk size, is what you hit first.
• Your traffic is spiky or growing fast. The CPU, memory, and IO caps decide your ceiling, and you can hit a wall the pricing page never mentioned.
• You treat the unlimited disk as cloud storage for backups or media. That use is usually against the AUP and is a common trigger for suspension.

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.

A checklist for reading past "unlimited"

Run through this before you buy any plan that uses the word:

1. Find the inode (file count) limit. If it is not documented, ask support in writing.
2. Find the per-process CPU and memory caps, and whether long-running processes get killed.
3. Find the disk IO or IOPS limit, not just the storage size.
4. Read the acceptable-use policy for the "excessive use," "resource abuse," and suspension clauses.
5. Confirm whether storing backups or media archives on the disk is allowed or prohibited.
6. Ask whether "unlimited bandwidth" comes with connection or request-rate throttling.
7. Note whether support answers plainly or dodges. Evasiveness is a result in itself.
8. Set up your own off-site backups regardless, since suspension can lock you out without notice.

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.