Choose hosting capacity from current usage, growth, and working space
The key takeaway
For a WordPress blog, company site, or online store, article count alone cannot determine required capacity. Measure current usage counted against the plan, then add projected growth, peak temporary space for backups or migration, and planned sites. Finally, leave enough free space to respond without interrupting work.
Basic formula
Projected usage = current usage + monthly growth × months + planned additions
Required capacity = (projected usage + peak temporary space) ÷ (1 − target free-space ratio)
For example, with 8 GB in use, growth of 0.6 GB per month for 12 months, an 8 GB temporary backup on the same server, and a 15% free-space target, the requirement is approximately 27.3 GB. Start comparing plans at 30 GB or more. The result differs if the backup can be saved directly outside the plan's allowance or the host's backups do not count toward it.
What does hosting storage include?
Hosting capacity is the limit on data the account can store. What counts toward disk usage varies by provider and plan. Do not assess headroom from website files alone; check these four categories separately.
Website files
These include WordPress core, themes, plugins, original and generated images in uploads, PDFs, CSS, and JavaScript. WordPress creates multiple image sizes on upload, so original image totals alone do not represent actual usage.
Database
This can hold posts, pages, comments, users, settings, products, orders, sessions, and plugin data. Downloading the WordPress directory alone normally does not retrieve the MySQL or MariaDB database.
Email and logs
If email runs on the same host, inboxes, sent mail, attachments, and spam can grow. Access and error log retention also affects capacity.
Backups and temporary files
On-server backups, migration archives, caches, temporary update files, and staging environments also consume space. Even when the host's automatic backups do not count, ZIP or SQL files you create may count as ordinary files.
GB and GiB can produce different displayed values
One GB is one billion bytes; one GiB is 2 to the 30th power bytes. If a plan and control panel use different units, the same data can appear as different numbers. Small files can also consume more disk space than their actual sizes because of allocation units. Compare using consistent units, scope, and measurement times.

