What Is Clash?

Clash organizes core concepts, configuration syntax, rules, DNS, Premium features and advanced usage in English.

What is Clash?

Clash is a cross-platform, rule-based proxy core that runs at the network and application layers. It receives local traffic through HTTP, SOCKS, mixed-port or TUN-style entry points, evaluates the configured rules, and then sends each request through a direct connection, a rejected policy, a single proxy or a proxy group.

This English documentation is organized for users who need more than a one-click GUI workflow. It explains the core concepts behind profiles, rules, DNS, proxy groups, Premium-era features and advanced integrations so that configuration changes can be made deliberately rather than by guesswork.

The original Clash ecosystem includes the open-source Clash core published under the Dreamacro project and the historical Premium feature set that added capabilities such as TUN support and other advanced routing functions. Modern GUI clients may use Clash, Clash Meta or Mihomo-compatible cores, so always check which syntax your selected client supports.

Most users should start with a maintained GUI client instead of running the core manually. Choose a client from the download center, follow the matching setup tutorial, import the provider subscription URL, update the profile and use Rule mode for daily routing before adjusting DNS, TUN or custom rules.

  • Clash Verge Rev: a common desktop choice for Windows, macOS and Linux users who want a modern Mihomo-based GUI.
  • FlClash: a cross-platform client that is useful when you want a similar workflow across desktop and Android.
  • Clash for Android and Clash Meta for Android: Android options for VPN-mode proxy routing.
  • Stash, Shadowrocket and Quantumult X: iOS alternatives that support Clash-compatible profile and rule workflows within iOS platform limits.

If a subscription contains SS, VMess, VLESS, Trojan, Hysteria2, TUIC, AnyTLS, WireGuard or another node type, use the protocol center and the core matrix to confirm compatibility before troubleshooting. Keep the glossary and configuration examples nearby when editing profiles.

Feature overview

  • Inbound support for HTTP, HTTPS, SOCKS5, mixed-port and TUN-style entry points, depending on the core and client.
  • Outbound support for direct routing, rejection, proxy nodes and proxy groups; maintained Mihomo-compatible clients may also support newer types such as VLESS, Hysteria2, TUIC, AnyTLS, Mieru, Sudoku, MASQUE, TrustTunnel and OpenVPN. See the protocol center.
  • Rule-based routing by domain, domain suffix, domain keyword, IP CIDR, GEOIP, GEOSITE, process name and other supported matchers.
  • DNS features such as fake-ip and resolver policy, which help domain-based rules work even when traffic is intercepted at the network layer.
  • Remote providers for proxy lists and rule sets, allowing managed subscriptions and rule data to update without replacing the entire profile.
  • External controller APIs that let GUI clients and dashboards read runtime state, update configuration and inspect connections.

Some features depend on the selected core, client build, operating system permission model and whether the profile uses Clash, Clash Meta or Mihomo-compatible syntax.

License

The original Dreamacro Clash project is published under the GPL-3.0 license, with earlier historical versions using MIT licensing before the license change noted in the upstream repository. This site is an independent guide that organizes downloads, tutorials, documentation and FAQs; it does not operate proxy nodes or subscription services.

Common scenario guides