cPanel Problems

cPanel Disk Quota Exceeded

Intermediate Risk: medium

Last reviewed August 7, 2026

Hosting access often needed Database access usually not needed

Direct answer

When cPanel reports a disk quota exceeded, your hosting account has hit its allowed storage limit (or its inode/file-count limit) and the server is refusing new writes — uploads, email, backups, and even log files can start failing until you free space or the host raises the quota. Check the Disk Usage viewer to find what is actually large, clear obvious bloat like old backups, cache, and log files first, then request a quota increase if legitimate site growth caused it.

A disk quota exceeded error is a hard limit set by your hosting plan, not a bug — the server is deliberately blocking writes to protect shared infrastructure. This guide explains the difference between disk space and inode quotas, how to find what is actually consuming space, safe cleanup steps that will not touch your live site, and when the real fix is upgrading the plan rather than deleting more files.

Intermediate

Key facts

Verifiable numbers and definitions — each claim links to its source.

cPanel Disk Usage shows which directories consume the most space so you can target cleanup instead of guessing. (cPanel Disk Usage)
cPanel Support documents that an exceeded disk quota can block AutoSSL HTTP DCV file writes until space is freed. (AutoSSL DCV disk quota failure)
cPanel File Manager is the documented browser tool for browsing, downloading, and deleting files that count against account quota. (cPanel File Manager)

What the error means

Every hosting account on cPanel has a disk quota (total megabytes/gigabytes allowed) and often a separate inode quota (total number of files and folders allowed, regardless of their size). Hitting either one causes the server to reject new writes: uploads fail, email stops arriving or sending, cron jobs and backups can silently fail, and even WordPress can throw errors when it cannot write temporary files or logs. Because inodes count folders and files rather than bytes, an account can hit quota from having too many small files — cache, session, or log clutter — even while raw storage usage still looks moderate.

Common symptoms

Explicit “disk quota exceeded” message in cPanel, email clients, or WHM
File uploads (media library, backups, FTP) fail partway through or are rejected outright
Outgoing or incoming email stops working while other services still run
WordPress shows write-related errors (failed uploads, failed cache writes, failed log writes)
Automated backups fail silently or show incomplete/corrupted archives
cPanel’s own Disk Usage widget shows 90–100%+ of allotted space or inodes
AutoSSL renewal fails with a disk-quota-related error even though the site loads normally

Most likely causes

01 Genuine site growth — more media, more orders, more content than the plan was sized for
02 Accumulated backup archives stored on the same account instead of being downloaded and removed
03 Runaway log files (PHP error logs, access logs, mail logs) that were never rotated or cleared
04 Cache or session directories generating large numbers of small files (inode exhaustion) rather than large ones
05 Old plugin or theme files, unused installs, or leftover migration data never cleaned up after a move
06 Email accounts on the same cPanel account accumulating large mailboxes or spam
07 A hosting plan quota that was always too small for the site’s actual needs

What changed before the problem started

Traffic or order volume increased, generating more logs, sessions, or uploaded media
A backup plugin or manual backup process started storing archives on the same server
Error logging was left verbose (WP_DEBUG_LOG or similar) and accumulated over weeks or months
A migration, import, or duplicate install left extra copies of the site on the account
An email account was compromised or misconfigured and began generating large sent/received volumes

Troubleshooting steps

Troubleshooting flow

Genuine site growth — more media, more orders, more content than the plan was sized for

Accumulated backup archives stored on the same account instead of being downloaded and removed

Runaway log files (PHP error logs, access logs, mail logs) that were never rotated or cleared

Cache or session directories generating large numbers of small files (inode exhaustion) rather than large ones

01
Open cPanel Disk Usage to see what is actually large
Use cPanel’s Disk Usage Viewer to see space consumed by directory, sorted largest first. This tells you immediately whether the issue is one obvious folder (like `backups/` or `logs/`) or spread thin across many small files, which points toward an inode problem instead of a space problem.
02
Download and remove old backup archives from the account
Backup files (`.zip`, `.tar.gz`) are a very common single cause of exceeded quota because they duplicate your entire site’s size. Download any backups you need to keep to your local computer or a separate storage service, then delete them from the hosting account — do not store backups on the same disk you are backing up.
03
Clear PHP error logs, access logs, and other log bloat
Check `error_log` files at the account root and inside `public_html`, plus any dedicated logs folder. These can grow to gigabytes if debug logging was left on. Clear or truncate them, and turn off verbose debug logging (`WP_DEBUG_LOG`) once the current issue is diagnosed.
04
Empty cache, session, and temp directories through their own tools
If a caching plugin or session handler is generating large numbers of small files (an inode problem more than a space problem), clear it through the plugin’s own “clear cache” admin tool rather than deleting files manually, so the application state stays consistent.
05
Remove unused installs, staging copies, or leftover migration folders
Look for old WordPress installs in subfolders, duplicate site copies from a past migration, or unused subdomains still occupying space. Confirm nothing live depends on them before deleting, and keep a downloaded copy if there is any doubt.
06
Check email account sizes and clear large mailboxes
In cPanel’s Email Accounts or Disk Usage view, check whether one mailbox is consuming a disproportionate share of the quota (common with spam floods or never-emptied Sent/Trash folders). Clean up large mailboxes or move them to an external email provider if the account regularly runs tight on space.

