Export proxy credentials in the format your tool expects
The same assigned proxy can be represented as host:port:user:pass, user:pass@host:port, a URL or CSV. A different text format does not create a new IP.
Identify the parser
Read the destination tool's documentation. Some tools expect HTTP(S) URLs, some SOCKS5 endpoints, and some separate columns. A correct host with the wrong scheme or port will fail.
Export only assigned resources
Use the address list in the dashboard after delivery. Preview examples and placeholder credentials are not live proxies. Keep the exported file out of public repositories and shared folders.
Validate one line first
Test a single entry before importing hundreds. Confirm authentication, protocol, exit IP and country, then apply the same format to the rest of the list.
Worked example
Test one assigned line in the destination tool before importing a whole list. Examples include host:port:user:pass and user:pass@host:port; CSV needs the expected columns and header. The format must match both the tool and the assigned proxy protocol.
Common questions
Does a new export format create another IP?
No. Export only rewrites already assigned host, port and credentials. The number of IPs comes from the order.
Why does an imported line fail?
Check field order, escaping of special characters, HTTP(S) versus SOCKS5, port and authentication. Isolate the format problem with one line first.