Installers are pulled directly from each project's official GitHub Release page and distributed byte-for-byte identical to the source; covering Windows / macOS / Android / iOS / Linux, with setup guides and a protocol reference manual included.
This site never repackages, renames, or otherwise modifies any installer: files are pulled as-is from each project's GitHub Release page and distributed unchanged, byte-for-byte identical to the official release. Every download you click here resolves to the exact same file you'd get from GitHub directly. The mirror only solves the network-access problem of fetching files; it never adds any processing on top of them. If any link ever conflicts with the official page, the GitHub release is the authoritative source.
Applies to: all installers on the download page · Source: GitHub Release
The download page is organized into five platform sections — Windows, macOS, Android, iOS, and Linux — plus a dedicated mihomo core section for server and router users. Each platform lists multiple clients side by side, with recommended picks, supported architectures, and system requirements clearly marked. Desktop GUI users, mobile users, and command-line users can all find what they need on one page, without cross-referencing filenames and architecture suffixes across separate repo release pages.
Platforms: Windows / macOS / Android / iOS / Linux · Plus a dedicated mihomo core section
The mirror's listings follow each upstream repo's release cadence: once a new version appears on GitHub Release, the corresponding entry on the download page is updated, with version numbers and filenames shown in monospace on each card. Discontinued clients (such as Clash for Windows and ClashX Meta) are kept as clearly labeled archive entries, so users still running older setups can grab the last available version instead of hitting a dead link.
Archived: Clash for Windows · ClashX Meta
From importing a subscription to picking a proxy mode to verifying connectivity, the setup guide breaks first-time configuration into steps you can follow one by one: each step spells out where to click, what you should see, and what comes next, with clear continuity between steps. Platform-specific parts — Windows' TUN mode and service installation, macOS' network extension authorization and Keychain prompts — get their own dedicated sections, with links to common error fixes right where you need them, so you won't need to hunt down extra docs on your first setup.
Guide: start.html · Step-by-step, including platform-specific steps
The protocol reference page covers the background, design trade-offs, and best-fit use cases for common proxy protocols — Shadowsocks, VMess, Trojan, VLESS, Hysteria2, TUIC — comparing connection speed, resource usage, and mobile battery impact. It also explains the relationship between the original Clash, Clash.Meta, and the mihomo core, along with configuration compatibility differences. The goal is to help you pick the right protocol in your client, instead of getting stuck on a long list of unfamiliar terms in your subscription.
Guide: knowledge.html · Protocol and core reference
The FAQ page organizes common questions into four categories: basics, installation and setup, usage tips, and troubleshooting. The blog also includes full troubleshooting checklists covering frequent scenarios like "connected but no web access," "all nodes timing out," and "subscription parsing failed." Troubleshooting articles walk through elimination steps in a fixed order, with a way to verify each step and the exact fix to apply — the goal is pinpointing the failure point within ten minutes, not blindly reinstalling.
Guide: faq.html · blog/ technical notes
Clash started out as an open-source proxy core written in Go, gaining wide adoption in the community for its rule-based routing and policy group features. After the original repo was archived in 2023, the community fork Clash.Meta continued development and was renamed mihomo, adding broader protocol support and rule capabilities — it's now the core used by most mainstream GUI clients.
Clients such as Clash Verge Rev, FlClash, Clash Nyanpasu, and Clash Meta for Android are all open-source projects hosted on GitHub, where anyone can browse the source, file issues, contribute, or build from source. Each client has its own take on interface design and platform support — see our client comparison page for guidance.
GUI clients handle the interface, subscription management, and system proxy settings, while the actual traffic processing is handled by the built-in mihomo core. This means config files are largely interchangeable across clients — switching clients usually just means re-importing your subscription, not rewriting your config.
Listings on this site follow upstream GitHub Release updates without modifying or repackaging any files; archived projects keep their last available version with a clear status label. Whenever an entry differs from the official release page, the official GitHub release takes precedence.
clone the kernel repo
The mihomo core repository — the open-source core shared by today's mainstream Clash clients. Clone the repo directly if you want to build from source or track the changelog.