The Proxy Generator, Explained

The first selector decides which credentials go into your lines. The platform keeps two independent credential sets, and they are not interchangeable.

• Pay-per-GB — the credentials attached to your metered data balance. Traffic on these lines draws down the GB you have bought.
• Unlimited plan — credentials issued with a flat-rate unlimited plan. They exist separately from your GB credentials and bill against the plan, not your data balance.

Unlimited plans themselves — and the separate credentials that come with them — are purchased on the Unlimited Proxies page; the generator only consumes credentials you already hold. If you hold both sets, confirm the source before exporting. A list built from the wrong set still works, but it bills the wrong plan — and the mismatch is easy to miss until you check usage in the dashboard.

Rotating is the default. Every request through a rotating line exits from a different IP, which suits broad collection of public data where no request depends on the one before it.

Sticky pins one IP for the life of a session. The generator does this by writing a session id into the username (-s-abc123) plus an optional TTL in seconds (-ttl-600). Sessions default to 60 seconds and can run up to 86,400 seconds — twenty-four hours. Pick sticky when a workflow spans multiple requests that must come from a single address; the mechanics and TTL behavior are covered in sticky sessions.

Targeting narrows where your exit IPs sit, and the generator encodes it as username suffixes: -cc-US for a country, -co-EU for a continent (country and continent are mutually exclusive), -ct-Dallas for a city, -asn-13335 for a specific network. City names drop spaces and diacritics — São Paulo becomes SaoPaulo. Targeting stacks with the sticky parameters in one username, for example user123-cc-US-s-mysession-ttl-600. The full syntax and combination rules are in the geo targeting guide.

The quantity field accepts anything from 1 to 50,000 lines, so the same page covers a single browser proxy and a bulk export for a large job.

Seven output formats are available. Six are fixed:

• user:pass@host:port — the URL-style form most HTTP clients accept
• host:port:user:pass — the colon-separated form common in bulk tools
• http:// URL — a full scheme-prefixed HTTP proxy URL
• socks5:// URL — a full scheme-prefixed SOCKS5 proxy URL
• user:pass only — credentials without the endpoint, for tools that store the host separately
• host:port only — the endpoint without credentials

As a rule of thumb, scripting libraries and command-line tools take the URL-style forms directly, bulk software tends to import the colon-separated form, and browser or OS-level proxy settings usually ask for the endpoint and the credentials in separate fields — which is what the last two formats are for.

user123:pass456@<proxy-host>:80
<proxy-host>:80:user123:pass456
http://user123:pass456@<proxy-host>:80
socks5://user123:pass456@<proxy-host>:80
user123:pass456
<proxy-host>:80

The seventh option is a custom template. Write any line pattern using the variables {HOST}, {PORT}, {USER} and {PASS}, and the generator substitutes real values on every line. This handles tools with unusual import formats without any post-processing on your side.

Template:  {USER}:{PASS}|{HOST}|{PORT}
Output:    user123:pass456|<proxy-host>|80

1. 01Set the credential source, rotation mode, targeting, quantity and format, then generate the list.
2. 02Use Copy all to put every line on the clipboard — quickest for pasting straight into a tool or a config file.
3. 03Use the .txt download for large lists or anything you want to keep on disk; bulk software generally imports a plain text file with one proxy per line.

Before wiring a fresh export into anything important, run your credentials through the built-in proxy checker. It streams live results — IP, country, latency, working or failed — with an optional country filter and a limit of 50 checks per day, so you can confirm the list authenticates before a job depends on it.

If you are not sure which format a particular client expects, proxy formats and setup maps the common formats to concrete configuration examples for browsers, scripts and bulk tools.

Credentials can be regenerated at any time; the control is shown in the dashboard, and regenerating issues fresh credentials while the old ones stop working. It is the right move after pasting credentials somewhere they should not have been, sharing a list too widely, or retiring a tool that held them.

Every line the generator emits points at the same place: <proxy-host> on port 80. That single endpoint speaks HTTP, HTTPS via CONNECT, and SOCKS5, so the protocol choice lives in your client — or in the URL scheme you exported — not in a different hostname or port.

Credentials are not the only way in. If your traffic originates from fixed addresses, you can whitelist up to 3 exact IPs (no CIDR ranges) and connect to <proxy-host>:80 with no username or password at all. See IP whitelist authentication for setup and the trade-offs against credential auth.