Proxy connection format: IP:PORT:USERNAME:PASSWORD

How do I convert a line to a proxy URL?

Move the username and password to the front, joined by :, then add @, the IP, : and the port, and put a scheme in front. Most libraries accept this URL form.

The scheme of an HTTP proxy is http:// even when the website is https://: the scheme describes the connection to the proxy, and HTTPS sites go through a CONNECT tunnel. The SOCKS5 vs HTTP guide explains socks5 and socks5h.

How do I URL-encode special characters in a proxy password?

Replace each reserved character with % and its hexadecimal code, or let your language do it: urllib.parse.quote(password, safe='') in Python, encodeURIComponent(password) in JavaScript. RFC 3986 reserves these characters because they separate the parts of a URL. An unencoded @ in a password, for example, makes the tool read the rest of the password as the host.

Only the username and password need this. The IP and port never contain reserved characters. In the original IP:PORT:USERNAME:PASSWORD line nothing is encoded, so split it on the first three colons only: a password may contain : itself.

Can I convert a whole list at once?

Yes. Export your list as TXT from your account, then run one of the scripts below. Each reads proxies.txt (or the file you pass), splits each line on its first three colons, encodes the login and prints an HTTP URL and a socks5h:// URL per IP. If your account lists a separate SOCKS5 port, use that port in the SOCKS5 URL.

"""Turn IP:PORT:USERNAME:PASSWORD lines into proxy URLs, with safe encoding."""
import sys
from urllib.parse import quote


def to_proxy_url(line, scheme='http'):
    # maxsplit=3 keeps a password that itself contains ':' in one piece
    ip, port, user, password = line.strip().split(':', 3)
    return f'{scheme}://{quote(user, safe="")}:{quote(password, safe="")}@{ip}:{port}'


path = sys.argv[1] if len(sys.argv) > 1 else 'proxies.txt'
with open(path, encoding='utf-8') as handle:
    for line in handle:
        if line.strip():
            print(to_proxy_url(line))                    # HTTP proxy URL
            print(to_proxy_url(line, scheme='socks5h'))  # SOCKS5, DNS on the proxy

// Turn IP:PORT:USERNAME:PASSWORD lines into proxy URLs (Node.js 18 or later).
import { readFileSync } from 'node:fs';

function toProxyUrl(line, scheme = 'http') {
  const [ip, port, user, ...rest] = line.trim().split(':');
  const password = rest.join(':'); // a password may itself contain ':'
  return `${scheme}://${encodeURIComponent(user)}:${encodeURIComponent(password)}@${ip}:${port}`;
}

const lines = readFileSync(process.argv[2] ?? 'proxies.txt', 'utf8').split(/\r?\n/).filter(Boolean);
for (const line of lines) {
  console.log(toProxyUrl(line));
  console.log(toProxyUrl(line, 'socks5h'));
}

http://user-7:p%40ss%3Aw%2Frd%[email protected]:8000
socks5h://user-7:p%40ss%3Aw%2Frd%[email protected]:8000

What is in the TXT and CSV exports?

The TXT export has one IP:PORT:USERNAME:PASSWORD line per IP and nothing else, which suits scripts and tools that import proxy lists. The CSV export contains at least IP, port, username, password, country and end date, which suits spreadsheets and inventory.

Before you read the CSV in code, open it once and check the header row for the exact column names; read columns by name, not by position. Python's csv.DictReader does this. Keep both files private: they contain your proxy passwords. If a file leaks, write to support with the affected IPs, never the passwords.

Which format does my tool expect?

Most tools want either the URL form or separate fields:

• curl: -x http://USERNAME:PASSWORD@IP:PORT, or -x http://IP:PORT -U USERNAME:PASSWORD.
• Python requests and aiohttp: the URL form; see the code examples.
• Node.js (undici, https-proxy-agent): the URL form.
• Playwright and browsers: separate fields: server, username, password.
• Scraping frameworks and proxy managers: often the raw IP:PORT:USERNAME:PASSWORD line or USERNAME:PASSWORD@IP:PORT; check their import screen.

With the IP allowlist, every format drops the username and password: IP:PORT or http://IP:PORT. Username and password, or an IP allowlist (up to 10 IPs).