Proxy format
converter.

No. The converter is JavaScript running in your browser — the list never leaves the page. There is no upload, no request to our servers, no logging and no storage, so closing the tab discards everything. You can confirm it by opening your network tab, or by disconnecting from the internet after the page loads: it keeps working.

host:port, host:port:user:pass, user:pass:host:port, user:pass@host:port, host:port@user:pass, and full proxy URLs with an http, https, socks4 or socks5 scheme. It also reads CSV, TSV and spreadsheet rows, curl commands, HTTP_PROXY environment lines and quoted URLs pasted out of JSON or Python. Detection runs per line, so a list that mixes several formats converts in one pass.

Nothing but the writing. They carry the same four values, and the converter treats them as identical. The colon-separated form is what proxy sellers and GUI tools tend to export; the @ form is a proxy URL with the scheme left off, which is what HTTP clients and libraries expect.

Both are four colon-separated fields and neither is labelled, so the converter scores each reading on how host-like the candidate host is. An IP address is decisive, a dotted hostname is strong evidence, and a bare word is weak because usernames look the same. When both readings score equally it picks host-first, which is the more common of the two. The Detected line under the panes tells you which shape it settled on for every line.

No. Credentials are split on the first colon and the address on the last @, so a password containing either character survives the round trip. When the output is a proxy URL, curl command, environment variable or Python snippet, the username and password are percent-encoded, because an unencoded @ or / in a password produces a URL that silently parses to the wrong host.

Yes, with the address in square brackets: [2001:db8::1]:8080. Brackets are required rather than optional, because a bare IPv6 address is itself full of colons and cannot be told apart from the separators. A line that looks like an unbracketed IPv6 address is reported with that specific advice rather than a generic failure.

Where DNS resolution happens. With socks5 your own machine resolves the hostname and sends the resulting IP to the proxy; with socks5h the proxy resolves it. Use socks5h when the target should never see a DNS lookup from your network, or when the hostname only resolves correctly from the proxy location.

Every line that cannot be read is listed underneath with its original line number, the text as pasted and the specific reason — a port outside 1–65535, a host that is not a valid address or hostname, or a field count that does not resolve. Nothing is dropped silently, because a list that comes back shorter than it went in is the most expensive way this tool could fail you.

Only when the format you pick has somewhere to put them. host:port cannot carry a username and password, so choosing it drops them, and the page says so with a count of the affected lines. The Strip credentials switch does the same thing deliberately, which is what you want before sharing a list or filing a support ticket.

The first 20,000 lines of a paste are converted. Anything beyond that is reported as ignored rather than quietly cut, so you know to split the list. There is no account, no signup and no rate limit — the work happens on your own machine.