Proxy Format Converter: URLs, Lists and JSON

The tool accepts up to 1,000 lines and keeps their order. It validates the format without opening proxy connections. Select the protocol separately when the input has no URL scheme.

host:port:username:password places the endpoint first. username:password@host:port places credentials first. A full URL adds the protocol, such as http:// or socks5h://. The converter does not guess between these shapes.

Use square brackets around an IPv6 host, for example [2001:db8::1]:1080. Every entry needs an explicit port from 1 to 65,535. URL input can omit authentication; delimiter-based authenticated formats need both fields.

URLs are emitted with percent-encoded credentials. A literal @ in a URL password must be encoded as %40. In a raw host-first line, the password includes everything after the username separator, so colons in that password are preserved. A colon in a username requires URL or JSON output.

JSON connection fields preserve protocol, host, port, username and password separately. Check the receiving application’s field names before importing this data. The Playwright export produces an array of proxy objects; use one object for each browser or context.

Use HTTP for authenticated Playwright examples. For curl and Python Requests, socks5h requests proxy-side hostname resolution. Changing a string’s format cannot add support for a protocol that the receiving client or proxy does not provide.

For provider-specific setup, continue to the Apify custom proxy guide, n8n HTTP Request guide or Browserbase configuration guide.

If you need a Proxies.sx session, country or rotation mode, create the username in the username builder first. The format converter preserves your username; it does not change its routing tokens.

Fix invalid lines before exporting. Error messages show line numbers and format problems without repeating credentials. Downloaded output contains live credentials if you supplied them, so keep it out of repositories and shared logs.

Run a small request from your application after importing the configuration. A successful format conversion does not verify account access, available traffic or destination compatibility. Check mobile proxy stock and buying requirements before funding a new workload.