Local configuration tool
TUIC to Clash / Mihomo YAML
TUIC v5 only: UUID and password credentials, congestion control and UDP relay mode.
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 TUIC fields map to Clash
What this converter actually does, line by line. On the left is how it is written in a TUIC link; on the right is the field it becomes in the Clash config.
| In the link | In the Clash config | Notes |
|---|---|---|
uuid:password@host:port | uuid / password / server / port | TUIC v5 authenticates with both a UUID and a password; either one missing is an error. |
sni / alpn | sni / alpn | QUIC again, so TLS is implicit and there is no enable flag to set. |
congestion_control | congestion-controller | cubic, new_reno or bbr. Note the target names differ by more than punctuation — Mihomo says controller. |
udp_relay_mode | udp-relay-mode | native or quic. udp-relay-mode is accepted as an alias in the link. |
reduce_rtt | reduce-rtt | sing-box reads zero_rtt_handshake; a config that says reduce_rtt is silently ignored by it. |
disable_sni | disable-sni | In sing-box this is a shared TLS option, so it lands inside the tls block rather than on the outbound. |
token | Rejected with an error | A token means TUIC v4, whose wire format and authentication differ from v5 — there is no safe reinterpretation. |
FAQ
- Which client do I use after converting TUIC to Clash?
- Use Clash Verge Rev, Mihomo (Clash.Meta) or ClashX Meta. Original Clash and Clash Premium do not support TUIC at all — importing this config there leaves you with a node that never connects.
- Is this TUIC 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.