How Much Hosting Do You Need? Storage, Bandwidth and Resources
How to estimate the disk space, bandwidth, inodes and email storage your website really needs, with worked examples for a brochure site, a blog and a small online shop.
Table of Contents
Most small websites need much less storage and bandwidth than hosting plans advertise: a typical business site with a few dozen pages often uses well under 2 GB of disk space and a modest amount of monthly transfer. The numbers that usually run out first are inodes (the file count), email storage, and CPU or process limits, not raw disk space.
This guide shows how to estimate each figure for your own site rather than guessing.
Storage: what takes up space
Disk usage on a hosting account comes from four places:
- Website files: application code (WordPress core is a few tens of megabytes), themes, plugins and uploaded media. Media is almost always the largest part.
- Databases: usually small for content sites, often tens to a few hundred megabytes, but they grow with orders, logs and revisions.
- Email: mailboxes on the same account count against your quota and can grow by gigabytes a year.
- Backups and leftovers: old backup archives, cache folders and log files that nobody cleans up.
How to estimate
- Existing site: check the current host's disk usage page, or the size of a full backup.
- New site: estimate pages × images per page × average image size, then add the application and a database allowance.
Images decide the size
A site with 50 pages and 10 well-optimised images per page at about 150 KB each uses roughly 75 MB of media. The same images uploaded straight from a phone at 4–5 MB each would need more than 2 GB. Optimising images matters more than buying a bigger plan; see WordPress image optimization.
Bandwidth: how much traffic you will transfer
Bandwidth (data transfer) is the amount of data the server sends to visitors per month. A simple estimate is:
monthly bandwidth ≈ monthly page views × average page weight
Page weight is the total size of everything a page loads: HTML, CSS, JavaScript, fonts and images. You can see it in your browser's developer tools (Network tab) or in tools such as PageSpeed Insights.
| Example | Page views/month | Average page weight | Estimated transfer |
|---|---|---|---|
| Brochure site | 5,000 | 1.5 MB | about 7.5 GB |
| Active blog | 50,000 | 2 MB | about 100 GB |
| Small online shop | 30,000 | 2.5 MB | about 75 GB |
Returning visitors load fewer files thanks to browser caching, and a CDN serves images from its own network, so real transfer from your server is often lower than this. Add generous headroom for bots, crawlers and traffic spikes.
Inodes: the limit people forget
An inode is one file or folder. Plans often cap the number of inodes per account, for example in the hundreds of thousands. Things that consume inodes quickly:
- cache plugins that write one file per page variant;
- email, because many mail systems store each message as a separate file;
- image plugins that create several resized copies of every upload;
node_modulesfolders or unused application copies left on the server.
Your control panel shows the current inode count. If it creeps towards the limit, clean out old caches, backups and email folders.
Email storage
If you host email on the same account, estimate it separately:
mailboxes × expected size per mailbox
A busy mailbox can reach several gigabytes within a year or two. Set quotas per mailbox and archive old mail, or use a separate email service for larger teams. Setup on your phone and laptop is covered in how to set up email on your phone and Outlook.
CPU, memory and processes
Storage and bandwidth tell you how much the site holds and sends; CPU, memory and process limits decide how many visitors it can serve at once, especially for dynamic sites like WooCommerce. These limits are explained in hosting resource limits explained.
Worked examples
A local business website (15 pages, contact form, 3 mailboxes): about 300 MB of files, a 30 MB database and a few GB of email after a year. An entry-level shared plan is usually enough.
A content blog (400 posts, many images): 3–6 GB of media if images are optimised, a few hundred megabytes of database, and moderate bandwidth. Caching matters more than disk space.
A small online shop (500 products, several images each): media of several GB, a growing database, and CPU spent on logged-in customers and checkout. Choose a plan with comfortable process and memory limits; see WooCommerce hosting requirements.
Frequently Asked Questions
What happens if I exceed my storage or bandwidth?
It depends on the host: uploads and new email may fail when storage is full, and some hosts throttle or suspend accounts that exceed transfer limits. Check the plan's terms and keep an eye on usage.
Is unlimited bandwidth really unlimited?
Usually it means there is no fixed monthly cap, but fair-use rules and CPU and process limits still apply.
Should I buy more storage than I need?
Buy for the next year plus headroom, on a plan you can upgrade easily. Paying for unused resources rarely helps performance.
Choose a plan
Once you have rough numbers, compare them with the ServerNeed shared hosting plans. For the fundamentals of how hosting fits together, see what is web hosting.
Sources
Last updated 7 October 2026
