How much disk space does a WordPress site really need: reading your hosting report

The email arrives: disk space at 90%. The site is running fine, the daily backup has stalled, and it's unclear whether old photos from last year are to blame or something else nobody has ever looked at. Anyone paying for hosting each month needs to know what's consuming that space before deciding whether to clean up or upgrade to a larger plan.

What actually takes up space on a WordPress site

A clean WordPress installation with no content weighs very little. According to a guide published by Pasquale Ricciardi, a basic WordPress installation takes up minimal space—generally less than 100 MB across core files, theme, and essential plugins. Everything else filling your quota is:

• Media library: images, PDFs, videos uploaded to the wp-content/uploads folder. This is almost always the heaviest item on any site that's been around for a few years.
• Database: posts, pages, comments, metadata, theme and plugin settings, user data. According to technical guidance, the WordPress MySQL database stores all site-related data—posts, pages, metadata, theme and plugin settings, user credentials and so on—and this database grows exponentially with your site's content.
• Cache: files generated by optimisation plugins. These usually self-manage but consume space in the meantime.
• Local backups: if a backup plugin saves copies to the same hosting instead of external storage, it duplicates the entire site with each run.
• Logs and leftover files from uninstalled plugins, which continue taking up space even after removal because they often leave behind files and configurations that aren't automatically deleted, accumulating over time.
• Email, if your hosting shares the same disk quota for webmail and site: on many cPanel installations, mailbox space counts towards the same total.

The database: where the real weight hides

The database is rarely "large" in absolute terms, but it can slow your site well before filling the disk. The key thing to check is autoload in the wp_options table: data loaded on every page request, even if no plugin uses it any more. A database optimisation guide shows the query to run in phpMyAdmin to measure it:

SELECT SUM(LENGTH(option_value)) as autoload_size FROM wp_options WHERE autoload = 'yes';

The reference thresholds are: under 1 MB, no problem; between 1 MB and 3 MB, worth cleaning up; above 3 MB, the database is almost certainly one of the causes of slowdowns. The worst case observed by the guide's authors: sites with over 5 MB of autoload data, loaded entirely on every pageview before WordPress does anything else. The reason this data persists is simple: when a plugin is uninstalled without cleaning up its own data, the options remain in the table with autoload active.

The same applies to transients (temporary data with expiry dates): WordPress only removes them when requested after expiry, not through an active cleanup process, and on sites with irregular traffic or many plugins using transients, expired data accumulates in wp_options.

How to read the disk usage report in your hosting control panel

On cPanel, the report is called "Disk Usage" and sits in the Files section. A guide from Artera describes its structure: the system shows a resource usage summary on the main screen with a progress bar and colour coding—green for healthy, yellow for monitoring, red for critical. Within the Disk Usage section detail, data is divided by category: "MYSQL" shows database space, "Email Archives" shows archived mail space, "Email Accounts" shows total space for all active email accounts, and "Other Usage" shows system file space.

One detail not to overlook when comparing the report number against what "you'd expect": the value doesn't include files outside your home folder, so any additional storage or mounts won't appear in that figure.

On automatic alerts, the same provider explains how they're sent: the system periodically monitors space usage and sends automatic alerts at 80%, 90%, and 100% usage to the email address linked to your cPanel account. This is why the alert arrives before the site stops working: it's not an error, it's the threshold set by your provider.

How much space you actually need

There's no single number, but there are verifiable orders of magnitude. A table published by Shellrent suggests these average sizes:

Site type	Average size
5-page portfolio with optimised images	300–500 MB
Business showcase site	500 MB–2 GB
News portal or online magazine	over 5 GB
E-commerce with large product catalogue, images, and order history	over 10 GB
Site with multimedia content (video/audio) or user uploads	over 10–20 GB

Source: average website sizes by type, data published by Shellrent. These figures should be taken as guidance, not limits: the values are indicative and vary based on file optimisation, volume, and update frequency.

For those running a WooCommerce store, a more recent guide confirms the order of magnitude and explains why: an online shop consumes the most space because each product has multiple images—sometimes 5–10 per item—the database grows with orders, reviews, and customer data, and for a medium catalogue of a few hundred products, it's prudent to start with 10 GB, while larger catalogues or high-traffic stores may need 20 GB or more.

For a reference on real production sites, a managed host like Kinsta has published client examples: one customer with 3 WordPress sites uses 503.21 MB of a 15 GB allocation—significantly below Kinsta's average and using less than 200 MB per site. This is useful data showing that many 10–20 GB hosting plans remain largely unused on typical sites: when there is a problem, it's almost always concentrated in a single item (unoptimised media, accumulated local backups, database autoload), not the sum of everything.

When to worry

Three concrete signals, in order of urgency:

1. Alert at 90% or 100% from your provider: at that point, backups, cache, and plugin updates can fail for lack of temporary space, even if the site stays online.
2. wp_options autoload over 3 MB: this isn't a space problem but a speed one, and should be fixed anyway according to the thresholds noted above.
3. Anomalous "Other Usage" in your cPanel report: often local plugin backups, unrotated logs, or temporary files not cleaned up after an update—categories you won't spot scrolling through the media library.

If none of these three signals are present and space used stays under 70–80% of your plan, there's no urgency: still worth checking autoload size once though, because it affects performance before it affects disk space.