Used by hosting buyers across 10+ countries  ·  Reviews updated April 2026  ·  50+ Hosts Reviewed  · 

Is Unlimited Hosting Really Unlimited?

The Numbers Hosts Don't Always Show You

"Unlimited" bandwidth and storage are real claims, accurately made. CPU, concurrent processes, and inode counts are the actual ceiling — and most hosts don't publish those numbers. A few do. Here's what the fine print really says.

20%
Max server resources per account, InterServer entry tier
400,000
Inode cap, entry-tier shared hosting
~20
Concurrent entry processes, Hostinger shared hosting

Last Verified: June 2026

Search "unlimited hosting" and you'll find two camps: marketing pages promising unlimited storage, unlimited bandwidth, unlimited websites — and skeptic articles calling the whole thing a myth. Neither is quite right.

Bandwidth and storage genuinely are unmetered on most shared hosting plans today. What's almost never unlimited is everything behind them — CPU time, memory, concurrent processes, and inode count — and those are the resources that actually decide whether your site holds up under load. This guide shows the real, published numbers from two hosts that don't hide them.

FBWH Verdict

"Unlimited" is accurate for bandwidth and storage — these genuinely aren't metered on most shared plans, and almost no small site uses enough of either to matter.

CPU, processes, and inodes are the real ceiling — and InterServer and Hostinger are the most transparent hosts we've reviewed on this point, publishing exact numbers instead of vague fair-use language.

InMotion and Pressable use broader discretionary clauses instead of published numbers — standard for their category, but worth knowing going in.

What Hosts Actually Mean by “Unlimited”

When a shared hosting plan says unlimited bandwidth, it means there’s no fixed monthly data-transfer cap and no per-gigabyte overage bill. When it says unlimited storage, it means no fixed disk quota tied to your plan tier. Both are accurate, as far as they go — these companies aren’t lying about the resource named on the tin.

The catch is that “unlimited” only describes the resources named. It says nothing about CPU allocation, how many processes can run at once, how many files (inodes) your account can hold, or how much database load you can generate — and those are the resources that actually cap what a shared hosting account can do. A host can genuinely mean it when they say unlimited bandwidth and still ask you to upgrade for using too much CPU, because those are two completely different promises.

This isn’t a hidden trick unique to any one host — it’s standard across the industry, and it’s a reasonable way to run a shared server. The problem is that most hosts don’t tell you where the real ceiling is. A few do.

The Resources That Actually Have Limits — With Real Numbers

Most “unlimited hosting” articles stop at “read the fine print” without saying what the fine print actually contains. Here’s what it contains, from two hosts that publish real numbers instead of vague fair-use language.

InterServer ties its entry-level Standard plan to a published resource ceiling: a 20% cap on total server resources per account at any given time, and a 400,000 inode limit. Need more room? InterServer sells it directly as a named upgrade tier rather than burying the limit in legal text:

Plan Price CPU Memory Processes Inodes
Standard $2.50–7/mo 1 core 2GB 100 (30 entry) 400,000
Boost 2 $9.95/mo 2 cores 4GB 200 (60 entry) 800,000
Boost 4 $19.95/mo 4 cores 8GB 400 (90 entry) 1,200,000
Boost X $69.95/mo 10 cores 20GB 1,000 (300 entry) 3,200,000

That’s a genuinely useful way to think about “unlimited” hosting: the bandwidth and storage promise is real, but the practical ceiling is the CPU/process/inode tier you’re actually paying for — and you can see exactly where it sits before you sign up.

Hostinger takes a similar approach without a tiered upgrade path: shared hosting accounts are capped at 3GB of database storage across up to 300 databases, 300 FTP accounts, and 400 cron jobs, with a working limit of around 20 concurrent entry processes before requests start queuing. None of that contradicts “unlimited bandwidth” — it’s a different resource, capped to keep one account from slowing down everyone else on the same server.

See InterServer’s Published Resource Tiers →

The “Purpose” Gotcha — What Unlimited Storage Doesn’t Cover

There’s a second trap that has nothing to do with CPU or inodes: what you’re actually allowed to store. “Unlimited storage” sounds like license to use a hosting account as a backup drive or media archive. Most hosts explicitly say otherwise.

InMotion Hosting’s terms state plainly that while disk space and bandwidth are unlimited, the purpose of the hosting product is solely to host websites — using it for file storage or archiving content unrelated to a website is prohibited. InterServer goes further with a specific list of disallowed use cases on shared hosting: file archive sites, mirror sites, image and file upload services, and email archives are all called out by name, alongside the 400,000-inode ceiling that makes large file collections impractical anyway.

