File-count capacity · Provider limit comparison
Web Hosting Inode Limits Compared
Inodes measure file-system objects, not gigabytes. WordPress core files, plugins, themes, cache directories, thumbnails, logs, email, backups and staging copies can consume tens or hundreds of thousands of inodes before disk storage looks full.
At-a-glance answer
Published inode ceilings are clear for three providers. Two still require verification.
Current official articles still cite different inode thresholds. Verify the live account dashboard or current support confirmation instead of relying on one normalized public figure.
Current shared tiers have defined inode limits, but the reviewed public plan overview does not expose a simple plan-by-plan inode table for direct comparison.
Current published inode guidance
Five providers do not disclose inode policy the same way.
| Provider | Entry / mid / higher shared tier | What happens near or above the limit | Special caveat |
|---|---|---|---|
| Hostinger | 200k / 400k / 600k | New files/directories cannot be created at the limit; hPanel begins guidance at high usage. | Some services are stored separately and do not consume the same quota. |
| Bluehost | Do not normalize: current official pages cite different thresholds | File creation, email and server operations can be affected. | One article says 200k maximum; another describes 50k soft and 1m ToS threshold. |
| DreamHost | Defined by current plan, exact reviewed public figure not shown | Shared resource behavior still applies. | Verify the live panel or support before using inode count as a buying criterion. |
| SiteGround | 200k / 400k / 600k | High inode use affects I/O and can contribute to service restrictions. | Email messages count toward account inodes. |
| Namecheap | 300k / 300k / 600k | Website/email performance and file creation can be affected. | Above 200k, automatic server backup exclusion can apply outside Stellar Business. |
Original inode headroom tool
Inode Headroom Calculator
Model the file-count margin before adding another site, staging copy, backup set, cache, or mailbox archive.
What consumes inodes on a WordPress account?
- WordPress core, theme and plugin files.
- Every generated image size created by WordPress or plugins.
- Page-cache and object-cache files when the cache is file-based.
- Backup archives and, in some systems, unpacked backup trees.
- Staging and development copies that duplicate the production file tree.
- Error logs, security logs, temporary files and abandoned installer packages.
- Email messages when mail storage shares the same account inode pool.
Why inode headroom matters more than the headline maximum
A plan that technically allows 400,000 files should not be designed to sit at 399,000 every day. Backups, updates, cache rebuilds, imports and WordPress upgrades may need temporary file creation. A practical reserve also gives you time to investigate a sudden spike before the site starts failing.
How to reduce inode usage without breaking the site
- Find the directories consuming the most file objects.
- Remove abandoned backups and staging copies only after confirming a recoverable offsite backup exists.
- Delete unused plugins/themes and stale cache directories.
- Audit thumbnail generation and image sizes.
- Review email retention if mail shares the inode pool.
- Investigate malware or runaway logs when file count grows unexpectedly.
Do not mass-delete unfamiliar directories solely to reach a lower number. If the account repeatedly returns to the limit after cleanup, compare a larger plan or a hosting architecture with more appropriate capacity.
Claim-level official citations
Use the same source the capacity claim came from.
Resource terminology is not standardized across hosts. Recheck the provider documentation before buying or upgrading because thresholds, plan names, and public disclosures can change.
Research method & evidence discipline
Published limits are compared only when the underlying metric matches.
The page separates hard limits, soft thresholds, planning figures, shared-resource policies, and unavailable public data rather than converting unlike controls into one score.
Page-specific update history
Resource changes are recorded only after substantive verification.
- 01
August 8, 2026 Initial source-backed comparison, original capacity tool, provider caveats, and internal-link cluster published.
- 02
Metric discipline Unlike resource controls stay separate instead of being converted into a fake universal score.
- 03
Future revisions Record the previous value, new value, source, provider context, and verification date when a limit changes.