How Many Proxies Do I Need?
Updated:
The number of proxies you need depends on the job. For accounts, the basic rule is one fixed IP per important account, so your IP count roughly equals your account count. For scraping, it depends on how many requests per minute you need and how many requests a single IP can send to the target site before being rate-limited. For teams, you add up each person's needs and make sure nobody ends up sharing an IP across different accounts. This guide gives a formula for each case, worked examples and a way to add a buffer so you neither underbuy nor overbuy.
Start with what the proxies are for
The three common workloads use three different calculations. Do not apply a scraping formula to account management or the other way round: accounts need stable IPs tied to each identity, while scraping needs requests spread across many IPs.
| Workload | Unit | Basic formula |
|---|---|---|
| Managing multiple accounts | Accounts | Important accounts plus groups of minor accounts plus a buffer |
| Scraping, price monitoring | Requests per minute | Total requests per minute divided by safe requests per IP per minute, plus a buffer |
| Teams | People and profiles | Sum of each person's needs, with no IP shared between accounts |
Counting proxies for multiple accounts
Social and e-commerce platforms use the IP as one of several signals to spot related accounts. The safest approach is one dedicated IP per account, kept fixed. For ad accounts, shops with revenue and long-running accounts, treat this as a rule.
For low-value secondary accounts, some people group a few accounts on one IP to save money. That raises linking risk: if one account is reviewed, others on the same IP may draw attention. What is tolerated varies by platform and changes over time, so read the platform's rules and test small. For Facebook specifically, see our analysis of how many Facebook accounts per IP.
- Example: 5 ad accounts, 10 shops and 30 minor accounts split into 10 groups. You need 5 + 10 + 10 = 25 IPs, plus 2 or 3 spares.
- IP type: put ad accounts and large shops on ISP proxies and the rest on dedicated IPv4. Our IPv4 versus ISP task guide has a quick table.
Counting proxies for scraping
For scraping, IPs do not need to map to identities; you need enough of them that no single IP sends too many requests to one site. Every site has its own unpublished threshold, so you have to measure it.
Pick one IP, send requests at increasing rates and note when 429 errors, CAPTCHAs or block pages appear. Step back to a safe rate below that point. Then divide the requests per minute you need by the safe requests per IP per minute. Our guide to web scraping rate limits goes deeper.
- Example: you need 6,000 pages an hour, which is 100 pages a minute. Testing shows one IP is comfortable at about 10 pages a minute on that site. You need roughly 10 IPs, plus 2 spares.
- Need fewer IPs: cache responses, fetch only what you need, skip unchanged pages and spread requests across the day.
- Managing the list: with many IPs you need rotation and a way to drop failing ones. See proxy pool management.
Counting proxies for a team
A common mistake is handing one list of IPs to the whole team without recording which IP belongs to which account. Two people end up using the same IP for different accounts, or one account logs in from several IPs in a day.
List each person, their accounts and threads, calculate their needs as above and add them up. Then pin each IP to a profile in your antidetect browser or shared sheet so it belongs to exactly one account. See how to share proxies with a team safely.
How much buffer to add
Spares keep work moving when an IP fails, a new account is needed or one site blocks a particular IP. There is no standard number; base it on how critical the work is.
- Small tests: no buffer, buy more when needed.
- Revenue accounts: keep a few unused IPs of the same type and country ready.
- Continuous scraping: keep some extra IPs so you can drop blocked ones without losing throughput.
- Note: spares must be renewed on time too if you want to keep them. See how to renew a proxy and keep the same IP.
Start small and scale on real data
However carefully you calculate, the numbers are assumptions. Buy a small batch, run your real workload for a few days, measure errors and speed, then buy the rest. Check each batch with the proxy checker on arrival.
At VinaProxy you can buy from a single IP, choose the type (dedicated IPv4 in seven countries or static ISP in Vietnam and the US) and country per order, and add more later. Each IP goes to one customer with unlimited bandwidth, so the IP count is the only thing that drives cost. Current prices are on the pricing page.
Frequently asked questions
Does every account need its own proxy?
Important accounts such as ad accounts, shops and long-running profiles should each have one fixed IP. Minor accounts can be grouped, but the linking risk is higher.
How many IPs do I need for scraping?
Divide the requests per minute you need by the safe requests per IP per minute for that site. You have to measure the safe rate because every site differs.
Is buying extra proxies wasteful?
It is if you overbuy by a lot. Keep a small buffer based on how critical the work is and buy more when real data shows you need it.
Can one proxy be used on several devices?
Technically yes, since it uses username and password authentication. But if those devices log into different accounts, the accounts share an IP, which you should avoid for important ones.
Should I buy IPv4 or ISP when I need many proxies?
Most of a large order is usually dedicated IPv4 because the price per IP is lower. Reserve ISP proxies for your most valuable accounts.
Buy exactly the IPs you need
Start from one IP, choose type and country per order, add more as you grow. Unlimited bandwidth, automatic activation.
View pricing