Node HandbookNODE HANDBOOK中文
Online tool

vmess to Clash converter: vmess, vless, trojan and ss links into one Clash YAML

Paste vmess, ss, trojan, vless or hysteria2 share links, or a Base64 subscription, and get a Clash Meta YAML config. Runs in your browser. No upload, no account, no tracking of what you paste.

Updated 2026.11.19
Short version
  • Supports: vmess, ss, trojan, vless, hysteria2 and tuic share links, plus Base64 subscription blobs
  • Privacy: all parsing happens locally; nothing you paste leaves the page
  • Works with: Clash Verge Rev, FlClash, Karing, mihomo
  • Does not work with: the original Clash or Clash Premium kernel, which cannot read ws-opts or reality

Most people arrive here holding one vmess:// URL and wanting to convert vmess to a Clash config by hand. The field tables further down are the reference for that; if you have a mixed list instead, paste it above and convert the whole list at once. Nothing is installed and no subconverter backend is involved — the parsing runs in the page, so the result is identical on Windows, macOS, Linux and Android.

How to use it

  1. Paste your share links, one per line, into the left box. A whole Base64 subscription works too - it is detected automatically.
  2. Click Convert. The right box fills with a complete Clash Meta config.
  3. Click Download config.yaml and import it as a local profile in your client.

If you actually want a subscription that keeps updating rather than a one-off file, read the error index for the difference between a profile that failed to update and one that was never valid.

Convert

Waiting for input. All parsing happens in this browser tab - you can even disconnect from the network and keep using this page.

What usually goes wrong

SymptomCauseFix
"Unsupported proxy type"Client runs the original Clash kernelSwitch to a Meta kernel client: Clash Verge Rev, FlClash, Karing
Nodes appear but all time outThe password or port in the share link was rotatedRe-copy from the provider; use the subscription URL rather than a one-time conversion
ws nodes fail, tcp nodes workHost or path lost during conversionCheck that host and path are URL-encoded in the original link
reality handshake failsMissing public-key or short-idThe source link must carry both pbk and sid
Base64 decodes to gibberishProvider sent an encrypted format, not a universal subscriptionUse the provider's Clash subscription instead

Why not just use a hosted converter

Most online subscription converters submit your link to their backend, parse it there, and return the result. The operator can see your full node list, including passwords and ports. They also become a single point of failure: when the site goes down, gets blocked, or starts charging, every client that points at it fails on the next refresh. That failure mode is one of the most common causes of "subscription update failed" reports.

Here the conversion logic ships with the page. Your input is read into memory, parsed, and rendered into the output box with no network request at all. Open developer tools, watch the Network panel, and click Convert - nothing appears. The page still works with the network disconnected, which is the strongest proof available.

Supported link formats

vmess:// structure

A Base64-encoded JSON object with fixed fields: v version, ps name, add address, port, id UUID, aid alterId, scy cipher, net transport, host, path, tls, sni.

{
  "v": "2", "ps": "HK-01", "add": "1.2.3.4", "port": "443",
  "id": "uuid-here", "aid": "0", "scy": "auto",
  "net": "ws", "host": "example.com", "path": "/ws",
  "tls": "tls", "sni": "example.com"
}

net=ws becomes ws-opts; tls=tls becomes tls: true plus servername.

Two ss:// variants

SIP002: ss://base64(method:password)@host:port#name - only the credential is encoded. Legacy: ss://base64(method:password@host:port)#name - the whole body is encoded. Both are handled. Plugin parameters such as plugin=obfs-local are mapped to plugin-opts.

trojan:// and vless://

trojan://password@host:443?sni=host&allowInsecure=1#name. vless adds type, security (tls / reality / none), flow, pbk and sid. allowInsecure=1 maps to skip-cert-verify: true, which should only be used while diagnosing a broken certificate chain.

Convert each link type to Clash

Every scheme carries a different field set, and the field that trips people up is almost never the one they expect. These are the mappings this converter applies, written out so you can check the result by hand.

vmess to Clash: decoding the vmess:// payload

