Finding what's eating your disk space (and inodes)

Start with cPanel's Disk Usage tool. It breaks your account down by folder so you can see exactly what's heavy instead of guessing. Open cPanel from your service's cPanel tile, then look under Files for Disk Usage. It shows a tree view of every top-level directory sorted by size, and you can drill into subfolders from there.

Most bloat comes from a small list of repeat offenders: old backups sitting on the server, oversized mail storage, cache and log files, and media uploads nobody cleaned up. Work through them in that order and you'll usually free up real space fast.

Read the Disk Usage tree correctly

Disk Usage shows both files and databases, since both count against your storage quota. A few things to know before you start deleting:

• public_html is your website files and uploads. This is usually where media libraries balloon.
• mail holds every mailbox's messages. A few accounts with years of unarchived mail can be bigger than the site itself.
• logs and tmp are usually small but can spike if an app is misbehaving and writing errors in a loop.
• Database sizes show separately from files, this matters if a table has grown huge from spam comments, session data, or an old plugin that never cleaned up after itself.

Sort by size and open the biggest folder first. Don't start with a broad cleanup sweep, chase the largest number on the screen.

The usual suspects

Old backups on the server

If you or a past developer generated manual backups and left them in public_html or the home directory, they're often the single biggest line item. A full-site .tar.gz or a database dump can easily run into gigabytes. Move anything you want to keep off-server (download it, or store it elsewhere) and delete the copy on your hosting. You don't need to keep manual backups here anyway: see our backup options for how daily backups already work and how to restore from them without keeping your own copies around.

Mail storage

Old mailboxes with years of messages, especially ones with large attachments, add up. In cPanel, check Email > Email Accounts for a per-mailbox usage column, or use Disk Usage's mail breakdown to spot the worst offender. Archiving old mail locally in a desktop client (via IMAP) and then deleting it from the server, or setting a mailbox-level auto-purge for anything past a certain age, are the two practical fixes.

Cache and temp files

WordPress caching plugins, PHP session files, and application-level temp directories can accumulate faster than you'd expect, particularly on sites that generate a lot of resized images or PDF exports. These are almost always safe to clear since they regenerate automatically. If you're running WordPress with LiteSpeed Cache, purging the cache from its plugin settings clears the disk footprint immediately.

Media and uploads

Unoptimized images are the quiet killer, especially on WordPress sites where the media library keeps every generated thumbnail size for every upload. If wp-content/uploads is the biggest folder in your tree, an image optimization plugin or a one-time cleanup pass on unused sizes usually recovers the most space for the least risk.

Don't ignore inodes

Disk Usage tells you bytes, but inodes are a separate limit, roughly one per file, folder, email, and database row. A directory full of tiny files (think: a cache folder with tens of thousands of small entries, or a mailbox with thousands of individual messages) can hit your inode cap long before you're anywhere near your storage cap. Check where you stand on both in Services > your hosting > Information, covered in more detail in checking your hosting resource usage. If inodes are the tight limit, target folders with high file counts specifically, cache directories and mail are the usual culprits, rather than chasing raw disk size.

Cleanup order that won't bite you

1. Download or export anything you're not sure about before deleting it. Cache and logs are safe to delete; backups, mail, and databases are not.
2. Clear cache and temp files first. Zero risk, often a meaningful chunk of space back immediately.
3. Move manual backups off-server, then delete the on-server copy.
4. Archive and prune old mail.
5. Optimize or clean up media last, since it takes the most care to avoid breaking a live site.

If you're not sure whether a file is safe to remove, or a cleanup didn't free the space you expected, open a ticket from Support in the portal. A real person can look at your account directly and tell you what's actually safe to delete versus what's load-bearing.