Skip to main content
.com domains from $2.99 — free WHOIS privacy on every name

Blog · Plain Truth

“Unlimited” web hosting: where the ceilings actually hide

By the HostingFast team Published 27 July 2026 6 min read

Servers are physical objects. A disk stores a fixed number of bytes, a CPU carries a fixed number of cores, and a network port moves data at a fixed rate. When a plan promises "unlimited websites, unlimited storage, unlimited bandwidth", the ceilings have not vanished. They have been moved outside the comparison table and re-denominated in units most buyers have never encountered.

None of this means unlimited plans are a con. Plenty of sites run on them contentedly for years. It means you should map the ceilings before you move in, because colliding with one you never knew existed has a habit of happening on your biggest traffic day.

The four limits buried in the word unlimited

Inodes. Each file, folder and email on the account counts as one, and "unlimited storage" plans usually cap accounts somewhere between 100,000 and 500,000 of them. A WordPress install carrying a few years of uploads, cache files and mailboxes crosses into six figures without warning. Once you hit the cap, uploads fail, mail bounces, backups stall. Our glossary entry on inodes explains how to check where you stand.

CPU seconds and entry processes. Shared plans meter how much processor time your account consumes and limit how many PHP processes may run at once, commonly to 20 to 40. You tend to learn that ceiling exists the day a post takes off and visitors start stacking up behind 508 errors.

Bandwidth fair use. Behind "unlimited transfer" sits a clause letting the host throttle or suspend any account consuming "more than typical" resources. Typical is defined by the host, and the host is free to redefine it.

Workload and file-type restrictions. Most unlimited terms quietly ban using the space for backups, media libraries or file distribution, which are precisely the jobs a genuinely bottomless disk would be good for.

A number in print beats a promise of infinity

"20 GB NVMe, 1 TB bandwidth, 50 databases" is a commitment you can measure a host against, and it obliges the host to plan capacity honestly. "Unlimited everything" defers that conversation until you have already migrated in and opened a ticket. Even when the printed figure reads smaller, it is nearly always the better deal, because it was published with the intention of being honoured.

That is the design behind our plans: a declared storage allowance, a declared transfer allowance, a declared database count, all renewing at the rate you started on. Outgrow the figures and the answer is an upgrade you click, not an email about fair use.

A habit worth keeping: treat every "unlimited" badge as a signpost to the terms page. Search that page for inode, fair use, CPU and entry process. Those five minutes reveal more than the entire pricing grid.

Measure what your site really consumes

Site owners habitually guess high, and unlimited marketing is built to feed that instinct. Real numbers from ordinary sites: a 30-page business site with a modest gallery uses 1-3 GB of disk and under 20 GB of monthly transfer. A blog with five busy years of archives might reach 5-10 GB. A small WooCommerce store with 500 products runs 5-15 GB and rarely clears 100 GB of transfer. Against those figures, a stated 20 GB plan is not a squeeze. It is headroom.

The one resource that genuinely runs scarce on shared hosting is processor time under load, which makes the stack beneath you matter far more than the disk quota. NVMe storage and LiteSpeed caching shrink the CPU cost of serving a page to a fraction of an older stack's, so the same nominal limit carries several times further.

Quick answers

Does unlimited web hosting really have no limits?

No. Physical machines hold finite disk, CPU and network capacity. Unlimited plans simply relocate the limits into inode caps, CPU-second metering, entry-process ceilings and a fair-use clause in the terms. The limits are real, just harder to spot.

What is an inode cap and why should I care?

Every file, folder and email on your account is one inode. Unlimited-storage plans usually cap them between 100k and 500k, and an active WordPress site reaches that sooner than most owners imagine. Once capped, uploads and mail start failing regardless of how much 'unlimited' disk appears free.

Up next

More from the blog

The platform these posts come from

Flat renewals, limits stated up front, free migration and support that actually writes back — all of it bundled into a plan.

Browse Hosting Plans