Inode

Inode is a Linux filesystem metadata unit that stores technical facts about a file — size, permissions, timestamps, and where the data sits on disk. Every file and folder on a hosting account uses one inode, no matter how small the file is.

On shared hosting, you can run out of “slots” for files even when disk space in GB still looks fine. The limit is often the file count, not only storage bytes.

A Simple Analogy

Picture a library. Each book has a catalog card: title, shelf, last borrowed date. An inode is like that card — not the book’s content.

Shelves can still be empty while catalog cards run out. Then you cannot add new books. On hosting: uploads fail, new mail may bounce, and caches cannot write until inodes are freed.

Why It Becomes a Hosting Problem

Shared plans often cap accounts around 50,000–250,000 inodes (provider-dependent). Common burners:

“Unlimited disk” marketing can still hide a hard inode cap — one reason “unlimited” is never truly unlimited.

How to Check Usage

In cPanel, inode usage usually appears on the main dashboard next to disk usage.

Over SSH (when available), from the home directory:

find . -maxdepth 1 -type d -print0 | xargs -0 -I{} sh -c 'echo "$(find "{}" | wc -l) {}"' | sort -rn | head -20

The output shows which folders hold the most entries — start cleanup there.

What to Watch For

• Do not keep full backups inside the hosting account — move them off-server
• Trim old mail and spam; archive externally if needed
• Limit cache retention — enable auto-purge on cache plugins
• Ask for the inode limit before buying shared hosting; brochures often omit it
• Deleting one huge file frees one inode; deleting thousands of tiny files is what actually helps

FAQ