Proxy list toolkit

Proxy Formatter

Paste HTTP, HTTPS, SOCKS4, or SOCKS5 proxy lines, convert them between common formats, clean duplicates, and send the list to testing or IP location tools.

Proxy Conversion SOCKS / HTTP Formats Clean Lists Tester Handoff
1000 lines per conversion Local browser parsing, duplicate cleanup, saved templates, exports, and copy-ready proxy formats.

Proxy format examples: before and after

Choose the output format your application accepts. These examples use documentation-only IP addresses and sample credentials.

InputOutput settingsFormatted result
192.0.2.10:8080URL format; HTTPhttp://192.0.2.10:8080
192.0.2.11:8080:demo-user:demo-passUSER:PASS@HOST:PORT; preserve protocoldemo-user:demo-pass@192.0.2.11:8080
192.0.2.12:1080:demo-user:demo-passURL format; SOCKS5socks5://demo-user:demo-pass@192.0.2.12:1080

Use Auto detect for these inputs and leave Mask credentials off to reproduce the sample output. Changing the protocol changes the output text; it does not add protocol support to a proxy. Use a protocol supported by both the proxy and your application.

0 / 1000
0 proxies
Ready
Next tools: Check IP WHOIS

Your proxy list is processed locally in your browser and is never uploaded.

Proxy Formatter FAQ

Does Proxy Formatter upload my proxy list?

No. Parsing, formatting, copying, and custom templates run locally in your browser. The proxy list is not sent to WordPress or a third-party service.

Which proxy formats are supported?

The formatter supports HOST:PORT, HOST:PORT:USER:PASS, USER:PASS:HOST:PORT, USER:PASS@HOST:PORT, HOST:PORT@USER:PASS, URL format, CSV, space-separated lists, cURL, Python requests, proxychains, Chrome extension JSON, and custom output templates.

Can I keep or change the proxy protocol?

Yes. You can preserve the detected protocol or force HTTP, HTTPS, SOCKS4, or SOCKS5 in the output.

What can I use in custom templates?

Custom templates can use {protocol}, {host}, {port}, {user}, and {pass}. Empty username or password values are left blank.

Can I remove duplicates or sort the proxy list?

Yes. Cleanup options can trim blank lines, remove duplicate proxies, sort output, shuffle output, or mask proxy credentials for screenshots and support tickets.

Can I test the formatted proxies?

Yes. The Test proxies button stores the formatted list locally in your browser and opens the Proxy Tester page so you can check speed, protocol, status, and location.

Why are some lines marked invalid?

Lines are skipped when the selected input format does not match, the host is missing, or the port is outside the valid 1-65535 range.

How many proxies can I format at once?

This page currently accepts up to 1000 non-empty lines per conversion.

Proxy Format Converter Guide

Convert proxy formats for browsers, scripts, and automation tools

Use this proxy formatter to convert private proxy lists between host:port, host:port:user:pass, user:pass@host:port, protocol URL, CSV, cURL, Python requests, proxychains, Chrome extension JSON, and custom templates. It is useful when a proxy provider, browser extension, scraper, automation script, or proxy checker expects a different proxy syntax.

Clean messy proxy lists before importing

Large proxy lists often contain duplicate entries, blank lines, mixed separators, pasted spreadsheet rows, or trailing notes. The cleanup options help normalize the list before you copy it into a proxy manager, proxy switcher, browser profile, scraping tool, SEO tool, or testing workflow.

Local and private by design

Proxy credentials can be sensitive, so the converter runs in your browser instead of uploading the list to WordPress. You can format proxies, save custom templates, mask credentials, copy invalid rows, download results, and send a cleaned list to the proxy tester without exposing the list in a URL.

Proxy Tester Test formatted HTTP and SOCKS proxies for status, speed, protocol, final IP, and location. IPs Locations Paste IP addresses or proxy lists and find their country, region, city, and location details. IP WHOIS View your current IP address, approximate location, network data, and WHOIS registration details.

Format proxy lists before importing them

Most proxy import errors are boring: wrong separator, missing protocol, swapped username/password or an extra space. Format the list once, then paste the cleaned version into the tool that will actually use it.

  1. Parse the input format
  2. Validate and deduplicate
  3. Export the required format
Formatting turns messy proxy lists into import-ready rows.

Use it when

  • Convert proxy rows between common host:port:user:pass formats.
  • Clean lists before browser, scraper or SEO-tool import.
  • Reduce authentication errors caused by malformed proxy strings.

Next checks

  • Test a formatted sample before importing the whole list.
  • Keep protocol expectations separate from credentials.
  • Apply the formatted endpoint with the HTTPX examples or the PowerShell proxy test; keep real credentials out of logs and shared files.
  • If special characters are present, verify how the destination tool parses them.

After formatting a sample, follow the cURL proxy configuration examples, the Python Requests proxy guide or the n8n proxy setup guide for your destination application. Keep the protocol, endpoint and authentication method consistent with that application.

Proxy TesterProxy FormatterIP Location CheckerBlacklist CheckerPool size guide

Recommended next step

Test the cleaned list before using it

Formatting fixes syntax, but it does not prove connectivity, authentication, speed or the visible exit IP.

Need a new proxy list? Compare dedicated proxy plans and confirm protocol, authentication and location before ordering.

Open Proxy Tester View all proxy tools

Share a summary without your proxy list

Download only aggregate result counts for a support discussion. Proxy addresses, usernames, passwords and raw error messages are excluded. Existing list exports remain available in the tool.

Complete a test or conversion to enable the summary.

Generate your proxy configuration

Choose an application and enter one endpoint. Generation runs in this page: it does not connect to your proxy or save your entries. Credentials stay hidden in output until you explicitly include them.

Enter your endpoint and generate a configuration.

The request examples use example.com as a destination. Replace it only with a destination you are authorized to access. HTTP Basic and SOCKS authentication require provider support; a generated configuration is not a connectivity test.

Executed configurations and their limits

Retested October 12, 2026 with the configuration generator. Each protocol has two cases: IP authorization and synthetic username/password authentication.

Actual loopback checks, not provider performance
RuntimecURLHTTPSOCKS5
Windows PowerShell 5.1.26100.95498.21.02/2 passed2/2 passed
PowerShell 7.6.5, native mode Windows8.21.02/2 passed2/2 passed
Bash 5.0.17 on Linux7.68.02/2 passed2/2 passed

The fixtures checked the request target and decoded synthetic credentials. SOCKS5 checks also witnessed the destination hostname being supplied to the proxy. Both endpoints were on loopback; the fixtures answered locally without forwarding. These checks do not qualify HTTPS CONNECT, TLS, provider availability, latency or every shell version. The HTTPS destination in a generated example still needs a separate test with your authorized endpoint.

Select Windows PowerShell 5.1 for its quoted-empty workaround. Select PowerShell 7.3+ when native argument mode is Windows or Standard; an explicitly selected Legacy mode needs the 5.1 choice. POSIX shell uses the ordinary empty argument.

Scroll to Top