How to check WordPress and server usage accurately
Before calculating capacity, measure current usage under consistent scope and conditions. Record at least at the beginning and end of a month, preferably for three months or more, to see uneven growth from images or busy periods.
Total plan usage
Check account-wide disk usage and the limit in the hosting control panel. Ask support or consult specifications to see whether multiple sites, email, databases, and logs are included.
WordPress breakdown
In the WordPress dashboard, open Tools → Site Health → Info → Directories and Sizes to check WordPress, uploads, themes, plugins, and database sizes.
Growth drivers and temporary space
Inventory email, backup generations, staging, migration ZIPs, image regeneration, logs, and planned sites. Record normal usage separately from working peaks.
Scroll horizontally to view all columns.
| Where to look | What to record | Common misunderstandings |
|---|---|---|
| Hosting control panel | Account-wide usage, limit, and warning status | Totals may update with a delay. Check whether databases, email, and backups are included. |
| WordPress Site Health | Uploads, themes, plugins, database, and total installation size | It may not include all account email, other sites, or ZIP files in the home directory. |
| Email administration | Usage and limits by mailbox | Check sent mail, spam, attachments, and shared addresses as well as inboxes. |
| Backup settings | Coverage, destination, retention count, compressed size, and restoration method | Host-managed backups and backups you create may both exist. |
Optional commands if SSH is available
SSH may not be available on shared hosting. Command results may also cover a different scope from the plan quota. Use the hosting control panel for plan decisions and these commands as an aid to finding large directories.
Free hosting storage calculator
Enter current usage and growth to calculate normal projected usage, peak usage including backups or migration, and capacity including your target free-space ratio. The result is a minimum for comparing official specifications, not a recommendation for a particular plan.
There is no universal correct free-space ratio. Enter the maximum temporary capacity needed for the next update, migration, or backup and consider how long you need to respond after a warning. cPanel recommends at least 10% free space for an entire server, but for a shared-hosting plan prioritize your host's specifications and working requirements.
Hosting capacity ranges by site and use
These are starting points for comparison, not guarantees based on site type. Requirements vary greatly depending on whether images, email, and backups are external and whether multiple sites or staging environments share the account.
Scroll horizontally to view all columns.
| Capacity range | Possible uses | Conditions that make it workable | Often overlooked |
|---|---|---|---|
| 10 GB or less | Static sites, test environments, and small text-focused WordPress sites | Optimize images, keep email and backups externally, and add few sites | Temporary update, migration, and backup space can bring usage close to the limit |
| 20–50 GB | Company sites, general blogs, and small stores with few products | Record monthly growth and avoid hosting large amounts of video directly | Multiple backup generations, email, and staging can exhaust capacity |
| 50–100 GB | Multiple sites, photo-heavy blogs, and stores with growing product imagery | Manage generated images, logs, and backup retention and monitor regularly | Inode, database, CPU, or memory limits may be reached before storage capacity |
| 100–300 GB | Image-heavy media, medium-sized stores, many sites, and coexisting migration environments | Plan data storage, access, offsite backups, and recovery time | Shared-environment load, transfer, and usage restrictions apply separately from capacity |
| 300 GB or more | Large image archives, many sites, and large migration datasets | Consider how to divide responsibilities with object storage, CDNs, and video delivery services | Being able to store data is different from being able to deliver and restore it reliably |
Even at 100 GB, NVMe and SSD types, CPU and memory, PHP execution, databases, backups, transfer, and support differ. Do not choose on capacity alone; check requirements in the same comparison table.
Unlimited storage may still have conditions
Unlimited does not necessarily mean no limit for every use or condition. Terms or fair-use policies may address shared-environment stability, prohibit file-storage use, or provide for action against excessive use. Save the specifications and terms in effect when contracting and check the following limits.
File count and inodes
The number of files and directories may be limited even when storage space remains. Large numbers of generated WordPress images, caches, sessions, or small emails can reach that limit before the GB limit.
Database size and count
Website space and databases may have different limits or accounting. Check total size, per-database limits, number of databases, concurrent connections, and query load separately.
Mailbox limits
Individual mailboxes may have limits separate from the overall account. For mailboxes with many attachments, check how sent mail, spam, and trash are handled.
Backups and file-storage use
Check on-server backup retention count, coverage, duration, restoration fees, and how user-created backups are treated. Some services prohibit storing large files unrelated to the public website.
Prioritize what counts toward the allowance, inodes, databases, email, backups, behavior when limits are exceeded, and upgrade procedures over unlimited or large-capacity headlines. Ask the provider before signing if conditions are unclear.
Symptoms of insufficient server storage and a safe response order
When the limit is reached, operations requiring writes are affected first. Image uploads, post saves, updates, cache generation, logging, backups, and incoming email may fail. Creating another backup on the same full server can consume even more space with incomplete files.
Posts or images fail to save
Check usage, quota warnings, and error logs. Do not delete WordPress core, the active theme or plugins, or uploads without a reason.
Backups cannot be created
First confirm an existing valid backup and restoration method; use external storage or the host's restore function.
Email cannot be received
Check per-mailbox limits, large attachments, old sent mail, and spam; archive according to your retention policy.
Updates or migrations stop midway
Do not retry repeatedly. Prepare temporary space, a maintenance window, and rollback procedures before restarting.
Respond safely: record → identify → preserve → expand → verify
- 1Record usage, errors, and recent updates or migration work.
- 2Identify large backups, migration ZIPs, logs, caches, and email.
- 3Check whether items can be deleted and what recovery requires, then preserve them in a safe external location.
- 4If needed, consider an upgraded plan, additional capacity, another server, or external storage.
- 5Verify that saves, updates, backups, email, and monitoring alerts work again.
Measure capacity and page speed separately
More storage alone does not necessarily make a site faster, and high utilization alone does not always make it slower. Speed depends on server processing, the database, caching, image and JavaScript transfer, network, and real user conditions. Resolve shortages severe enough to cause write failures, but investigate speed separately with PageSpeed Insights and server logs.