This is the gotcha that catches genuinely well-meaning users, not abusers. Someone who treats their hosting account as a personal cloud drive, or builds a site that’s mostly a big media library, isn’t doing anything malicious — but they’re using “unlimited storage” for something it was never built to mean, and a fair-use review is the likely outcome.

When Fair-Use Limits Actually Get Triggered

Resource limits rarely matter on a normal day. The scenarios that actually trip them are almost always good news turning into a problem:

  • A successful marketing push or social mention sends a sudden traffic spike well above your site’s normal baseline, and concurrent processes or CPU usage spike with it.
  • A seasonal sales surge on an ecommerce site multiplies checkout and database activity — load that has nothing to do with bandwidth and everything to do with concurrent processes and database connections.
  • A plugin-heavy WordPress site accumulates CPU and memory overhead over time as more plugins, more cron jobs, and more database queries pile up — independent of traffic growth.

In each case, the account isn’t being “abused” in any meaningful sense — it’s outgrowing the resource tier it’s on. If you’re planning a launch, a sale, or anything that could meaningfully spike traffic, check your host’s actual CPU/process limits beforehand, not just the bandwidth and storage numbers on the pricing page.

Who Unlimited Hosting Is Actually Fine For

None of this means unlimited hosting is a bad deal — for the right site, it’s exactly the right amount of hosting. The resource ceilings above are generous enough that the vast majority of small sites never come close to them.

Unlimited shared hosting is a solid fit for: blogs, portfolios, brochure sites, small business sites, and most WordPress sites without heavy traffic or a large plugin stack. If your site gets a few thousand visits a month and isn’t running a store, you’re unlikely to ever think about CPU or inode limits again after signup.

Look elsewhere if: you’re running high-volume WooCommerce, anticipate a traffic spike from launches or campaigns, need guaranteed (not shared) CPU and memory, or your site is genuinely media-heavy.

Outgrown what shared hosting’s resource ceiling can handle? If you’re hitting CPU or process limits regularly, see our guide to moving from shared hosting to VPS for dedicated resources instead of a shared pool. Running WordPress specifically? Managed WordPress hosting builds the resource headroom into the plan rather than treating it as an upgrade path.

Host-by-Host: Who Actually Publishes the Numbers

Host Type Fair-Use Disclosure What's Actually Published
InterServer Shared/budget Specific numbers 20% resource cap, 400K–3.2M inodes by tier, $0.15/GB overage fee
Hostinger Shared/budget Specific numbers 3GB/300 databases, 300 FTP accounts, 400 cron jobs, ~20 concurrent processes
InMotion Shared/reseller General clause Website-purpose-only restriction, no published numeric caps
Pressable Managed WordPress General clause "No disproportionate infrastructure load," sole discretion, no published numbers

This isn’t a ranking of better or worse hosts — Pressable and InMotion’s broader language is standard for their category, and managed WordPress hosting in particular tends to manage resource allocation behind the scenes rather than exposing raw server specs to customers. But if precise, published numbers matter to you, InterServer and Hostinger are currently the most transparent shared hosts we’ve reviewed on this specific point.

See Hostinger’s Shared Hosting Plans →

Frequently Asked Questions

If bandwidth is unlimited, can my site never go down from traffic?

No. Bandwidth being unlimited only means data transfer isn’t capped or billed by the gigabyte. Your site can still slow down or become temporarily unavailable if a traffic spike exceeds your plan’s CPU, memory, or concurrent process limits — which are separate from bandwidth entirely.

Is “unmetered” the same as “unlimited”?

Functionally, yes, in most hosting marketing — both mean there’s no fixed cap and no overage billing on that specific resource, typically bandwidth. Neither term extends to CPU, processes, or storage purpose restrictions.

Will I get charged extra if I go over a fair-use limit?

It depends on the host. InterServer documents a specific overage fee ($0.15/GB on excess shared hosting resource use). Others, including Pressable and InMotion, are more likely to request you upgrade plans or reduce usage rather than bill you directly — check the specific host’s terms before assuming either outcome.

Does “unlimited storage” mean I can use hosting as a backup drive?

No. Most hosts, including InMotion and InterServer, explicitly restrict storage to website-related files and prohibit using the account as a file archive, backup drive, or media mirror — regardless of how much storage technically remains.

Want the Most Transparent Picks?

If published numbers matter to you over vague fair-use language, InterServer and Hostinger are the two shared hosts in this guide that actually show their work — exact CPU, process, and inode limits, not just a promise to “review on a case-by-case basis.”

See InterServer's Resource Tiers → See Hostinger's Shared Plans →