Installer links sorted by platform, plus complete walkthroughs for subscription import, system proxy, and TUN mode. The client is always free, open-source, comes with English documentation, and covers five delivery platforms: Windows, macOS, Android, iOS, and Linux.
The download page is split into five bays by operating system, each listing multiple client options alongside system requirements and install notes. If you're unsure which client to pick, the first card in each platform is the current recommendation; clicking any bay below jumps straight to that platform's section on the download page.
Built for Windows 10/11 x64, with an installable GUI client that supports one-click system proxy toggling and service-mode TUN.
Go to Download → GATE / M-02Separate installers for Apple Silicon and Intel—check your chip type before downloading. Runs as a persistent menu bar control.
Go to Download → GATE / A-03Direct APK install, mainly for arm64 devices. Traffic is captured through the system VPN interface, and VPN permission is required on first connection.
Go to Download → GATE / I-04Install Clash Plus from the App Store; after the store process finishes, follow the tutorial to import your subscription and get started.
Go to Download → GATE / L-05Provides deb/rpm GUI clients and core binaries, compatible with major desktop distros; server setups can run the core directly.
Go to Download →Go to the download page, find your platform's bay, and install the recommended client. Windows and macOS just need the installer wizard; installing the APK on Android means allowing the source when prompted; iOS goes straight through the App Store. After the first launch, the client sits in the system tray or menu bar.
Copy the subscription link from your provider, then paste and download it on the client's Profiles page. Once imported, the node list and routing rules fall into place automatically; if the list is empty or a parse error shows up, first check whether the link is complete and unexpired, then work through the troubleshooting page's checklist.
Turn on the system proxy switch (or enable TUN mode if needed), then pick a node inside the proxy group on the proxy page—running a latency test first can help. Next, visit a target site to confirm the connection works; if the browser doesn't respond, check the proxy switch, port conflicts, and rule mode—most issues come from one of these three.
Project history. Clash started as an open-source proxy core built around rule-based routing, gaining wide adoption thanks to its clear YAML config syntax and proxy-group design. After the original core repository was archived, the community fork mihomo (formerly Clash.Meta) took over maintenance, keeping the config format compatible while adding more protocols and rule types—it's now the core adopted across mainstream Clash-family clients.
Open-source ecosystem. The core and the main GUI clients listed here (Clash Verge Rev, FlClash, Clash Nyanpasu, and others) are all publicly hosted on GitHub under licenses like GPL-3.0, with commit history, issue discussions, and release notes fully visible. This site never modifies or repackages any installer—every link points to each project's official release channel.
How the core and clients relate. GUI clients handle the interface—importing subscriptions, switching nodes, toggling the system proxy—while the core does the actual protocol handshakes, rule matching, and DNS handling. That's why the same config file works across different clients without rebuilding it, and why it's safe to try several clients when deciding which one to use.
Update process. Download links on this site point to each client's latest stable release, with the version list checked and refreshed regularly. Clients that are no longer maintained (such as Clash for Windows and ClashX Meta) are clearly marked as archived but kept downloadable for existing users who still need them. System requirements and install notes for each platform are listed bay by bay on the download page.
The mihomo core source is publicly hosted—clone it directly to inspect the build scripts and release history:
git clone https://github.com/MetaCubeX/mihomo.gitWhat's the relationship between Clash and mihomo?
mihomo is the community fork that continues the Clash core, with compatible config syntax and extended protocol support—every client listed here runs on it.
What if the node list is empty after importing a subscription?
Check the link's completeness and expiration first, then check the server response format and your local network—working through them in order usually finds the cause.
Why don't UWP apps on Windows use the proxy?
UWP apps are restricted by Windows' network isolation from loopback access by default; you need to lift the loopback restriction or switch to TUN mode instead.
What do proxy groups, nodes, and rules actually mean?
A node is an exit line, a proxy group is a set of nodes plus a selection strategy, and rules decide which traffic goes to which group—each layer references the one below it.
Import errors and empty node lists after updates usually trace back to one of four causes: expired links, server response format, User-Agent restrictions, or local network issues. This article walks through diagnosis and fixes in troubleshooting order.
A profile is the complete config unit a Clash client loads, containing subscriptions, nodes, and rules within it. This article covers where config files come from, where they're stored, how updates work, and how to switch between multiple profiles.
Certificate errors aren't always the proxy's fault: system clock drift, captive portal hijacking, the MITM decryption switch, and missing certificate chains can all trigger them. This article explains how proxies interact with TLS certificate validation and offers fixes for each scenario.