Routing is Clash's core capability. The rules section of the config file matches traffic line by line using types such as DOMAIN, DOMAIN-SUFFIX, DOMAIN-KEYWORD, IP-CIDR, GEOIP and RULE-SET; a hit is handed to the corresponding proxy group, and anything unmatched falls through to MATCH. Rule order is priority, so put the most specific rules first. Unlike all-in-one global proxy tools, sites in mainland China connect directly without entering the tunnel, saving bandwidth and keeping speeds up; only domains that need a proxy go through a node. The GeoIP database needs regular updates, and Chapter 3 of the advanced manual covers subscription-based rule-set management in full.
Read the matching chapter of the advanced manualA proxy group decides which exit node receives matched traffic. select is manual choice, suited to a fixed daily setup; url-test automatically picks the fastest node by latency, with configurable test interval and tolerance to avoid constant flipping; fallback switches down the list when the primary node fails; load-balance spreads connections across multiple nodes. Groups can be nested—for example, regional sub-groups inside an "auto-select" group, one layer for policy and one for nodes. Switching groups in the client panel takes effect immediately without restarting the core. Chapter 1 of the advanced manual gives config examples and use cases for each type.
Read the matching chapter of the advanced manualA subscription is a node list issued by your provider—essentially a config link fetched on a schedule. Clients can hold multiple subscriptions at once, each with its own update interval. Local overrides let you append your own rules and proxy groups without editing the subscription source, and they survive every refresh; that is the key difference from editing the subscription file directly, where changes are wiped out on the next update. Chapter 6 of the advanced manual has full examples of merging subscriptions, anchor reuse and override templates. Treat subscription links like account credentials—never paste them into public forums or group chats.
Read the subscription setup guideDNS configuration directly affects routing accuracy. The core has a built-in DNS server and supports nameserver, fallback and nameserver-policy for grouped resolution by domain, sending domains inside and outside China to different upstreams. With Fake-IP enabled, domain decisions are made at the DNS stage, avoiding the leaks caused by resolving first and matching later; domain sniffing can recover domains misjudged by IP direct rules from the TLS handshake. A common problem is ISP-hijacked system DNS breaking routing and slowing everything down; Chapter 4 of the advanced manual provides a recommended config template and a symptom-by-symptom diagnosis order.
Read the matching chapter of the advanced manualThe default system proxy only handles apps that honor HTTP / SOCKS proxy settings; games, command-line tools and some clients ignore it entirely. TUN mode creates a virtual network adapter in the core and takes over all TCP and UDP traffic on the device via the routing table, working with Fake-IP to achieve true global routing—apps that ignore the system proxy are still matched by the rules. On Windows it requires installing the service mode or running as administrator; on macOS the first launch needs a one-time authorization. Chapter 5 of the advanced manual covers stack selection (gvisor / system / mixed) and handling conflicts with virtual machines and other NIC-based software.
Read the matching chapter of the advanced manualAll five platforms share the mihomo core; the difference lies in the GUI wrapper. On Windows and macOS, Clash Plus and Clash Verge Rev are actively updated; Android offers Clash Meta for Android and FlClash; iOS is served by Clash Plus on the App Store, official site clashplus.io; on Linux desktops use Clash Verge Rev, while servers and routers run the core directly with a config file. The download page lists every available client by platform with maintenance status and system requirements; discontinued clients are archived separately and demoted, no longer recommended for new users.
Go to the client download roundupPick the installer for your system on the download page: Clash Plus on Windows, the right chip architecture build on macOS, and the app store or direct APK on phones.
STEP 02Open the client's subscription or profile page, paste the subscription link and hit update; once the node list appears, the import succeeded. If the link is dead, ask your provider for a new one.
STEP 03Choose rule mode and a node, turn on the system proxy, then visit an IP lookup site to confirm your exit address has changed—that completes the first connection.
The original Clash project went open source around 2019. After the author archived the repository in 2023, the community carried on under the name Clash.Meta, later renamed mihomo. Nearly every active client on all platforms today is built on this core; the original rule syntax and config structure were fully inherited, and configs written years ago still work.
The core and all major clients are released under open-source licenses such as GPL-3.0. The source code is public, so anyone can audit how traffic is handled—there is no black box. The community has built GUI clients, rule sets, subscription converters, external dashboards and more around the core, forming a complete toolchain users can freely combine.
On this site, "Clash" refers to the whole ecosystem: the mihomo core parses configs, matches rules and establishes connections, while GUI clients handle subscription management, node display and on/off controls. Once you understand this split, switching clients requires no relearning—config syntax and rule experience carry over across all platforms.
The core and each client release independently. Version numbers and download URLs on our download page are resolved live from a version manifest on every visit—no fixed versions are hard-coded into the page. Discontinued clients get an archived badge and are removed from recommendations. Guides and the manual are revised as core behavior changes, with the update date noted at the end.
git clone https://github.com/MetaCubeX/mihomo.gitUsually a network issue or a dead link: turn on the proxy before updating, or retry on a different network; if it still fails, ask your provider whether the link has changed. Step-by-step checks are in the troubleshooting board.
UWP apps on Windows are subject to loopback restrictions—enable loopback exemption in the client. Command-line tools and games ignore the system proxy; use TUN enhanced mode to take them over. Both cases have dedicated entries in the troubleshooting board.
An unreachable test URL or overly high test concurrency will both show as timeout. Switch the test URL to a reachable address, or simply trust real browsing results—the latency number is only a reference.
Switch from global routing to rule mode, lower the log level below warning, and disable background keep-alive as needed—battery drain usually drops noticeably after these three changes. Per-platform power-saving settings are in the troubleshooting board.
The complete flow from downloading and installing to importing a subscription and enabling the system proxy, covering common Windows install pitfalls plus permission and port-conflict fixes.
Read moreWhat to do after launching Clash for the first time: import a subscription, pick a node, test latency, and confirm the proxy is working via both a web page and the command line.
Read moreUpdate failures usually come down to network conditions, dead links or client settings. This post checks each cause and suggests sensible auto-update intervals.
Read more