Practical position
Mihomo is the mainstream core used by many modern Clash-compatible clients. It preserves the Clash YAML workflow while extending modern outbound types such as VLESS, Hysteria2, TUIC, AnyTLS, Mieru, Sudoku, MASQUE, TrustTunnel and OpenVPN.
Positioning
Mihomo YAML for modern GUI clients, complex subscriptions, TUN, DNS, rule providers and newer protocols.
| Item | Meaning |
|---|---|
| Status | Current mainstream |
| Profile format | Mihomo YAML for modern GUI clients, complex subscriptions, TUN, DNS, rule providers and newer protocols. |
| Protocol check | Use the core/protocol matrix |
Best Use Cases
- Most new users choosing a maintained Clash-compatible GUI.
- Subscriptions containing VLESS Reality, Hysteria2, TUIC, AnyTLS or similar types.
- Users who need richer DNS, TUN, rules and API behavior.
Compatibility Notes
Protocol support depends on the selected core, client build, operating-system permissions and profile syntax. Treat provider subscription names as hints, then verify the actual parsed node fields in the client log.
- Mihomo is Clash-compatible, but old fields should still be reviewed.
- A node appearing in the UI does not mean the network path works; check UDP, TLS, SNI and Reality details.
- Different clients can bundle different Mihomo versions.