Open cPanel Disk Usage to see what is actually large

Use cPanel’s Disk Usage Viewer to see space consumed by directory, sorted largest first. This tells you immediately whether the issue is one obvious folder (like `backups/` or `logs/`) or spread thin across many small files, which points toward an inode problem instead of a space problem.

Download and remove old backup archives from the account

Backup files (`.zip`, `.tar.gz`) are a very common single cause of exceeded quota because they duplicate your entire site’s size. Download any backups you need to keep to your local computer or a separate storage service, then delete them from the hosting account — do not store backups on the same disk you are backing up.

Clear PHP error logs, access logs, and other log bloat

Check `error_log` files at the account root and inside `public_html`, plus any dedicated logs folder. These can grow to gigabytes if debug logging was left on. Clear or truncate them, and turn off verbose debug logging (`WP_DEBUG_LOG`) once the current issue is diagnosed.

Empty cache, session, and temp directories through their own tools

If a caching plugin or session handler is generating large numbers of small files (an inode problem more than a space problem), clear it through the plugin’s own “clear cache” admin tool rather than deleting files manually, so the application state stays consistent.

Remove unused installs, staging copies, or leftover migration folders

Look for old WordPress installs in subfolders, duplicate site copies from a past migration, or unused subdomains still occupying space. Confirm nothing live depends on them before deleting, and keep a downloaded copy if there is any doubt.

Check email account sizes and clear large mailboxes

In cPanel’s Email Accounts or Disk Usage view, check whether one mailbox is consuming a disproportionate share of the quota (common with spam floods or never-emptied Sent/Trash folders). Clean up large mailboxes or move them to an external email provider if the account regularly runs tight on space.

When to stop troubleshooting

Stop deleting files yourself once you are unsure whether something is safe to remove (unfamiliar folders, files tied to an active integration, or anything you did not create). If cleanup does not bring usage meaningfully below quota, if inode exhaustion persists after clearing obvious caches, or if the account keeps hitting quota every few weeks despite cleanup, that is a sign the plan is undersized — escalate to your host for a quota/plan change rather than repeating manual triage.

Information to collect before requesting help

01 Current disk usage and inode usage percentages from cPanel’s Disk Usage Viewer
02 Largest directories/files identified from that viewer
03 Whether backups are currently stored on the same hosting account
04 Size and count of error/access log files
05 Whether any single email mailbox is unusually large
06 Whether the quota exceeded is new or a recurring pattern
07 Hosting plan name/tier and its advertised disk and inode limits

How a professional repairs the problem

A technician reviews the Disk Usage breakdown to separate a true space problem from an inode problem, removes or relocates backups and log bloat safely, clears cache/session directories through proper tooling rather than blind deletion, sets up ongoing log rotation and off-account backup storage, and — when the site has simply outgrown the plan — presents usage evidence to justify a quota increase instead of recurring manual cleanup.

Frequently asked questions

What is the difference between disk quota and inode quota? +

Disk quota limits total storage in megabytes or gigabytes. Inode quota limits the total number of files and folders, regardless of their size. An account can exceed its inode limit while still having plenty of raw disk space left, usually from too many small files like cache or session data.

Is it safe to delete backup files from the hosting account? +

Yes, once you have downloaded a copy you want to keep somewhere else (your computer or cloud storage). Backups should never be the only copy stored on the same disk they are protecting, and they are one of the most common causes of exceeded quota.

Why does clearing cache sometimes not fix a quota problem? +

If the real issue is raw disk space from large media files, database size, or backup archives, clearing cache (which mainly affects inode count from small files) will not free much space. Check the Disk Usage breakdown to target the actual largest consumer.

Can exceeding quota break email even if the website still loads? +

Yes. Email delivery and storage often fail before or independently of the website, since incoming mail needs disk space to store messages. A full quota commonly shows up first as bounced or missing email.

Will my host automatically increase my quota if I hit the limit? +

Usually not automatically — most hosts require you to request an upgrade or purchase additional storage. Some plans do send warning emails as you approach the limit, so check your account email for prior notices.

Does AutoSSL failing mean my disk quota caused it? +

It can — AutoSSL needs to write validation files and certificate data to disk, and a full quota can cause renewal to fail with a disk-related error even though the current certificate and site still appear to work normally until it expires.

Repair dispatch

Still Need Help Fixing Your Website?

If you are not comfortable editing website files, changing server settings, repairing a database, or troubleshooting a live website, professional help may prevent additional damage or downtime. We will review the problem before accepting the repair.

You will receive a clear explanation of the likely cause.
We will tell you if the issue falls outside our repair scope.
No additional work will be performed without approval.
A backup should be created whenever access and website condition allow it.

Emergency repair Request diagnosis

Do not share passwords through an unencrypted contact form — use Password Pusher (self-destructing link). Prefer a dedicated Rescue 404 admin account, not your personal owner login; if you cannot create one yet, we will add ours after repair.