Windows
For Windows 10 / 11 desktops. Clash Plus leads the lineup, alongside Clash Verge Rev, FlClash, Clash Nyanpasu, and the archived Clash for Windows.
Go to Download →Open Source Project · All-Platform Clients Updated Continuously
Featuring Clash Plus, Clash Verge Rev, FlClash, and other official clients across five platforms, paired with step-by-step guides: from subscription import and rule-based routing to advanced mihomo config. Versions listed clearly, with direct links to official releases.
Each of the five platforms carries several client options, and the first entry on every platform card is always Clash Plus. Not sure which to pick? Check the detailed breakdown on the client comparison page first, then click any platform card to jump straight to its section in the download hub, where system requirements and version numbers are listed in full.
For Windows 10 / 11 desktops. Clash Plus leads the lineup, alongside Clash Verge Rev, FlClash, Clash Nyanpasu, and the archived Clash for Windows.
Go to Download →Separate installers for Apple Silicon and Intel. Clash Plus and Clash Verge Rev take the top spots, FlClash is an alternative, and ClashX Meta is archived for reference.
Go to Download →For Android 7.0 and up. Besides Clash Plus, choose from Clash Meta for Android, FlClash, or Surfboard, with ARM64 and universal packages available.
Go to Download →Clash Plus is available on the App Store, compatible with both iPhone and iPad; check clashplus.io for release notes and usage instructions.
Go to Download →On desktop distros, install Clash Verge Rev or FlClash (deb / rpm); on servers and routers, run the mihomo core directly, with multi-architecture binaries available.
Go to Download →Routing, subscriptions, kernel, rules, DNS, and control panels—the six capabilities users ask about most, explained one by one; the seal mark on each panel's left is that panel's keyword.
Traffic gets routed by domain, IP range, and GeoSite databases: sites in mainland China connect directly, sites outside China go through a proxy node, and ad or tracking domains get blocked outright. Rules are matched top-down, and the first match decides the outcome, with unmatched traffic falling to a FINAL catch-all. The whole routing table lives in a config file—import it once and it keeps working, no need to set a proxy for every app individually; when the logic needs to change, just edit the text and save for hot-reload.
A single subscription link keeps the entire node list up to date—clients pull updates on schedule, and any node changes or parameter tweaks sync automatically without manual re-adding. Multiple subscriptions can coexist, with local overrides layered on top: the provider's original config stays untouched, while custom ports, DNS, and rule patches are stored separately, so updating the subscription again won't wipe them out. Switching devices just means re-importing the same link to restore everything.
Every client here runs on the mihomo (formerly Clash Meta) core: fully compatible with original Clash config syntax, plus support for newer protocols like VLESS, Hysteria2, and TUIC, along with rule sets, domain sniffing, TUN mode, and more. The core keeps getting updated while old config files still work as-is, so upgrading a client doesn't mean relearning anything, and routing behavior stays consistent across desktop and mobile.
Built-in support for over a dozen match types—DOMAIN, DOMAIN-SUFFIX, IP-CIDR, GEOSITE, GEOIP, and more—each rule needing just three fields to define where traffic goes. Rule sets offload tens of thousands of domain entries to remotely maintained lists, referenced with a single line in the config; clients auto-update these lists on schedule, so routing always tracks the latest data without manual upkeep. The advanced config guide has examples for every type.
The built-in DNS server routes queries by domain: mainland China domains go through ISP DNS, others go through encrypted DNS, sidestepping both DNS poisoning and cross-contamination. Fake-IP mode returns a placeholder address first and resolves the real destination only when the connection is actually made, bypassing the system DNS cache for faster first connections, and keeping domain-based routing valid even under proxy protocols; a fallback list handles resolution failures.
The core ships with a RESTful external control API—hook it up to a panel like Yacd or metacubexd, and you can switch nodes, view active connections, test latency, and change modes right in the browser. The panel is a static web page that can be self-hosted or opened directly from an online version; the API listens on localhost by default and is protected by a secret key, so both a computer and a phone can control the same core.
From install to connected, the whole process boils down to three steps; screenshots, button locations, and troubleshooting details are laid out step-by-step on the setup guide page—here's just the outline.
Pick a client for your system from the download hub: Clash Plus is the top choice for Windows and macOS, Android also has Clash Meta for Android and FlClash, and iOS users can get Clash Plus from the App Store. Installation works like any other app—no need to flip the proxy switch right away.
Open the client's subscription or profile management page, add a new subscription, paste the link your provider gave you, and confirm—the node list will pull in right away. From then on, the client updates it on schedule; if the link ever stops working, the list just stays at its last successful state, and previously imported nodes remain unaffected.
Set the mode to Rule, pick a node with low latency from the list, then turn on the system proxy switch. Finally, visit an IP lookup page—if the exit address matches the node's location, you're connected. If nothing changes, work through the troubleshooting checklist in the setup guide; most issues get pinpointed within two passes.
Clash went open source under the GPL-3.0 license in 2018, and became one of the most widely used proxy clients on desktop and mobile thanks to its rule-based routing and multi-protocol support. After the original repo stopped receiving updates in 2023, the community carried development forward around the mihomo (Clash Meta) core: new protocols, rule sets, and TUN mode have kept evolving ever since, with the config system fully inherited—no gap in the ecosystem, and no need for existing users to rewrite their configs.
The kernel does the actual work; the client is just the shell around it. mihomo handles protocol parsing, rule-based routing, and DNS; graphical clients like Clash Plus, Clash Verge Rev, and FlClash build the interface, system integration, and subscription management on top of the kernel, each playing to its own strengths. Every kernel update benefits all the clients built on it—that's how the Clash ecosystem works together.
The download hub only lists official releases that are still actively maintained or significant enough to matter; clients that have stopped receiving updates are clearly marked "No Longer Maintained" and kept archived for reference, not recommended for new installs. Every download links directly to the official release page or app store, with no repackaging and nothing extra bundled in—what you install is exactly what the page describes, and version numbers can be checked against the official release pages.
Download links are maintained through a central version list, and pages automatically resolve to each client's latest release when loaded; version numbers are listed in full on each card, and if the list can't fetch a version, that slot is simply hidden rather than left as a placeholder. Clients also include their own update checks, so once installed, they keep pace with official releases without needing to revisit this site.
Start by installing the client for your system from the download hub, then follow the three-step setup guide: import a subscription, choose Rule mode, and turn on the system proxy. You're usually connected within ten minutes, and there's no need to touch any advanced settings right away.
Rule mode is the everyday choice: sites in mainland China connect directly, sites outside China go through a node. Global mode is only meant for short-term troubleshooting, and Direct mode effectively turns off routing altogether. You can switch between all three anytime without affecting your existing config.
This is usually caused by network conditions or an expired link: try switching networks and manually updating again—the node list will stay at its last successful state in the meantime. If it still fails, work through the troubleshooting checklist in the setup guide; most issues get resolved within two passes.
Yes. The config is plain YAML text, and the setup guide covers the basics like ports and modes; for deeper topics like proxy groups, rule sets, and DNS, the advanced config guide covers each in its own chapter—just back up your file before making changes.
What to do the first time you connect after importing a subscription: pick the right node, use latency tests to narrow down your options, then confirm the proxy is actually working with an IP lookup.
Read More →Subscription update failures are usually tied to network conditions, expired links, or client caching. Work through the causes in order, then enable scheduled auto-updates to keep the node list current.
Read More →A full walkthrough of installing the Clash client on a Linux desktop, plus running the proxy from the command line with the mihomo core, including startup-on-boot configuration.
Read More →