Proxy format converter
Every vendor hands you the same four facts in a different order, and every client wants a different one. Paste whatever you were given and take whatever you need.
The part worth having: credentials are percent-encoded wherever the output is a URL. Session-based residential proxies put the session in the username, and the separators vendors pick are the same characters that end a URL field, so a working password produces a 407 that never says why.
Any of the usual shapes, mixed together is fine. Lines starting with # are ignored. Tabs and commas work, so a spreadsheet column pastes straight in.
Percent-encoded. This is the form that breaks when credentials contain a colon or an at sign.
Questions
What is the difference between host:port:user:pass and user:pass@host:port?
Only the order, and which one a vendor hands you is arbitrary. Most proxy sellers issue host:port:user:pass because rotators expect it; the at-sign form is what HTTP clients read, because it is the userinfo half of a URL. This tool reads either and tells you which shape it found.
Why does my proxy password stop working inside a URL?
Because a colon or an at sign in the password ends the field early. In http://user:pass@host:port the first colon separates user from password and the last at sign separates the credential from the host, so a password containing either truncates and the proxy answers 407. Percent-encoding the credential fixes it, and every URL form on this page is encoded.
Is it safe to paste proxy credentials into this page?
Everything runs in your browser. Nothing you paste is sent to us or to anyone else, and there is no analytics on the field. You can confirm that by opening the network tab, or by disconnecting before you paste.
Should I use HTTP or SOCKS5 for my proxy?
If your work is HTTP requests, the HTTP endpoint is the same network at the same price and needs no extra client support. SOCKS5 matters when the traffic is not web traffic, which covers mail clients, game traffic and some automation tooling.