Web Hosting & Domains / Account maintenance
Disk space measures how much data you store; an inode limit restricts how many filesystem objects your hosting account can contain. Thousands of tiny files can exhaust a file-count allowance while gigabytes remain available. Check both figures, identify the directories responsible, and remove only data you can safely replace or recover before paying for a larger plan.
If uploads or updates fail despite a reassuring storage meter, this guide helps you separate the possible causes. The practical goal is to recover usable headroom and stop unnecessary files accumulating again.
Record your current file count, the account limit, disk usage, and the exact error. Ask your host whether the restriction applies to your account or the underlying server. A server-wide filesystem problem needs the provider’s attention; deleting your own files may not solve it.
01 / Inodes versus disk space: two different constraints
An inode holds information about a filesystem object. For hosting-account management, think primarily in terms of files and directories. cPanel explains why many small files can exhaust available inodes even when storage remains. This does not mean every filename always represents a separate inode in every filesystem situation, but file count is the useful starting point in a hosting dashboard.
| Resource | What it measures | What to investigate |
|---|---|---|
| Disk space | Stored data, usually reported in MB or GB | Large archives, media, mail and databases |
| Inodes / file usage | Filesystem objects counted against a limit | Large numbers of small files and directories |
| Bandwidth | Data transferred over a period | Traffic and download volume |
| CPU and memory | Computing resources used by running work | Application activity and concurrent workloads |
Hypothetical example: an account has a 300,000-file allowance and uses 270,000 files: 90% of that allowance. Its storage meter shows 8 GB used out of 40 GB: 20%. Both readings can be correct. Compressing existing images may reduce their bytes without reducing the number of files.
Also distinguish a provider’s account quota from the underlying filesystem’s capacity. Buying extra storage helps only if the actual restriction changes. Ask for the specific file-count allowance rather than assuming “more GB” includes more inodes.
02 / Check the right hosting statistics
In cPanel, look for File Usage in the statistics area. cPanel documents this as the number of files and directories used by the account; the provider must enable the statistic. Missing information does not prove that no limit exists.
Open Files → Disk Usage separately to identify directories consuming storage. Its size-based view answers a different question from an inode breakdown. The Disk Usage documentation also warns that backups near an account’s disk quota may fail when required files cannot be written.
Some hosts add a directory-level inode report. For example, Namecheap documents an Inodes Usage menu showing paths and their counts. Other control panels use different labels. Request a breakdown from support if you only have the account total.
- Confirm whether the allowance is per website, hosting account, or subscription.
- Ask whether hosted email and staging copies share it.
- Check for separate warning, enforcement, and backup-eligibility thresholds.
- Record when the statistics were last refreshed.
Do not copy another host’s limit into your diagnosis. Your plan’s current policy and support response determine what happens on your account.
03 / Find the source of file growth
Begin at the account level, then expand the largest file-count directories. Write down each path, its purpose, the application or person responsible, and whether it is actively growing. Avoid sorting only by file size: a tiny-file directory can be the main problem.
| Location or purpose | Question to answer | Preferred next step |
|---|---|---|
| Application cache | Is this disposable generated content? | Use the application’s documented purge control |
| Staging or old site copy | Is anyone still using it? | Confirm ownership and removal through its management tool |
| Mailbox storage | Which folders contain the most messages? | Review retention and archive requirements with the mailbox owner |
| Media uploads | Are image variants still referenced? | Audit usage before removing anything |
| Backup or deployment directory | Which copies are required for recovery? | Confirm an independent copy and retention policy |
If you compare two reports, avoid double-counting a parent directory and its children. A total for the website directory may already include its uploads and cache subdirectories. You need to identify the largest contributors, not add every displayed row together.
A sudden burst of unfamiliar files is a reason to involve the application maintainer or host before mass deletion. Preserve the relevant paths, timestamps, and error details. A high count alone does not establish an infection or identify a security incident.
04 / Clean up without losing necessary data
Protect a usable recovery copy first
Confirm that an independent backup exists and covers the data you might change. WordPress backup guidance covers both site files and the database. An export of posts alone is not a complete recovery plan; see our explanation of WordPress exports versus full backups.
If the account is already full, avoid creating another large local archive as your first move. Ask the host about supported downloads, remote backups, or temporary capacity. Check that a downloaded archive opens and contains the expected material before removing the server copy.
Use the tool that owns the files
SiteGround’s inode-cleanup guidance identifies old staging copies and file-based caches as possible contributors. Remove a retired staging site through its staging manager after its owner confirms it is no longer needed. For cache, use the application’s documented purge function and investigate rapid regrowth rather than repeatedly deleting the directory.
Treat backup retention separately from staging retention. Keep the recovery points your business needs, verify an independent destination, and adjust the job that creates excess copies. Deleting yesterday’s files while leaving an uncontrolled schedule running only postpones the same decision.
Review email with the mailbox owner
Where mail is stored in the same account, include it in the investigation. cPanel’s Email Disk Usage interface can sort mailbox information by message count or storage. Review the actual folders before using removal controls. Export required correspondence, confirm retention needs, and check whether deletion synchronizes to other devices.
Do not remove internal mailbox files directly through File Manager. Use the mail application or the provider’s supported controls so the mailbox remains consistent.
Be careful with WordPress media
One uploaded image can produce additional files. WordPress’s attachment-metadata documentation describes creation of thumbnails and intermediate sizes. Multiple versions are not automatically waste: pages may rely on them.
Audit references and required sizes with the site maintainer before removing variants. Avoid manually deleting files solely because their names contain dimensions. Likewise, reducing image quality or converting a file format does not inherently reduce file count if the originals and extra variants remain.
Understand what Trash does
cPanel File Manager normally moves deleted items to Trash; Empty Trash permanently removes them. Moving files into another folder in the same account is not a dependable way to reduce the account’s file count. Review Trash contents and confirm recovery copies before emptying it.
Leave unfamiliar configuration files, active application code, and database storage alone. If you cannot explain why an item is safe to remove, get its owner involved.
05 / Verify recovery and prevent a repeat
Make one controlled change, record it, and refresh the statistics after the provider’s stated update interval. SiteGround says its figures can take up to ten minutes to update; other providers may differ. Avoid escalating deletion while waiting for a delayed counter.
- Confirm that file count decreased and disk usage remains within its allowance.
- Retry the operation that originally failed, such as a small upload.
- Check representative pages, images, forms, and any affected mailbox.
- Confirm that scheduled backups complete and recovery copies remain available.
- Review the count again after normal cache, backup, and deployment activity.
Assign an owner to the folder that caused the growth. Agree on retention, an expected range, and a review interval. The useful metric is not just today’s free capacity, but whether normal work consumes it at a sustainable rate.
06 / Decide whether to upgrade
Cleanup fits an account dominated by obsolete copies or unnecessary generated data. A higher allowance may fit an account whose legitimate working files already approach its limit. Compare the resource you need rather than the plan name.
After cleanup, an account uses 180,000 of 250,000 allowed files. If its measured net growth is 10,000 files per month, 70,000 files of remaining capacity represents roughly seven months at that unchanged rate. This is planning arithmetic, not a forecast: imports, staging copies, and seasonal activity can change the result.
Before upgrading, obtain the new inode allowance, its scope, backup conditions, migration implications, and renewal cost in writing. More CPU, storage, or advertised websites may not change the binding file limit. Our shared versus managed WordPress hosting guide helps compare the broader support and maintenance responsibilities once capacity requirements are clear.
07 / Send a useful support request
Give support enough evidence to distinguish a quota issue from another failure:
- The account identifier, exact error, affected action, and time it occurred.
- Current file count and allowance, plus disk usage and quota.
- The largest directory counts and recent growth, if available.
- Cleanup already performed and when the statistics were checked afterward.
- A request to confirm account-level enforcement, server-wide capacity, and any separate backup restriction.
Ask for the next action that addresses the confirmed limit. Do not send passwords or private file contents just to explain a count.
Frequently asked questions
Does free disk space mean uploads should still work?
Not necessarily. An inode quota or underlying filesystem limit can prevent new files even with free bytes. Permissions and other failures are also possible; check the exact error and ask the host to confirm the cause.
Will compressing images fix an inode warning?
It can reduce storage, but keeping the same number of image files does not reduce file count. Removing genuinely unnecessary variants can help only after confirming they are unused and recoverable.
Does a database cleanup always reduce inodes?
No. Removing database rows does not translate into one fewer filesystem file per row. Diagnose database size and hosting file count as separate measurements.
Should I upgrade immediately after a warning?
First identify what is growing and which limit applies. Upgrade when the needed working data requires more capacity, or when cleanup cannot provide sufficient headroom for normal operations.
Capture both hosting meters, identify the three largest file-count directories, and assign an owner to each. Confirm a usable recovery copy, make one supported cleanup change, and measure the result before deciding what to buy.
Sources and editorial notes
Provider and WordPress documentation was checked on 24 October 2026. Interface availability and quota policies vary by host and plan. Numerical examples are hypothetical; no hosting benchmark or hands-on product test is claimed. Primary documentation is linked beside the relevant explanations.
Add comment