A central hub for Clash clients on Windows, macOS, Android, iOS and Linux, built on the actively maintained mihomo core, with support for rule-based routing and subscription link import; the accompanying docs, config field references and troubleshooting guides are revised alongside each core release.
Six entries map to the six platform sections on the download page; clicking one jumps straight to the matching tab. Each platform's clients, version numbers and system requirements are listed in full there; recommended picks are all actively maintained projects built on the mihomo core, while discontinued legacy versions are marked separately so existing users can plan a migration.
Pick a station along the orbit to see the problem it solves, how to use it, and key parameters. Six stations cover the full chain from core to client, switching to a vertical timeline on narrow screens.
Global proxy mode forces all traffic through the tunnel indiscriminately, while rule-based routing evaluates each rule in the config file one by one: requests matching local domains and IP ranges go direct, requests matching listed services go through the proxy, and everything else falls back to MATCH. Rules support domain suffixes, keywords, IP-CIDR and GEOSITE databases among other match types, evaluated top to bottom with first match winning — this saves proxy bandwidth and keeps local services from being routed the long way around and slowed down.
MODE rule · MATCH DOMAIN-SUFFIX / IP-CIDR / GEOSITE · FINAL MATCH
After the original Clash core repository was archived in late 2023, the community fork mihomo (formerly known as Clash.Meta) picked up maintenance and became the default core for most mainstream GUI clients today. It stays compatible with legacy config syntax while adding support for newer protocols like VLESS, Hysteria2 and TUIC, and keeps pace with updates to the GEO database and DNS module. Every actively maintained client listed on this site is built on this core.
KERNEL mihomo · PROTO ss · vmess · trojan · vless · hysteria2 · tuic
Paste a subscription link issued by a provider or self-hosted panel, and the client pulls in every node and rule in one go — no need to enter server details one by one. Multiple subscriptions can coexist and auto-refresh at a fixed interval; if a subscription temporarily fails, the last cached copy is kept so you don't lose connectivity outright. If the format isn't Clash YAML, run it through a subscription converter first — full steps are in the setup guide.
FORMAT yaml · INTERVAL 86400s · SOURCE subscription-url
System proxy mode only affects apps that honor proxy settings — some games, command-line tools and UWP store apps bypass it entirely. TUN mode creates a virtual network interface to intercept all outbound traffic at the network layer, paired with fake-ip DNS resolution, so even apps that ignore the system proxy still follow the routing rules. Desktop platforms require admin privileges or core authorization to enable it; mobile platforms achieve the same effect through the system's VPN interface.
TUN enabled · STACK system / gvisor / mixed · DNS fake-ip
Policy groups bundle multiple nodes into a switchable set: the select type lets you pick manually, url-test periodically probes latency across the group and auto-switches to the fastest node, and fallback promotes the next node in order when the current pick fails. Different services can be bound to different groups — streaming pinned to a specific region, everyday browsing handled by an auto-test group — keeping connection quality stable during node fluctuations without manual intervention.
GROUP url-test / fallback / select · TEST generate_204 · INTERVAL 300s
The same config syntax covers Windows, macOS, Android, iOS and Linux: desktop has Clash Verge Rev and FlClash, mobile has Clash Plus and Clash Meta for Android, and servers or routers can run the mihomo core binary directly. Switching devices just means exporting your subscription or config file — routing rules and policy group behavior stay consistent across platforms, so there's no new interface logic to learn.
TARGET windows · macos · android · ios · linux · router
The original Clash core repository was archived and removed by its author in November 2023, but the project itself didn't disappear: the core was picked up by a community fork, and GUI clients branched off into several active forks. Understanding this history is the starting point for judging "which version is still worth installing" — see our article What Are Clash, mihomo and Verge Rev? for the full breakdown.
mihomo is the current de facto standard core, handling protocol implementation, rule matching and DNS resolution; GUI clients like Clash Verge Rev, FlClash and Clash Nyanpasu are just interfaces wrapped around that core. Interface differences don't affect config compatibility — the same YAML file can be moved directly between clients.
Both the core and mainstream clients are developed openly on GitHub: commit history, issue discussions and release artifacts are all publicly visible, and anyone can review the source or build it themselves. This is one of our selection criteria for recommended clients — closed-source repacks or clients of unclear origin are never listed here.
Links on the download page resolve each project's latest release list at page load, so version numbers stay in sync with upstream releases; the setup guide and config field reference are revised alongside major core updates, with outdated screenshots and dead steps removed periodically. If you spot a broken link or stale content, cross-check it against the version number listed on the download page.
If you prefer to build it yourself or need to deploy the core on a server, clone the mihomo repository and follow the build instructions in the repo.
git clone https://github.com/MetaCubeX/mihomo.git
Most desktop and mobile users don't need to compile anything — head to the download page for a GUI client instead.
The app itself still runs, but the core and rule data no longer get updates and new protocols won't work — migrating to Clash Verge Rev is recommended. See the FAQ page for the reasoning and migration path.
Subscriptions are issued by providers or self-hosted panels; this site only provides clients and documentation, no nodes of any kind. See the setup guide for import steps once you have a link.
They're fine for quickly verifying that your client config works, but speed, stability and privacy are all unreliable — not recommended for everyday traffic. The FAQ page has concrete criteria for judging this.
Clash Plus is on the App Store — search for it there or go through clashplus.io — and future versions update automatically through the store, no manual reinstalling required.
Articles cover troubleshooting, ecosystem choices and advanced configuration, sorted newest first — here are the three latest.
A browser flagging an invalid certificate isn't always the site's fault: system clock drift, a node performing a man-in-the-middle intercept, or a leftover packet-capture root certificate can all trigger it. This article walks through each error type and when to stop using the current node immediately.
Read more →From DOMAIN-SUFFIX and IP-CIDR to GEOSITE, this article walks through the syntax and use cases for each match type, with a focus on the top-to-bottom priority logic and whether custom rules belong before or after subscription rules.
Read more →After the original Clash was archived, the core and GUI clients branched into several forks. This article maps out how the mihomo core relates to GUI projects like Verge Rev, FlClash and Nyanpasu, so you can pick the right client for your platform.
Read more →