Group

Basic

Front proxy/Landing proxy

Another method to construct a simple proxy chain.

"Front proxy" is the entry node and "landing proxy" is the exit node.

Balancer or custom full config can't be the front proxy or the landing proxy.

Front proxy and landing proxy will not be applied to custom full config, balancer or proxy chain.

Subscription

Some service providers (so-called "airport") and software providing services (so-called "airport panel") provide differentiated treatment or even refuse to provide service judging by the user agent. You may have to configure a suitable user agent yourself.

Here are the user agent strings of some popular proxy software on Android (replace ${} with the actual values yourself).

Software	User agent
v2rayNG	v2rayNG/${VERSION_NAME}
Clash Meta for Android	ClashMetaForAndroid/${VERSION_NAME}
sing-box	SFA/${VERSION_NAME} (${VERSION_CODE}; sing-box ${VERSION_NAME}; language ${LOCALE_CODE}), example of ${LOCALE_CODE}: zh_Hans_CN

Although this software supports parsing the configuration of some other software to obtain necessary infomation to connect to a server, it is only a workaround for the severe vendor lock-in.

Only general information necessary for connecting to a server will be parsed. Users should control their own preference and behavior. It is recommended to use other software if you want the software to do all things for you.

Only UTF-8 encoding is supported for URI encoding and decoding and config parsing.

In this software, QR code is only for URI encoding and decoding. A URI has been percent-encoded and is therefore compatible with the ASCII character set. For the supported character sets for QR code decoding, please refer to ZXing.

Subscription type

Raw

Due to the URI schemes of a mess and the JSON-like and YAML-like formats full of private features invented by popular proxy software, parsing is done on a best-effort basis, and the success rate and accuracy are not guaranteed.

Share link (URI and URI-like strings)

Share link with public specification, or a collection of share links joint by newline (\n or \r\n or \r), or the Base64 (standard, URL-safe or MIME, with or without padding) encoded form of the collection.

While it is possible to parse some undocumented shared link fields of unknown origin, there is no guarantee.

Some URI scheme maintainers intend to promote their own software and restrict user behavior rather than improve the interoperability between software, so some overly objectionable URI scheme details are not followed.

Protocol	URI Scheme	Import	Export
VMess/VLESS	VMessAEAD / VLESS 分享链接标准提案	✓	✓
VMess	VMess 分享链接说明	✓
VMess	Proposal: VMess Share Link Standard	✓	✓
Trojan	trojan-url	✓	✓
Shadowsocks/Shadowsocks 2022	SIP002 URI scheme	✓	✓
Shadowsocks	URI and QR code	✓
Hysteria 2	URI Scheme	✓	✓
AnyTLS	URI 格式	✓	✓
Juicity	Link Format	✓	✓
mieru	Simple Sharing Link	✓	✓
TrustTunnel	TrustTunnel Deep Link Specification	✓	✓

The backup link starts with exclave:// is from SagerNet's private "SN link" starting with sn://. It is in fact the binary dump of internal database and it does not guarantee forward or backward compatibility. It should only be used for local backup and restore of software settings, and should NOT be used for share. It continues to exist only because alternative is not currently implemented, and it will be removed once a suitable backup and restore solution is implemented in the future.

mihomo/Clash configuration

YAML-like format. Parse proxies only.

V2Ray JSONv4 configuration

JSON-like format. Parse outbounds only. Can also parse a single OutboundObject. "V2Ray" here means V2Ray, the modified V2Ray by this software, or Xray.

V2Ray JSONv5 configuration

JSON-like format. Parse outbounds only. Can also parse a single OutboundObject.

sing-box configuration

JSON-like format. Parse outbounds and endpoints. Can also parse a single outbound or endpoint.

WireGuard configuration

WireGuard configuration (INI format).

Shadowsocks configuration

Shadowsocks configuration (JSON format).

SIP008

SIP008 Online Configuration Delivery, for Shadowsocks only. A superset of Shadowsocks configuration.

Used traffic, remaining traffic and expiration time

For SIP008 subscriptions, used traffic and remaining traffic are read from JSON item bytes_used and bytes_remaining in the subscription content.

For other subscriptions, used traffic, remaining traffic, and expiration time are read from item upload, download, total and expire in the HTTP response header Subscription-Userinfo (this is a private field used by many proxy software). Some "airports" and "airport panels" selectively and exclusively provide this parameter based on the user agent, and you may need to set a suitable user agent yourself.