Frontispiece · Entry HEADWORDPlate Edition · First Printing
Clash/klæʃ/ · noun · open-source proxy clientClient downloads and configuration reference for every platform
This site catalogs the Clash ecosystem in an encyclopedic style: client installers for five platforms, mihomo core configuration methods, rule-based routing and proxy group usage, and a selection guide for proxy protocols. Every entry sticks to plain facts and usage.
Six entries catalog the most essential capabilities in everyday Clash use, numbered Plate II through Plate VII. Click any entry title to expand its detailed explanation; together they form a minimal but complete map of Clash knowledge.
Plate II
Preset rules decide where every connection goes: domestic sites route direct, traffic bound outside the region goes through a proxy, and ad domains get rejected outright — all handled automatically by the rule table, no manual switching required.
Explication
Rule-based routing works top-down: the first match wins. The core matches connections against the rules list in order, and matching types include DOMAIN, DOMAIN-SUFFIX, GEOSITE, GEOIP, IP-CIDR, and more, usually with a MATCH rule as the catch-all at the bottom. Rule order is strategy: pin frequently visited local sites to DIRECT for speed, force sensitive services through the proxy, and block ad domains with REJECT. For a hands-on walkthrough, see Rule-Based Routing in Practice.
Plate III
Group several nodes together and expose them as a single exit using strategies like manual selection, automatic latency testing, or failover — the brain behind node scheduling.
Explication
There are four common proxy group types: select for manual picking; url-test for periodic latency checks that auto-switch to the fastest node; fallback for ordered failover; and load-balance for spreading connections across the group. Proxy groups can nest — for example, layering a manual select group on top of an auto-select group — so rules only need to point to the outermost group name, and adding or removing nodes later requires no rule changes. For how proxy groups pair with rules, see Custom Rules Explained.
Plate IV
A single subscription link keeps every node and rule in sync: the client pulls updates on a schedule, and any node changes on the server side sync down automatically.
Explication
A subscription link typically returns a Base64-encoded node list or a full YAML config. Paste the link into the client's Subscription or Profile page, save it, and update manually or on a recurring schedule; multiple subscriptions can coexist and be referenced by different proxy groups. Treat subscription URLs as credentials — never leak them or post them publicly. For step-by-step import and update instructions, see Step 2 of the Getting Started Guide.
Plate V
System proxy routes traffic that follows the OS proxy settings into the client; TUN mode uses a virtual network adapter to take over all device traffic, including apps that ignore system proxy settings.
Explication
System proxy only changes the OS-level HTTP/SOCKS proxy settings, so only apps that respect those settings get routed; TUN mode creates a virtual network adapter and intercepts traffic at the network layer, covering UDP, games, and command-line tools under your routing rules, though it requires driver authorization on first use. The two can run independently or together: system proxy is enough for everyday browsing, while TUN is worth enabling when you need full device coverage or are playing region-locked games.
Plate VI
The built-in DNS module handles domain resolution: nameserver and fallback split resolution between local and overseas domains, while fake-ip mode speeds up first connections and blocks DNS poisoning.
Explication
Clash's DNS config decides where and how a domain gets resolved: nameserver handles regular queries, fallback deals with poisoned results, and you can even route different domains to different upstreams. fake-ip mode returns a placeholder address first and resolves the real one only once a connection is established, speeding up first connections while preventing local DNS leaks. For field-by-field meaning and troubleshooting, see DNS Configuration Explained.
Plate VII
Mainstream protocols like Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are all supported — pick based on your line quality and use case.
Explication
Each protocol makes different trade-offs: the SS family is lightweight and general-purpose; VMess and Trojan lean on TLS for camouflage; VLESS trims the handshake; Hysteria2 and TUIC run on QUIC and hold up better on lossy connections. The mihomo core supports all of them — the client side just needs to import nodes correctly. For background, resource usage, and picking guidance on each protocol, see the comparison entries on the Protocol Reference page.
Vol. IIPlatform Catalog · PLATFORMS
Client Downloads for Every Platform
Each of the five platforms catalogs its own set of applicable clients: Clash Plus is the top pick for both desktop and mobile, while Linux also gets the mihomo core listed for servers and routers. Click any entry to jump to the matching section on the downloads page.
The full Getting Started guide boils down to three steps: install the client, import a subscription, and connect. Here's the short version; see the guide for the complete walkthrough.
Download and Install the Client
Go to the downloads page for your device: on Windows, run the downloaded installer and follow the wizard; on macOS, open the dmg and drag the client into Applications; on Android, install the apk or get it from an app store; on iOS, install Clash Plus from the App Store. The top pick for each platform carries a "Top Pick" badge — go with that if you're new.
Import a Subscription Link
Open the Subscription or Profile management page in the client, create a new subscription, paste the full subscription link provided by your service into the address field, save it, and run an update once manually; the node list and routing rules get written locally right away and can update automatically on a schedule afterward — no need to paste the link again.
Choose a Mode and Connect
On the client's home screen, pick a run mode: Rule mode automatically routes traffic based on your rules and works well for everyday use; Global mode sends all traffic through the proxy and is meant only for temporary troubleshooting. Then flip on the System Proxy switch and visit a site outside your region to confirm connectivity — your first connection is now set up.
Clash isn't a single, isolated app — it's a lineage made up of the original project, community forks, and a wide range of clients. Understanding that history clarifies exactly what you're downloading today.
Origins · The Original Clash
Clash was written in Go and first released publicly around 2018. It turned rule-based routing into a client's core design: a single YAML config describes nodes, proxy groups, and rules together, letting local and overseas traffic route automatically down separate paths. The original repository racked up tens of thousands of stars before it was archived; in late 2023, the original author archived the repo and mainline development stopped, but its configuration model lives on across the entire ecosystem.
Lineage · Meta and mihomo
After the original stopped receiving updates, the community fork Clash Meta picked up core maintenance, later renaming itself to mihomo. The new core stayed compatible with Clash's config syntax while adding new protocols like VLESS, Hysteria2, and TUIC, plus TUN enhancements, rule sets, and more — making it the shared core underneath today's mainstream clients. The lineage between the two and their config compatibility is covered in more depth on the Protocol Reference page.
Ecosystem · A Galaxy of Clients
Splitting the core from the interface is the basic layout of the Clash ecosystem: GUI clients like Clash Verge Rev, Clash Nyanpasu, FlClash, and Clash Plus all run on the mihomo core, each making its own trade-offs in interface language, subscription management, and platform coverage. The downloads page catalogs them platform by platform and marks which are still maintained versus archived.
Curation · What This Site Includes
Download entries on the downloads page track the upstream release list and get updated in sync; clients that are no longer maintained (such as Clash for Windows and ClashX Meta) are clearly labeled "No Longer Maintained" and kept for archival purposes only — they're not recommended for new installs. Entries stick to plain facts and usage, and clients of unclear origin are not included.
Vol. VFAQ Digest · FAQ
Frequently Asked Questions
The four most-searched questions from the full FAQ page, answered up front; the complete FAQ is organized into basics, setup, usage tips, and troubleshooting.
Which client should I use as a first-timer?
Clash Plus is the top pick on every platform: it has an English interface, and subscription import and rule-based routing work right out of the box; for other clients and system requirements, see the downloads page.
Where do I paste the subscription link?
Open the client's Subscription or Profile management page, create a new subscription and paste the link in, then run a manual update once to load your nodes; see the full Getting Started Guide for step-by-step details.
How do I make the client launch on startup?
Most desktop clients have a "Launch on Startup" toggle in Settings — just turn it on; for platform-specific details and silent-start options, see the FAQ page.
What is a DNS leak, and how do I check for one?
A DNS leak means domain lookups bypass the proxy tunnel, potentially exposing what you're accessing; it usually comes down to nameserver and fallback settings — see the FAQ page and the DNS configuration guide for troubleshooting steps.