What Is an Inode Limit?

Category: Hosting Basics · Updated 2026-10-30

An inode limit caps the total number of files and folders a hosting account may contain, counted individually no matter how small each one is. A plan can hit its inode limit while still having plenty of unused disk space left, because the limit is about quantity of items, not total size. Shared hosts commonly set inode limits anywhere from roughly 100,000 to 500,000.

What an inode actually is

On Linux filesystems, an inode is a data structure that stores metadata about a single file or directory, such as its permissions, owner and location on disk. Every file, every folder, and every email message stored as an individual file uses exactly one inode. A server has a fixed number of inodes available, and hosting providers divide a share of that total among accounts to keep any single customer from exhausting it.

Why hosts limit inodes separately from disk space

Filesystem performance: directories with an extremely large number of files can slow down backups, scans and file listings for everyone on the server.
Fair use: a tiny file still consumes a full inode, so counting files prevents accounts from gaming disk space rules by storing millions of small files.
Backup reliability: backup systems that walk the filesystem file by file take much longer and are more likely to fail on accounts with huge file counts.

Common causes of a high inode count

Cause	Why it adds up
Caching plugins	Generate a separate cached file for many page and device combinations
Large email archives	Each stored message is its own file in common mailbox formats
node_modules or vendor folders	Package dependencies can add tens of thousands of small files
Session files	PHP or application sessions stored as individual files on disk
Old backups left on the account	Extracted backup archives duplicate the full file count

Checking inode usage

Most control panels display inode usage alongside disk space on the account summary page. With shell access, you can count files directly:

# Count files and folders in the current directory, recursively
find . | wc -l

# Check inode usage for the whole filesystem
df -i

If you are near the limit, clear cache directories, prune old email, and remove dependency folders that are not needed in production first, since those are usually the fastest wins.

Frequently asked questions

What is an inode in simple terms?

An inode is the record a Linux filesystem keeps for each file or folder. Every single file, no matter how small, uses one inode, and a server only has a finite number available.

Can I run out of inodes while still having free disk space?

Yes. Inode limits count the number of files and folders, not their size, so an account full of many tiny files can hit its inode cap long before disk space runs out.

What usually causes a high inode count on shared hosting?

Caching plugins, large email archives, dependency folders like node_modules, and session files are the most common causes, since each generates many small individual files.

How do I check my inode usage?

Check the usage meter in your hosting control panel, or run find . | wc -l in a folder or df -i on the whole filesystem if you have shell access.

What happens if I exceed my inode limit?

New files typically fail to save, which can break uploads, email delivery, cache generation and even software updates, even though the account may still have unused disk space.

Does deleting large files free up inodes?

Only if those files are a meaningful share of your total file count. Freeing inodes effectively usually means deleting many small files, such as cache or old email, rather than a few large ones.