Blog · Plain Truth

The truth about “unlimited” web hosting

By the HostingAlly team Published 27 July 2026 6 min read

An unlimited server does not exist. Disk platters come in sizes. Processors come with a fixed number of cores, and network ports run at a stated speed. So when a plan advertises "unlimited websites, unlimited storage, unlimited bandwidth," what has happened is that the caps got shifted somewhere the comparison table never looks, usually deep in the terms of service, and counted in units most buyers have never met.

None of this makes unlimited plans a scam. Plenty of sites sit on one for years without trouble. The point is to know where the actual ceilings sit, since the moment you collide with a limit nobody mentioned is always the worst possible moment to find out.

The four limits hiding inside “unlimited”

Inodes: each file and each folder sitting on your account counts as one, and 'unlimited storage' plans usually stop accounts somewhere between 100,000-500,000 of them. Run WordPress for a few years, with image uploads, cache files and mail piling up, and you reach six figures without noticing. Hit the cap and uploads fail, mail bounces, backups stop dead. Our glossary entry on inodes shows you how to check your own count.

CPU seconds and entry processes: a shared plan meters the processor time your account consumes and caps how many PHP processes may run concurrently, often at just 20-40. Then traffic spikes, the welcome sort, the kind that follows something going viral, and that is precisely when the entry-process ceiling introduces itself, with visitors stacking up behind 508 errors.

Bandwidth 'fair use': every unlimited transfer clause keeps the right to throttle or suspend any account drawing 'more than typical' resources. Who decides what counts as typical? The host does, never you, and the bar moves.

File-type and workload clauses: read most unlimited terms closely and you'll find backups banned, media libraries banned, file distribution banned. Which is to say, banned for precisely the jobs a truly unlimited disk would be good at.

Why honest plans print numbers instead

Print "20 GB NVMe, 1 TB bandwidth, 50 databases" on a plan and you have a promise somebody can be held to, plus a host forced into honest capacity planning. Print "unlimited everything" and the real conversation gets postponed until you're already moved in and raising a support ticket. So the stated figure usually wins, even where it looks like the meaner offer, because it was written with the intention of keeping it.

Our plans work that way: a storage figure, a bandwidth figure, a database count, all stated, all renewing at the same price you started on. Outgrow those numbers and you upgrade in place. No fair-use email lands in your inbox.

Shopping around? Treat any 'unlimited' claim as an instruction to open the terms page. Then search that page for 'inode', 'fair use', 'CPU' and 'entry process'. Five minutes spent there will teach you more than the entire pricing page does.

Estimating what you actually need

Site owners wildly overestimate what they need, and unlimited marketing eats well on that. Here are real figures from ordinary small sites. A 30-page business site with a modest gallery sits on 1-3 GB of disk and pushes under 20 GB of monthly transfer. A busy blog carrying five years of posts might reach 5-10 GB. A small WooCommerce store with 500 products lands at 5-15 GB, and rarely crosses 100 GB of transfer. Set against that, a printed 20 GB plan isn't a compromise at all. It's headroom.

On shared hosting the one truly scarce thing is CPU under load, so what sits underneath matters far more than the disk figure. NVMe storage paired with LiteSpeed caching drops the processor cost of a single page view to a fraction of what an older stack would spend, which means an identical 'limit' stretches several times further.

Quick answers

Is unlimited web hosting actually unlimited?

No. Real servers run out of disk, processor and network like everything else. What unlimited plans do is relocate the limits into inode caps, CPU-second meters, entry-process ceilings and fair-use clauses buried in the terms of service. Still limits. Just harder to see.

So what is an inode limit, and why should it matter?

One inode covers one file, one folder, or one email on your account. Plans selling unlimited storage generally cap inodes at 100k-500k, and a busy WordPress install gets there sooner than owners expect. Once you're at the cap, uploads break and mail stops arriving, however much 'unlimited' disk is supposedly still free.