vmess:// is Base64 over a JSON object, so the whole link is unreadable until it is decoded. add becomes server, port stays port, id becomes uuid, aid becomes alterId and scy becomes cipher. Transport lives in net: ws becomes ws-opts with path and a Host header taken from host. tls=tls becomes tls: true plus servername from sni. Clash only accepts auto, aes-128-gcm, chacha20-poly1305 and none as cipher values; anything else has to be normalised before import.

ss to Clash: SIP002 and the older ss:// encoding

Two encodings circulate and they fail differently. SIP002 looks like ss://base64(method:password)@host:port#name and only the credential is encoded. The older form is ss://base64(method:password@host:port)#name and encodes the entire body, which is why a naive split on @ produces a broken server address. Both map to type: ss with cipher, password, server and port. A plugin=obfs-local parameter becomes plugin: obfs with mode and host under plugin-opts; v2ray-plugin maps the same way with mode: ws.

trojan to Clash: password, SNI and allowInsecure

The password sits in the userinfo position, before the @, and the port is almost always 443. Query parameters carry the rest: sni becomes sni, type=ws adds ws-opts, and allowInsecure=1 becomes skip-cert-verify: true. That last flag disables certificate checking, so it belongs in a diagnostic session, not in a profile you keep. Output type is trojan.

vless to Clash: UUID, flow and reality keys

vless has no password; identity is the UUID in the userinfo position. It needs a Clash Meta / mihomo core, because the original Clash core has no vless support at all. flow=xtls-rprx-vision is copied verbatim, security=reality adds reality-opts with public-key from pbk and short-id from sid, and fp becomes client-fingerprint. Drop any of those three and the node authenticates but never carries traffic.

hysteria2 to Clash: QUIC over UDP

hysteria2 rides QUIC over UDP, so it also requires mihomo — the original Clash core cannot run it. hysteria2://password@host:port maps password to password; sni, obfs and obfs-password are carried across unchanged, and up/down become bandwidth hints. If the client reports an unknown proxy type, the core is the problem, not the link.

subscription to Clash: one Base64 blob, many nodes

A subscription URL usually returns one Base64 blob that decodes to a list of share links, one per line. Converting it means decoding once, parsing each line by its scheme, then emitting a proxies: list. Two failure modes dominate: the response was HTML (a login page or an error page) rather than Base64, or the decoded text mixes several schemes and one line is malformed, which aborts the whole parse. This tool reports the line that failed instead of silently dropping it.

If you have used subconverter before, the difference is where the work happens: subconverter is a service you point a client at, and the client re-fetches a converted profile every time it updates. Here the conversion is a one-off, and the YAML is a file you keep. That matters when the source subscription changes daily — with a converter URL your client silently picks up nodes you never looked at, while a fixed YAML only changes when you regenerate it.

To convert a whole subscription to Clash online, paste the subscription URL rather than a single link; if the subscription is behind a login or a per-user token, download it first and paste the decoded text.

After converting

Generating the file is step one. Once it is imported, confirm three things: a proxy group has a usable outbound selected, the log shows requests actually entering the proxy, and your egress IP really changed. Compare the before and after result with the IP check.

If nothing loads at all, first separate a broken config from a client that never took over the network - those two have completely different troubleshooting paths. The error index groups them by the exact string the client prints.

FAQ

Does it upload my nodes anywhere?

No. Parsing and generation run in the page. To verify, open the Network panel and click Convert - the request count stays at zero.

Why "unsupported proxy type"?

The kernel is too old. vless, hysteria2, tuic and ws-opts require the Clash Meta (mihomo) kernel.

Base64 output is gibberish?

The provider did not send a universal subscription. Use their Clash subscription format, or decode first to see what is actually inside.

Is the result safe to keep long term?

It works until the provider rotates credentials. For steady use, import a subscription URL so the client can refresh it.

Scope

This tool converts formats only. It does not supply nodes, test speed, or claim a node works. Every server address in the output came from text you pasted; nothing is stored or forwarded. The generated config is deliberately minimal: one select group, one url-test group, and only GEOIP,CN,DIRECT plus a MATCH fallback. No third-party rule sets are bundled - layer your own in the client if you need full routing.