MiyaIP 简体中文 local tools

MiyaIP local proxy tool

Proxy Format Converter
Mixed input, unified output

Batch identify common HTTP and SOCKS proxy writing methods, and uniformly convert them into standard URIs or compact formats compatible with old software. All content is processed within the current browser only.

Do not upload proxyCredentials not savedSupports 10,000 rows

Conversion rules

Determine the protocol and target format first

Inputs with a protocol preferentially use their own protocol; lines without a protocol use the default protocol.

One per row, allowing for mixing of different protocols and arrangements.

0 lines · 0 B

Support domain name, IPv4, private network address and [IPv6]:port; Empty lines will be ignored.

Only include successfully converted lines, in the same order as the input.

Waiting for conversion

Credentials are masked by default. Credential-free formats also remove authentication fields from JSON and CSV.

Once you paste the proxy list you can start the conversion.

Format selection suggestions

Prefer standard URIs and make them compatible with older formats when needed

Format conversion only changes the writing method, and does not verify whether the proxy is online, nor does it determine whether the protocol is consistent with the server's real capabilities.

Standard URI
socks5://user:pass@host:1080

Protocol and authentication information is clearest, special characters can be percent-encoded, recommended for configuration files and modern clients.

Host priority
host:port:user:pass

Commonly seen in bulk proxy files, but the protocol needs to be set separately in the using software, and the credentials cannot safely contain delimiters.

Account priority
user:pass@host:port

It is intuitive to read, but the protocol field is still missing; when the account number and password contain colons or @, standard URIs should be used instead.

host port only
host:port

Suitable for non-certified proxies. Selecting this output will explicitly delete existing credentials, please check the summary prompts before exporting.

accuracy bounds

Four-part formats can be ambiguous without a standard URI

For four paragraphs of colon text, MiyaIP will check which of the second and fourth paragraphs is a valid port to distinguish host:port:user:pass with user:pass:host:port. If both locations look like valid ports, it will be marked as ambiguous, rather than mistaking the account for the host.

IPv6 must use square brackets in compact form, e.g. [2001:db8::10]:1080. When you need to use colons, @, spaces, or other special characters in credentials, use a standard URI and percent-encode it.

FAQ

About local conversion and credentials

Will these proxies be connected during conversion?

No. The page only parses and rearranges text, no DNS queries, port connections, or availability checks are performed. Use the MiyaIP Proxy Checker when you need to verify connectivity.

Why do some rows say "Missing Authentication Information"?

You selected a target format that must contain a username and password, and the inputs are only host and port. The tool will not generate fake empty accounts, so errors will be retained for you to check.

Why did the special characters in the credentials change?

Standard URIs are percent-encoded so that characters such as colon and @ no longer conflict with format delimiters; the original credentials are restored when the URI is parsed again.

Will JSON and CSV contain passwords?

meeting. They are complete local transformation files generated on your own initiative and may contain original credentials. Please save it in the same way you protect your proxy configuration and do not upload it to a public location.