What Are Inodes in Web Hosting? The Hidden Limit That Blocks Uploads (2026)

What are hosting inodes? Find out why uploads fail with free disk space, compare limits at Hostinger and other hosts, and learn to reduce usage.
What are inodes in hosting? The hidden limit that stops you uploading a file while your space is empty
What are inodes in hosting? Your space is empty but you cannot upload a single file: the limit that never shows on the disk meter
💡 Affiliate Disclosure: This post contains affiliate links. If you buy through them, we may earn a commission at no extra cost to you. Affiliate Disclosure.
📅 Updated October 2026 The explanation draws on the Linux manual (inode(7)) and CloudLinux's official documentation. The limits come from the help and plan pages of Hostinger, Bluehost (updated July 6, 2026), HostPapa, IONOS and InterServer's terms, all read on October 12, 2026, and from Namecheap's plan table.

Your hosting panel says you are using 3 GB of 50 GB, yet the file manager refuses to upload a small image, mail does not arrive, and your site breaks when it tries to save temporary data. Space is not the problem. The problem is a second limit that does not show on the disk meter, called inodes. This article explains what it is from the ground up, why hosts set it, how big the limits are at different companies, and how to see your own usage and bring it down with practical steps.

The short version: an inode is a record in the file system that belongs to one file or one folder, and the inode limit on your plan is the maximum number of files and folders you may have, however big they are. When you reach it, you cannot create a new file even if plenty of disk is left.

📋 Quick summary: inodes in one table