Storage checklist before purchase and during operation
Go beyond an estimate: assign measurement locations, owners, warnings, and response deadlines. Before deleting data or changing plans, verify that a backup can be restored.
Accounting scope and limits
- How website files, databases, email, logs, and backups count toward the allowance
- GB or GiB units and control panel update time
- Inodes, database size and count, and mailbox limits
- How multiple domains and staging are included in totals
Current usage and growth
- Record the same scope at least twice a month
- Identify large categories such as uploads, databases, and email
- Check monthly growth and seasonal peaks
- Estimate 12 months ahead and planned additional sites
Working space and recovery
- Allow temporary capacity for updates, migration, and image regeneration
- Check backup destinations, retention count, coverage, and restoration method
- Decide what stops at the limit and whom to contact
- Check lead times for upgrades and migrations
Monitoring and operations
- Set contacts to receive usage alerts
- Check capacity numerically as well as by color
- Set a monthly review date, owner, and recording location
- Monitor capacity, speed, and data transfer as separate measures
Official sources reviewed
On July 28, 2026, we checked the following official materials on WordPress usage, backups, and image generation; cPanel storage, email, and free space; units; and speed measurement. cPanel is an example of an environment using that software, and not all hosting control panels calculate totals the same way.
- WordPress.org: Site Health screen
- WordPress Developer Resources: Backups
- WordPress Developer Resources: Responsive Images
- cPanel & WHM Documentation: Disk Usage
- cPanel & WHM Documentation: Email Disk Usage
- cPanel & WHM Documentation: How to Manage Your Hard Drive Space
- NIST: Prefixes for binary multiples
- Google for Developers: About PageSpeed Insights
Frequently asked questions about hosting storage
How many GB does a WordPress blog need?
Article count alone cannot determine it. Measure current website, database, email, and backup usage and monthly growth, then add a 12-month projection and temporary update and backup space. A small text-focused site with external backups can start comparing around 10 GB; sites with many images or emails may need 20–50 GB or more.
Is 30 GB enough for a company website?
It can be a candidate if current usage including email, images, backups, and staging fits within 30 GB with working space remaining. For company sites adding recruitment information, PDFs, project photos, multilingual pages, and email attachments, use monthly growth rather than a fixed number.
What percentage of storage should remain free?
No single figure fits every shared host. Decide based on the maximum temporary space required for the next update, migration, or backup and how long you need to respond to a warning. Use cPanel's 10% server-administrator recommendation as a reference, while prioritizing your provider's warning thresholds and your own work requirements.
Is assuming 1 MB per image enough?
Not necessarily. Size depends on format, dimensions, compression, and image content, and WordPress and themes generate multiple derived images. Upload representative images and measure the increase in uploads to establish a more reliable per-article estimate.
Is a server with more storage faster?
Capacity alone does not determine speed. Capacity is a storage limit; speed results from CPU and memory, database, caching, data transfer, network, and other factors. Check execution conditions for candidates and measure separately with PageSpeed Insights and server logs after launch.
What should I delete first when storage runs out?
First verify a valid backup and identify large items. Failed temporary backups, old migration archives, and unneeded caches or logs may be candidates, but check retention obligations and recovery requirements. Do not delete WordPress core, active themes or plugins, uploads, or the database without understanding them.
Related selection and operations guides
Choose capacity for growth and recovery, not just what fits today
Look beyond current website files to everything counted against the plan, including databases, email, logs, and backups. Record usage consistently and add 12 months of growth and temporary space for updates, migration, and recovery. Even with unlimited plans, check inode and use restrictions and measure capacity and speed separately.

Editorial and verification approach
Finite Field Editorial Team
We organize articles on web production, WordPress, and servers so readers can measure their own conditions and make decisions. We avoid expired prices, unsupported fixed capacities, false claims that capacity causes speed, and conclusions influenced by advertising; we identify official sources and calculation assumptions.