Account Limits
Inode — The Quota That Fills Up While the Disk Looks Empty
A client is using a fraction of their storage and cannot upload anything, and nothing in the panel they can read explains why.
Straight answer first
An inode is the filesystem's record for one file or one folder, and because hosting plans cap the count it limits how many items an account may hold — which is the ceiling client accounts reach first.
It is the limit nobody sells against and everybody eventually meets. Below: the budget clients cannot see, the four things that consume it, how overselling interacts with the count, and how to run the upgrade conversation honestly.
Written by the Hosting Seller staff · Checked 24 August 2026
100+
Terms, defined for resellers
2 min
To read between tickets
Plain
English, not marketing copy
24/7
Counter cover, yours included
Bytes and inodes are two separate budgets. A million tiny cache files can exhaust the count while barely touching the storage figure, and one large video does exactly the reverse. Clients only ever look at the storage figure.
The usual gluttons are cache folders, mail archives where every message is a file, session files, and dependency trees of the node_modules variety. On a portfolio, that means the accounts closest to the ceiling are rarely the ones you would guess.
The budget your clients cannot see
A client looks at a storage bar sitting at eleven per cent and concludes there is plenty of room. Meanwhile the count is at ninety-eight per cent and uploads have started failing with messages that mention neither number.
That gap is where the angry ticket comes from. Explain the two budgets once, in the client's language, and the same event becomes a routine maintenance job instead of evidence that your hosting is broken.
The four things that eat inodes on client sites
Application caches that rebuild themselves. Mail archives, because every message is a separate file. Session files nobody prunes. And dependency directories left behind by a build that ran on the server once.
All four are renewable categories, which is the good news: they can be cleared without losing anything the client values. A count that climbs while the content stands still is always one of these.
Overselling and the number you actually watch
Overselling is switched on from the start, which lets you allocate generously and pay for the accounts you genuinely hold rather than the headroom you might one day fill. That is a margin advantage, and it is not a licence to stop watching.
The figure that matters is the real consumption across the shelf, not the sum of what you allocated. Allocation is a sales decision; consumption is a capacity fact, and only one of them will wake you up.
The upgrade conversation, done honestly
When an account genuinely needs more, say so with the numbers in front of the client and offer the cleanup first. Purging a stale cache is free and buys months, and offering it before the invoice is what makes the eventual upgrade credible.
Upgrades apply to the account in place with no move between plans, so the conversation is about the right size rather than about a migration project. That makes it a much easier email to send.
Written for whoever carries the account
A definition that stops at 'what it is' leaves you to work out the invoice line on your own. Every entry here goes on to the part that matters: who pays, who explains it, and what breaks once you hold forty accounts.
The renewal price printed on the tag matches the order price, so a quote you gave a client last year still works this year.
- 100+ terms, written for people billing clients
- Every definition carries its commercial consequence
- White-label boundaries flagged where they exist
- Cross-linked, so one lookup answers three tickets
Why Hosting Seller
On every plan, as standard
Two budgets, explained once
Why a client staring at an eleven per cent storage bar cannot upload anything, in words they will accept.
The four renewable categories
Caches, mail, sessions and dependency trees — all clearable without losing anything the client values.
Overselling without surprises
Allocate generously, watch real consumption across the shelf, and know which of those two numbers matters.
Sized for a portfolio
Everything here is written for the person holding forty accounts, not the person holding one.
Grounded in kit you resell
Examples point at cPanel, WHM and hosting you would actually put a client on, not at an abstract diagram.
Paragraphs you can forward
Several sections are worded so they can go straight to a client without being translated first.
First Steps
From choosing to live
- 1
Watch consumption, not allocation
Overselling makes the allocated total meaningless as a capacity figure. The number worth a monthly glance is what the shelf is actually using.
- 2
Clear the renewables before you sell an upgrade
Purge caches, prune sessions, archive old mail, remove dependency directories. Offering the free fix first is what makes the paid one credible.
- 3
Put the two budgets in the client's onboarding note
One paragraph explaining that storage and file count are separate limits. It converts a future angry ticket into a scheduled maintenance job.
In the Box
Packed with every plan
- Real consumption across the shelf reviewed monthly, not allocation
- Cache, session and mail cleanup offered before any upgrade is quoted
- Overselling switched on from the start, across every reseller tier
- Room to grow into hundreds of client accounts on one reseller plan
- Upgrades applied to the account in place, with no move between plans
- Daily backups on every plan, with restores you run yourself
- WordPress Toolkit, with updates applied for you across the estate
- WebP image optimisation built in and costing nothing
- WHM in the box on reseller plans, so accounts get created without a ticket
- The renewal price printed on the tag matches the order price
Across the Counter
Things people ask us all the time
A client says the disk is nearly empty but uploads are failing. Why?
They are reading the storage figure and hitting the file-count ceiling. The two are separate budgets and a site with a runaway cache can exhaust the count while using very little space. Check the count in the panel's statistics, clear the renewable categories, and the account starts working again.
Does overselling apply to the file count as well?
Overselling lets you allocate more than you hold, across the resources your plan governs, which is what makes the margin work. What it cannot do is create capacity. Track what the shelf actually consumes rather than what you have promised, because the second number is a sales artefact.
How do I bring a client account down without deleting their work?
Start with application caches, since they rebuild. Then session files, then old mail, then dependency directories left over from a build. Those four are always the bulk of it, and none of them contain anything the client would miss. Leave uploads and databases alone entirely.
Should I set file-count limits per client package?
Yes, deliberately, rather than letting one account consume the shelf. Sensible per-package limits give you an early warning on the specific account causing trouble instead of a platform-wide problem you have to unpick under pressure.
Read next
Domain Names
Search, register and transfer client names, with year one free when the hosting is ordered annually.
VPS Hosting
KVM virtual servers with root access, DDoS filtering and one flat price, for the account that has outgrown shared.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Resell hosting without explaining our name.
White-label cPanel behind your own nameservers, free migrations on every account you bring, and a price list that does not move under you.
See Domain Names plans