Disk Space vs Bandwidth vs Inodes: The Hosting Limits Explained

Disk space is how much data your account stores, bandwidth (data transfer) is how much data your site sends to visitors each month, and inodes are the number of files and folders in your account, regardless of their size. A fourth limit, processing power (CPU, RAM and concurrent processes), decides how many visitors your site can serve at the same moment. You can run out of any one of them while the others look fine, and each one fails in a different way.

Disk space: what actually fills it

Disk space is the simplest limit, but people underestimate what counts towards it. On a typical cPanel account it includes:

• Website files: code, themes, plugins and, above all, uploaded images and PDFs.

• Databases: a WooCommerce store with years of orders, logs and sessions can reach several gigabytes.

• Email: every mailbox on the account. One employee who never deletes attachments can use more space than the website.

• Backups stored inside the account: backup plugins that save archives to wp-content are the most common surprise. Ten daily copies of a 2 GB site is 20 GB.

• Logs and temporary files: an error_log file that nobody reads can grow to gigabytes.

Rule of thumb: keep at least 20% free. A full disk does not just block uploads; it breaks sessions, cache writes and database operations, and can produce the server errors described in our guide to fixing 500, 502, 503 and 508 errors.

Bandwidth: how much your site sends

Bandwidth on hosting plans usually means monthly data transfer: the total size of everything the server sends. A quick estimate is average page weight × monthly pageviews. If your pages average 2 MB and you get 30,000 pageviews a month, that is about 60 GB, before counting bots, downloads and images loaded by other sites.

Two points that confuse people:

• Transfer is not speed. Monthly transfer (GB per month) is different from port speed (Mbps). A 1 Gbps port can move at most about 125 MB per second, shared across everything on that link.

• Bots count. Crawlers, scrapers and vulnerability scanners download pages too. On small sites they can be half of all traffic.

The cheapest bandwidth saving is image optimisation: resize to the size you display, serve WebP, and enable browser caching. A CDN also serves static files from its own network, which reduces what leaves your server.

Inodes: the limit nobody expects

On Linux, every file and every folder uses one inode, a small record that stores where the file lives and who owns it. A 1 KB cache file and a 1 GB video each cost one inode. That is why an account can hit its inode limit while using only a fraction of its disk space.

What consumes inodes fastest:

• Page cache: some caching plugins write one file per page, per device type, per language. A store with 5,000 products can produce tens of thousands of cache files.

• Email: mail is stored one file per message. A mailbox with 60,000 messages uses 60,000 inodes.

• Image thumbnails: WordPress creates several resized copies of every upload, and many themes and plugins add their own sizes. One upload can become 6 to 10 files.

• Backups extracted inside the account, old staging copies and test installs.

• PHP session files that are never cleaned up.

• Developer folders such as node_modules or vendor, which can hold tens of thousands of small files.

When inodes run out, the symptoms look random: uploads fail, plugin updates stop halfway, the cache stops working and new email may not arrive. If you see those together, check file usage first.

Processing limits: CPU, RAM and entry processes

Shared servers divide CPU and memory among accounts. Many cPanel servers use CloudLinux, which tracks per-account usage of CPU, physical memory, IO, the number of processes and entry processes (how many requests are being handled by PHP at the same moment). When an account hits these limits, pages slow down first, then visitors start seeing 508 or 503 errors.

Traffic is rarely the real cause. Uncached pages, a heavy search or filter page, WP-Cron running on every visit, and bots hammering wp-login.php are. Fix those before you pay for more resources. On IM HOST shared hosting we do not publish fixed per-account CPU or RAM caps; heavy usage is throttled under fair use rather than suspended, so a busy day slows the site instead of taking it offline.

How to see your usage in cPanel

• Statistics sidebar on the cPanel home page: disk usage, bandwidth, file usage (inodes), databases and email accounts.

• Files → Disk Usage: a folder-by-folder breakdown, including mail and databases.

• Metrics → Bandwidth: monthly transfer, split by HTTP, email and FTP.

• Metrics → Resource Usage: CPU, memory and entry-process limits hit over time (on CloudLinux servers).

If you are new to the panel, our beginner's guide to cPanel shows where each tool lives. With Terminal access in cPanel, these commands find the heaviest folders by size and by file count:

du -h --max-depth=1 ~ 2>/dev/null | sort -h | tail -15
du --inodes --max-depth=1 ~ 2>/dev/null | sort -n | tail -15

Run the second command again inside the biggest folder (for example ~/public_html/wp-content) to drill down until you find the culprit.

Cleanup steps that actually free space and inodes

1. Move old backups out. Download archives from wp-content/updraft, wp-content/ai1wm-backups or your home folder to your computer or cloud storage, then delete them from the server. IM HOST website hosting already includes free daily backups, so storing extra copies inside the same account adds risk and uses quota.

2. Clean the mailboxes. Empty Trash and Spam, archive old mail locally, and ask users to delete large attachments. Mailboxes are often the single biggest inode consumer.

3. Purge and limit the cache. Clear the page cache, disable separate mobile cache if your theme is responsive, and exclude search and filter URLs from caching.

4. Delete what you do not use: inactive themes and plugins, old staging copies, test installs and .zip files left after uploads.

5. Clean the database. Remove spam comments, expired transients and old post revisions. Limit future revisions by adding define( 'WP_POST_REVISIONS', 5 ); to wp-config.php.

6. Fix image habits. Resize photos before uploading; a 6 MB phone photo displayed at 1,200 pixels wide is wasted space and transfer.

7. Truncate runaway logs. Read the end of any large error_log to fix the cause, then empty it.

8. Keep large media elsewhere. Videos and big downloads belong on a video platform or object storage, not on a shared hosting account.

Signs you need to upgrade, not just clean

• Usage climbs back to the limit within weeks of a proper cleanup.

• Pages are cached and bots are under control, but you still hit process limits at peak times.

• The database keeps growing because the business is growing, not because of junk.

• You need things shared hosting is not built for: background workers, custom services, root access.

• You manage several sites and one busy site affects the others.

The next step depends on the site. A growing WordPress site often does well on managed WordPress hosting with CDN, one-click staging and daily backups. A site that needs its own resources and root access is ready for a VPS; this guide on when to move from shared hosting to a VPS walks through the signals.

Frequently asked questions

What happens when I run out of inodes?

The account cannot create new files. Uploads and updates fail, cache stops working, sessions break and incoming email may be rejected. Deleting files, cache and old email frees inodes immediately.

Does email count toward my hosting disk space?

On most cPanel hosting, yes. Mailboxes on your domain live in the same account as the website and share the same disk space and inode count. Check Disk Usage in cPanel to see how much mail takes.

How many inodes does a WordPress site use?

As a rule of thumb, a fresh install is a few thousand files. A real site with years of uploads, thumbnails, plugins and cache commonly reaches tens of thousands. Stores with large catalogues and per-page caching can go higher.

Is unmetered or unlimited bandwidth really unlimited?

Not in the physical sense. Transfer may not be counted against a monthly cap, but port speed, server resources and fair-use rules still limit how much traffic one account can push. Plan around what your site actually needs.

If your site needs room to grow without juggling limits every week, compare our shared hosting plans, which run on NVMe storage with free daily backups and email accounts included. Our engineers can also help you find what is eating your quota.