Item In plain words
Inode A record in the file system that stores the details of a file or folder (type, size, permissions, dates), but not its name or its content
The inode limit The maximum number of files and folders your account may hold, regardless of their total size
What counts Every file and every folder, and at some hosts email too (Bluehost's article counts it, HostPapa counts email, and Hostinger says it does not count email)
When you reach the limit New files and folders can no longer be created, so uploads, updates and backups fail, and mail may stop
Where to see it The resource usage page (Hostinger), File Usage in cPanel, or the command df -i over SSH
Published limits (examples) From 50,000 (Bluehost, a soft limit) to 200,000 (Hostinger Web Single), 600,000 (the top Hostinger Web plan) and 5 million (Hostinger Cloud Enterprise Plus)

What is an inode? The definition from the ground up

The Linux manual page inode(7) describes the idea this way: every file in a file system has an inode holding its metadata, and every file has an inode number that is unique within the file system. Bluehost's help page explains that it stores all the details about a file except its name and its data: its size, its type (regular file, directory or symbolic link), its permissions (who can read, write and execute it) and its timestamps (created, last accessed, last modified).

An analogy

Picture a big library: the disk is the shelf space, measured in meters, and the inodes are the index cards. Every book gets a card however small it is, and if you run out of cards you cannot add a new book even though the shelves are empty. That is exactly what happens in hosting.

Why does file size not matter?

Because the limit counts the number of items, not their size. A thousand small files totaling 5 MB take a thousand inodes, while one 5 GB video takes one. That is why your account can be full of inodes with the disk almost empty. As Hostinger puts it, once you reach the limit you cannot create new files or folders even if disk space is available.

Why do hosts set an inode limit?

In its knowledge base, HostPapa explains that the system checks a file's inode when it reads or writes the file, and that the more files and folders there are, the more resources it takes to collect the data and find a file in a large index table. Bluehost says it limits accounts because that is best for shared server performance. In other words, the limit is a way to share a shared server's resources fairly between its accounts and stop one account from overloading it (see What Is Web Hosting).

How is the limit enforced technically?

On hosts that run CloudLinux, its documentation says inode limits work at the level of the disk quota and are enabled on the /home partition only, and that they are supported on cPanel, Plesk and DirectAdmin. There is a hard limit that stops the user writing and a soft limit that can be exceeded for a set period called the grace period, which defaults to seven days, after which the user is denied any additional use. An end user can monitor their usage only through cPanel. To understand the whole system, read What Is CloudLinux.

📊 Want a panel that shows your inode usage, your plan's limit and a breakdown by folder?
Hostinger: its Resources Usage page shows the current count against the plan limit, and its help center says email, databases and automatic backups are stored separately and do not count
☑️ See Hostinger plans

What happens when you reach the limit?

Companies agree on the general effect, no new files, and differ in the details:

Company What its page says
Hostinger You cannot create new files or folders even with free disk space, and sites may stop or show errors in the file manager. At 80% or more of the limit, the usage page shows tips to fix it
HostPapa The account behaves as if the disk were full: no uploading files, no receiving mail and no writing to MySQL, and cPanel shows errors because it cannot save temporary files. A site may stop working if its application needs to save temporary data
Bluehost The limit is 50,000 inodes per cPanel account and it is "soft": you can still upload when you reach it, but going past 1,000,000 files violates the terms of service and may lead to suspension
CloudLinux (soft limit) The soft limit can be exceeded until the grace period ends (seven days by default), after which any additional use is denied
⚠️ An important note: these symptoms look like other faults. You may blame a plugin or think the disk is full. If uploads and updates fail for no clear reason while you have space, check your inodes before you change anything.

How big is the inode limit at different companies?

The numbers range from 50,000 to 8 million. These limits were read from each company's own pages on October 12, 2026:

Company and plan Published limit Note
Hostinger Web (Single, Premium, Unlimited) 200,000 / 400,000 / 600,000 From the "parameters and limits of hosting plans" help page
Hostinger Cloud (Startup to Enterprise Plus) 2 million to 5 million Agency plans have 4 million to 8 million. VPS plans are listed as "Unlimited" inodes
HostPapa 150,000 to 600,000 Essentials 150,000, Growth 300,000, Premium 450,000, Elite 600,000, from HostPapa's resource chart. Elite also advertises unmetered storage
Namecheap (Stellar Plus) 300,000 "Unmetered" storage with a 300,000-file limit. Namecheap's plan table lists 300,000 for Stellar and Stellar Plus and 600,000 for Stellar Business
IONOS 262,144 per contract With 100 to 500 GB of storage. IONOS's help center gives 262,144 as the maximum number of files for Linux web hosting
InterServer 400,000 In InterServer's terms of service: a single shared hosting account is limited to 400,000 inodes at any given time
Bluehost (shared) 50,000 (soft limit) Going past 1,000,000 files violates the terms. The page also points to its acceptable use policy for accounts above 200,000 inodes

The most important lesson is that the "unlimited storage" slogan does not mean unlimited files. Look at the file cap before you buy. Our HostPapa review, IONOS review and Namecheap vs Bluehost comparison are a good place to start.

🔎 Want hosting that publishes its limits as numbers in a clear table?
HostPapa: its resource chart gives the inode limit for each plan, from 150,000 to 600,000
☑️ See HostPapa plans

Where do inodes go on a WordPress site?

Most sites do not reach the limit with their original files, but with what piles up around them:

  • Thumbnails. According to the WordPress developer reference, WordPress generates intermediate sizes by default (thumbnail, medium, medium_large and large), plus every size that themes and plugins register, and recent versions can add more for large originals. So one image can mean five files or more (the original plus four copies), and a library of 10,000 images could come close to 50,000 files. That is an illustrative calculation, not a measurement of any particular site.
  • Cache files. Caching plugins save a ready-made copy of each page, and HostPapa points out that temporary files, cache files and sessions are causes of reaching the limit.
  • Backups. Backups that plugins create inside the site pile up, and Hostinger advises deleting old backups and forgotten staging environments.
  • Unused plugins and themes. Every installed plugin or theme carries many files even when it is deactivated. Hostinger advises deactivating and uninstalling what you do not use.
  • Logs. Hostinger advises checking the logs folder (.logs) and deleting what you do not need.
  • Email. At hosts that count it (Bluehost and HostPapa), every old email uses an inode.

How do you see your current usage?

  • Hostinger: in the control panel open Websites, then Dashboard, choose Hosting plan and then Resources Usage. The chart shows the current count against the plan limit. For a breakdown by folder, Hostinger's help pages point to File Manager's directory size calculation, or an SSH command on Premium and above. After you delete files, use Recalculate usage on that page.
  • cPanel: Bluehost says File Usage (its article also calls it Files Count) appears in the Statistics section and shows only the total, without telling you which folder is heaviest. For folders, use Disk Usage. To learn about the panel, read What Is cPanel.
  • SSH or a VPS: the command df -i shows inode usage on file systems (Bluehost recommends it for VPS and dedicated servers). To count what is in each folder of your site, go into the site folder and run:

# Counts the files and folders inside each folder, largest first (read-only)
for d in */; do echo "$(find "$d" | wc -l) $d"; done | sort -rn | head -10

The command deletes nothing, and it does not include hidden folders (the ones that start with a dot, such as .logs), so check those yourself.

🧰 Is your site already big and in need of much higher limits?
Vultr: VPS servers with root access, so you control the file system and its quotas instead of a limit your host sets for a shared account
☑️ See Vultr servers

How do you reduce inode usage? Six steps

The steps are based on Hostinger's, Bluehost's and HostPapa's help pages, and they work on most shared hosting:

1
Take a full backup first. Download the site's files and export the database before you delete anything, because deletion is usually permanent.
2
Know your limit and your usage. Open the resource usage page, File Usage, or df -i and write down the current number and the limit, so you can measure the effect of your cleanup.
3
Find the heaviest folder. Use the folder breakdown in Hostinger's panel or the counting command above. You will often find a cache folder, backups, images or logs.
4
Delete cache, logs and old backups. Empty the caching plugin's storage, delete backups that plugins created inside the site (after downloading what you want to keep), and check .logs.
5
Clean up WordPress. Uninstall unused plugins and themes, delete old staging environments and forgotten subsites, and delete the extra thumbnails your theme does not use (a dedicated tool or plugin can do this).
6
Archive what you rarely need. Combine old file folders into a single archive with tar or zip, then delete the originals, so the archive is one inode instead of thousands. If usage stays close to the limit, upgrade your plan or move to a VPS.
If you can no longer get into the file manager: Hostinger says its 24-hour boost feature temporarily raises resources if you cannot reach the file manager because of the limit. HostPapa advises upgrading your plan if the cause is a lot of email, or temporary files and sessions.

Common myths

The idea The truth
"My space is empty, so there is no problem" Inodes are a separate limit and can fill up while the disk is almost empty
"My files are big, so I am close to the limit" The limit counts files, not their size. The problem is usually thousands of small files
"Unlimited storage means unlimited files" Many companies advertise unlimited storage and set a file cap (Namecheap and HostPapa in the table above, and InterServer in its terms)
"Email has nothing to do with the limit" It varies: Bluehost and HostPapa count it, Hostinger says its hPanel plans do not, so read your own company's policy
"A VPS has no limit" Hostinger lists inodes as unlimited on its VPS plans, and Bluehost says the limit on a VPS depends on the plan and that an excessive number of inodes hurts performance. You get more control, but the file system's physical constraint does not disappear

🎯 Who needs to care about this, and who can wait?

✅ It matters to you now if:

  • Your site is a WordPress site or a store with thousands of images and products
  • You use caching plugins or backups inside the site
  • You host several sites in one account
  • You are seeing failed uploads or updates for no clear reason
  • "Unlimited storage" offers have tempted you

⚠️ It is less urgent if:

  • Your site is small and its file count is clearly low in your panel
  • Your site is on a platform that does not count files (such as sites built with Hostinger's AI Builder, which the company says do not use inodes)
  • You manage a VPS with quotas you set yourself

🏆 The verdict: what to do after reading this

Read the inode limit on your plan before you buy, the way you read the disk space, and check your usage now and then before it reaches 80%. If you reach it, the fix is usually cleanup (cache, backups, logs, forgotten plugins), and if all your files are needed, upgrade the plan or move to the cloud or a VPS.

  • Open your hosting panel now and write down the current count and the limit.
  • Make cleanup part of your maintenance: forgotten plugins, old backups, piled-up cache.
  • When you compare hosts, put the "file limit" next to the space, the RAM and the processor.
💡 Want big storage and an explicit file limit that suits a mid-sized site?
Namecheap: its plan table lists unmetered SSD storage and a 300,000-file limit for Stellar Plus
☑️ See Namecheap plans

✅ Frequently asked questions about inodes

❓ What is an inode?

A record in the file system that holds the metadata of each file or folder (type, size, permissions, dates), but not its name or its content, and every file has an inode number that is unique within the file system. In hosting it usually means the number of files and folders in your account.

❓ What is the inode limit in hosting?

The maximum number of files and folders your account may hold. Limits vary: 200,000, 400,000 and 600,000 on Hostinger Web plans (Single, Premium, Unlimited), a soft 50,000 on Bluehost shared hosting, 150,000 to 600,000 at HostPapa, 262,144 at IONOS and 400,000 at InterServer.

❓ Does file size affect the inode count?

No. Every file or folder takes one inode whatever its size. A thousand small files take a thousand inodes, and one big video takes one. That is why the limit can fill while your disk is almost empty.

❓ What happens if I exceed the inode limit?

You cannot create new files or folders even if disk space is available. Hostinger says your sites may stop and show errors in the file manager, and HostPapa lists failed uploads, no incoming mail, no writing to MySQL and cPanel errors. At Bluehost the limit is soft, but going past 1,000,000 files violates the terms and may lead to suspension.

❓ Does email use inodes?

It depends on the company. Bluehost says the count includes email messages, HostPapa counts email among the counted items, and Hostinger says email, databases and automatic backups are stored separately and are not counted on its hPanel plans. Read your company's policy.

❓ How do I find out how many inodes I am using?

At Hostinger, from Resources Usage in the plan's dashboard. In cPanel, from File Usage in the Statistics section. Over SSH, with the command df -i, which Bluehost recommends for VPS servers. For folders, use the breakdown in Hostinger's panel or count files with commands.

❓ How do I reduce my inode usage?

Take a backup first, then delete cache, logs and old backups, clean WordPress of unused plugins, themes, staging sites and extra images, archive old files into one file with tar or zip, and review email at companies that count it. If that is not enough, upgrade the plan.

❓ Does WordPress create many files from each image?

Yes. According to the developer reference, WordPress generates intermediate sizes by default (thumbnail, medium, medium_large and large), and every size a theme or plugin registers adds another copy. So one image can mean five files or more, and it multiplies with plugins that create copies in other formats.

❓ Does a VPS have no inode limit?

Hostinger lists inodes as unlimited on its VPS plans, and Bluehost says the limit on VPS and dedicated servers depends on the plan, that you control resources with root access, and that excessive inodes hurt performance. The restriction is lighter but does not vanish.

❓ What are a soft limit and a hard limit?

On CloudLinux systems, the hard limit stops the user writing immediately, while the soft limit can be exceeded during a grace period that defaults to seven days, after which any additional use is denied. Bluehost describes its limit as "soft", so reaching it does not stop uploads.

❓ Should I clean up or upgrade my plan?

Start with cleanup because it is free: cache, logs, old backups and forgotten plugins. If all your files are necessary, or the cause is a lot of email, sessions and temporary files (as HostPapa says), upgrading or moving to a VPS is the lasting fix.

❓ Why do hosts advertise unlimited storage and still set a file limit?

Because a server's resources are not set by gigabytes alone: HostPapa says a large number of files weighs down the index table the system searches for a file. That is why you see "unlimited storage" with an explicit file limit, as with Stellar Plus at Namecheap (300,000) and Elite at HostPapa (600,000).
🏢 Do you need high limits for several sites in one account?
IONOS: plans range from 100 to 500 GB of storage with a limit of 262,144 files per contract, so compare your need before you subscribe
☑️ See IONOS hosting

Have you ever hit the inode limit? Tell us in the comments what you found and how you fixed it.

Related articles you may find useful

🛡️ What Is CloudLinux

The system that enforces resource and inode limits on accounts. Read the guide

🎛️ What Is cPanel

The panel that shows File Usage and resource usage. Read the guide

🖥️ What Is a VPS

An option that gives you more control when shared limits feel tight. Read the guide

☁️ What Is Cloud Hosting

Resources that can grow as your site does. Read the guide

🌐 What Is Web Hosting

The basics: what a host stores and what it limits. Read the guide

About the author

Hossam Hassan
I’m Hossam Hassan, a tech writer and the founder of Technoa5bar. I write practical guides, reviews and comparisons on web hosting, AI tools, website building, SEO, digital marketing and making money online, so you can choose the right tools with con…

Post a Comment