Proxy Format

The same proxy, written six ways. All of them carry the same four values; only the order and the separators change.

<login> and <password> stand for your credentials; with ProxyField the username also carries the targeting, as in <login>-country-us-city-new_york. SOCKS5 runs on the same gate.proxyfield.io:7000. Each line has the form host:port:username:password, as in gate.proxyfield.io:7000:<login>-country-us-city-new_york:<password>.

The URL style follows the generic URI syntax (RFC 3986): scheme, then //, then the optional login and @, then host and port.

The scheme describes how your tool talks to the proxy, not the website's protocol. An http:// proxy URL is the normal choice for fetching https:// sites.

A SOCKS5 proxy is written like any other, with the SOCKS scheme:

socks5h://<login>-country-us-city-new_york:<password>@gate.proxyfield.io:7000
socks5://<login>-country-us-city-new_york:<password>@gate.proxyfield.io:7000
gate.proxyfield.io:7000:<login>-country-us-city-new_york:<password>

These lines show the format; ProxyField's gateway takes SOCKS5 on the same port, 7000, with the same username and password as HTTP. In list format there is no scheme, so the tool has a protocol selector, and you pick SOCKS5 there. ProxyField's examples use socks5h://, so the gateway resolves the website's hostname, for example to get DNS answers for the proxy's country; use socks5:// in tools that accept only that scheme. In Python, requests needs the requests[socks] extra for SOCKS URLs (Requests: SOCKS). Not every client sends a SOCKS5 username and password; proxy authentication explains which ones don't. More on the protocol: SOCKS5 proxies.

When a tool asks for "proxy" in one box, try the URL style first; when it imports a list, host:port:user:pass is the usual default.

This short Python script turns any of the list styles into URLs, percent-encoding the login so special characters can't break it. Save your proxies one per line in proxies.txt:

from urllib.parse import quote

def to_url(line, scheme="http"):
    line = line.strip()
    if "://" in line:
        return line  # already a URL
    parts = line.split(":")
    if len(parts) == 2:  # host:port
        return f"{scheme}://{line}"
    # note: a user:pass:host:port line whose password is all digits is read as host:port:user:pass
    if len(parts) >= 4 and parts[1].isdigit():  # host:port:user:pass
        host, port, user, password = parts[0], parts[1], parts[2], ":".join(parts[3:])
    elif "@" in line:  # user:pass@host:port
        login, hostport = line.rsplit("@", 1)
        user, password = login.split(":", 1)
        host, port = hostport.rsplit(":", 1)
    else:  # user:pass:host:port
        user, password, host, port = parts[0], parts[1], parts[2], parts[3]
    return f"{scheme}://{quote(user, safe='')}:{quote(password, safe='')}@{host}:{port}"

with open("proxies.txt") as f:
    for line in f:
        if line.strip():
            print(to_url(line))

Going the other way is one f-string: f"{host}:{port}:{user}:{password}". A converter only rewrites text; to see whether a line works, test it with the proxy checker.

Guides and settings screens write proxies as proxy.example.com:8080 or http://user:[email protected]:8080 to show the format. example.com is a domain reserved for documentation, so the line cannot work; replace the host, port and login with your own. The proxy server address explainer covers what each part means, and proxy port covers the number after the colon.

• A scheme in a host field. Device settings want gate.proxyfield.io, not http://gate.proxyfield.io:7000.
• Special characters in the password. In a URL, @, :, / and # must be percent-encoded (@ is %40). The script above does it.
• Swapped order. user:pass:host:port and host:port:user:pass look alike; if a tool rejects every line, check which order it wants.
• Hidden spaces and line endings. Lists copied from spreadsheets can carry spaces or Windows line endings that become part of the password.
• The wrong scheme for the protocol. A SOCKS5 proxy written as http://, or the reverse, fails at the first byte.

ProxyField's configurator in the dashboard generates as many proxy lines as you need, and every line points at the same gateway, gate.proxyfield.io:7000; the username carries the targeting (country and city in the example, <login>-country-us-city-new_york). Region, session and session time go in the same username: -region-<region>, -session-<id> and -ttl-<seconds> (30 to 129,600 seconds, 20 minutes by default), as in <login>-country-us-region-new_york-city-new_york-session-he9f2qga-ttl-600; every part after the login is optional. The quick start walks from purchase to the first request.