Skip to content

SOCKS5 → QR

SOCKS5 to QR code converter

Feed in a SOCKS5 proxy string in any common layout and get a QR code your mobile client can scan. The parsing rules are documented below, format by format.

One proxy per line; common formats are recognized

Client app

Generated in your browser, never uploaded

Scan to import

Paste a proxy and generate; the QR code appears here

  • Forgiving parserColon, @, ## and comma layouts are all understood, and host:port:user:pass is told apart from user:pass:host:port.
  • IPv6 friendlyBracketed IPv6 addresses parse correctly and keep their brackets in the link.
  • URL-encoding awarePercent-encoded usernames and passwords in socks5:// URLs are decoded before encoding into the QR.

How to use it

  1. 01

    Enter the string

    Paste one or more proxy strings.

  2. 02

    Choose the output

    Shadowrocket, Nekobox, v2rayNG or generic SOCKS5.

  3. 03

    Export

    Scan, copy the link or download a PNG.

Recognized input formats

host:port · host:port:user:pass · user:pass:host:port · user:pass@host:port · host:port@user:pass · host:port##user##pass · host,port,user,pass · socks5://user:pass@host:port · socks5h:// and http:// prefixes · [IPv6]:port:user:pass

Output link examples

Shadowrocket: socks://Base64(user:pass@host:port)?obfs=none&method=strict&remarks=name. Nekobox / v2rayNG: socks://Base64(user:pass)@host:port#name. Generic: socks://Base64(user:pass@host:port).

Frequently asked questions

The details to know before you choose.

How do I convert an IPv6 endpoint to a QR code?

Wrap the IPv6 host in brackets, for example [2001:db8::1]:1080:user:pass, then choose your client. That example address is for illustration only.

What if the password contains a colon?

In host:port:user:pass, everything after the third colon is treated as the password. Alternatively use a socks5:// URL with a percent-encoded password.

Can the proxy host be a domain?

Yes. The domain is written into the link as-is and resolved by the client when it connects.

Can http:// proxies be converted?

They are read, but the output is always a SOCKS5 link. Make sure the port really serves SOCKS5, or the imported profile will not connect.

Where does the conversion happen?

In your browser. The page never sends the proxy string to a server.

How do I check the converted proxy works?

Run it through the proxy test in the GEOSK5 IP geolocation tool to see the exit IP and location.

Explore the documentation