Proxy Formats Explained: ip:port:user:pass, user:pass@host and URL

The same proxy can be written in four or five ways, and every tool wants a different one. Here is what each part means, which format goes where and how to convert a whole list without breaking it.

By Tomas LindqvistUpdated: 3 min read
Proxy formats explained — the same proxy written as ip:port:user:pass, user:pass@host:port and a socks5:// URL

A proxy format is simply the order in which a proxy's address, port, username and password are written. The most common one, ip:port:user:pass, lists the four parts separated by colons. Other tools want user:pass@ip:port or a full URL such as socks5://user:pass@ip:port. The proxy is the same — only the notation changes.

Getting the format wrong is one of the most frequent reasons a working proxy "does not connect". This guide explains each part, the common formats, which tools expect which one and how to convert a list safely.

The four parts of a proxy

PartExampleWhat it is
Host203.0.113.10 or gw.example.comThe proxy server's IP address or hostname
Port8000The port the proxy listens on; HTTP and SOCKS5 may use different ports
Usernameuser123Your login for the proxy
Passwords3cretThe password that goes with the username

Some proxies also need a protocol — HTTP(S) or SOCKS5. It is not part of the plain colon formats, so you choose it separately in the tool's settings.

Key takeaway: every format carries the same four pieces of information. If a proxy works in one tool but not another, check the order of the parts and the protocol before anything else.

Common proxy formats

FormatExampleTypically used by
ip:port:user:pass203.0.113.10:8000:user123:s3cretProxy lists, antidetect browsers, bulk import fields
user:pass@ip:portuser123:s3cret@203.0.113.10:8000Scripts, command-line tools, some bots
URL with schemesocks5://user123:s3cret@203.0.113.10:8000curl, Python requests, browser extensions, apps that need the protocol
ip:port only203.0.113.10:8000IP-whitelisted proxies, or tools with separate login fields
Separate fieldsHost, Port, Username, Password boxesOperating system settings, browsers, Telegram

Which format does your tool want?

  • Antidetect browsers — usually accept ip:port:user:pass in a quick-paste field, with the protocol picked from a list. See our antidetect browser proxy setup guide.
  • Browsers and operating systems — use separate fields; the browser asks for the username and password when you first connect. See how to set up a proxy in your browser.
  • curl and code — want the URL form, for example curl -x socks5h://user:pass@ip:port https://example.com.
  • Telegram — separate fields for server, port, username and password; choose SOCKS5.
Tip: in URL form, socks5h:// asks the proxy to resolve domain names, so DNS lookups also go through it. Plain socks5:// resolves them on your own machine.

Converting a proxy list

If you have a list in ip:port:user:pass and a tool wants user:pass@ip:port, you only need to reorder the parts on each line:

  1. Split each line on colons — you get four parts: host, port, username, password.
  2. Rebuild in the new order — for example user:pass@host:port, or add a scheme in front for a URL.
  3. Watch special characters — if a password contains : or @, URL formats need it percent-encoded (@ becomes %40).
  4. Test one line first — import a single proxy, check that it connects, then import the rest.

In a spreadsheet, put the list in one column, use "Split text to columns" with the colon as a separator and join the columns back in the order you need. Many tools also offer an import option where you choose the format from a menu.

Format mistakes that look like a dead proxy

  • Swapped parts — a tool reading user:pass:ip:port as ip:port:user:pass will try to connect to your username.
  • Wrong protocol — a SOCKS5 port used as HTTP (or the reverse) fails or times out. Read SOCKS5 vs HTTP proxies for the difference.
  • Extra spaces or line endings — copied lists can carry hidden spaces or Windows line endings; trim them.
  • Login missing — using ip:port on a proxy that needs a username and password returns an authentication error (often HTTP 407).
Important: proxy credentials are like a password. Do not paste lists into public converters or shared documents; reorder them locally in a spreadsheet or text editor. Still stuck? Work through proxy server not responding.

Proxy formats in mistPROXY

Every mistPROXY order shows your credentials as host:port:user:pass in the dashboard, ready to paste. You can also download the list as user:pass@ip or in URL format, so there is nothing to convert by hand. Proxies work over HTTP(S) and SOCKS5 with username and password authentication. Read how it works, compare plans in pricing and create a free account — or ask our team on Telegram at @mistnetwork.

Frequently asked questions

What does ip:port:user:pass mean?
It is a proxy written as four parts separated by colons: the server address, the port, the username and the password, in that order.
What is the difference between ip:port:user:pass and user:pass@ip:port?
Only the order. Both contain the same information; the @ form puts the login first and is common in scripts and URLs.
How do I write a SOCKS5 proxy as a URL?
Use socks5://user:pass@ip:port, or socks5h:// if you want the proxy to resolve domain names as well.
Why does my proxy not work after importing a list?
The most common causes are parts in the wrong order, the wrong protocol, hidden spaces or a missing username and password. Test a single line first.
What if my password contains @ or a colon?
Colon formats may break, and in URL formats the character must be percent-encoded, for example @ as %40.

Related articles

Latest articles

All articles