For a small informational site, estimate monthly data transfer from page views and the bytes actually transferred for each view. Then compare that estimate with the exact plan’s definitions and usage policy. A transfer estimate is a planning input; it cannot tell you whether a provider will accept a workload under a plan’s terms.

A defined, illustrative workload

Assume one informational site receives 1,000 page views in a billing month and transfers an average of 0.8 decimal MB of page content per view. The simple estimate is 1,000 × 0.8 MB = 800 MB, or 0.8 decimal GB for that month. These are example inputs, not an industry benchmark, traffic forecast, or recommended hosting allowance. Replace them with measurements from your own analytics and hosting account.

For planning, calculate monthly transfer (GB) = monthly page views × average transferred page size (MB) ÷ 1,000. This page uses decimal units: NIST lists mega as 10⁶ and giga as 10⁹, so 1,000 MB equals 1 GB under this convention. A provider dashboard may display units or rounding differently; check its documentation.

Bandwidth and monthly transfer are different

In everyday hosting plan copy, “bandwidth” is often used for the amount of data transferred over a period. In networking, bandwidth can also mean a data-transfer rate. A monthly transfer estimate is a volume over a billing window; it does not estimate peak requests per second, server capacity, page speed, CPU use, or memory demand.

Use the page-view bandwidth calculator to model page views, transferred size, and an explicitly entered cache share. The simpler hosting needs estimator changes page-view and page-size assumptions without a cache input. Both are scenarios; measure actual transfer in the host’s dashboard and check what traffic that dashboard includes.

“Unmetered” does not answer every limit question

Provider terms define what a plan measures and what happens when use affects shared resources. For example, Bluehost’s account-limits summary describes shared hosting bandwidth as unmetered, while its usage policy says unmetered resources are not infinite and remain subject to its Terms of Service and Acceptable Use Policy. Its high-traffic guidance also notes that shared CPU and memory resources can affect performance. This is one provider’s policy example, not a rule for every host or plan. The linked Bluehost pages were checked November 3, 2026.

Check the plan before relying on a headline allowance

1. Open the terms for the exact plan and account type. Record the billing month or measurement window and whether the allowance is a hard cap, metered charge, fair-use condition, or unmetered description.
2. Check which directions and services count: visitor downloads, uploads, backups, email, staging, and CDN-origin traffic may be treated differently. Do not assume an item is included unless the provider says so.
3. Find the account’s bandwidth or transfer report. Confirm its date range, units, refresh delay, and whether it reports the same services the plan terms cover.
4. Read the response to high use: overage fees, throttling, requests to reduce use, temporary restrictions, or plan changes. Ask support for a written explanation if a term is unclear.
5. Compare the measured billing-period usage with the plan rule and keep a margin for traffic variation. A buffer is your planning choice, not a prediction of growth.

For hosting and domain costs over time, use the website cost calculator; it accepts your own prices and does not infer plan suitability. See the hosting plan cost method for a separate example comparing prepaid introductory terms with renewals.

Sources checked November 3, 2026

• NIST Guide to the SI, Chapter 4 — SI decimal prefixes, including mega (10⁶) and giga (10⁹).
• Bluehost Account Limits Summary — describes its shared-hosting bandwidth terms and separate account resource limits.
• Bluehost usage policy — explains its use of “unmetered” and that use remains subject to Terms of Service and Acceptable Use Policy.
• Bluehost guidance on high website traffic — discusses shared resource effects and its unmetered-bandwidth explanation.