SOCKS5 QR code generator

When you spot-check on mobile, skip typing proxies into a phone. Paste the list, generate client-specific socks:// links and QR codes, and scan them one by one.

$ kimi tools qr --client shadowrocketDeveloper tools

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

  • 01Standard link encoding

    Shadowrocket expects the whole authority in Base64 while v2rayN-style clients encode only the credentials; the tool picks the right one.

  • 02Batch, one by one

    Paste a whole set, get one code per line and step through them without re-pasting.

  • 03Copyable links

    Besides the image, copy the import link itself to share with teammates or drop into a test script.

Workflow

From paste to result in three steps

  1. step_1

    Paste the list

    One proxy per line; common separators are recognized.

  2. step_2

    Choose the client

    Pick Shadowrocket, Nekobox or v2rayNG for the test device.

  3. step_3

    Scan or copy

    Scan to import, or copy the socks:// link for another tool.

How is a socks:// link encoded?

Shadowrocket uses socks://Base64(user:pass@host:port) plus obfs, method and remark parameters. Nekobox and v2rayNG follow the v2rayN convention: socks://Base64(user:pass)@host:port#remark. The tool uses UTF-8 safe Base64, so passwords with non-ASCII or special characters encode correctly.

Where does this help?

Checking regional content on mobile, seeing how an app behaves behind different exits, or handing a fixed exit to a colleague in the field. For large collection jobs, configure proxies directly in your crawler instead.

Frequently asked questions

Use a task or environment name in the remark. Batch generation appends a sequence number so profiles are easier to distinguish in your Android client.