Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Web hosting

Hosting inode limits: why file count can stop a site before storage is full

Published August 2026 · 2 min read · Updated 2026-09-05

Shared-hosting inode limits cap the number of filesystem objects an account can create. Sites with millions of tiny cache/session/image derivative/mail files can exhaust inodes while using modest gigabytes, so storage planning should track file count as well as bytes.

Find the high-file-count directories

Use the control panel or shell tools where available to inspect inode/file usage by directory. Narrow from home/site to wp-content/cache, sessions, mail, logs, node_modules/vendor, thumbnails, backups, and temp paths.

Do not delete mail or application queues merely because they contain many files.

Expire generated data

Configure cache/session/temp/log retention and remove stale staging copies, old deployment artifacts, abandoned dependencies, and local backups that have an independent copy elsewhere.

For WordPress, audit image sizes generated by themes/plugins and cache plugins that leave old trees.

Change application storage pattern when needed

A workload that legitimately creates millions of small persistent objects may not fit shared hosting even if total bytes are low. A VPS or purpose-built storage/data model may provide more control.

Database and object-storage decisions should follow application access patterns, not inode count alone.

Monitor both quota dimensions

Alert on file-count/inode percentage and bytes. Track growth rate so cleanup/upgrade can happen before new mail/uploads/sessions fail. Keep the directory-level count from each review so a new cache, plugin, deployment artifact, or mailbox pattern is visible before it consumes the remaining file budget.

  • Measure file count by directory.
  • Apply retention to generated files.
  • Move legitimate huge-file-count workloads appropriately.
  • Monitor bytes plus inodes.

Next step

Count files, mail, caches and generated assets when an inode quota is near its limit, then reduce unnecessary file growth without deleting required site data.

Explore DotMoose web hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Virtualmin vs cPanel: Which Control Panel Should You Choose?

Virtualmin vs cPanel compared on licensing cost, account and site management, email, DNS, backups and migration, so you can pick the control panel that fits how you host.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

More web hosting guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move