An inode is a filesystem record that stores the metadata for a single file or folder. In practical terms, your inode count is the total number of files and folders in your hosting account, and most shared hosting plans include an inode allowance alongside the disk-space allowance. If you reach the inode limit you can be blocked from creating new files even when you still have disk space free. That usually shows up as failed uploads, broken login sessions, a site that stops saving changes, or email that will not deliver.
This guide shows you how to see what is using your inodes and how to safely bring the count down. It applies to any Noiz hosting account, whatever software you run.
Last reviewed: 27 July 2026. This is general file and disk housekeeping guidance for Noiz hosting and applies regardless of which control panel your plan uses.
How to access your files
You need a way to see and delete files in your account. Any of the following works:
- File Manager in your Noiz hosting control panel (Plesk on South African shared hosting). This is the quickest option for a browse-and-delete cleanup and needs nothing installed.
- FTP or SFTP with a client such as FileZilla, using the connection details from your control panel.
- SSH, where your plan includes shell access. SSH is the fastest way to count files and remove large directories in bulk.
Find out what is using your inodes first
Before you delete anything, work out where the files actually are so you spend your effort in the right place. Over SSH, from your account's home directory, this lists your top-level folders ordered by how many files each one contains:
for d in */; do echo "$(find "$d" | wc -l) $d"; done | sort -nThe folders at the bottom of the list are your biggest inode consumers. To see the total number of files in the current folder and everything beneath it, use:
find . | wc -lIn the control panel File Manager you can achieve the same thing by opening your largest directories to see what is inside them. Once you know where the bulk of your files live, work through the sections below.
Safe ways to reduce your inode count
The most reliable way to reduce inodes is to remove files and folders you no longer need. The cases below are the ones that most often account for a bloated inode count. Keep a copy of anything you are unsure about before you delete it.
1. Remove old backups and staging sites
Scheduled backups, or backups created by third-party tools such as auto-installers, often fill all the available space on an account if they are left unchecked. A single backup can contain a full second copy of your site and its files, doubling that part of your inode count. Download the backup files to your own computer, then delete them from your hosting account. Do the same with any staging or development copies of your site that you no longer need, which frees a large number of inodes in one go.
2. Delete inactive plugins and themes
If you run WordPress, delete any plugins and themes that are not in use rather than only deactivating them. Deactivating leaves all of the code in your directory, so it still counts against your inode quota. Removing unused plugins and themes also reduces your attack surface, because dormant code is a common route in for attackers, and it keeps the WordPress admin lighter to load.
3. Remove unused image sizes
Many WordPress themes and plugins generate several resized copies of every image you upload, and it is unlikely that all of them are actually shown on the front end. Each generated size is a separate file and therefore a separate inode. Review your theme and media settings, keep only the sizes you use, then regenerate the thumbnails to purge the rest. A plugin such as Regenerate Thumbnails does this cleanly and removes the orphaned sizes for you.
4. Clear cached files
Nearly all modern web applications cache content to disk by default, which can quietly build up a very large number of small cache files. Clear your application's cache folder regularly. Most applications offer a purge option in their administrative area, which is safer than deleting files by hand because it lets the software rebuild only what it needs. For WordPress, look inside the wp-content folder for directories named cache and clear them.
5. Remove development dependency folders
Folders such as node_modules (from Node.js and npm) and vendor (from PHP Composer) are among the heaviest inode consumers there are, often holding tens of thousands of files each. If a project has been built and deployed, these folders are frequently no longer needed in your live web directory and can be removed. Over SSH:
rm -rf node_modulesOnly delete a dependency folder once you are certain the running site does not need it, and never run rm -rf against a path unless you are sure of it, because it deletes without asking.
6. Delete the .opcache folder
If you have an .opcache folder in your web directory, it can accumulate cached PHP files that are safe to clear. Delete it over SSH or in the File Manager. It will be rebuilt automatically the next time your site runs.
7. Clear old logs and session files
Application logs, error logs, and PHP session files build up steadily and are rarely needed once they are more than a few days old. Look for large numbers of files in folders named logs, tmp, or a PHP sessions directory, and clear out anything old. These files regenerate on their own, so removing them is low risk.
8. Clean up your email accounts
Email adds a lot to your inode count because each message is stored as an individual file, so a mailbox with thousands of messages uses thousands of inodes on its own. Empty the Junk and Spam folders, which tend to accumulate quickly, and empty the Trash or Bin folders, which often hold large numbers of deleted messages. Archiving very old mail to your own computer can save a meaningful number of inodes if you are on a tight quota, but download and verify that archive before you delete anything from the server, so you do not lose data you still need.
Still running low?
If you have worked through this list and still need more headroom, upgrading to a plan with a higher inode allowance is the cleanest fix. Noiz support can confirm your current usage and recommend the right plan for your site; open a ticket from your client area and the team will help.
