Page transfer estimator
See how page size and monthly page views affect data transfer.
Enable JavaScript to calculate using your inputs.
Your inputs stay in your browser. An estimate, not a quote.
How the calculation works
Estimated decimal GB = average MB × page views ÷ 1,000. The planning margin is added separately. This rough model excludes bots, downloads and API requests; caching and third-party assets can make hosting traffic differ from browser transfer.
Before you decide
Run a low, expected and high-cost scenario. Confirm contract terms and what is excluded, then keep the assumptions alongside your result. A precise calculation is only as useful as the figures you put into it.
Read the planning guides →Use the number as a decision aid.
What page transfer means
Page transfer is the data a browser downloads to display a page, including HTML, CSS, JavaScript, images and fonts. The original source image size may differ from the transferred asset after resizing and compression. Measure an actual page in browser developer tools when possible.
A worked estimate
A 1.5 MB page viewed 10,000 times represents roughly 15 decimal GB of browser transfer. Adding a twenty-percent planning margin gives 18 GB. The result is a capacity estimate, not a direct hosting bill, because providers count traffic differently and cached third-party assets may not use your allowance.
Traffic the model excludes
Bots, file downloads, video, APIs, admin activity and cache misses can add traffic. A page view can request different assets on mobile and desktop. Content delivery networks may absorb some transfer while still charging under their own terms. Compare the estimate with hosting measurements after launch.
Reduce weight deliberately
Resize images to their displayed dimensions, choose an appropriate format, remove unused scripts and avoid loading large assets on every page. Test appearance and function after each change. A smaller total is useful only when the page still communicates and works correctly.