"Unlimited" hosting in India: what it actually means (and what to watch out for)
8 min read · 05-Mar-2024
villagehosting.in team
5 March 2024
"Unlimited bandwidth. Unlimited storage. Unlimited websites." If you've shopped for Indian shared hosting in the last ten years, you've seen this marketing everywhere. Spoiler: it is not unlimited. Here is what those words actually mean, where the real limits are, and how to pick a plan based on what genuinely matters.
This applies to all major hosting providers
Every major hosting company in India uses similar "unlimited" marketing language. This article explains the mechanics, not any single company's practices. Read the Terms of Service for any host you're considering.
What "unlimited" actually means (legally)
Every Indian hosting company that advertises unlimited plans has a Terms of Service document with usage policies. The key phrase to look for is "acceptable use" or "fair use policy". A common version reads something like:
"Resources are shared among users on the same server. Accounts using resources that adversely affect other users may be suspended or asked to upgrade to a dedicated plan."
This means unlimited = unlimited until you use enough to bother other users. The hosting company is the sole judge of when that threshold has been crossed.
This isn't fraud — it's a business model designed around the statistical reality that most shared hosting accounts use very little. The hosting company sells 500 accounts on a server sized for 50 heavy users, counting on the other 450 to never actually need heavy resources.
Unlimited storage: the real limit
"Unlimited storage" on Indian shared hosting hits one or more of these practical caps first:
Inode limit: An inode represents one file or folder. Shared hosting almost always caps inodes regardless of storage marketing language. Common limits: 100,000–500,000 inodes.
A fresh WordPress installation uses ~2,000 inodes. Add WooCommerce, plugins, and two years of product images: easily 50,000–100,000 inodes.
If you're running a media-heavy site, stock photo blog, or any site that generates many small files (WordPress cache files, for example), you'll hit the inode limit long before disk space becomes an issue.
Individual file size limits: Some hosts cap single file uploads at 256 MB or 512 MB. This rarely matters for websites but blocks database imports or large media uploads.
Storage class: "Unlimited" storage may mean unlimited space on slow SATA drives, while SSD storage (which actually matters for database performance) is limited.
Unlimited bandwidth: where it breaks down
Bandwidth marketing is the most misleading. Here's how it actually works:
Port speed throttling: Most shared hosting accounts are on 100 Mbps or 1 Gbps shared ports. Your account gets a fraction of that. During traffic spikes, your allotment drops further.
Concurrent connection limits: More important than raw bandwidth. Shared hosting typically allows 4–25 simultaneous PHP processes per account. During a traffic spike, requests beyond that limit queue and then time out. No amount of "unlimited bandwidth" helps when you've hit your concurrent connection ceiling.
CDN is separate: If you're serving large files (videos, high-res images), the hosting company expects you to use a CDN. Streaming gigabytes of video through shared hosting would trigger the fair use policy regardless of the "unlimited" marketing.
International bandwidth: Indian hosting providers typically measure bandwidth differently for international traffic. If your audience is primarily outside India, your effective bandwidth allowance may be lower.
Unlimited websites: the addon domain trap
"Unlimited websites" sounds great for agencies and developers who want to host multiple clients. The reality:
All sites share one cPanel account's resources: All those "unlimited" websites compete for the same CPU time, RAM, and concurrent connections as your primary domain. Hosting 20 WordPress sites on one shared account means all 20 are resource-constrained together.
Email limits: Many shared hosting plans cap email addresses per account (50–100 addresses) even while claiming unlimited domains.
SSL limits: AutoSSL covers all domains, but there are rate limits. If you're adding many domains rapidly, you may hit Let's Encrypt rate limits (5 certificates per domain per week).
Database limits: Despite "unlimited" websites, many plans limit the number of MySQL databases (25–100). Multiple WordPress sites each need their own database.
What you should actually measure
When evaluating an Indian hosting plan, ignore "unlimited" claims and look at:
Guaranteed RAM: For PHP applications, look for at least 256 MB per account. WordPress with caching and a few plugins needs 64–128 MB. WooCommerce with product images needs 256 MB+.
CPU throttling: Some hosts explicitly state CPU usage limits (e.g., "up to 25% of one CPU core"). Others are vague. Ask before buying.
Inode count: Ask for the inode limit. A good shared hosting plan for a WordPress site with WooCommerce should have at least 250,000 inodes.
Concurrent connections/PHP workers: How many simultaneous requests can your account handle? 10–25 is typical. A site getting 1,000 visitors/day with no caching will hit this regularly.
Backup policy: Are daily backups included? How many days of history? Some "unlimited" plans charge extra for backups.
Data center location: Is the server physically in India? Chennai, Mumbai, Delhi NCR data centers give Indian visitors 20–50ms latency vs 200–400ms for servers in Singapore or the US. For an Indian audience, this matters more than the storage marketing.
Ask the host directly
Email support before buying and ask: 'What is the inode limit? What is the max concurrent PHP processes? What CPU limits apply?' A host that won't answer these questions honestly is telling you something about how they'll handle problems after you've paid.
When unlimited shared hosting is enough
Despite the caveats, shared hosting is genuinely sufficient for many Indian websites:
- Informational websites (10–50 pages, no e-commerce, under 500 visitors/day): shared hosting handles this easily
- Small WordPress blogs (under 100 posts, minimal plugins, under 200 visitors/day): works well
- Landing pages (single-page marketing sites, forms connected to email services): well within limits
- Small WooCommerce stores (under 100 products, under 20 orders/day): manageable with good caching
When to stop believing the marketing
Move to VPS when:
| Signal | What's actually happening |
|---|---|
| White screen of death during plugin updates | Hitting PHP memory limit |
| Site goes down during product launches or social media traffic | Concurrent connection limit hit |
| Cron jobs randomly fail | CPU time limit being enforced |
| File uploads silently fail | Inode limit reached |
| Hosting company "suspends" account for high resource usage | Fair use policy enforcement |
| Need to run Node.js, Python (Django/Flask), or custom software | Can't on shared hosting |
What honest hosting pricing looks like
A truthful hosting plan description would read something like:
"Shared hosting on a server with 500 other accounts. Your account gets up to 256 MB RAM, 25 PHP workers, 250,000 inodes, and 100 GB of SSD storage. Bandwidth is monitored and you'll be contacted if you consistently exceed 10 GB/month. Daily backups kept for 14 days."
That's not what the marketing pages say. But that's the kind of specificity that lets you evaluate whether a plan fits your actual needs.
The jump from shared hosting to a ₹999–1,499/month managed VPS is one of the highest-ROI upgrades an Indian small business website can make. You get guaranteed resources, root access, the ability to run any software, and no more guessing what "unlimited" means in practice.
Understanding what you're buying is step one. Step two is buying what your website actually needs.