The short answer
A full web page loaded in a browser uses about 2 to 3 MB. A plain HTML or API request uses about 20 to 200 KB. Multiply by how many pages you load a month, add 20% for retries, and you have your pack size. Most small projects fit in 2 to 10 GB a month.
The page weight comes from the HTTP Archive Web Almanac, which measures the median mobile home page at a little over 2 MB. Your own targets may be lighter or much heavier.
Rough figures by task
| Task | Data per action | 1 GB is roughly |
|---|---|---|
| Scraping HTML only (no browser) | 50 to 200 KB per page | 5,000 to 20,000 pages |
| Calling a JSON API | 5 to 50 KB per call | 20,000 to 200,000 calls |
| Headless browser, images blocked | 0.5 to 1 MB per page | 1,000 to 2,000 pages |
| Full browser, everything loaded | 2 to 5 MB per page | 200 to 500 pages |
| Social media app session, 10 minutes | 30 to 150 MB | 7 to 30 sessions |
| Watching or checking video ads | 5 to 20 MB per ad | 50 to 200 ads |
These are estimates to plan with, not promises. Measure your own traffic using the steps below before you buy a big pack.
How to measure your real usage
- Buy the smallest pack and run your normal job for a day.
- Check the dashboard. Most sellers show how much data you have used.
- Divide by the number of pages or actions you ran. That is your real cost per action.
- Multiply by your monthly volume and add 20% for retries, failed pages and growth.
In a browser you can also open the developer tools, go to the Network tab and reload the page. The total at the bottom shows how much one page transferred.
A worked example
Say you check 300 product pages a day with a headless browser, with images blocked.
- One page uses about 0.8 MB.
- 300 pages a day is 240 MB a day.
- Over 30 days that is about 7.2 GB.
- Add 20% for retries and you need about 8.6 GB a month.
Load the same pages with images and you could need three or four times as much. The way you load pages matters more than the number of pages.
Seven ways to use less data
- Skip the browser when you can. If the data is in the HTML or an API, a plain HTTP request is 10 to 50 times lighter.
- Block images, fonts and video in headless browsers. In Playwright, route those resource types to
abort. - Block trackers and ad scripts unless you are checking ads.
- Send only the traffic that needs it through the proxy. Static files from a CDN often load fine without one.
- Turn on compression. Send
Accept-Encoding: gzip, brso pages arrive compressed. - Cache what does not change. Do not download the same page twice in a day.
- Stop retry loops. A broken script that retries forever can burn a pack overnight. Cap retries at two or three.
Picking a pack size
Per-GB prices fall as packs grow, so it is tempting to buy big. Only do that once you know your usage. Start small, measure for a week, then buy the pack that covers about a month to three months of work.
Proxare sells mobile proxy data in prepaid packs that stay valid for 12 months, so unused GB do not disappear at the end of the month:
| Pack | Price | Per GB |
|---|---|---|
| 2 GB | $4.49 | $2.25 |
| 10 GB | $18.99 | $1.90 |
| 100 GB | $169 | $1.69 |
| 1,000 GB | $1,490 | $1.49 |
Card prices in USD, checked October 2026. Crypto is 5% cheaper, and a 1 GB trial is $2.49 with crypto.
For how this compares with paying per port, see mobile proxy pricing.
Frequently asked questions
Does the proxy count upload and download data?
Usually yes. Most sellers count all traffic in both directions. Downloads are almost always the larger part.
Why did I use more data than I expected?
The usual causes are images and video loading in a browser, retry loops, and pages that keep loading data in the background. Block what you do not need and cap retries.
Is 1 GB enough to test mobile proxies?
For a test, yes. 1 GB is enough for a few hundred full pages or thousands of light requests, which is plenty to see whether a target accepts the IPs.
Buy mobile proxies here
Real carrier IPs, sold per GB on Proxare. From $1.49 per GB, packs from 2 GB, card or crypto.