Residential proxy pricing: what a GB buys for your job

Originally published on proxymint.

Residential proxy pricing per GB explained: what a GB buys in pages, traffic per 1,000 pages, expiry and run-outs, and when another tier fits the job better.

TL;DR

• proxymint sells residential per GB. Packages are one-off with no renewal, and the rate drops as the package grows.
• A GB means pages only once page weight is known. At the 22 KB median HTML size one GB is about 45,000 pages; at the 1.8 MB median mobile inner page it is about 550 full renders.
• 1,000 pages move as many GB as one page weighs in MB. Full renders at 1.8 MB move about 1.8 GB per 1,000 pages, and the fetch method moves that far more than the package size does.
• Nothing renews and no expiry is set on the GB. A package bought for a quarterly job is still on the balance for the next run.

Key takeaways

• Budget in pages, not GB. Fetch 20 representative pages through the real client, average the bytes and multiply by the page count, plus 20-30% headroom.
• Pick the fetch method before the package size. HTML or JSON instead of a full render cuts the traffic per page by one or two orders of magnitude.
• Size the package to the job. Read the rate for that quantity on the pricing page.
• Buy one package per job. One package sized to the job means one order and one balance to watch.
• Match the tier to the job. Lenient bulk work fits datacenter ports, and fixed-address work fits static ISP IPs.

Read the full guide on proxymint, with the commands, tables and sources.