Clash Meta vs Original Clash: A Comprehensive Comparison

When setting up Clash, one of the first decisions you face is choosing between the original Clash core and Clash Meta. While they share the same foundation, there are significant differences in protocol support, rule engine capabilities, DNS handling, and more. This guide breaks down every key difference to help you make the right choice.

History: From Original Clash to Meta Fork

The Rise and Fall of Original Clash

Clash was originally developed by Dreamacro as a multi-platform, rule-based proxy client written in Go. Thanks to its flexible rule engine and broad protocol support, it quickly became the most popular proxy tool in the community.

The Birth of Meta

After the original repository was removed, community developers created multiple forks based on the last publicly available source code. Clash Meta (maintained by MetaCubeX) emerged as the most successful and active fork. It not only inherited all features from the original but also added new protocols and capabilities.

Protocol Support: Meta Goes Further

Protocol support is the most critical difference between the two. Meta has significantly expanded the range of supported protocols:

Meta-Exclusive Protocols Explained

Vless + Reality: Currently the most censorship-resistant protocol combination. Reality simulates real TLS fingerprints, making it extremely difficult to detect and block. For users who frequently face interference, this is the top choice.

Tuic: A QUIC-based UDP protocol with ultra-low latency, ideal for gaming and real-time communication.

Hysteria2: A high-performance QUIC protocol with excellent tolerance to packet loss, perfect for unstable network conditions.

WireGuard: A lightweight VPN protocol with exceptional performance, suited for scenarios requiring stable persistent connections.

Rule Engine: Meta Is More Flexible

The rule engine determines how Clash routes different types of traffic. Meta adds numerous rule types beyond the original:

Original Clash Rule Types

• DOMAIN: Exact domain matching
• DOMAIN-SUFFIX: Domain suffix matching
• DOMAIN-KEYWORD: Domain keyword matching
• IP-CIDR: IP range matching
• IP-CIDR6: IPv6 range matching
• SRC-IP-CIDR: Source IP range matching
• GEOIP: Geolocation-based matching
• DST-PORT: Destination port matching
• SRC-PORT: Source port matching
• MATCH: Catch-all rule

Meta's Additional Rule Types

RULE-SET Rule Providers

RULE-SET is one of Meta's most important enhancements. It allows you to define rules in external files and reference them on demand, keeping your main configuration lean:

rule-providers:
  reject:
    type: http
    behavior: domain
    url: "https://cdn.jsdelivr.net/gh/MetaCubeX/meta-rules-dat@release/lite/reject.yaml"
    path: ./ruleset/reject.yaml
    interval: 86400
  
  proxy:
    type: http
    behavior: domain
    url: "https://cdn.jsdelivr.net/gh/MetaCubeX/meta-rules-dat@release/lite/proxy.yaml"
    path: ./ruleset/proxy.yaml
    interval: 86400
  
  direct:
    type: http
    behavior: domain
    url: "https://cdn.jsdelivr.net/gh/MetaCubeX/meta-rules-dat@release/lite/direct.yaml"
    path: ./ruleset/direct.yaml
    interval: 86400

rules:
  - RULE-SET,reject,REJECT
  - RULE-SET,proxy,Proxy
  - RULE-SET,direct,DIRECT
  - GEOIP,LAN,DIRECT
  - MATCH,Proxy

LOGICAL Composite Rules

LOGICAL rules let you combine multiple rules using boolean logic for fine-grained traffic routing:

rules:
  # Only proxy google.com traffic on port 443
  - LOGICAL-AND,
    - DOMAIN,google.com
    - DST-PORT,443
    ,Proxy
  
  # Direct traffic from bilibili.com or douyin.com
  - LOGICAL-OR,
    - DOMAIN,bilibili.com
    - DOMAIN,douyin.com
    ,DIRECT

DNS Handling Differences

DNS handling is crucial for a proxy tool, directly affecting access speed and pollution prevention.

Original Clash DNS Capabilities

• Support for nameserver and fallback configuration
• DoH (DNS over HTTPS) support
• Geolocation-based DNS query splitting
• Fake-IP mode support

Meta's DNS Enhancements

Nameserver Policy is a standout Meta DNS feature:

dns:
  enable: true
  enhanced-mode: fake-ip
  nameserver-policy:
    # Use domestic DNS for Chinese domains
    "+.baidu.com":
      - "https://dns.alidns.com/dns-query"
    # Use foreign DNS for international domains
    "+.google.com":
      - "https://dns.google/dns-query"
    # Wildcard: all other domains
    "+":
      - "https://dns.alidns.com/dns-query"
      - "https://dns.google/dns-query"

Configuration Syntax Differences

While Meta and the original share largely compatible configuration syntax, there are some differences to note:

1. Configuration Header Declarations

Meta recommends new header fields to declare kernel-specific options:

# Meta kernel configuration
profile:
  store-selected: true
  store-fake-ip: true

# Global client fingerprint
global-client-fingerprint: chrome

2. Proxy Group Type Differences

Meta adds the dialer-proxy field, allowing chained proxies (proxy over proxy):

proxies:
  - name: "ss-over-trojan"
    type: ss
    server: example.com
    port: 443
    cipher: aes-256-gcm
    password: "your-password"
    dialer-proxy: "trojan-relay"  # Route through trojan-relay proxy

3. TLS Configuration Enhancements

Meta significantly enhances TLS configuration with more fingerprinting options:

proxies:
  - name: "vless-reality"
    type: vless
    server: example.com
    port: 443
    uuid: your-uuid
    network: tcp
    udp: true
    flow: xtls-rprx-vision
    reality-opts:
      public-key: your-public-key
      short-id: your-short-id
    client-fingerprint: chrome  # Client fingerprint spoofing
    tls: true

4. Compatibility Notes

Client Support Landscape

Since the original Clash is no longer maintained, the vast majority of active clients have switched to the Meta core:

Performance Comparison

Performance is another important dimension many users care about.

Memory Usage

Due to additional protocol and rule type support, Meta uses slightly more memory than the original. With few rules, the difference is minimal (about 10-20MB). However, when rule sets exceed thousands of entries, Meta's optimization mechanisms (such as binary mrs format) significantly reduce memory consumption.

CPU Usage

In daily use, CPU usage is nearly identical between the two. Meta's Vless/Reality protocols may incur marginally higher CPU overhead in some scenarios, but the difference is within 5%.

Network Throughput

When using the same protocols, network throughput is essentially the same. Meta's Tuic/Hysteria2 protocols are UDP-based and show clear throughput advantages in high packet loss environments.

Rule Matching Speed

Meta's mrs binary rule format loads and matches significantly faster than the YAML text format used by the original. If your configuration has a large number of rules, Meta's performance advantage is very noticeable.

Migration Guide: Moving from Original to Meta

If you're still using the original Clash core, here are the complete migration steps to switch to Meta:

rule-providers:
  # Meta-specific rule sets (mrs format, better performance)
  reject:
    type: http
    behavior: domain
    url: "https://mirror.ghproxy.com/https://github.com/MetaCubeX/meta-rules-dat/releases/download/latest/lite/reject-domain.mrs"
    path: ./ruleset/reject.mrs
    interval: 86400

Which Should You Choose?