Windows
The main desktop lineup: Clash Plus is the top pick, with Clash Verge Rev, FlClash, and others listed alongside it. Works out of the box on Windows 10 64-bit and above.
Go to DownloadsAll Clash clients in one place: installers for Windows, macOS, Linux, Android, iOS and the mihomo core sit side by side, free and open-source, with full documentation included. Available whenever you need it.
Pick the column that matches your device: each one leads with our top recommendation, plus alternatives and archived builds on the same shelf. Click "Go to Downloads" to jump straight to that platform's section, where version numbers, requirements, and download links are all laid out on the card.
The main desktop lineup: Clash Plus is the top pick, with Clash Verge Rev, FlClash, and others listed alongside it. Works out of the box on Windows 10 64-bit and above.
Go to DownloadsSeparate builds for Intel and Apple Silicon. Clash Plus and Clash Verge Rev are featured, with menu-bar-style clients available as alternatives.
Go to DownloadsBoth .deb and .rpm packages are available. Server and router users can grab the mihomo core command-line build directly, with multiple architectures supported.
Go to DownloadsClash Plus and Clash Meta for Android are featured, with arm64 and arm builds listed side by side. Surfboard is also available as an alternative.
Go to DownloadsClash Plus is live on the App Store — install directly from the store page, and check clashplus.io for release notes and usage instructions.
Go to DownloadsThe mihomo core command-line build is also available in the core section of the download page, aimed at server and router users. Desktop and mobile users should stick with the GUI clients above.
A quick preview of the tutorial page's main flow: import a subscription, pick a mode, verify the connection. Full details for each step — exactly where to click, what to look for, and what's next — are covered on the tutorial page. Here, just remember the order and what counts as done for each step.
Open the client's config page, paste your subscription link into the input field, and confirm the download. A new entry showing up in the config list means it worked. Subscription links come from your service provider — usually starting with http and including a token parameter — and can be copied from your account dashboard. After importing, remember to select the config to activate it.
At the top of the Proxies page, you'll find three modes: Rule, Global, and Direct. For everyday use, pick Rule mode, which routes traffic through the proxy or directly based on your rules. Global mode sends all traffic through the currently selected node — handy for quick troubleshooting. Direct mode bypasses the proxy entirely, effectively turning off routing.
Turn on the system proxy toggle and visit a site that was previously blocked. If it loads, you're done. If it still doesn't load, don't rush to swap nodes or subscriptions — check the "System Proxy Not Working" section on the troubleshooting page first. Most issues come from browser proxy extensions or terminal environment variables, not the nodes themselves.
Every client and core listed here comes from a publicly available open-source repository: the code is auditable, changes are tracked, and versions can be verified. The four sections below walk through that lineage, and the core's source repo is one clone command away on the right.
The original Clash project went public on GitHub around 2019, and its rule-based routing and broad protocol support made it a go-to proxy client core on desktop and mobile. After the original project stopped receiving updates, the community continued building on its public codebase, giving rise to the mihomo (Clash Meta) core and a range of GUI clients. Every client listed here traces back through this same open-source lineage to a specific repository.
Source code for the core and mainstream clients is hosted in public repositories, open for anyone to review, file issues, or submit patches. Protocol implementations, routing rule syntax, and config file fields are all documented right in the repo, and every change leaves a commit record you can diff between versions — no need to take anyone's word for it. For a networking tool like this, having the implementation out in the open is the most basic form of trust.
mihomo is the renamed version of the Clash Meta core, and it handles the actual traffic interception and protocol processing. GUI clients like Clash Verge Rev and FlClash are interface layers built on top of the core, handling config editing, node display, and toggle interactions. Choosing a client really just means choosing an interface you like — the underlying protocol capabilities depend on the core version. The "Kernel & Architecture" section of the glossary breaks this relationship down in more detail.
Download links on this page point to each client's official release channel. Version numbers are pulled from the release manifest when the page loads and shown in the card details, so what you get is always the current release. Most clients include a built-in update checker — open the settings page to see if a new version is available and follow the prompt to upgrade, no need to come back here. Core versions are refreshed in the core section of the download page as new releases come out.
Only publicly released clients and core versions make the list, organized by platform and tagged with maintenance status. Projects that are no longer maintained stay listed but are marked as archived for historical reference — not recommended for new users. System requirements and architecture info on each card come straight from the project's own release notes, so a quick glance is enough to confirm it fits your device.
The four questions visitors ask most often, each with a one-line pointer and a link to dig deeper. More answers live across the glossary, tutorial page, and troubleshooting page, organized by topic.
mihomo is the renamed version of the Clash Meta core, and most GUI clients available today are built on top of it, handling the actual traffic interception and protocol processing. The differences between the original Clash, mihomo, and the various GUI clients are explained in detail under "Kernel & Architecture" in the glossary.
Clash Plus is the top pick for all five platforms, so it's a safe default for whatever device you're using. Want to compare more options? The download page lists every available client by platform, along with maintenance status, system requirements, and supported architecture, plus alternatives and archived versions — everything you need on one page before you decide.
Subscription links are issued by your service provider, usually available with one click from your account dashboard — this site doesn't provide or resell subscriptions. Once you have a link, follow step one on the tutorial page to import it into your client. A new entry in the config list means it worked, and you can set an auto-update interval from there.
Check two separate paths: browsers first, for extension conflicts and proxy add-ons, then the terminal, for environment variables and config files. The troubleshooting page has a dedicated section walking through each step to help pin down the cause — in most cases, it has nothing to do with node quality.
One latest post each from Advanced, Subscription, and Troubleshooting — titles tell you exactly what's inside, so just click and read. The full archive is on the blog page, sorted by date and updated as issues and versions evolve.
A breakdown of how TUN mode takes over all system traffic: how the virtual network adapter works, how it differs from a system proxy, setup steps for each platform, and common pitfalls.
SubscriptionBefore you swap subscriptions over a failed update, work through the link, network, and client settings step by step — then set up a proper auto-update interval.
TroubleshootingSystem proxy toggle is on but nothing changes? Check browser and terminal settings separately to track down exactly why the proxy isn't taking effect.