The truth about 'unlimited' hosting

Every shared host advertises unlimited storage, unlimited bandwidth, unlimited inodes, unlimited everything. The word means almost nothing. Here is what the fair-use clause actually covers, what triggers the call from the host's abuse team, and how to read the small print before you sign.

The hosting industry settled on "unlimited" as a marketing term sometime in the early 2010s and has never let go. Every shared host of any size advertises unlimited storage, unlimited bandwidth, unlimited databases, unlimited email accounts. The customer reads "unlimited" and assumes it means what the word means. It does not.

"Unlimited" in the hosting industry means "we have not put a hard number on it, but we reserve the right to put a soft number on it the moment you become inconvenient." The fair-use clause that accompanies every unlimited plan is where the real limits live. They are real, they are enforced, and they bite people every day.

What the fair-use clause actually says

Read the terms of service of any unlimited shared host and you will find roughly the same set of restrictions, phrased slightly differently each time:

• You may not consume "excessive" CPU, memory or disk I/O.
• You may not run "applications not directly related to website hosting."
• You may not use the storage for "backup or archival purposes."
• You may not exceed an unspecified inode count or file count.
• You may not run database queries that the host deems too heavy.
• You may not run cron jobs more frequently than the host allows.

Each of these is the lever the host pulls when your account becomes operationally expensive. The word "excessive" is doing a lot of work. In practice it means whatever the host's abuse system decides it means, and the threshold is not stable.

The metrics that actually trigger the call

Three numbers come up over and over again when people report being asked to upgrade or leave an unlimited plan:

Inodes. Most shared hosts cap inodes at 250,000 or 500,000 per account, even on unlimited plans. An inode is roughly a file, plus some accounting for directories and metadata. Sites that store many small files (image caches, session files, WordPress with several caching plugins) hit this limit easily. The page only mentions "fair use" until you trip it.

CPU seconds. Shared hosts measure CPU time per account, often by the minute. A WordPress site that runs uncached PHP on every request consumes more CPU per page than a static site by orders of magnitude. Plans typically allow somewhere between 10 and 60 CPU seconds per second, after which requests get throttled or queued. The host does not advertise the number, but it is in the resource policy.

Database concurrent connections. Shared MySQL pools cap concurrent connections at numbers like 25 or 50 per account. A site that gets a small traffic spike and hits that ceiling will see "database error" messages, not "your plan does not include enough connections."

The accounts that get suspended

Shared hosting is a business model that depends on most accounts using a tiny fraction of the server's resources. The hosts subsidise the heavy users with the revenue from the light users. The moment a user becomes a heavy enough drain to threaten that subsidy, the abuse team is paged. The most common reasons for the call:

• The site is using more than its share of CPU time over a sustained period.
• The account is being used to store hundreds of gigabytes of files that are not visibly part of a website (zip archives, image galleries with no traffic, backup files).
• A cron job is running every minute and consuming meaningful CPU each time.
• An email account is sending bulk mail in numbers that look like a marketing operation.
• A WordPress plugin is misbehaving and hammering the database.

The host's response is usually a friendly email asking you to optimise the site or move to a VPS plan. Repeat offenders get the account suspended, sometimes without notice.

How to read the small print

Before signing up for any unlimited plan, look for these specific clauses:

• The inode cap or file count limit. If the number is not in the terms, the support team almost certainly has one they will quote when you call.
• The CPU policy. Look for words like "throttling," "fair share" or "resource policy."
• The backup-storage clause. Most unlimited plans explicitly forbid using the unlimited storage for backups, archives or any data that is not part of an actively served website.
• The cron-frequency limit. Many shared hosts cap cron jobs at no more often than every 15 minutes.
• The MySQL connection cap. The number is rarely on the marketing page but always in the resource policy.

When unlimited is genuinely fine

Shared hosting works for the use case it is sized for: a small to medium content site, well below ten thousand visitors a month, with a reasonable WordPress or static setup, no specialised heavy database workload. The "unlimited" marketing claims are functionally true at that scale because nobody is using enough resources for the host to notice.

The plans become a problem when the site outgrows the implicit limits. The transition is rarely smooth. The customer thinks they have unlimited resources; the host knows they do not; the abuse email arrives the week before a campaign launch. Knowing the limits in advance and planning the move to a VPS at the right time saves everyone the painful conversation.

The honest pitch the industry could make

The shared hosting category could be honest about what it sells: a small slice of a shared machine, sized for casual use, with quiet limits that work for most customers most of the time. That pitch would not test well in marketing focus groups, which is why we have "unlimited" instead. But the customers who get bitten by the limits are the ones who took the word at face value.

If you are picking a shared host, read the fair-use clause. If your site is going to be the kind that pushes the limits, get a VPS instead. The price difference between a serious shared plan and an entry-level VPS is small enough that the predictability of a VPS is worth the slight premium.