SASami A. · Oct 28, 2026 · 8 min read

When a host says "unlimited," treat it as "limited, with the limit written somewhere else."

Shared hosting plans have advertised “unlimited” storage, bandwidth, email accounts and sites for years. It is one of the most successful words in the industry, and it is a promise that nobody can keep. Disks are finite. Network links are finite. A server has a fixed number of CPU cores shared by every account on it.

This essay argues a simple position: when a host says “unlimited,” treat it as “limited, with the limit written somewhere else.” That is not an accusation of fraud. Most hosts are not lying in a legal sense, because the real limits are in the terms of service. The problem is that the headline and the contract describe two different products, and the headline is the one you buy on.

Why unlimited cannot be literal

A physical server has a set amount of storage, memory, processor time and network capacity. Hosting companies sell that capacity to many customers at once, counting on the fact that most sites use a tiny part of what they are nominally allowed. That is a reasonable business. It is the reason shared hosting is cheap.

But a business that depends on most customers using very little cannot promise every customer unlimited use. If a handful of accounts really did consume without limit, the other accounts on the server would suffer. So the host needs a mechanism to prevent that, and the mechanism is a policy that sets practical limits without printing them in large type.

The word “unlimited” therefore carries an unwritten asterisk. The honest version would be “no fixed cap on this particular number, within what we consider normal use of a site like yours.” That is a different sentence, and it is hard to put on a pricing card.

Where the real limits hide

If storage and bandwidth are “unlimited,” the limits move to places the pricing page does not emphasize. These are the common ones.

  • Inodes. An inode is a record the file system keeps for each file or folder. A site with a lot of small files, such as cache files, image thumbnails or email, can hit an inode ceiling long before it fills the disk.
  • CPU and memory. Many shared plans restrict how much processor time or RAM an account can use at once. A busy site, or a slow plugin, can reach that ceiling and see slowdowns or errors.
  • Concurrent processes. Dynamic pages need PHP workers. When there are more simultaneous requests than workers, visitors wait or get an error page.
  • Disk activity. Some hosts limit read and write speed, which affects backups, imports and large uploads.
  • File types. Acceptable use policies often restrict hosting large archives, backups or media files, even where storage is called unlimited.
  • Fair use. A catch-all clause that lets the host judge whether your usage is reasonable.

Not every host applies every limit, and the details differ by provider and plan. That is exactly the point: the limits exist, they vary, and you have to read for them.

A concrete example from a host’s own help page

You do not have to take this on trust, because some hosts document it. HostGator’s help article on inode limits says it enforces a limit of 100k/250k inodes on its shared accounts, and that exceeding the threshold set out in its terms of service violates its Acceptable Use Policy and may get the account flagged for review or suspended. For dedicated servers, the same page says no specific inode limit is enforced, and warns that an excessive number of inodes hurts performance.

The page does not explain what the two numbers mean, and it does not argue that the plan is unlimited. But it shows the pattern clearly. There is a number. There is a consequence. And the number appears in a help article, not on the front of the plan card. Other hosts publish similar limits in their own documentation under different names. Check the one you use, because the figures change and a blog post, including this one, is not the source of truth.

Why the practice persists

If “unlimited” misleads, why does it survive? Because it works commercially, and because it works for most customers.

Most sites are small. A brochure site, a small blog or a local business page uses a tiny part of any reasonable allocation. For those customers the word “unlimited” is, in practice, harmless: they will never meet the limit. The host gets a strong marketing line, and the customer gets a working site.

The trouble falls on the minority who grow. Sites that gain traffic, add an online store, run a membership plugin or accumulate years of media will eventually meet a limit. They meet it at the worst time: a sale, a mention in the press, a busy season. Then the host cites the fair-use clause, and the customer discovers that “unlimited” was the introductory price of a relationship they did not fully read.

The strongest defence of the word

There is a fair argument on the other side, and it deserves a hearing. Hosts say that publishing hard numbers invites customers to push right up to them, and that “unlimited” with a fair-use policy is easier to understand than a table of inodes and CPU seconds. Most site owners do not know what an inode is. A plain promise that you can host a normal website without watching a meter is, to them, a useful promise.

That argument has merit. A host that said “up to 250,000 files” would be giving customers a number that most of them cannot interpret. And a fair-use policy is a reasonable way to handle abuse: someone using a shared account as a file archive or a video host is imposing costs on others.

