Skip to content
MinniHost Guides

Hosting Storage and Bandwidth Estimator

By Posted

Monthly transfer is visits × pages per visit × page weight, reduced by whatever share is served from a cache or CDN and raised by bot traffic. Storage is your files, database and mail, grown over time, plus the backup copies you keep. Page weight is yours to enter; the optional presets are the HTTP Archive Web Almanac medians for October 2024 (2.31 MB mobile, 2.65 MB desktop), not a typical figure for your site. The estimate does not predict a bill or reflect any host's allowances.

Bandwidth and storage estimator

Enter your own assumptions. Page weight is a labelled input; the presets are dated medians from public data, not your site. Nothing leaves your browser.

Traffic and storage

Your own figure, for example from your analytics.

Used when 'My own value' is selected. Measure it in your browser's Network tab.

Your assumption; empty counts as 0.

Your assumption; empty counts as 0.

1 means no spike. Empty counts as 1.

Your assumption; empty counts as 0.

Estimate

How the estimator works

Transfer and storage
transfer per month (GB) = visits × pages × page weight (MB) × (1 − cached%) × (1 + bot%) ÷ 1000
peak-month transfer = transfer × peak multiplier
storage(t) = (files + database + mail) × (1 + growth)^t + backups × (files + database) × (1 + growth)^t
t
years from now (0, 1, 2)
backups
number of full backup copies kept; each is assumed the size of files + database at that time

Worked example

Given: 10,000 visits a month, 2 pages per visit (example only); page weight 2.5 MB (example only); 40% cached, 20% bot overhead, peak multiplier 2.

  1. Raw transfer: 10,000 × 2 × 2.5 ÷ 1000 = 50 GB
  2. After cache and bots: 50 × 0.6 × 1.2 = 36 GB
  3. Peak month: 36 × 2 = 72 GB

Answer: About 36 GB a month, 72 GB in a peak month, with these example assumptions.

Page weight data

Median page weight, HTTP Archive Web Almanac 2024 (October 2024)
DeviceMedian page weightSource
Mobile 2,311 KBSource 1
Desktop 2,652 KBSource 1

Medians across the web, not a target. KB is converted to MB by dividing by 1000.

Assumptions and limits

  • Every percentage and multiplier except the preset page weights is your own assumption.
  • Caching, bots and spikes vary by site; use your analytics or host reports where you have them.
  • The estimate says nothing about your host's allowances, plan names or overage rules. Compare it with their documentation.
  • Email, logs, temporary files and database overhead can add to storage.

Your questions answered

Where do I find my real page weight?

Open your page in a browser's developer tools, go to the Network tab, reload and read the total transferred size. Test a few typical pages and average them.

What is the cached share?

The portion of bytes that do not come from your host because a browser cache or CDN served them. If you do not use a CDN, a low value such as 0 to 30 is a cautious planning choice; this is your assumption, not a measured fact.

Why add bot traffic?

Crawlers and automated requests also use transfer. The percentage is your own assumption; your host's or CDN's traffic reports show the real share.

How big a plan limit do I need?

Compare the monthly and peak figures with the transfer and storage limits your host publishes. This page does not know any host's limits.

Does "unlimited" mean no limits?

Not necessarily. Read the host's terms for fair-use, inode and resource limits. This estimator makes no claim about any plan.

Is a GB 1000 or 1024 MB?

This page uses 1 GB = 1000 MB. Plans differ in how they count, so leave some headroom.

Where this comes from

  1. HTTP Archive, Web Almanac 2024, Page Weight chapter (median page weight, October 2024) (almanac.httparchive.org) Opened 2026-11-17. The 2025 chapter was also opened, but its median figures were not used because the page gave them without a clear month.

More on this topic