The core performs proxying and rule matching. The client manages UI, profiles and switches. A protocol is a node or outbound type. Empty node lists, unsupported Reality/Hysteria2/TUIC/AnyTLS fields and incomplete imports usually start with core compatibility.
How to Choose
- For modern Clash-compatible GUI clients such as Clash Verge Rev, FlClash and Clash Party, check Mihomo compatibility first.
- Older clients such as Clash for Windows, ClashX and ClashX Pro belong mostly to the original Clash or Premium era and may not support newer protocols.
- sing-box, Xray-core and V2Ray-core are not Clash YAML cores; their configuration formats are different unless a client provides conversion.
- iOS clients often use their own implementations, so check whether the app supports Clash profiles, Mihomo fields or the exact protocol you need.
Common Core List
Clash Core
The original Dreamacro Clash core established the familiar Clash YAML model, rule routing, proxy groups, RESTful API and Fake-IP DNS concepts.
- Config format
- Clash YAML
- Typical use
- Older clients, classic protocols, basic rule routing
Clash Premium
Clash Premium historically added advanced features such as TUN, Rule Providers, scripts and eBPF. It still appears in old tutorials, but most new users should not look for it as a standalone path.
- Config format
- Clash YAML with Premium fields
- Typical use
- Old tutorials, TUN, script rules, rule providers
Clash.Meta Core
Clash.Meta is the enhanced Clash-compatible name many older clients and tutorials still use. In current troubleshooting, check whether the client has moved to Mihomo.
- Config format
- Clash.Meta / Mihomo-compatible YAML
- Typical use
- Older Meta clients, migration-era profile fields
Mihomo Core
Mihomo is the core used by many current Clash-compatible clients, with broader protocol, DNS, TUN, rule and API capabilities. Treat “Meta/Mihomo” labels as a reason to check the Mihomo docs.
- Config format
- Mihomo YAML
- Typical use
- Clash Verge Rev, FlClash, Clash Party, newer protocols
sing-box
sing-box is an independent universal proxy platform, not a Clash core. It supports many inbounds, outbounds, DNS, routing and TUN features, but it does not use Clash YAML directly.
- Config format
- sing-box JSON
- Typical use
- Hiddify, Karing, official sing-box clients, server deployments
Xray-core
Xray-core belongs to the Project X / Xray ecosystem and is often seen with VLESS, REALITY and XTLS-style setups. It is usually managed by Xray/V2Ray-family clients.
- Config format
- Xray JSON
- Typical use
- v2rayN, NekoRay/NekoBox-style clients, VLESS Reality
V2Ray-core
V2Ray-core is the Project V core that many early VMess/V2Ray clients and server configurations were built around. Its configuration and routing model differ from Clash-compatible cores.
- Config format
- V2Ray JSON
- Typical use
- VMess, V2Ray ecosystem clients, server configs
Proprietary Client Cores
Shadowrocket, Quantumult X and some iOS or commercial clients may use their own implementations. They can still import some Clash-style profiles, but support depends on the app.
- Config format
- Client-specific / Clash-compatible / converted subscription
- Typical use
- iOS, App Store clients, lightweight mobile use
Core and Protocol Compatibility
A single subscription may contain SS, VMess, VLESS, Trojan, Hysteria2, TUIC, AnyTLS, WireGuard and other node types. Whether they show up, test or connect depends on both the subscription and the core.
| Problem | Check first | Next step |
|---|---|---|
| Subscription import check | Subscription format and supported protocol types | Use a Mihomo-compatible client or ask for a Clash/Mihomo profile |
| VLESS Reality has a problem | VLESS, Reality, fingerprint and flow support | Check the client core version and logs |
| Hysteria2/TUIC does not connect | UDP, QUIC, port and protocol support | Check system permissions and network conditions |
| Clash YAML does not work in sing-box | Different config format | Use client conversion or write sing-box JSON separately |
These Are Not Cores
- Clash Verge Rev, FlClash, Clash Party, ClashX and Clash for Windows are clients, not the core itself.
- VLESS, Trojan, Hysteria2, TUIC and AnyTLS are protocols or outbound types, not client cores.
- A subscription provider, airport/service brand or node name is not a core.
- Proxy groups, DIRECT and DNS are routing behaviors or policies, not remote proxy protocols.