But the defence proves less than it seems. It justifies a policy against abuse. It does not justify a headline that implies no limits exist. The honest alternative is easy to write: “Designed for typical websites. Heavy use may need a different plan.” That is still readable, and it does not require anyone to learn what an inode is.

What this means for a WordPress site

WordPress sites have a particular exposure here because they are dynamic. Every uncached page view runs PHP and queries a database. That makes CPU, memory and process limits the ones that matter most, far more than disk space. An ordinary blog is fine. A WooCommerce store, a membership site or a site with heavy search and filtering is a different matter, and those are exactly the sites that tend to outgrow a shared plan.

Files matter too. Backup plugins, image optimizers and caching plugins can each create large numbers of files. If your host limits inodes, a plugin you installed to make the site faster can push you toward the limit. Our speed optimization guide covers how caching fits in, and where it does and does not reduce server load.

So the useful question for a WordPress owner is not “how much storage do I get?” It is “what happens when my site gets busy, and who tells me before it does?”

How to read a hosting plan honestly

You can protect yourself without being an expert. Here is a short routine to follow before buying, and to repeat when you outgrow a plan.

  1. Find the acceptable use policy and the terms of service. Search the text for “inode,” “CPU,” “process,” “fair use,” and “unlimited.” Note every number you find.
  2. Look for numbers on the plan page itself. A host that lists PHP workers, RAM and CPU for each plan is giving you something you can compare. A host that lists only “unlimited” is not.
  3. Ask what happens at the limit. Does the site slow down, get throttled, go offline, or does the host contact you first? Ask support directly and keep the reply.
  4. Check the renewal price. Introductory rates and renewal rates can differ, and a plan that looks cheap for the first term may not be the plan you are actually comparing.
  5. Check the backup and restore terms. Find out whether backups are included, how long they are kept, and whether restoring one costs extra. Our guide to backup plugins explains why you should keep your own copies off the server regardless.
  6. Match the plan to the site. Pick the plan by the kind of site you run, not by the biggest number on the page. Our guide to hosting by use case sorts the options that way.

When “limited” is actually better

There is a counterintuitive point here. Plans that state their limits are often easier to live with than plans that hide them. If a managed WordPress host says you get a certain number of visits per month or a set number of PHP workers, you can plan around it. You can watch your usage, see the limit approaching and decide when to upgrade.

A plan that states no limit gives you nothing to plan around. You learn where the line is only after crossing it. Our comparison of managed and VPS hosting looks at the other end of the scale, where you rent defined resources and manage them yourself, and the capacity you pay for is the capacity you get. That is more work, but it is also more honest about what a server is.

A host you can predict is worth more than a host that sounds generous. If you are already considering a move, our migration guide walks through doing it without losing data or search rankings.

What should change

The fix is not complicated. Hosts could publish the main limits on the plan page: inodes, CPU or process counts, and what happens when an account hits them. Regulators in several countries already require advertising to be accurate and not misleading, and “unlimited” is exactly the type of claim that advertising rules treat with caution. We will not claim here that any specific host has broken a specific rule, because that is a legal question and depends on the jurisdiction and the wording.

What a customer can reasonably expect is that the claim on the front matches the terms in the back. When it does not, the customer should be able to see that without reading a contract. Until that happens, the reading falls to you.

Conclusion

“Unlimited hosting” is a promise nobody can keep, because hardware is finite and shared. For a small site it usually costs you nothing, and that is why it survives. For a growing site it can become an unpleasant surprise at the moment you can least afford one.

So read the policy, find the numbers, and ask what happens at the limit. Choose a plan by the kind of site you run and by how predictable the host is, not by the biggest word on the pricing card. And whichever host you pick, keep your own backups somewhere else. If you want a host that tells you where the ceiling is, that is a sign of a better provider, not a worse one.

← All opinion

SponsoredNibWP

Stop clicking. Start telling.

Ask your AI to build pages, fix speed and nail SEO, and NibWP does it on your WordPress site in minutes.

Try NibWP.com

Get the WPMusk Sunday brief

One email a week with our newest tutorials, honest tool reviews and resources you won’t find on the blog. No spam, unsubscribe in one click.

Newsletter (Sunday brief)