Local configuration tool
Hysteria2 to Clash / Mihomo YAML
Converts Salamander obfuscation, bandwidth hints and port hopping into Mihomo's field names.
Conversion happens entirely in your browser. Links are not uploaded, saved, or placed in the page URL.
Conversion result
Why some links are rejected
A parameter that cannot be mapped without changing how the connection behaves is reported rather than dropped. For a Mihomo config that means certificate pinning, TUIC v4 tokens, and uTLS fingerprints on the QUIC-native protocols, where a handshake has nowhere to put one. A silently weakened config is worse than a rejected line.
How to import into Clash Verge Rev
Profiles → new Local profile → pick the downloaded YAML. Clash Verge Rev, Mihomo and ClashX Meta all read the same file; original Clash and Clash Premium do not.
How Hysteria2 fields map to Clash
What this converter actually does, line by line. On the left is how it is written in a Hysteria2 link; on the right is the field it becomes in the Clash config.
| In the link | In the Clash config | Notes |
|---|---|---|
password@host:port | password / server / port | The Hysteria 2 URI spec allows a colon inside the auth string, so it is kept intact. |
sni | sni | Hysteria2 runs over QUIC, so TLS is always on and neither target has a tls toggle to set. |
obfs=salamander + obfs-password | obfs / obfs-password | salamander is the only obfuscation defined; obfs without a password is an error. |
up / down | up / down ("100 Mbps") | Mihomo wants a string with a unit, sing-box wants a bare number. Both are produced for you. |
mport | ports ("443,8000-9000") | Port hopping. The separators differ — a hyphen in Mihomo, a colon in sing-box. |
alpn / insecure | alpn / skip-cert-verify | insecure and allowInsecure are the same parameter; using both is an error. |
pinSHA256 | Rejected with an error | Certificate pinning has no equivalent field in either target, and dropping it would weaken the connection. |
fp | Rejected with an error | uTLS fingerprints are a TCP-TLS concept; a QUIC handshake has nowhere to put one. |
FAQ
- Which client do I use after converting Hysteria2 to Clash?
- Use Clash Verge Rev, Mihomo (Clash.Meta) or ClashX Meta. Original Clash and Clash Premium do not support Hysteria2 at all — importing this config there leaves you with a node that never connects.
- Is this Hysteria2 converter free, and does it upload my node links?
- It is free and needs no account. The conversion is done by JavaScript inside this page, on your own machine: links are never uploaded, never written into the page URL, and never stored. Closing the tab is all the cleanup there is.
- Can I convert a subscription link straight to Clash?
- Yes, but paste the body the subscription URL returns — usually one long base64 string — rather than the URL itself, which the browser cannot fetch across origins. Mixed protocols in one subscription are fine. Subscription to Clash converter
- The Clash config converted fine but will not connect — what now?
- This page only translates links into a config: it checks the structure, never whether the server is reachable. Confirm the same link works in the client you copied it from, then check the client version — the XHTTP transport needs Mihomo 1.19 or newer.
This creates a one-time local configuration, not an auto-updating subscription. It checks configuration structure, not whether a server is reachable.