Web Hosting Inode Limits: What They Mean and How to Check
An inode limit is a cap on how many files and directories a hosting account can hold. It is separate from the amount of storage measured in gigabytes. A site can have disk space left and still reach its file-count limit. This matters most when a plan hosts many sites, stores mail on the server, or keeps multiple backup copies and image sizes.
What counts toward the inode limit?
On a typical file-based hosting account, each file and directory uses an inode. That includes WordPress core files, themes, plugins, uploaded images and their generated sizes, cached files, logs, and mail stored on the account. A single large video file may use fewer inodes than thousands of tiny cached files while consuming much more disk space. Databases are usually measured separately, so check your host’s definition rather than assuming every database row is an inode.
Why does a host set a file-count limit?
Shared servers serve many customers. Large numbers of files can complicate account backups, scans, migrations, and file-system operations even when those files use little space. Providers set different thresholds and policies for different plans. For example, SiteGround says its shared plans have inode quotas, while HostGator documents inode thresholds in its account guidance. These are examples of provider policies, not a universal industry limit; verify the exact plan and current terms.
What happens when you approach or reach the limit?
The consequence depends on the host. You may get a dashboard warning, be unable to create more files, find that backups exclude an oversized account, or be asked to clean up or upgrade. Hostinger describes inode monitoring and cleanup for its plans. Do not assume that running out of inodes produces the same error or grace period at every company.
How to check your usage safely
- Find the inode or “file usage” reading in the hosting dashboard; compare it with the quota for the exact plan.
- Look at directories using many files: caches, backups, old staging copies, logs, and stored email are common candidates.
- Check whether the provider counts files in subdomains, add-on sites, and mailboxes against the same account quota.
- Keep a verified backup before removing anything. Delete through the application or a documented host tool when possible.
- Recheck the count after cleanup; dashboards may update with a delay.
Never remove unfamiliar WordPress, plugin, or application files simply because a folder is large. A cache can often be purged from its own settings. An old backup can be removed only after you know another usable copy exists. Our backup guide explains how to keep a copy outside the hosting account.
Which questions matter before buying?
- What is the inode quota on the plan I will actually buy, and where is it documented?
- Are email and staging files counted in the same quota?
- Is there an earlier threshold at which backups or other features change?
- Can I see file usage by directory, and what happens at 80%, 100%, and above the limit?
- What does an upgrade cost at renewal, and does it increase the file quota?
If you run one modest brochure site, the count may never become a practical problem. If you run multiple WordPress installs, a busy media library, or host mailboxes, it deserves a spot on the comparison sheet. Look at storage, inode quota, CPU and memory limits together instead of treating the largest advertised number as the whole plan. For the other tradeoffs, read shared versus VPS versus cloud hosting and how to compare renewal costs.
Inode limit FAQ
Is an inode the same as a gigabyte?
No. Inodes represent file-system items; gigabytes measure storage size. You can hit either limit first.
Do WordPress plugins and image thumbnails count?
On file-based hosting, plugin files and generated image files generally contribute to the count. The number depends on the installation and the host’s accounting method.
Will “unlimited storage” remove the inode cap?
Do not assume so. Read the provider’s resource and acceptable-use terms for the specific plan.