"Unlimited" hosting: what it really means, in the fine print

What "unlimited" actually means

The marketing phrase "unlimited disk space" or "unlimited bandwidth" assumes a specific reading: the host does not apply a per-customer cap on that resource. The TOS adds a modifier: "as long as you use it reasonably for normal website purposes."

"Normal website purposes" is then defined in the Acceptable Use Policy as:

• Not using the host as general-purpose cloud storage
• Not backing up non-website data
• Not running "resource-intensive" applications
• Not sending bulk mail

None of those are technical. They are discretionary judgments the host makes case-by-case. "Unlimited" becomes "unlimited until we say otherwise."

The WHT thread on Bluehost's unlimited TOS and the older HN discussion both center on the same structural issue: the word "unlimited" is technically a fiction.

The inode ceiling

An "inode" is a filesystem data structure — one inode per file or directory. Every file you upload, every email in your inbox, every cached PHP file, every WordPress plugin file counts against your inode count.

Typical inode limits on "unlimited" shared hosting:

Hitting the inode limit triggers "we cannot create more files" errors in cPanel, WordPress upload failures, and (commonly) a forced-upgrade email citing "excessive file count."

A WordPress site with 20 plugins and a typical caching setup uses ~50,000 inodes. Add email storage with 10,000 messages across mailboxes (each message = 1 inode) and you are at 60,000. Add nightly incremental backups retained for 30 days, and you are at 200,000+. The cap is hit faster than customers expect.

CPU, memory, and entry-process caps

The second layer of "unlimited" limits — documented on some hosts, cited verbally on others:

• CPU time per second — 10% of a shared core is typical. A slow WordPress query can exceed this for seconds at a time and trigger throttling.
• Physical memory per process — 512MB–1GB. PHP requests exceeding this get a white-screen 500.
• Entry processes — concurrent HTTP requests per account. Bluehost cap is typically 20. Exceed during a traffic spike → connection-refused errors.
• IOps (disk operations per second) — 1024 IOps is typical. WordPress with heavy disk-logging plugins exceeds this quickly.
• MySQL connections — 15–25 concurrent typically.

None of these are in the marketing copy. All are enforced by CloudLinux LVE resource limits or equivalent on the server side.

Real limits by host

Composite published-or-leaked limits on budget shared plans, 2026:

What honest limit disclosure looks like

Cloudways, Kinsta, and LaunchPad Host do not advertise "unlimited" anything. We publish:

• Disk space in GB
• Inode count explicitly
• CPU and RAM LVE limits
• Entry process count
• Database count (often just "unlimited" with a note that real-world databases max out around 500 before MySQL itself becomes unhappy)
• Monthly bandwidth in GB (with fair-use defined as per-hour throughput)

The tradeoff: the headline number looks less generous than "unlimited." The compensation: you know, before signing up, exactly what you get. No surprise suspension emails because you exceeded a limit that was never stated.