> For the complete documentation index, see [llms.txt](https://help.proxidize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.proxidize.com/getting-started/choose-between-mobile-and-residential-proxies.md).

# Choose Between Mobile and Residential Proxies

Compare Proxidize Mobile and Residential proxies by coverage, plans, IP behavior, and use case to pick the right product for your workflow.

Proxidize offers two managed proxy products: **Mobile Proxies** and **Residential Proxies**. This guide helps you pick the right one based on where you need IPs, how hard they need to be to detect, and how you plan to use them.

If you're still learning the basics, start with [What are Proxidize Proxies?](/getting-started/what-are-proxidize-proxies.md)

### Quick answer

***

* **Choose Mobile Proxies** for the most authentic, hardest-to-block IPs, ideal for QA and app testing, ad verification, Market Research, and other. Available in the United States only.
* **Choose Residential Proxies** for broad global coverage across **195+ countries** with city and ISP targeting, ideal for scraping, monitoring, and geo-targeted work, especially outside the US.

### At a glance

***

<table data-search="false"><thead><tr><th></th><th>Mobile Proxies</th><th>Residential Proxies</th></tr></thead><tbody><tr><td><strong>IP source</strong></td><td>U.S. mobile network IPs</td><td>Real residential-ISP IPs</td></tr><tr><td><strong>Coverage</strong></td><td>United States only, state and city level</td><td>195+ countries, state, and city + ISP level</td></tr><tr><td><strong>Plans</strong></td><td>Per Proxy or Per GB</td><td>Per GB</td></tr><tr><td><strong>Protocols</strong></td><td>HTTP, SOCKS5</td><td>HTTP, SOCKS5</td></tr><tr><td><strong>IP behavior</strong></td><td>ISP-controlled; a sticky IP typically holds ~1–4 hours</td><td>ISP-controlled; a sticky IP typically holds ~1–3 hours</td></tr><tr><td><strong>Data</strong></td><td><ul><li>Per Proxy: unlimited with a 50 GB fair-use threshold</li><li>Per GB: pay per GB, no rollover</li></ul></td><td>Pay per GB, unused data rolls over and never expires</td></tr><tr><td><strong>Best for</strong></td><td><ul><li>ad verification.</li><li>mobile app/QA testing.</li><li>SEO/SERP Monitoring </li></ul></td><td><ul><li>Global/geo-specific browsing and scraping.</li><li>Travel/fare aggregation.</li><li>Global market research</li></ul></td></tr></tbody></table>

### When to choose Mobile Proxies

***

Mobile proxies route traffic through real devices on U.S. ISP networks. Because ISPs share IPs across many real users (CGNAT), mobile IPs are very hard for platforms to block, which makes them the strongest choice for any workflow that benefits from a genuine mobile identity.

They come in two plans:

* **Per Proxy:** a dedicated proxy with its own controls and rotation options (rotate button, scheduled interval, or rotation URL). Best for long-running workflows.
* **Per GB:** usage-based access to the shared mobile pool through Access Points. Best for variable or large-scale mobile workloads.

Mobile proxies are U.S-only. For any other country, use Residential. To compare the two plans in depth, see [Per Proxy vs Per GB](/proxidize-proxies/perproxy-vs-pergb.md).

### When to choose Residential Proxies

***

Residential proxies use residential-ISP IPs from a pool spanning 195+ countries, with city-level and ISP-level targeting. They're the right choice for:

* [Web scraping](https://proxidize.com/use-cases/web-scraping/) and large-scale data collection
* [Price monitoring](https://proxidize.com/use-cases/price-monitoring/) and [SEO monitoring](https://proxidize.com/use-cases/seo-monitoring/)
* [Market research](https://proxidize.com/use-cases/market-research/) and [AI/LLM data collection](https://proxidize.com/use-cases/ai-llm-training/)
* [Brand Protection Monitoring](https://proxidize.com/use-cases/brand-protection-monitoring/)
* Any work that needs coverage outside the United States

Residential is Per GB only, and unused data rolls over, it never expires.

### Still not sure?

***

* Need U.S. mobile IPs with the highest trust level, for example for ad verification or mobile app testing → **Mobile**
* Need a specific country outside the U.S., or the widest coverage → **Residential**
* Want the lowest entry price → **Residential Per GB**, our lowest perGB rate

Both products work with any proxy-compatible tool and are managed from your dashboard at [app.proxidize.com](https://app.proxidize.com). When you're ready, follow the [Quick Start](/getting-started/quick-start-with-proxidize-proxies.md).

### Related

* [What are Proxidize Proxies?](/getting-started/what-are-proxidize-proxies.md)
* [Quick Start with Proxidize Proxies](/getting-started/quick-start-with-proxidize-proxies.md)
* [Setting Up Your Proxidize Proxies](/getting-started/setting-up-your-proxidize-proxies.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.proxidize.com/getting-started/choose-between-mobile-and-residential-proxies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.