Open-source project archive · Clients tracked continuously
CODENAME: CLASH
A download archive of Clash clients for Windows, macOS, Android, iOS, and Linux. Supports rule-based routing and TUN mode, built on the open-source mihomo core, with subscription import guides and a troubleshooting manual.
INDEX / Platform Entries
CORE
mihomoFormerly Clash.Meta. The open-source core shared by graphical clients, handling protocol handshakes, rule matching, and traffic forwarding.
LICENSE
FEATURE
Rule-based routing / TUN mode / subscription management / multi-protocol support / group testing. Core capabilities detailed in the index below, DOC-01 through DOC-05.
Five core features filed under case numbers. Click an index entry on the left to expand its brief on the right.
Decides whether each connection goes direct or through a proxy, based on domain, GeoIP, IP range, and similar conditions. A typical setup: sites in mainland China connect directly for speed, while sites outside China route through a proxy node as needed. Rules are matched top to bottom and support types such as DOMAIN-SUFFIX, DOMAIN-KEYWORD, GEOIP, and RULE-SET, and can reference remote rule sets that update automatically, or append custom entries in the config file. Unlike manually toggling a proxy switch, rule routing is configured once and stays in effect, so no manual intervention is needed when visiting different sites — this is the core capability that sets Clash apart from simple proxy tools.
Uses a virtual network adapter to intercept all traffic at the system network layer, closing the gaps left by system proxy mode. Some command-line tools, game clients, and background services ignore system proxy settings; with TUN enabled, this traffic is also routed through Clash's rule engine. On desktop, enabling TUN for the first time requires driver or administrator permission; on mobile, the same effect is achieved through the VPN interface. TUN mode can be combined with rule routing — intercepted traffic still follows the rules, so enabling TUN does not mean all traffic goes through the proxy. See the tutorial and troubleshooting pages on this site for setup steps and conflict handling.
A subscription is a URL provided by a service provider; once fetched, the client automatically parses all nodes and settings, so there's no need to enter server addresses one by one. Every client supports importing via pasted link, scheduled auto-updates, and multiple subscriptions at once — when providers or nodes change in bulk, updating the subscription once syncs everything. Some clients also support subscription conversion and merging with local configs, letting you layer custom rules on top without altering the original subscription. Subscription links come from your chosen service provider; this site does not provide node services. See the tutorial page for import steps.
The mihomo core extends the protocol stack of the original Clash core, supporting not only common protocols like Shadowsocks, VMess, Trojan, SOCKS5, and HTTP, but also newer ones such as VLESS, Hysteria2, TUIC, and WireGuard. Different protocols vary in handshake overhead, resistance to interference, and transfer performance; when a subscription mixes nodes of multiple protocols, the client can manage and switch between them all within a single config, with no need for separate tools per protocol. See the site's terminology reference and troubleshooting page for what each protocol term means.
Nodes can be organized into policy groups for coordinated dispatch: a url-test group periodically pings the nodes in it and auto-selects the fastest one; a fallback group checks availability in order and switches to a backup node when the preferred one fails; a select group leaves the choice to you. A rule's target can point to a policy group instead of a single node, enabling setups like "streaming uses the auto-test group, work traffic uses a specific regional group." When node counts are high and quality varies, a well-designed group setup significantly cuts down on manual switching, and latency test results are visible right in the client UI.
Clients are available for all five platforms. Click a card to jump to the matching section on the download page, where it will scroll straight to that platform's installer list.
Covers Windows 10 / 11, with several graphical clients available, including our top pick, Clash Plus.
Go to Download ->Separate builds are provided for Intel and Apple Silicon chips — confirm your chip type before downloading.
Go to Download ->APKs are provided for arm64 and other architectures — most modern devices should use the arm64 build, and traffic is intercepted via the VPN interface.
Go to Download ->Install Clash Plus through the App Store — the store link and instructions are in the iOS section of the download page.
Go to Download ->A deb package and a graphical client are available; for servers and routers, the mihomo core can be used directly.
Go to Download ->Getting from install to working setup usually takes under ten minutes. This is a condensed version of the tutorial page's main flow — see the tutorial page for full steps and screenshots.
Pick the installer matching your current OS from the download page and install it as you would any standard software. On first run, Windows may show a security prompt — choose to allow it; macOS may require allowing the app in System Settings for confirmed sources; on mobile, grant VPN permission before traffic can be intercepted.
Copy the subscription URL from your service provider and paste it into the client's subscription or config page to import. Once successful, the node list fills in automatically — it's also worth enabling automatic subscription updates so you don't have to re-import manually whenever nodes change.
For everyday use, choose rule mode, turn on the system proxy switch, then pick a node with normal latency from the node group. Open a site that needs the proxy to confirm connectivity, then open a directly-accessible site to confirm routing works correctly — once both pass, setup is complete.
Every client and core listed on this site is an open-source project from a public repository. The following facts are provided for reference.
HISTORY / Project Timeline
The original Clash core was released to the open-source community in 2018, and became the de facto standard in this space thanks to rule-based routing and a clean YAML config format. After the original repository stopped receiving updates in 2023, the community fork Clash.Meta continued development and was renamed mihomo, now maintained by the MetaCubeX organization, keeping backward compatibility with the original config format while extending protocols and features.
RELATION / Core vs. Clients
mihomo is the command-line core, handling protocol implementation, rule matching, and traffic forwarding; graphical clients like Clash Plus, Clash Verge Rev, and FlClash wrap it with a UI, adding subscription management, node switching, and a system proxy toggle. The same config file works across different clients, so switching clients doesn't require rewriting your rules.
ECOSYSTEM / Client Landscape
Clients for each platform are maintained independently by different open-source teams, with major projects released under the GPL-3.0 license — code, build scripts, and release history are all verifiable in public repositories. Discontinued legacy clients (such as Clash for Windows and ClashX Meta) are marked as archived on the download page separately, for users who still need compatibility with older systems.
UPDATE / How Listings Are Tracked
Version information on this site's download page follows each project's official release channel; the page fetches the current version list on load and refreshes download links accordingly. If the list is unreachable, the most recently cached installer links are kept as a fallback. This site only archives client software and documentation — it does not provide any node or subscription service.
SOURCE / mihomo Core Repository
git clone https://github.com/MetaCubeX/mihomo.git
To review the core source code or build it yourself, clone the repository above. Graphical client repository links can be found on each project's official page.
The four questions new users ask most often, each with a one-line pointer. Full answers are collected on the FAQ page.
Your node service provider issues it from their user panel — copy it and paste it into the client; this site does not provide subscriptions. See FAQ for details.
First update the subscription to confirm the nodes haven't expired, then check your system clock and whether the system proxy is enabled, ruling out issues one by one. See Troubleshooting for details.
Use rule mode day to day for automatic direct/proxy routing; global mode is only for temporary use when troubleshooting or in special cases. See FAQ for details.
Enable fake-ip in the config's dns section, or correctly split responsibilities between nameserver and fallback, then verify with a leak-test site. See Troubleshooting for details.
Tutorials and config deep-dives are archived in reverse chronological order — the three most recent are listed below.
A roundup of the ten questions beginners ask most: where subscription links come from, rule mode vs. global mode, what to do when all nodes time out, whether to enable TUN, and more — each with a directly actionable answer and further reading links.
Read Full Article ->A line-by-line breakdown of the dns section in a Clash config: how nameserver and fallback divide responsibilities, the difference between fake-ip and redir-host modes, when DNS hijacking applies, plus ready-to-use config examples and leak-prevention notes.
Read Full Article ->Using the common case of direct connections for mainland China sites and proxy routing for sites outside China, this article covers the syntax, match order, and priority of rule types like DOMAIN-SUFFIX, GEOIP, and RULE-SET, with a complete, ready-to-use rule snippet.
Read Full Article ->