Windows
Clash Plus and Clash Verge Rev both ship installers for Windows 10 and later, supporting both system proxy and TUN mode traffic takeover.
Go to Download
Open-source project · clients updated across all platforms
Clash for Mac
Client downloads and setup guides across every platform. From installation and subscription import to rule-based routing and troubleshooting, all in one place, covering macOS, Windows, Android, iOS and Linux.
Always free
Open source
Detailed docs
5 platforms covered
DOWNLOAD
Get the Client for Your Platform
Each of the five platforms has a mature client to choose from, and the download page lists every installer and system requirement by operating system. Below is a one-line summary for each platform with a direct link that jumps straight to that section of the download page, so there's no need to hunt through a long list.
macOS
Separate installers are provided for Intel and Apple Silicon chips. Clash Plus is the top pick, sitting in the menu bar so you can switch nodes and modes without opening the main window.
Go to DownloadAndroid
APK installers are offered for arm64 and other architectures, using the system VpnService to take over traffic, with automatic subscription updates and rule-based routing matching the desktop clients.
Go to DownloadiOS
Clash Plus is available on the App Store and installs directly from there; future versions are distributed automatically, with subscriptions and rules configured the same way as other platforms.
Go to DownloadLinux
Clash Verge Rev is recommended, with deb and rpm installers; for servers and routers you can use the mihomo core binary directly, which has its own section on the download page.
Go to DownloadFEATURES
Core Capabilities, One at a Time
What matters about a Clash client isn't the interface — it's the mechanisms built into the core. Once you understand what each one solves, every line in a config file makes sense. The five features below are ordered by how often you'll use them, each linking to its own documentation.
Rule-Based Routing
Using domain names, IP ranges and geolocation databases, the core routes each connection to the right proxy group or direct exit. Rules are matched top to bottom and stop at the first hit: common sites go direct, cross-border services go through the proxy, ad domains get blocked outright — all defined in a single config file. Unlike flipping a proxy toggle by hand, rules written once keep working indefinitely, with no extra steps needed when visiting different sites day to day; the syntax and ordering principles for each rule type are broken down line by line in the docs and technical notes.
Read the DocsSubscription Sync
Get a subscription link from your provider, paste it into the client, and every node plus its preset routing rules imports at once. The client refetches on a set interval, so when the server side updates nodes, the local list syncs automatically — no need to maintain server addresses and ports by hand. For issues like subscriptions failing to update, empty node lists after import, or YAML parse errors, the site has a layered checklist covering network connectivity, link validity and format compatibility that you can work through step by step.
See Import StepsFake-IP Resolution
With Fake-IP enabled, DNS queries return a virtual address from a reserved range immediately, while connection setup and real resolution happen in parallel — noticeably cutting first-byte latency and reducing DNS leak risk. Cases that depend on real addresses, like LAN printers or certain gaming platforms, can be excluded item by item via the fake-ip-filter list without affecting acceleration on everything else. A dedicated technical note compares its resolution flow against the traditional Redir-Host mode at the mechanism level.
Read the Deep DiveSystem-Level Takeover
A system proxy only affects apps that respect proxy settings — command-line tools and some desktop software bypass it and connect directly. TUN mode creates a virtual network interface at the system level, taking over all outbound traffic, and combined with global mode ensures every process goes through the set exit. Enabling TUN on macOS and Windows involves permission grants and DNS hijacking settings respectively; getting the order wrong can look like a total network outage, so the docs walk through each platform step by step with a rollback path.
See Setup StepsConsistent Across Platforms
The same subscription and rules work on mature clients across macOS, Windows, Android, iOS and Linux: Clash Plus and Clash Verge Rev lead on desktop, while mobile has both app-store builds and APK installers. Every client is built around the same core, so nodes, proxy groups and rules mean exactly the same thing everywhere — switching devices takes almost no relearning. Which client best fits your platform and habits is covered point by point on the comparison page.
See the ComparisonOPEN SOURCE
The Open-Source Ecosystem & How It's Maintained
Every client and core listed on this site is an open-source project with a public repository — code is inspectable and versions are traceable. The four points below explain how this ecosystem runs and how the download links here stay in sync with upstream releases.
Project History
The Clash core was originally released as open source and, thanks to its rule-based routing design, gradually became the de facto standard among similar tools. After the original repository stopped receiving updates, the community carried forward its config format and core ideas — the ecosystem never really stopped, it kept evolving on new core forks, and most existing configs migrate over smoothly.
Core vs. Client
mihomo (formerly Clash Meta) is the actively maintained core fork, handling protocol implementation, DNS processing, rule matching and other low-level work; graphical clients like Clash Plus, Clash Verge Rev and FlClash wrap an interface and system integration on top of it. Picking a client really just means picking a shell — the routing power comes from the shared core underneath.
Community Maintenance
The core and major clients all accept issue reports and code contributions on public platforms, with public commit history and release notes for every change to protocols, rule types and config fields. When something behaves unexpectedly, checking the changelog for your version usually pinpoints the cause faster than blindly reinstalling.
Update Mechanism
The download links on this site track upstream version numbers, with the version info on the download page fetched at runtime by script rather than edited by hand. Rule databases like GeoIP and GeoSite are also released regularly upstream and can be updated from within the client — the exact steps are covered in a dedicated section of the docs.
git clone https://github.com/MetaCubeX/mihomo.git
Cloning the core repository gives you the full source for protocol implementation and rule matching; most users can just use the graphical clients on the download page without building anything themselves.
FAQ
Frequently Asked Questions
These are the questions that come up most often for first-time users. Each one gets a one-line answer here, with the full breakdown and steps on the FAQ page.
What's the relationship between Clash and mihomo?
mihomo is the community-maintained Clash core fork, backward-compatible with the config format; every graphical client wraps an interface around it, and routing power comes from the same core.
Read the Full AnswerWhat if the node list is empty after importing a subscription?
First confirm the link wasn't truncated, then check whether the subscription format is one the client supports, and finally verify your local network can reach the subscription URL — these three steps usually pinpoint it.
Read the Full AnswerGlobal mode or rule mode — which should I use?
Use rule mode for everyday browsing, which routes automatically by site; only switch briefly to global mode when you need to force all traffic through the proxy, such as when debugging a routing issue.
Read the Full AnswerDo I need to update the GeoIP database manually?
Most clients support a one-click check and update for GeoIP/GeoSite databases in settings; if geographic rule matching seems clearly off, updating the database usually fixes it right away.
Read the Full AnswerNOTES
Latest Technical Notes
In-depth articles on rule syntax, connection verification, subscription troubleshooting and more — the three most recent, newest first.
Clash Custom Rule Syntax and Match Priority, Fully Explained
A line-by-line breakdown of the syntax and match order for rule types like DOMAIN, DOMAIN-SUFFIX, IP-CIDR and GEOIP, explaining the top-to-bottom, first-hit-wins principle, plus ordering tips for writing custom rules that don't accidentally override each other.
Your First Clash Connection: Picking a Node, Testing Latency and Confirming the Proxy Works
For first-time Clash users: how to pick and switch nodes in the node list, how to run a latency test and read the results, and two ways — browser and command line — to confirm the proxy is actually working.
Clash Subscription Failures and Parse Errors: Common Causes and a Self-Check Checklist
Covers typical issues like subscriptions failing to update, empty node lists after import, and YAML parse errors, with a checklist across four layers — network connectivity, link validity, format compatibility and client settings — you can work through item by item.