Loading...

Knowledge Base
Home 
 
/
 Understanding and resolving inode limit warnings

Understanding and resolving inode limit warnings

If your account has received a notice about exceeding the permitted number of files, this guide explains what it means and how to fix it.

In this article, we will discuss:

What is an inode?

An inode is a record on the server for every single file or folder stored on your hosting account—including website files, logs, cache files, and temporary data. Each item on the server, no matter how small, counts as one inode.

Note: Shared hosting plans include a maximum of 200,000 inodes. This is the combined count of all files and directories across your entire account, not including emails.

 

Why does the limit exist?

On a shared server, many customers' websites run side by side on the same hardware. When one account stores an extremely high number of files, it puts strain on the shared file system — slowing down file lookups for every account on that server.

The 200,000 inode limit ensures fair, consistent performance for everyone. Under the Terms of Service and Acceptable Use Policy, accounts are expected to store only files related to an active website— not backups, archived data, or unrelated content.

 

What directories are causing the issue?

The notice you received includes a list of the top directories on your account that are using the most inodes. These are the areas to focus on first. Common contributors include:

Directory Common cause
./  (account root) Often old installs or abandoned site files
./backups Backup folders under web root or *.zip, *.tar, *.tar.gz files  
./tmp  CMS session and temporary files 
./cache or /wp-content/cache  Plugin and page cache accumulation 
./logs  Access and error log files 

The email we sent you includes the exact inode counts for your account. Start by focusing on the folders with the highest usage. You can also log in to your account and open the Resource Usage widget on the main dashboard to view your current inode usage, limit, and top directories.

 

How to reduce your file count

Here are the most effective ways to bring your account back under the 200,000 inode limit:

Remove cache files

If you're running WordPress or another CMS, caching plugins can generate tens of thousands of small files. Clear your cache from the plugin settings panel or delete the contents of the ./cache directory using your File Manager or FTP.

 

Delete old backups stored on the server

Backups must not be stored on your hosting account. This is one of the most common causes of file limit violations. Download your backups locally or to cloud storage, then remove them from the server.

 

Disable backup processes that create duplicate backups

In many cases, inode overages are caused by automated backup tools repeatedly backing up files that are already backed up. This creates unnecessary duplicate copies ("backups of backups") and can rapidly consume tens of thousands of inodes. To prevent this from happening again:

  1. Check any CMS backup plugins (such as WordPress backup tools) and disable server‑side storage or exclude existing backup directories from future backup jobs.
  2. Review cron jobs or scheduled tasks that create recurring backups and confirm they are not targeting folders that already contain backup files.
  3. If you use an external backup service, configure it to store backups off‑server (local device or cloud storage only), not within your hosting account.

 

Remove files not permitted under our Terms of Service

If your account contains any files that are not permitted under our Terms of Service (for example, archived media or software unrelated to an active website), those files must be removed from your hosting account. Removing this data can also help reduce your inode usage.

 

Remove abandoned website installs

Old WordPress, Joomla, or other CMS installations that are no longer active can contain thousands of files. If you're no longer using a site, remove its files entirely rather than leaving them inactive on the server.

 

Clear log files

Log files in the ./logs directory accumulate over time. Deleting or trimming older log files is safe for active websites and can free up a significant number of inodes.

 

How to back up files before removing them

Before deleting any files, we recommend downloading them if there's any chance you'll need them later. There are two easy options:

  • FTP client—Download files to your local computer using a free client like FileZilla. Connect with your FTP credentials and transfer the files you want to keep.
  • Cloud storage—Upload files to Dropbox, Google Drive, OneDrive, or a similar service, so they're safely stored off the server.

Once your files are safely backed up, you can remove them from the server without worry. Removing files via FTP is permanent; there is no Recycle Bin or undo.

 

How to request the removal of files

If you'd like our team to remove specific files or directories on your behalf, we can do that — but we need your explicit written authorization first. This is a permanent, irreversible action, so we require the following statement in your reply:

"You have my permission to permanently remove the files and/or directories listed below from my account. I understand that the data will be permanently removed and cannot be recovered."

(List the exact file paths or directory names you want removed)

Important: We cannot remove files without this statement. We will not remove anything beyond exactly what you specify. Data removed this way cannot be recovered.

 

What happens if I ignore the notice?

Your notice may include a response deadline. If the inode count has not been brought below 200,000 by that date:

  1. Your hosting account may be temporarily deactivated to protect server performance for other customers.
  2. If the issue remains unresolved, we may need to cancel your services and remove all data stored on our servers.
  3. Once canceled, data cannot be recovered.
Note: Replying to the notice or contacting our support team before the deadline, even if you have not fully resolved the issue, is always the right move. We want to work with you to find a solution.

 

Frequently asked questions

How do I check my current inode count?

Log in to your account. Look for the Resource Usage widget on the main dashboard, this will show your current inode usage and the limit.

 

Can I increase my inode limit?

Shared hosting plans have a fixed limit of 200,000 inodes. If your website legitimately requires more, you may need to transition to a hosting solution that supports higher inode usage. Our support team can review your needs and discuss options (if available).

 

Why do I have so many files in ./tmp?

The tmp directory is used by your CMS and scripts to store temporary session data and transient files. Some platforms don't clean these up automatically. You can safely delete the contents of ./tmp (not the directory itself)—your site will recreate needed temp files on the next visit.

 

I deleted files, but my count hasn't changed—why?

Inode counts in the Resource Usage tool are updated weekly. Click the “Refresh” link to view the latest inode usage data. This process may take 24-48 hours since our scanner must scan your entire account.

 

What files am I allowed to store?

As stated in our Terms of Service, you may store files directly related to an active website (HTML, CSS, images, scripts, database files) and active email. Backups, archived data, and files not related to a live website or email service must be stored off the server, per our Acceptable Use Policy.