Windows
Clash Plus is the top pick for 64-bit Windows 10/11, with Clash Verge Rev and FlClash as alternatives. Clash for Windows is discontinued and kept around only for reference.
Go to DownloadsSorted by symptom · Fixed step by step
Open-Source Proxy Client · Fixes by Symptom
Diagnose first, then prescribe. Three things are covered here: client downloads for every platform, subscription and configuration tutorials, and symptom-based troubleshooting — across Windows, macOS, Android, iOS, and Linux. Every fix lists prerequisites, steps, and how to verify it worked.
Five Cards at the Counter
Clients, subscriptions, rules, troubleshooting, core — these are the five things you'll deal with day to day using Clash. Pull each card to see what it solves, how to use it, and how it differs from what you'll read elsewhere.
Know your platform before you install. The download page is organized by Windows, macOS, Android, iOS, and Linux: Clash Plus is the top pick for both major desktop OSes, Android offers Clash Meta for Android and FlClash as alternatives, iOS uses Clash Plus from the App Store, and Linux desktop users go with Clash Verge Rev. Each entry lists system requirements, current version, and maintenance status — discontinued clients are archived separately so you don't grab an outdated one by mistake.
Going through a platform-specific entry avoids stale versions and repackaged installers you'd find scattered across the web. Server and router setups get their own section at the bottom of the download page for the bare mihomo core.
A subscription link is where your configuration comes from: paste it into the client's config page and confirm the import, and the core pulls down nodes and rules, then keeps updating on a set interval. The tutorial page breaks this into four steps — import the subscription, pick a mode, turn on the connection, and confirm it's working — with exactly what to click and what you should see at each step.
Updating a subscription overwrites local edits, so use the override or merge feature if you want to keep custom rules. For running multiple configs side by side and switching between them by use case, see the dedicated article on configuration file basics and management.
Rule mode is the main event here: it sorts every connection into direct, proxy, or block based on domain suffix, keywords, IP range, and region. Proxy groups are how you control that sorting — manual selection, auto-select by latency, and automatic failover each serve a different purpose. The glossary page defines all three group types in detail.
To see which rule a connection actually matched and which proxy group it landed in, check the client's log page for a per-connection hit record — that's the first place to look when routing behaves unexpectedly.
Don't jump straight to switching nodes when something breaks — figure out what's actually wrong first. The troubleshooting page is organized by symptom: no internet access, node timeouts, subscription failures, slow speeds, DNS issues, and system proxy not applying. Each one has its own flowchart: check the logs to narrow down the stage, then work through ports, system proxy, TUN, and DNS in order, with clear criteria for each branch.
The single most useful test is bypassing the system proxy and hitting the client's local port directly — whether that connects or not instantly splits the problem into "before the client" or "after the client."
mihomo is the community-maintained fork that picked up development after the original Clash core was archived. It's GPL-3.0 open source, stays compatible with the old config syntax, and adds capabilities like TUN mode and rule sets. Nearly every GUI client covered on this site runs on it now, with new releases still shipping monthly.
There are two running modes: system proxy only intercepts traffic from apps that honor proxy settings, while TUN mode creates a virtual network adapter that captures traffic system-wide. For exactly when to turn TUN on and what it costs you in overhead, see the quantified breakdown in the glossary and help center.
Pick Your Platform · All 5 Covered
Get the right package first, worry about config later. The five cards below give a one-line rundown per platform plus a link; the full client list, system requirements, version numbers, and the bare core download are all on the download page.
Clash Plus is the top pick for 64-bit Windows 10/11, with Clash Verge Rev and FlClash as alternatives. Clash for Windows is discontinued and kept around only for reference.
Go to DownloadsSeparate builds for Intel and Apple Silicon, with Clash Plus as the top pick — it sits in the menu bar and lets you toggle the system proxy on demand. ClashX Meta is discontinued and archived for reference only.
Go to DownloadsClash Plus is the top pick, with Clash Meta for Android or FlClash as alternatives. Per-app routing lets you send only specific apps through the proxy, saving both battery and data.
Go to DownloadsClash Plus on the App Store works on both iPhone and iPad, with full subscription import and rule mode support. Check clashplus.io for release notes.
Go to DownloadsDesktop Linux users should grab the deb or rpm package for Clash Verge Rev. Servers and routers skip the GUI entirely and run the bare mihomo core directly.
Go to DownloadsBehind the Scenes · Open-Source Ecosystem
This site only reports publicly verifiable facts: project history, ecosystem makeup, core lineage, and release channels. No inflated numbers, no made-up claims — just what's listed below.
The Clash core went open source under GPL-3.0 around 2019, gaining traction among proxy tools for its rule-based routing design. When the original repository was archived in late 2023, the community didn't disappear — mihomo picked up core development, GUI clients kept shipping updates independently, and the ecosystem carried on.
Built around the same core, the ecosystem includes independent clients like Clash Verge Rev, FlClash, Clash Nyanpasu, and Clash Meta for Android — each with its own interface and focus, but sharing a compatible config format, so switching clients doesn't mean relearning the syntax.
Most clients people call "Clash" today are actually running on the mihomo core: it's compatible with the original Clash's config and rule syntax while adding features like TUN mode, rule sets, and scripting. The glossary page has a dedicated entry mapping out the core and client lineage if you want to verify it.
Clients ship releases through GitHub Releases and app stores. The version numbers and download links on this site's download page are pulled live each time the page loads, always pointing to the current release channel — no stockpiling outdated installers, no re-hosting someone else's build.
The core and most clients have publicly auditable source code. If you want to verify implementation details, track changes, or contribute, just clone the repository:
git clone https://github.com/MetaCubeX/mihomo.git
Star counts and issue activity for each repository are public: mihomo and the major clients have repos with star counts in the hundreds of thousands, active issue trackers with maintainer and community responses, and a full release history you can trace.
FAQ · Four Quick Answers
These are the four questions that come up most often — quick answers here, with links to the full write-ups in each relevant section.
mihomo is the community-maintained fork that took over core development after the original Clash core was archived in late 2023. It keeps the config syntax compatible while adding features like TUN mode and rule sets. Most clients people call "Clash" today actually run on it. See Glossary for the full lineage.
Use Rule mode for everyday use: local sites connect directly while everything else routes through the proxy, balancing speed and coverage. Global mode sends all traffic through the proxy — turn it on temporarily for troubleshooting or when visiting obscure sites that no rule matches. More entries in the Help Center.
Your subscription link comes from whichever service you're using — it looks like an https URL that bundles nodes and rules. Once you have it, paste it into the client's config page to import. This site only covers how to use one; it doesn't provide or resell subscriptions. See the tutorial page for import steps.
For everyday browsing, the system proxy is enough. Turn on TUN mode when you need to capture traffic from apps that ignore the system proxy — some games and command-line tools fall into this category. It creates a virtual network adapter that intercepts all system traffic, which uses a bit more in resources if left running. See the Help Center for how to decide.
More Q&As in the Help Center; term definitions in the Glossary; full symptom-based troubleshooting in Troubleshooting.
Notes from the Desk · Usage Tips
Notes and write-ups from actual day-to-day use, newest first. The three most recent are below; the full archive is in the blog.
How do you keep configs consistent across your computer, phone, and tablet when they're all running Clash? A comparison of subscription-based distribution, WebDAV sync, and manual export/import, and when each one makes sense.
Read More →Staring at a long node list with no idea where to start? A breakdown of four factors — latency, traffic multiplier, exit region, and protocol type — and which nodes make sense for browsing, streaming, and gaming.
Read More →When a connection fails, check the logs first. Common Clash log entries sorted by error keyword, with what each one points to and where to look next.
Read More →