Hosting · Explainer
What Is an Inode Limit on Shared Hosting?
Short answer
An inode limit caps how many files and folders your hosting account can hold, whatever their size, and every file, folder, email and cache file uses one inode. CloudLinux enforces the limit through disk quotas, with a soft limit you can exceed for 7 days and a hard limit that blocks new files. At the hard limit, uploads, updates and incoming email fail.
Key takeaways
- One inode equals one file or folder, so a count of files matters more than their size.
- CloudLinux sets a soft limit with a 7-day grace period and a hard limit that blocks new files.
- Email messages, cache files, backups and image sizes are the biggest inode users.
- At the hard limit, uploads, plugin updates and incoming email all fail.
- Hostinger caps cPanel plans at 500,000 or 750,000 inodes, and cloud plans at 1,650,000.
What is an inode limit?
An inode limit caps how many files and folders your hosting account can hold, whatever their size.
An inode is a small record the filesystem keeps for each file or folder, holding its size, owner, permissions and location on disk. CloudLinux states the number of inodes shows how many files and folders an account has.
A 1 KB text file and a 100 MB video each use exactly one inode.
The limit is a file count, not a disk space limit. You can have gigabytes of free disk space and still be blocked, because the two limits measure different things. Disk space caps how big your files can be, while inodes cap how many of them you can have.
What counts toward your inode limit?
Every file and folder in your account counts, including email, cache files, backups and logs.
WordPress core, themes and plugins add up to thousands of files before you publish a single post. Each plugin ships with its own files, and a site with 20 plugins holds far more inodes than a site with 5.
Media uploads add more with every image, and each image also creates extra files for its display sizes.
Email is easy to miss, since each message in a mailbox is one inode. A mailbox with 10,000 messages uses 10,000 inodes, and spam and trash folders count too. Cache files, session files, log files and old backups stored inside the account all count as well.
What is the difference between a soft limit and a hard limit?
A soft limit can be exceeded for a grace period, while a hard limit blocks new files at once.
CloudLinux lets hosts set both limits through disk quotas, and the limits apply to the home partition only. The hard limit prevents a user from writing data to disk, so nothing new can be saved.
The soft limit can be exceeded for a period of time, and the default grace period is 7 days.
After 7 days over the soft limit, you are denied any additional resources until the count drops back below it. Hosts can change the grace period with the edquota tool, but 7 days is the default CloudLinux ships. Treat a soft limit warning as a deadline, not a suggestion.
What happens when you hit your inode limit?
No new files can be written, so uploads, updates, backups and incoming email start to fail.
A hard limit blocks every write to disk, which breaks more than uploads. Plugin and theme updates fail partway, since they cannot save new files.
WordPress cannot create cache files, so pages slow down. Incoming email bounces or vanishes, because each message needs a new file on disk.
The site itself often keeps loading, since reading files still works. That makes the problem confusing: visitors see the site fine, while the owner cannot upload a single image.
Hostinger notes that keeping usage under the limits prevents errors such as 503 Service Temporarily Unavailable.
What are typical inode limits by host?
Published inode caps vary widely, from 500,000 on entry cPanel plans to 1,650,000 on cloud plans.
Hostinger publishes inode limits for its cPanel hosting: 500,000 on the Silver plan and 750,000 on the Gold plan. Its cloud hosting plans all list 1,650,000 inodes, whatever the tier. The table below shows the figures from Hostinger's support page, updated 6 November 2026.
| Hostinger plan | Inode limit | Disk size |
|---|---|---|
| cPanel Silver | 500,000 | 30 GB |
| cPanel Gold | 750,000 | 50 GB |
| Cloud Basic | 1,650,000 | 20 GB |
| Cloud Standard | 1,650,000 | 40 GB |
| Cloud Premium | 1,650,000 | 60 GB |
| Cloud Corporate | 1,650,000 | 120 GB |
CloudLinux shows a cPanel sidebar with inodes at 151 of 100,000 in its own documentation, which shows how the count is displayed to users. Caps differ by host and plan, and some hosts do not publish the number at all.
The only figure that matters is the one on your plan page or in your panel.
How do you check your inode usage?
Open the Statistics sidebar in cPanel, where file usage is shown next to your disk and bandwidth figures.
CloudLinux states that end users can monitor inode usage through cPanel, and that the Statistics sidebar shows the count against the limit. The same screen shows CPU, memory and entry process use, so you can see all your limits in one place.
Namecheap's guide points to the same Stats widget on the right side of cPanel.
For detail, open the Disk Usage tool in cPanel, which breaks the count down by folder. It shows which folders hold the most files, so you can see at once whether email, cache or backups are the problem.
Check it monthly, since inode counts creep up a little every day and jump suddenly after a backup.
How do you free up inodes?
Delete what you do not need, starting with the folders that hold the most files.
First, clear cache folders and delete old backups stored inside the account, and keep backups off site instead. Our guide to cPanel backup versus plugin backup explains how to store backups away from the account.
Then delete unused plugins, themes and staging copies, since each one ships hundreds or thousands of files.
Next, clean up email. Delete old messages, empty spam and trash, and set auto-delete on folders you never read. A mailbox that has collected mail for years can hold more inodes than the whole WordPress install.
Then check image sizes and logs. Remove image sizes your theme never uses, and delete log and session files that grow without limit.
Hostinger states its limits are fixed per plan, so if you still sit near the cap after cleaning, the next step is a higher plan, not a setting change.
How many inodes does a WordPress site need?
A small WordPress site needs a few thousand inodes, and the count grows with plugins, media and mail.
Core, a theme and a handful of plugins use a few thousand files, which is a tiny share of a 500,000 cap. The count climbs as you add plugins, upload images and keep email on the server.
A site with many plugins, a large media library and years of stored email can reach six figures without ever feeling large.
Watch the share, not the raw number. If your panel shows 400,000 of 500,000 inodes used, you have 20% headroom left, and one backup run can close that gap.
Read your plan's numbers with our guide to reading hosting CPU and RAM limits, and set a reminder to check the count each month.
What mistakes should you avoid?
Do not store backups in the account, keep every email forever, or ignore the soft limit warning.
The most common mistake is treating backups as free, since a backup of the account stored inside the account doubles the file count. A nightly backup kept for 30 days can use more inodes than the site itself.
Store backups off site, and keep at most one recent copy in the account.
The second mistake is ignoring the soft limit. The 7-day grace period passes fast, and once the hard limit hits, updates and email stop with no warning.
If cleaning does not bring the count down, ask the host about the next tier before the grace period ends. A 500 error after a failed update is often the first sign the disk would not take another file.
Frequently asked questions
Is an inode limit the same as a disk space limit?
No. An inode limit counts files, not size. A 1 KB file and a 100 MB video each use one inode. You can run out of inodes while gigabytes of disk space sit free, and you can fill the disk while thousands of inodes remain. Check both figures in cPanel, not just one.
Why does my email use so many inodes?
Email is stored as files, so each message uses one inode. A mailbox with years of mail, plus spam and trash folders, can hold tens of thousands of inodes. Delete old messages, empty spam and trash, and consider moving mail to a dedicated email service if the count keeps growing.
Do cache files count toward my inode limit?
Yes, if the cache is stored as files inside your account. Some cache plugins create one file per cached page, and a site with many pages can hold thousands of cache files. Clear the cache folder regularly, and check the Disk Usage tool to see how many files the cache holds.
Can I buy more inodes without changing plans?
Usually only by moving to a higher plan. Hostinger states its limits are fixed per plan and cannot be raised one at a time. Clean up first, since deleting old backups, email and unused plugins often frees tens of thousands of inodes, and only upgrade if the count stays high.
Do all hosts have inode limits?
No. Managed WordPress hosts and VPS plans often set no published inode cap, or set it by disk size instead. Shared hosting is where the limit bites, because hundreds of accounts share one server. Check the plan terms before signing up, and ask the host for the number in writing.
Sources
- Limits CloudLinux Documentation
- Parameters and Limits of Hosting Plans in Hostinger Hostinger Support
- A Handy Guide to Resource Limits or What is LVE? Namecheap
- How to Adjust User Inode Limits via CloudLinux's LVE cPanel Support
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
