Convert Proxy Lists to Clash, Shadowrocket, or v2rayN
Standard URIs make protocol and authentication explicit and percent-encode special characters. The converter also accepts host-first and account-first compact forms, unauthenticated host and port, domains, IPv4, and bracketed IPv6, then normalizes exact duplicates.
Choose normalized text for exchange, Clash or Mihomo YAML for a client profile, Shadowrocket configuration, or v2rayN and v2rayNG links. Conversion changes configuration declarations only; it does not perform DNS queries, open ports, or prove that an endpoint supports the selected protocol.
How Ambiguous Proxy Formats Are Handled
For four colon-separated fields, the parser checks whether the second or fourth field is the only valid port to distinguish host:port:user:pass from user:pass:host:port. If both positions look like ports, the row is rejected as ambiguous instead of guessing which field is the host.
IPv6 in compact forms must use brackets. Credentials containing colons, at signs, spaces, or other delimiters should use a standard URI with percent-encoding. Invalid rows stay visible for review while valid rows continue through conversion.
Keep credentials under your control
Parsing and formatting run in the current browser without uploads or storage. Credentials are masked by default; displaying, copying, exporting, or generating an importable file with real credentials requires explicit confirmation.
Review client compatibility before importing. Supported client targets cannot preserve SOCKS4 semantics losslessly, and forcing SOCKS5 changes only the declaration rather than the actual proxy server. A usable downloaded profile may contain credentials and must be protected.
