Here’s a hosting concept that catches people out: your account has a limit on the number of files it can hold, separate from how much disk space they use. That limit is measured in inodes, and hitting it causes confusing errors even when you appear to have space free. Here’s how inodes work and how to keep them in check.
What an inode is
In simple terms, each file and each folder on your account uses one inode. So a million tiny files use a million inodes, regardless of whether they total a few megabytes or many gigabytes. Your hosting plan has both a disk-space limit and an inode limit, and you can hit either one first.
Why it matters
When you approach the inode limit, things start failing in ways that look like a disk-space problem but aren’t: emails bounce, backups won’t complete, uploads fail, and you may not be able to create new files. Yet your disk-usage bar shows plenty of room. The mismatch is the tell-tale sign of an inode issue rather than a space issue.
Checking your inode usage
Your cPanel statistics sidebar usually shows a File Usage or inode figure alongside disk usage. If that number is climbing toward its limit, it’s time to investigate what’s generating so many files.
The usual culprits
- Cache folders: caching plugins and systems can generate huge numbers of small cache files. Clearing the cache often frees thousands of inodes instantly.
- Email: each message is a file, so a mailbox with hundreds of thousands of emails (and their Trash and Junk) uses a lot of inodes. Clearing old mail helps.
- Session files: some applications create temporary session files that accumulate if not cleaned up.
- Old backups and logs: archives and log files add up too.
Reducing your inode count
To bring the number down: clear your caches, empty email Trash and Junk folders and archive or delete very old mail, remove old backups (after downloading them off-server), and delete files and folders you no longer need. Compressing a folder of many files into a single archive dramatically cuts inode usage while keeping the contents.
Preventing it going forward
Set caching to clear old files automatically, keep email tidy, and don’t let backups pile up on the server. A little routine housekeeping keeps inodes comfortably below the limit.
When you’ve genuinely outgrown the plan
If your site legitimately needs a very large number of files — a big application, a huge media library — you may simply need a plan with a higher inode allowance. If you’re hitting the limit and can’t find obvious things to clear, send us a ticket. We can help identify what’s using your inodes and recommend the right plan for your needs.
