How to Read the Inode Usage Section in cPanel

A hosting account can show plenty of available disk space and still run into a limit. That usually happens when it has accumulated too many files. Learning how to read the inode usage section in cPanel helps you catch this issue before it interferes with email, backups, uploads, or normal website updates.

For most small websites, inode usage stays in the background. But WordPress plugins, old backups, email attachments, cache files, and development copies can raise the count faster than expected. cPanel gives you a simple number to monitor. The key is knowing what that number means and what action makes sense.

What an inode means on a hosting account

An inode is a record the server uses to keep track of a file or folder. In simple terms, one file generally uses one inode, and one directory generally uses one inode too.

A single photo, PDF, email message, cache file, or plugin file counts as an inode. A folder holding those files also counts. That is why a site with thousands of very small files can reach an inode limit even when its storage usage is relatively low.

For example, a 2 GB video may use only one inode. By comparison, a WordPress cache directory with 100,000 small generated files may use 100,000 or more inodes while using less total disk space. Neither situation is automatically a problem, but they consume different hosting resources.

Where to find inode usage in cPanel

The location varies slightly by cPanel theme and hosting configuration, but inode information is commonly shown in the Statistics panel on the right side of the cPanel home screen. It may appear as File Usage, Inode Usage, or a line that shows a number such as 24,500 / 250,000.

Some accounts also display a percentage, such as 10% or 92%. If you see only the current file count, check your hosting plan details or contact support to confirm the account limit.

The number before the slash is your current inode usage. The number after the slash is the maximum number of inodes allowed on the account. In the example above, the account is using 24,500 files and folders out of a 250,000-file limit.

Start by comparing the current count with the account limit. A low percentage means there is no immediate concern. A high percentage means you should look for the cause before the account reaches its cap.

As a practical rule, usage below 70% is usually comfortable for a stable site. Between 70% and 85%, keep an eye on it, especially if you use automated backups, receive frequent email, or run a busy WordPress site. Above 85%, plan a cleanup soon. At or near 100%, the server may not be able to create new files reliably.

That can lead to issues such as failed WordPress updates, incomplete backups, problems receiving email, failed form submissions, or errors when visitors upload files. The exact effect depends on the account setup, but leaving no room for normal site activity is never a good idea.

Do not confuse inode usage with the Disk Usage section in cPanel. Disk usage measures how much storage capacity your files use. Inode usage measures how many files and folders exist. You need to check both, because one can be high while the other stays low.

A quick example

Suppose your cPanel account shows:

182,000 / 200,000 inodes

That means your account is at 91% of its file-count allowance. Even if the Disk Usage tool says you have several gigabytes available, your account has little room left to create new files. A backup plugin that creates thousands of archive segments could push it over the limit.

On the other hand, 15,000 / 200,000 inodes is only 7.5% usage. There is no need to remove files simply because the feature exists. The goal is to monitor the trend and clean up when the count is growing without a clear reason.

What commonly raises inode counts

Many inode issues come from ordinary website tools doing their job for too long without cleanup rules. WordPress is a common example because themes, plugins, image sizes, revisions, caches, logs, and backup archives all create files.

Email can also be a major source. Every message stored in a mailbox counts as a file, and messages with attachments may create additional files. Accounts that collect years of invoices, contact form notices, newsletters, and spam can build a high inode count quietly.

Look for these common sources when the number rises quickly:

Old full-account backups and backup plugin archives stored in the hosting account
WordPress cache folders, session files, temporary files, and error logs
Unused staging sites, test installations, and old subdomains
Large email mailboxes, including Spam and Trash folders
Unused themes, plugins, installers, and duplicate website copies

A high count is not always caused by one large folder. It can be thousands of tiny files spread across cache, email, and temporary directories. That is why checking recent changes matters. If inode use jumped after installing a plugin or changing backup settings, start there.

How to reduce inode usage safely

Use cPanel’s File Manager to review files, but avoid deleting items at random. Website files can be interdependent, and removing an unfamiliar folder may break part of your site. If you are unsure whether a file is needed, ask your hosting support team before removing it.

Begin with the lowest-risk cleanup: empty the Trash folder in File Manager, then check unused email folders. Delete messages you no longer need from Inbox, Sent, Spam, and Trash, and download any records you need to keep. If your business relies on email history, consider archiving older messages locally or through an email service designed for long-term mail storage.

Next, review backups. Keeping one recent backup on the hosting account can be useful, but storing many old backup archives there uses both disk space and inodes. Download or move older copies to separate backup storage, then remove only the copies you have confirmed are no longer needed. Before deleting a backup, make sure another usable copy exists.

For WordPress sites, clear cache files from within the caching plugin whenever possible. Most well-built plugins provide a clear-cache option. This is safer than manually deleting folders because the plugin knows which generated files can be recreated. Review the plugin’s retention settings too. Some backup, security, image optimization, and logging plugins can retain files indefinitely unless you set a limit.

Unused WordPress themes and plugins are also worth removing. Keep the active theme and a current default WordPress theme for troubleshooting, then delete themes and plugins you no longer use. Deactivating a plugin does not remove its files, so deactivated plugins can still contribute to inode use.

Be careful with these folders

Avoid deleting core folders such as public_html, wp-admin, wp-includes, or active plugin directories just to lower the count. Do not remove files from a live website unless you know their purpose or have a current backup.

Log files deserve a closer look. Large error logs can point to a website problem that needs to be fixed, not just deleted. You can often remove an old log after reviewing it, but if it returns and grows quickly, address the plugin, theme, or configuration error creating it.

Keep inode usage from climbing again

A one-time cleanup helps, but sensible maintenance prevents the same issue from returning. Set backup retention limits so only a few recent copies remain in the account. Schedule cache cleanup through your plugin settings. Empty Spam and Trash folders regularly, and remove test sites once they are no longer needed.

It also helps to check inode usage after major changes. Review it after launching a staging site, importing a large mailbox, changing backup tools, or adding plugins that generate images, reports, logs, or cache files. A monthly check is enough for many smaller sites. Stores, membership sites, and sites with heavy email activity may benefit from more frequent review.

If your website legitimately needs a large number of files, cleanup may not be the right long-term answer. A larger hosting plan or a different setup may give you the capacity you need. The best choice depends on whether the files are temporary clutter or essential to your business.

When to contact hosting support

Contact support if inode usage is near the limit and you cannot identify the source, if the count keeps rising after cleanup, or if your website has begun showing update, upload, or email errors. Support can help confirm where usage is concentrated and whether account limits or a plan change should be considered.

For Visiba customers, this is the kind of issue expert support can help investigate without making you guess which files are safe to remove. A quick review is often better than risking a working website to save a few thousand files.

The inode number in cPanel is not a warning to panic. Treat it like a practical capacity gauge: leave room for your website to work, clear out files you no longer need, and investigate sudden growth before it becomes an interruption.