> 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/proxidize-proxies/mobile-proxies/mobile-pergb.md).
# Mobile - PerGB
The **Mobile Per GB** plan is a monthly subscription to a data package that gives you access to Proxidize's shared U.S. mobile pool.\
Instead of paying per proxy, you choose a data package and use it across as many proxies as you like. It's ideal for variable workloads, short-term campaigns, and large-scale scraping and automation.
Mobile proxies are U.S. only. Available package sizes run from 50 GB up to 20,000 GB. Per GB and data does **not** roll over. Your package is to be used within its billing period.
To change your data, you manage your package subscriptions: subscribe to an additional package to add more, or cancel a package to reduce (your remaining GB stays available until that package's billing period ends). Each package is its own subscription with its own billing date.
***
### Access Points
You work with Per GB through **Access Points**: independent proxy configurations that all draw from the same data balance. You can create unlimited Access Points and delete them anytime (a deleted name can't be reused).
Each Access Point has its own:
* Protocol (HTTP or SOCKS5)
* Hostname type (IP or DNS)
* IP mode (Sticky or Randomize)
* Location (city or Random City)
* Authentication method (see below)
#### Authentication
When creating an Access Point, you'll choose how it authenticates, either via **User / Pass (Named)** or **IP Whitelist**.
* **User / Pass:** enter an Access Point name (letters, numbers, and underscores only); credentials are generated automatically.
* **IP Whitelist:** authenticate by approved public IP. Each whitelisted IP creates one dedicated Access Point, with its configuration (protocol, hostname, IP mode, location) set at creation. If your public IP changes, add the new one or access stops.
**IP Whitelist Configuration**
IP Whitelist Access Points include a **Configuration** section where you can set the following options directly at creation:
* **Proxy Type:** HTTP or SOCKS5
* **Hostname:** IP or DNS
* **IP Mode:** Random or Sticky
* **Location**
These settings apply specifically to the IP Whitelist Access Point and determine how proxy traffic is routed for requests originating from your whitelisted IPs.
{% hint style="warning" %}
**Note:** IP Whitelisting authenticates based on your source public IP address. If your public IP changes (e.g. due to ISP reassignment, VPN usage, or network changes), access will stop working until the new IP is added to the allowlist. For frequently changing IP environments, User/Pass may be more reliable.
{% endhint %}
***
### Getting your proxies
All of your proxies are listed together under the **Formatted Proxy List** section of the dashboard. There, you'll be able to see every proxy in one place, choose your protocol and format, and copy them individually or export in bulk (batches of 10, 20, 50, or 100). Formats:
* `IP:Port:Username:Password`
* `Username:Password@IP:Port`
To build a mixed list with different settings per batch (country, city, ISP, protocol, stickiness, Access Point), use the [Session Builder](/proxidize-proxies/pergb-session-builder.md) and export it all as one list.
***
### Changing your IP
Per GB has no rotate button and no rotation URL. To get a new IP, change the **session key** in your credentials, or select a different proxy from the pool. Use **Refresh Session IDs** to regenerate all session credentials at once.
* **Sticky IP:** the same IP for the duration of a session, identified by a session key. Mobile sticky IPs are carrier-controlled and typically hold \~1–4 hours.
* **Randomize IP:** a new IP on every request; best for scraping and high-volume automation.
### Generating additional proxies
Per GB gives access to the full pool, so there's no fixed proxy count. In **Sticky IP** mode, the username contains a session segment in the format `-s-<10-character token>`. Change that token to any other value to get a different proxy from the pool. You can script this to build large proxy lists automatically.
***
### Targeting
City-level targeting across major U.S. cities, with all locations accessible at once via separate Access Points. Use **Random City** to rotate across available U.S. cities. Carrier selection works the same as elsewhere on Mobile, choose a carrier or select **Fastest**.
***
### Port mapping
Control how ports are assigned to your proxies using the **Port Mapping** dropdown in the dashboard toolbar.
Two modes are available:
* **Static:** Ports are fixed and do not change between sessions.
* **Dynamic:** Each proxy is assigned a dedicated HTTP and SOCKS port automatically. Ports follow a standardized order, making them easier to scan and validate across your proxy list.
**Dynamic Port Ranges**
| Protocol | Range | Order |
| -------- | ------------- | ---------- |
| HTTP | 18000 → 20000 | Descending |
| SOCKS | 20002 → 22002 | Ascending |
With Dynamic mode, every proxy gets its own unique port for both HTTP and SOCKS, no overlap, no ambiguity.
{% hint style="info" %}
Dynamic is recommended for most setups. The predictable port ordering makes it straightforward to cross-reference proxies in bulk exports or scripts.
{% endhint %}
***
## Basic cURL Example (Auto-Generated)
To help you test your proxy setup instantly, Proxidize displays a pre-filled CURL command based on your selected protocol (HTTP or SOCKS5). This command includes your proxy host, port, and credentials, making it easy to verify functionality from the command line.
**You can:**
* Copy and paste the command into your terminal for quick testing.
* Switch protocols to auto-generate a cURL snippet that matches your chosen settings.
* Use the example as a template when integrating proxies into scripts or tools.
This feature is especially useful for troubleshooting or verifying proxy connectivity without needing additional software.
***
### Related
* [Per Proxy vs Per GB](/proxidize-proxies/perproxy-vs-pergb.md)
* [Residential Proxies (also Per GB)](/proxidize-proxies/residential-pergb.md)
* [Setting Up Your Proxidize Proxies](/getting-started/setting-up-your-proxidize-proxies.md)
* [Proxidize API](/proxidize-rest-api/proxidize-api.md)
* [Upgrade or Downgrade your subscriptions](/account-and-billing/billing-and-subscriptions/how-to-upgrade-downgrade-or-change-your-subscription.md)
***
### Need Help?
If you have any questions, concerns, or need further clarification, feel free to reach out to us via live chat or email us directly at .
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.proxidize.com/proxidize-proxies/mobile-proxies/mobile-pergb.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.