How to write a proxy format string: host:port:user:pass, http(s)/socks5 URLs, and four-field client mapping—always use console values; fake placeholders only; links to HTTP/SOCKS setup and quickstart.
What this page solves
The first integration blocker is often not “rotating or static,” but how to write the host, port, username, and password the console already gave you: as `host:port:user:pass`, as a proxy URL, or as four separate client fields. This guide is a practical proxy string format and field-mapping checklist.
Keep three layers separate:
- Format — how the string or fields are arranged (this page).
- Protocol — HTTP vs SOCKS5 — see HTTP / SOCKS5 setup.
- Product — rotating by GB vs static by IP·month — see rotating vs static, dynamic, and static.
Hard rule: host, port, credentials, and protocol always come from the console / order response. Every example below uses clearly fake placeholders. Do not treat them as production values, and never paste real or reusable private credentials into docs, tickets, or chat.
Gather four values before you pick a format
Confirm in the console:
| Field | Meaning | Watch-outs |
|---|---|---|
| Host | Proxy entry hostname or address | Console wins; do not guess or reuse stale screenshots |
| Port | Access port | Do not assume “1080/8080 always works” |
| Username | Auth username | May include region/session suffixes—console wins |
| Password | Auth password | Do not leak; old values die after rotation |
Add one more: protocol (HTTP or SOCKS5). Protocol chooses the URL scheme and the client dropdown; it is not the same as product type. Step-by-step smoke tests live in Docs quickstart. Programmatic order/extract flows live in API integration.
Format A: host:port:user:pass (colon-separated)
Many tools, bulk-import boxes, and third-party panels accept a colon-separated one-liner. A common order is:
```text proxy.example.invalid:10000:USER_EXAMPLE:PASS_EXAMPLE_NOT_REAL ```
Mapping:
- `proxy.example.invalid` → Host
- `10000` → Port (example only; not a promise)
- `USER_EXAMPLE` → Username
- `PASS_EXAMPLE_NOT_REAL` → Password
Common mistakes
- Wrong order. Some UIs expect `user:pass@host:port` or other layouts. Follow the target tool’s docs plus console one-click copy—there is no universal law.
- Extra colons. If username or password contains `:`, a four-part colon string becomes ambiguous. Prefer split fields or a URL with encoding.
- Whitespace. Trim leading/trailing spaces; do not merge two lines into one.
- Treating examples as production. The host above is `*.example.invalid` and will not reach a real gateway—replace with console values.
If the console offers “copy proxy string,” prefer that exact format. This page is a mapping aid, not a override of the console.
Format B: proxy URL
HTTP clients, many libraries, and some environment variables prefer a URL:
```text http://USER_EXAMPLE:[email protected]:10000 ```
For SOCKS5 (only when the console says so):
```text socks5://USER_EXAMPLE:[email protected]:10000 ```
Key points:
- Scheme must match console protocol: often `http://` / `https://` (per console notes) or `socks5://`.
- Userinfo sits before `@` as `username:password`.
- host:port sits after `@`.
- If username or password includes `@`, `:`, `/`, `%`, spaces, and similar characters, percent-encode the userinfo before building the URL. Follow your client library’s rules—do not invent a half-finished encoding scheme by hand.
- Some tools want only `host:port` in the host box and separate auth fields—do not paste a full URL into Host unless the UI explicitly asks for a proxy URL.
URL shape does not change billing units: rotating stays mostly per GB; static stays mostly per IP × month. Public price pointers are on pricing; console wins.
Format C: split client fields
Browsers, desktop clients, antidetect panels, and many SDKs expose four (or more) separate inputs:
| Common client label | Fill with |
|---|---|
| Proxy type / protocol | HTTP or SOCKS5 (console) |
| Host / Server / Address | Console Host |
| Port | Console Port |
| Username / User | Console Username |
| Password | Console Password |
Rule of thumb: split the values. Do not dump the entire `host:port:user:pass` string into the Host box unless the UI clearly says “paste full proxy string.” Optional region/session/sticky parameters belong only where the console or Docs define a field. Sticky ≠ static—see sticky session vs static IP.
Format variant × where it is used
| Format variant | Example shape (fake placeholders) | Typical use | Watch-outs |
|---|---|---|---|
| Four-part colon | `host:port:user:pass` | Bulk import; “one line per proxy” panels | Password with `:` breaks parsing |
| Host:port + separate auth | `host:port` plus user/pass boxes | UIs that split address and credentials | Do not put username into Host |
| HTTP(S) URL | `http://user:pass@host:port` | curl, request libraries, some env vars | Encode special characters |
| SOCKS5 URL | `socks5://user:pass@host:port` | Tools that require SOCKS | Scheme must match protocol |
| Four labeled fields | Protocol / Host / Port / User / Pass | Browsers, desktop apps, most antidetect UIs | Map field-by-field to console |
| Host:port only | `host:port` | Allowlist or no-user modes if console returns that | Do not invent “no auth” |
All sample hosts (`proxy.example.invalid`), ports (`10000`), users (`USER_EXAMPLE`), and passwords (`PASS_EXAMPLE_NOT_REAL`) are fake. Production configs must use console values.
Fake placeholders and credential hygiene
- In docs, screenshots, tickets, and chat, use fake placeholders or redaction.
- Do not paste live passwords into Notion, raw email, or public repos.
- After rotation, old strings are dead—copy again from the console.
- When sharing with teammates, prefer “who can open the console” over forwarding plaintext secrets.
- ZTProxy services are for lawful, authorised use only; mainland China is not supported; no account farming and no login-wall bypass.
How this connects to protocol, product, API, and Docs
| If you are stuck on… | Go here |
|---|---|
| HTTP vs SOCKS5 and client checklists | HTTP / SOCKS5 setup |
| Rotating vs static; sticky meaning | Rotating vs static · Sticky vs static · How to choose |
| Programmatic order / extract | API integration |
| Step-by-step commands and smoke tests | Docs quickstart |
| Which product to buy and list prices | Dynamic · Static · Pricing |
This page does not reprint the full API reference and does not invent a `/products/*format*` SKU—format is a configuration writing pattern, not a sellable product line.
Short smoke-test and triage list
- Re-copy Host / Port / User / Pass / protocol from the console; discard stale screenshots.
- Match the client protocol dropdown to the console (HTTP vs SOCKS5).
- For URLs: check `@` placement and userinfo encoding.
- For colon strings: confirm the tool’s expected order; if the password contains `:`, switch to split fields.
- Run a small smoke test; read whether the client says auth failure vs host unreachable.
- Commands and deeper steps follow quickstart; protocol triage follows zt-07.
Public price pointers (console wins): about $0.40/GB; 100 TB pack about $0.20/GB (whole pack); shared about $1.50; dedicated about $5/IP/month—see pricing.
FAQ
What does “proxy format” mean?
It usually means how to write Host, Port, Username, Password (plus protocol) as one string or as several client fields. The three common patterns are colon-separated credentials, a proxy URL, and split fields—follow your tool and the console.
Is host:port:user:pass always in that order?
A common industry layout is Host → Port → User → Pass, but it is not a global standard. Follow the target tool and console one-click copy. Wrong order causes auth failures or wrong endpoints.
When should I use a URL versus a colon string?
Use an `http://` or `socks5://` URL when the tool asks for a proxy URL or env var. Use a colon string for bulk “one line” imports. Use split fields when the UI shows four boxes. Do not paste a full URL into Host unless the UI asks for a proxy URL.
What if the username or password has special characters?
Colon strings can become ambiguous—prefer split fields. If you must use a URL, percent-encode the userinfo. Do not drop raw `@`, `:`, or spaces into a URL without encoding.
Can I copy field values from this page’s examples?
No. `proxy.example.invalid`, `10000`, `USER_EXAMPLE`, and `PASS_EXAMPLE_NOT_REAL` are fake placeholders. Production values must come from the console / order response.
Is this the same as HTTP/SOCKS5 or rotating/static?
No. Format is “how to write.” Protocol is HTTP vs SOCKS5. Rotating/static is product choice. See HTTP/SOCKS setup and rotating vs static.
Should I paste a real password into a support ticket?
Prefer not to. Redact or use an authorised secure channel. Keep fake placeholders in docs and chat to reduce credential leak surface.
Is mainland China supported? Where is the API guide?
No. All ZTProxy proxy products do not support use in mainland China. For programmatic access see API integration; for step-by-step commands see quickstart. More guides: Guides hub.
All ZTProxy proxy products do not support use in mainland China.
Next steps
- Open the console and copy Host / Port / User / Pass / protocol (not the fake host on this page).
- Pick colon string, URL, or four fields based on your tool—use the table above.
- Unsure about protocol → HTTP / SOCKS5 setup.
- Smoke-test → Docs quickstart; programmatic → API integration.
- Product and price → dynamic · static · pricing; overview → how to choose.
Copy real fields from the console → choose a format variant → smoke-test in quickstart
Still unsure? In-site support or [email protected]. Console wins for fields; fake placeholders only; no real credential samples; mainland China not supported; residential only; price and inventory follow backend and console.