Skip to main content
🔥 Hosting from ₹49/mo · Save up to 43% on 3-year plans · Free domain + Free SSL + Free migration · Ends in --d --h --m --s Claim offer →

The "unlimited hosting" myth: inode & CPU limits still exist

By HostStack Editorial · · All posts

"Unlimited disk space. Unlimited bandwidth." These phrases appear on almost every Indian shared hosting sales page. They are not lies — but they are carefully worded truths that obscure real limits you will hit. Here is what "unlimited" actually means and what limits actually matter.

What "unlimited" actually means

Read any shared hosting terms of service carefully. You will find "fair use policy" or "resource usage policy" language. The translation: unlimited means no hard overage fee, not no limits. If you use resources in a way that affects other customers on the shared server, you get throttled, suspended, or asked to upgrade. The limits are just not expressed in simple numbers on the sales page.

The limits that actually get you: inodes

An inode is a filesystem record for every single file, folder, and symbolic link on your account. WordPress alone uses several thousand inodes. Add WooCommerce, 20 plugins, a cache plugin, and backup archives — and you are at 50,000–100,000 inodes. Most Indian shared hosting plans cap inodes at 100,000–300,000, regardless of "unlimited" disk space claims.

What happens when you hit the inode limit: cPanel refuses to create new files. This manifests as WordPress plugin install failures, email delivery failures, and random PHP errors — all of which look like hosting downtime to you but are actually you being throttled for hitting an invisible limit.

Common inode exhausters:

  • WordPress backup plugins storing 30+ daily backups on the server (UpdraftPlus should send to Google Drive, not local)
  • WooCommerce product images with multiple thumbnail sizes generated for each image
  • Cache plugin directories with hundreds of thousands of cached page fragments
  • WordPress core and plugin update files not cleaned up after updates
  • Spam email in mailboxes (each email is a file)

The limits that actually get you: CPU time

Shared hosting allocates CPU time per account. On Linux shared hosting using CloudLinux (standard in India), each account gets a CPU limit in "entry processes" and "LSAPI" workers. When you exceed these during peak traffic, PHP requests queue or fail — showing 508 or 503 errors to visitors.

Signs you are hitting CPU limits: site is slow specifically during business hours (10 AM–1 PM IST, 7–10 PM IST), pages load fine at 3 AM, error logs show Resource limit reached. The fix is upgrading to cloud hosting or a VPS where you get dedicated CPU allocation.

The limits that actually get you: bandwidth

Unlimited bandwidth typically means no bandwidth overage fees, not truly unlimited transfer. Most Indian shared hosts will contact you or suspend the account if you consistently exceed 50–100 GB per month. A high-traffic blog with unoptimised images can hit this. Solution: use Cloudflare CDN (free) to offload 60–80% of bandwidth from your origin, staying well under any fair-use threshold.

What to actually check before buying hosting

Ask these specific questions:

  • What is the inode limit per account? (If they won't tell you, assume 100,000.)
  • What is the CPU entry process limit per account?
  • What happens when limits are exceeded — throttle or suspend?
  • Is there a fair use policy and where is it published?

HostStack publishes limits clearly on plan pages. VPS plans have no inode limits — you own the whole filesystem.

Frequently asked questions

What is an inode limit in hosting?

An inode is a filesystem entry for every file, folder, or symlink. Shared hosting caps inodes at 100,000–300,000 even when disk space is marketed as unlimited. WordPress with WooCommerce and backups easily reaches these limits, causing file creation failures.

What does unlimited bandwidth actually mean in Indian hosting?

Unlimited bandwidth means no overage fees, not no limits. Fair use policies allow hosts to suspend or throttle accounts using resources that impact other shared hosting customers.

How do I check my inode usage on cPanel?

Log into cPanel → bottom of dashboard → Inodes statistic. It shows current usage vs limit. If above 80%, clean up backup archives, cache directories, and old WordPress update folders.

Chat on WhatsApp Real human · usually replies in minutes