Free Proxy List Formatter & Validator
Validate proxy list syntax and convert HTTP, HTTPS and SOCKS endpoints locally. Normalize IPv4, IPv6, hostnames and credentials, remove duplicates and export formatted lists.
Supported input and output rules
host:port host:port:username:password username:password@host:port http://username:password@host:port socks5h://[2001:db8::1]:1080
For proxy URIs, percent-encode reserved characters in usernames and passwords. Four-field input treats credentials literally; use URI output for credentials containing reserved delimiters. All formats need an explicit port. IPv6 addresses must be enclosed in brackets.
Protocol labels are preserved; choosing SOCKS5h does not test remote DNS behavior, and choosing HTTPS does not prove TLS is supported by the endpoint. Hostnames are checked for syntax only. The tool does not discover or provide proxies.
How to use proxy list formatter & validator
Paste up to 2,000 lines. Supported formats are listed below. Blank lines and lines starting with # are ignored.
Set a default protocol for entries without one, choose the output format, and decide whether credentials should be included.
Validate and format the list. Review invalid line numbers and the normalized entries, then copy or download the valid output. Syntax validity does not establish connectivity.
Privacy and scope
Proxy hosts and credentials stay in this page. Parsing uses no API, DNS query, connection attempt or server upload. No inputs are saved in browser storage. Clipboard copies and downloaded files can contain secrets if you explicitly include credentials.
The tool does not save inputs in browser storage. Reset or leave the page to clear its in-page state. Downloads and clipboard copies remain wherever you save or paste them.
Frequently asked questions
What does this proxy validator check?
It parses and validates endpoint syntax, supported protocol labels, IPv4 octets, bracketed IPv6 addresses, ASCII DNS hostnames, ports and credential encoding. It normalizes hosts, optionally removes duplicates and converts output. It makes no network requests and does not test whether a proxy is online, fast, anonymous, safe or accepting the supplied credentials.
Which proxy formats are supported?
Use host:port, host:port:username:password, username:password@host:port, or protocol://username:password@host:port. Supported protocols are HTTP, HTTPS, SOCKS4, SOCKS4a, SOCKS5 and SOCKS5h. IPv6 must be bracketed. URLs require an explicit port and may have only an optional trailing slash, with no other path, query or fragment.
How are credentials handled?
All processing happens locally. Credentials are omitted from output by default; explicitly enable them if your client needs authenticated proxies. URI credentials are percent-decoded for comparison and percent-encoded for output. Four-field credentials are interpreted literally. Reserved delimiters may require URI output. Input credentials are never uploaded, saved or included in invalid-line messages.
How does duplicate removal work?
Duplicates match normalized protocol, hostname or IP, numeric port and decoded credentials. Different credentials or protocols count as different proxy configurations. If you strip credentials or protocols from output, distinct configurations can therefore produce identical endpoint lines.
Why are some proxy lines rejected?
Ambiguous or unsafe formats are rejected, including abbreviated or octal-looking IPv4, out-of-range ports, unbracketed IPv6, unsupported schemes, whitespace, executable URL parts and malformed encoded credentials. Unicode hostnames should be converted to their ASCII punycode form first. Private or local endpoints are allowed because they can be legitimate internal proxies; no claim of public reachability is made.