20% alennus residential

Trustpilot4.5 stars4.5 / 5

Proxy formatter

Convert proxy lists between every common layout - host:port, user:pass@host:port, full URLs and ready-made snippets. Deduplicate, swap credentials, force a protocol, all in your browser.

Formatter

Convert any proxy list into the format you need

Paste a list in any common layout. Detection runs per line, so mixed lists are fine. Everything happens in your browser - credentials never leave this page.

Smart detection reads each line on its own.

Custom template supports {scheme} {host} {port} {user} {pass}.

Credentials

List handling

Output tweaks

Input

Output

Input lines

0

Parsed

0

Duplicates removed

0

Skipped

0

Output lines

0

No parse errors. Unrecognised lines would be listed here with a reason.

Supported formats

Every layout providers actually ship

There is no standard for proxy list files, so the same pool arrives in a different shape from every vendor. These are the layouts the parser understands on both sides of the conversion.

FormatExample
host:port203.0.113.10:8080
host:port:user:pass203.0.113.10:8080:alice:s3cret
user:pass:host:portalice:s3cret:203.0.113.10:8080
user:pass@host:portalice:[email protected]:8080
host:port@user:pass203.0.113.10:8080@alice:s3cret
scheme://user:pass@host:porthttp://alice:[email protected]:8080

How it works

Four steps from messy export to usable list

01

Paste the list

Drop in whatever your provider gave you. Detection reads each line separately, so exports that mix authenticated and open proxies parse in one pass.

02

Pick the target format

Plain layouts for scrapers and bots, a full URL for HTTP clients, snippets for curl, Python and Node, or a custom template when a tool expects something unusual.

03

Clean it up

Remove duplicates, swap credentials, force a protocol, sort by host or port, cap the number of lines and add a prefix or suffix per row.

04

Copy or download

Take the result to the clipboard or save it as a .txt file that is ready to feed into your scraper, proxy manager or browser profile.

Where it helps

Formatting is the boring part of every proxy workflow

A pool is only as usable as the file it arrives in. These are the conversions that come up again and again.

Scrapers and crawlers

Most frameworks expect a single proxy URL per request. Converting once up front avoids per-request string building and the bugs that come with it.

Browser automation

Puppeteer, Playwright and antidetect browsers usually take host:port plus separate credentials, so stripping or splitting the auth part is the common step.

Proxy managers

Rotators and load balancers tend to import host:port:user:pass. Deduplicating by endpoint first keeps the pool honest and the stats readable.

Team handover

Replacing the username and password on an entire list is the quickest way to move a pool to a new sub-user without touching the endpoints.

FAQ

Questions about proxy formats

What proxy formats can the formatter read?

It reads host:port, host:port:user:pass, user:pass:host:port, user:pass@host:port, host:port@user:pass and full proxy URLs such as http://user:pass@host:port or socks5://host:port. Lines separated by spaces, tabs, commas, semicolons or pipes are normalised before parsing, and detection runs per line so a mixed list works without cleanup.

Are my proxies or credentials uploaded anywhere?

No. Parsing and formatting run entirely in your browser with client-side JavaScript. Nothing is sent to a server, logged or stored, which matters because a proxy list with credentials is effectively a password.

How do I change the username or password on a whole list?

Type the new username or password into the credentials fields. Every parsed line is rewritten with those values, which is the fastest way to rotate a shared login or move a list between sub-users. Leave a field empty to keep the original value.

How does duplicate removal work?

Two modes: remove duplicate host:port pairs, which catches the same endpoint listed with different credentials, or remove identical output lines, which only drops exact copies. The counter shows how many lines were discarded.

Which format should I use for curl, Python or Node?

curl and most HTTP clients want a full URL such as http://user:pass@host:port. The formatter ships ready-made outputs for a curl command, a Python requests proxies dictionary and a Node proxy string, plus a custom template with {scheme}, {host}, {port}, {user} and {pass} placeholders for anything else.

Does the formatter validate that proxies work?

No. It validates structure - hostname shape and a port between 1 and 65535 - and reports the lines it could not parse with a reason. Checking whether an endpoint is alive requires sending traffic through it, which a browser tool cannot do reliably.

Need proxies that are worth formatting?

Datacenter, residential and mobile pools with sticky sessions, city-level targeting and pay-as-you-go pricing.

Explore residential proxies

Aloita

Valmiina scrapingiin suuressa mittakaavassa?

Käynnisty minuuteissa käytön mukaan laskutettavilla proxyilla, reaaliaikaisilla tilastoilla ja tuella tarvittaessa.

RedScrape logoScrape

Premium-luokan konesali-, residential- ja mobiiliproxyt ammattimaiseen web scrapingiin ja tiedonkeruuseen.

Yhteisö

© 2026 RedScrape.com. Kaikki oikeudet pidätetään.

Palvelun tarjoaa TechNode LLC