What “Unlimited Bandwidth” Actually Means on Shared Hosting
We may earn a commission if you buy through our links. It does not change what we recommend or what you pay. How this works.
Unlimited bandwidth is real in the sense that the host will not bill you per gigabyte. It is not real in the sense that you can use as much as you want. The constraint has simply moved to a different metric, and that metric is in the acceptable use policy rather than on the pricing page.
The short version
- Bandwidth is rarely the real limit. CPU and processes are.
- Inode limits cap file count, which affects large media libraries.
- Enforcement is usually throttling, not a bill.
- Read the acceptable use policy, not the feature list.
Where the limits actually are
| Limit | Typical range | What hits it |
|---|---|---|
| CPU seconds | Per hour or per day | Uncached PHP, heavy plugins, bots |
| Entry processes | 10–40 concurrent | Traffic spikes |
| Inodes | 100,000–500,000 | Large media libraries, many small cache files, backups |
| Memory per process | 256–512MB | Imports, image processing |
| Database connections | 25–50 concurrent | Traffic, or a plugin opening connections carelessly |
| I/O throughput | MB per second | Backups and large file operations |
Inodes catch people out
An inode is one file or directory. A WordPress install is tens of thousands before you add anything. A media library with several generated sizes per upload multiplies quickly, and cache plugins generate a file per cached page.
Check yours:
df -i .
find . -type f | wc -l
# biggest directories by file count
for d in wp-content/*/; do echo "$(find "$d" -type f | wc -l) $d"; done | sort -rnThe usual culprits are cache directories, backup archives stored on the server, and unused image sizes registered by a theme you no longer use.
What happens when you exceed a limit
Rarely a bill. Usually throttling: the site slows, returns 503 responses during spikes, or the host emails asking you to optimise or upgrade. On repeated breaches, suspension.
How to stay comfortably inside
- Cache aggressively. A cached page costs almost no CPU.
- Block bad bots at the server or CDN level before they reach PHP.
- Store backups off-server, not in wp-content.
- Unregister image sizes you do not use, then regenerate.
- Serve static assets through a CDN so they never touch your server.
- Audit plugins for ones running scheduled tasks far more often than necessary.
Watch out
Cache plugins that generate a file per page per device type can consume inodes rapidly on a large site. If you are near an inode limit, check the cache directory first.
When to move up
- Repeated throttling notices despite good caching.
- Uncacheable traffic — a store, a membership site, a forum.
- TTFB consistently above half a second on cached pages.
- An inode count you cannot reduce without deleting things you need.
Common questions
Is unlimited bandwidth a lie?
Not exactly. Transfer genuinely is not metered. The resources needed to generate that transfer are.
What is a reasonable traffic level on shared hosting?
With good caching, a content site handling tens of thousands of visits a month is usually fine. The variable is how cacheable your pages are.
Will a CDN help with these limits?
Substantially. Static assets served from the edge never consume your server’s CPU, processes or I/O.
Sumit
Writes everything on TechMozz.