How Many Proxies Do You Need to Cop Sneakers?

The most common copping mistake isn't the bot or the proxy type — it's not having enough IPs. Here's the simple math for how many proxies a drop actually needs.

Coppers spend hours debating which bot and which proxy type to buy, then lose the drop for a boring reason: they did not have enough IPs. Too few proxies for too many tasks quietly recreates the exact per-IP purchase cap you bought proxies to beat. The good news is the math is simple, and once you know it you stop guessing — and stop cramming ten tasks onto three IPs and wondering why they all got banned together.

The core rule: one clean IP per task

Retailers cap purchases per IP and per account, so every checkout task needs its own dedicated IP to look like an independent buyer. That gives you the baseline number:

Count your tasks, not your accounts. If you run 25 tasks on a drop, you need at least 25 clean IPs — one per task — so no two attempts share an address.
Add headroom for retries and burns. Some IPs get flagged mid-drop; a buffer (roughly 20–30% extra) keeps every task on a clean address.
Match the type to the site. Those IPs should be residential for Shopify/SNKRS and ISP for footsites — the count rule is the same, the type follows the site.

Diagram showing tasks mapped one-to-one to clean IPs with a buffer for burns, versus many tasks crammed onto few IPs getting capped — Count tasks, not accounts: one clean IP per task, plus a buffer for burns. Cram tasks onto few IPs and the per-IP cap links them.

Residential is priced by bandwidth, not IPs

Here is the nuance that trips people up. Residential proxies are usually sold by gigabytes of traffic, not by a fixed number of IPs — you draw as many IPs as you need from a large rotating pool and pay for the data you use. So the real question for residential is not 'how many IPs can I buy' but 'do I have enough bandwidth for my task count.' Sneaker checkouts are lightweight, so a modest data plan covers a lot of tasks; you just want a pool big enough that every task gets a fresh, unique IP.

ISP proxies, by contrast, are typically sold as a fixed set of static IPs — so there you do buy a specific number, one per task you plan to run on footsites.

A simple sizing guide

Casual (a few pairs): 5–10 clean IPs, one per task, residential for most sites.
Serious (double-digit pairs): 25–50+ tasks means 25–50+ IPs, plus a burn buffer, split residential/ISP by site.
Group/cook scale: a large residential pool (measured in bandwidth) plus a block of static ISP IPs for footsites, sized to your peak concurrent task count.

How QuantumProxies fits

QuantumProxies scales to whatever your task count demands: a large residential pool priced by bandwidth so you can draw a fresh IP for every task without buying a fixed list, plus static ISP proxies in the exact quantity your footsite tasks need. Start small on a free trial, size up to your real drop plan, and never lose a release again to the one number nobody talks about — how many clean IPs you actually had.

Size your proxy pool for copping

Start with a free trial, count your tasks, and give each one a clean IP with room to spare. The best bot in the world is still one entry if it's sharing an address.