Image storage and transfer planner

Plan an image-heavy portfolio with your own file-size, upload, retention, and traffic assumptions. This rough estimate covers image files only; it is not a provider quote or a recommendation that a plan will fit.

Enter the first five workload values. Leave the three inventory fields at 0 if they do not apply.

How the estimate works

Steady-state image storage (GB) = average image size (MB) × new images per month × retention months ÷ 1,000. The model assumes uploads continue at a constant rate and each image is deleted after the retention period.

Monthly image transfer (GB) = average image size (MB) × average images loaded per page view × monthly page views ÷ 1,000. It assumes each counted image transfers its full entered size on each page view.

Current media inventory scenario = measured live media-folder size + any retained originals on the same account that are outside that folder. Backup storage scenario = that live inventory × the entered number of full backup copies. The combined figure adds the live inventory and those copies. Enter the folder size from a provider dashboard or file measurement that matches your question, and count only copies that include both entered media amounts.

For example, if your own measurements are 2 MB per file and 3 images per page view, enter those values along with your monthly uploads, retention period, and page views. The result is conditional on your inputs; it is not a typical portfolio or traffic benchmark.

Scope and limits

This planner uses decimal units: 1 GB = 1,000 MB. NIST defines SI prefixes such as mega and giga as decimal powers. Provider dashboards may use other display conventions, rounding, or measurement windows, so compare like units.

The steady-state storage figure is a separate upload-rate scenario; do not add it to the measured inventory unless you have established that the readings cover different files. The measured inventory uses the folder size you enter, so it can already include generated image sizes and thumbnails. It excludes files outside that folder unless you enter them as retained originals. The backup scenario assumes every entered full copy contains the two entered media amounts at their uncompressed measured sizes; it does not model databases, compression, incremental backups, excluded directories, or off-account copies. The transfer figure excludes HTML, CSS, JavaScript, video, downloads, bots, cache effects, and CDN behavior. Caching can reduce some origin transfers; cache misses and other requests can increase measured use. Neither output determines a suitable plan.

Provider terms can include storage, file-count, CPU, or transfer conditions. As one dated example, Bluehost's account limits summary describes shared-hosting bandwidth as unmetered while also listing separate account resource limits. Its disk-usage guidance describes account reporting; this does not establish rules for other providers or plans. Both pages checked November 3, 2026. Read the terms for your exact plan and compare them with its account dashboard.

Sources

• NIST Guide to the SI, Chapter 4 — decimal SI prefixes; checked November 3, 2026.
• Bluehost Account Limits Summary — updated October 8, 2026; describes shared bandwidth and account resource limits.
• Bluehost disk-space and bandwidth usage guidance — account reporting; checked November 3, 2026.
• WordPress Media Library screen — describes media and the uploads directory.
• WordPress backup documentation — explains that a typical full-site recovery needs both files and the database, and identifies uploads among WordPress files.

For a separate monthly page-transfer example and provider-term checklist, see bandwidth limits and monthly transfer. For a user-entered estimate from page views and average page size, use the hosting needs estimator.