The truth about unlimited bandwidth in WordPress hosting is simple: no host gives away infinite data transfer, and the ones advertising it are usually capping you somewhere else. Bandwidth is cheap at wholesale rates, so providers hand it out freely while quietly metering CPU, memory and concurrent processes instead. Once you know where the real ceiling sits, plan comparison gets much easier.
What “Unlimited Bandwidth” Actually Means
Bandwidth, in hosting terms, is the total volume of data your server sends to visitors over a billing month. A visitor loads a page weighing 2 MB, and that’s 2 MB of transfer. Multiply by pageviews and you have your monthly figure.
When a host advertises unlimited data transfer, they’re making a statistical bet. The overwhelming majority of shared hosting accounts move under 100 GB a month, so the handful that move 2 TB get absorbed by the average. That’s not fraud, it’s just pooled-resource math, and it works fine until your site becomes the outlier.
The word “unlimited” in these plans is a marketing convention rather than a technical guarantee. Every provider backs it with an acceptable use policy that reserves the right to throttle, suspend or force an upgrade. Read that document before you read the pricing table.
Where the Real Limits Hide
The constraint that actually stops a WordPress site is almost never raw transfer. It’s the compute budget behind it. Here’s what we see limited in practice, even on plans marketed as unlimited web hosting:
- CPU seconds and entry processes: typically 1 to 2 vCPU equivalents on shared plans, with hard caps on how many PHP workers can run at once (often 20 to 40).
- PHP workers: the single biggest throttle on dynamic pages. Ten workers means ten uncached requests processed simultaneously, no matter how much bandwidth you have.
- Inodes: file count limits, commonly 200,000 to 500,000. Large media libraries and backup plugins blow through these faster than people expect.
- Database queries and I/O throughput: usually capped at 1 to 10 MB/s of disk read/write on entry plans.
- Monthly visits: managed hosts increasingly meter visitors instead of gigabytes, which is at least honest about what’s being counted.
So a plan can be genuinely unlimited on transfer while capping you at a level that fails during a moderate traffic spike. The bottleneck moved; the marketing didn’t.
How Much Bandwidth Does a Real Site Actually Use?
Do the arithmetic once and the anxiety usually disappears. According to the HTTP Archive page weight report, the median web page transfers roughly 2.5 MB on desktop and just over 2 MB on mobile.
Use this formula: monthly pageviews x average page weight x 1.3 (for bots, feeds and repeat assets) = monthly bandwidth. A blog with 50,000 monthly visitors averaging 1.8 pages each and a 2 MB page weight lands near 234 GB. A brochure site with 3,000 visits a month rarely clears 15 GB.
Two things change that number quickly. Self-hosted video is the biggest offender, since a single 5-minute 1080p clip can push 150 MB per view. Uncompressed hero images are the second, and a properly configured CDN plus modern image formats often cuts total transfer by 40 to 60 percent.
For a closer look at this topic, see our guide: WooCommerce Hosting Requirements: Why Shared Hosting Fails Online Stores.
For a closer look at this topic, see our guide: How to Price WordPress Maintenance and Hosting for Agency Clients.
For a closer look at this topic, see our guide: Automated Threat Hunting in WordPress Hosting Environments.
Related reading: Is Your WordPress Host GDPR and CCPA Compliant?.
The Gap Nobody Advertises: Concurrency Beats Volume
Here’s the part the Reddit threads get right and the sales pages skip. Sites don’t fall over because they exceeded a monthly gigabyte figure. They fall over because 400 people arrived in the same 90 seconds and the server had eight PHP workers.
Bandwidth is a monthly average. Concurrency is a per-second reality. If your newsletter goes out at 9am and 2,000 subscribers click within ten minutes, your monthly transfer barely moves while your queue depth spikes hard enough to time out.
This is why server-level caching matters more than any transfer allowance. A cached page served from memory skips PHP and MySQL entirely, which means one worker can serve hundreds of requests. Pair that with modern runtimes, because PHP 8.3 and above processes requests measurably faster than the 7.x builds still running on neglected accounts.
How to Read a Hosting Plan Honestly
We tell people to ignore the headline features and go straight to the specifics. Ask a provider these questions before you buy:
- How many PHP workers does this plan include? If they won’t say, that’s your answer.
- What happens at the limit? Throttling, a 508 error, an overage bill, or a support ticket asking you to upgrade? The difference matters for revenue sites.
- Is there an inode or file count cap? Get the number in writing.
- Is the CDN included or metered separately? Some “unlimited” origin plans bill CDN traffic per gigabyte.
- Where is usage reported? You need a dashboard showing real transfer and resource data, not a monthly surprise.
That last point is underrated. Without visibility into your own hosting metrics, you’re guessing about whether you’re near a ceiling. We’d rather show you a graph than a footnote.
Metered vs Unlimited: Which Is Safer?
A clearly metered plan is usually the better deal, oddly enough. If a host says 500 GB and 100,000 visits, you can plan, forecast and budget. If a host says unlimited, you’re relying on their tolerance rather than a contract.
Budget providers like the big shared-hosting brands lean hard on the unlimited framing because it converts. That doesn’t make them bad, and plenty of small sites run happily on them for years. It just means the useful comparison is resources per dollar, which is exactly how we structure our affordable WordPress hosting plans: published limits, no fine-print throttling.
If you’re evaluating a move, remember that transfer allowances rarely explain performance differences. Our breakdown of what actually changes when you switch hosts covers the variables that do move Core Web Vitals.
Free Hosting and “Unlimited”: A Special Case
Free WordPress hosting that promises unlimited bandwidth is funding itself somehow, usually through ads injected into your pages, aggressive resource throttling, or upsells triggered the moment you get traffic. Expect shared IPs, no staging, and no Git-based deployment workflow for anyone doing real development work. For a hobby project that’s fine. For anything with revenue attached, the math stops working around month three.
Frequently Asked Questions
Is 10 GB bandwidth enough for a website?
Yes, 10 GB per month comfortably covers roughly 2,000 to 4,000 pageviews at typical page weights of 2 to 2.5 MB. That’s enough for a small brochure site, a portfolio, or a new blog, but a single embedded video or an unexpected social media share can consume it in a day. Sites expecting steady growth should plan for 100 GB or more.
What is the cost of an unlimited hosting plan?
Unlimited-branded shared hosting typically runs $3 to $15 per month on a multi-year introductory term, renewing at $10 to $30. Managed WordPress plans with published resource limits generally start around $20 to $35 per month. The renewal rate, not the promotional price, is the number worth comparing.
Which is the fastest hosting for WordPress?
The fastest configurations combine LiteSpeed or NGINX with server-level full-page caching, PHP 8.3+, object caching via Redis, and NVMe storage, which together deliver sub-1-second load times for most sites. Raw hardware matters less than the caching layer, since a cached page skips PHP entirely. Independent testing from Google’s Core Web Vitals guidance is a better benchmark than any host’s own numbers.
Is WordPress better than GoDaddy?
These aren’t competitors: WordPress is the software, GoDaddy is one company that sells hosting for it. The real question is whether GoDaddy’s managed WordPress product suits you, and for sites needing granular resource control, staging and developer tooling, specialist hosts generally offer more. You can run identical WordPress installs on either.
Want Hosting With Limits You Can Actually See?
We publish our resource numbers instead of hiding them behind the word unlimited, and every plan includes LiteSpeed caching, a global CDN and free migration. Compare our scalability options or start a 14-day trial and watch your real usage data for yourself.
[…] Related reading: The Truth About "Unlimited Bandwidth" in WordPress Hosting. […]
[…] Uncached bot traffic. AI crawlers, price scrapers and vulnerability scanners hit uncacheable URLs (search pages, faceted filters, ?add-to-cart) and each one costs a full PHP execution. This is also why raw bandwidth numbers mislead people, a point we cover in the truth about unlimited bandwidth. […]
[…] Related reading: The Truth About "Unlimited Bandwidth" in WordPress Hosting. […]