Practical position
Clash.Meta is a common enhanced fork name in the Clash ecosystem. The name still appears in clients and subscriptions, but current project and documentation context usually points to Mihomo.
Positioning
Clash.Meta / Mihomo-compatible YAML; always check the actual bundled core version.
| Item | Meaning |
|---|---|
| Status | Legacy Meta name |
| Profile format | Clash.Meta / Mihomo-compatible YAML; always check the actual bundled core version. |
| Protocol check | Use the core/protocol matrix |
Best Use Cases
- When a client or provider still says Meta Core or Clash Meta.
- When a subscription supports Meta but has a problem in the original Clash format.
- When deciding whether newer protocols require a Mihomo-compatible client.
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.
- Clash.Meta in a client name is not enough to prove compatibility.
- A provider saying “Clash Meta” does not guarantee every field works in your client.
- An old Meta build may still miss newer protocols.