A single hub for Windows, macOS, Android, iOS, and Linux installers. An open-source proxy client built on rule-based routing and YAML configuration, supporting subscription import, TUN mode, and multi-protocol nodes, with matching setup guides and troubleshooting docs.
Six fundamental capabilities of a rule-based proxy client, each mapped directly to a real day-to-day use case. See the tutorial page for step-by-step instructions and the glossary for term definitions.
Traffic is matched line by line against domain keywords, domain suffixes, IP ranges, GeoIP data, and process names, then routed to a proxy, direct connection, or blocked. Rules are matched top to bottom and stop at the first hit, with MATCH catching anything unmatched at the end. Compared to blanket proxying, rule-based routing keeps local sites on a direct connection while sending target sites through a node as needed, saving bandwidth and cutting latency. Rule sets can be maintained remotely, so updating one config covers every device with almost no manual work.
Creates a virtual network adapter at the system level that captures all outbound traffic, including command-line tools and game clients, closing the classic gap of "only the browser goes through the proxy." The mihomo core has built-in TUN support, so there's no need to configure a proxy for each app individually; paired with fake-ip DNS mode, it also cuts down resolution wait time. Enabling it for the first time requires granting the client administrator or VPN permissions, and the tutorial page walks through the toggle location on each platform.
Paste a subscription link to import every node and group at once; the client pulls updates on a set schedule so node changes never require manual config edits. Multiple subscriptions can coexist and be switched by use case; when an update fails, the log shows the HTTP status code and where parsing broke, making it easy to tell a dead link from a local network issue. Sharing one subscription link across multiple devices is the simplest way to keep configs in sync.
Proxy groups organize nodes into switchable sets: select for manual choice, url-test for automatically picking the lowest-latency node, fallback for ordered failover, and load-balance for spreading traffic. Rules point to a proxy group rather than a specific node, so swapping nodes never requires touching the rules. With sensible grouping, video, downloads, and work traffic can each use their own group without competing for bandwidth, and the current routing is easy to read at a glance in the dashboard.
Built-in HTTP latency testing probes a given URL and shows each node's response time in milliseconds, flagging timed-out nodes in red. url-test groups switch automatically based on results, and both the test interval and tolerance are adjustable to avoid frequent flips from minor jitter. Test URLs and timeout thresholds can be customized in the config; combined with handshake records in the logs, this quickly distinguishes a dead node from a local network fault.
The core exposes a RESTful control API that web dashboards use to display live connections, throughput, and logs in real time, and to switch nodes, change proxy mode, or trigger latency tests. Start troubleshooting from the dashboard: the connection list confirms which rule a request matched and which node it used; logs are level-based, and setting the level to debug reveals full DNS resolution and protocol handshake detail.
Each of the five platforms has multiple client options; the download page groups them by platform with a recommended order and system requirements. Click a platform to jump straight to its section.
For Windows 10/11 desktops; Clash Plus is the top pick, with Verge Rev and other GUI options also available.
Go to DownloadUniversal installer for Intel and Apple Silicon, sits in the menu bar, supports system proxy and TUN mode.
Go to DownloadDirect APK install using VpnService for system-wide traffic capture, with per-app proxy and auto-updating subscriptions.
Go to DownloadClash Plus is available directly on the App Store, with the same subscription import flow as desktop.
Go to Downloaddeb packages and binary releases; desktops use a GUI client, while servers and routers can run the core directly.
Go to DownloadFrom installation to confirming the proxy works, the standard flow is just three steps. This is a condensed preview; full screenshots and platform differences are on the tutorial page.
Pick the installer for your platform on the download page and finish installing it, then open the client's subscription or config manager, paste the link your provider gave you, and confirm the import. Once it succeeds, the node list and proxy groups appear automatically with no manual config editing needed.
Leave the proxy mode on the default "Rule mode," which routes traffic automatically per the config. Open the proxy group screen and pick a low-latency node in the manual-selection group; if unsure, run a latency test once and sort by lowest milliseconds.
Turn on the "System Proxy" toggle (use TUN mode instead for command-line tools or system-wide traffic), then visit a target site to confirm it connects. If it doesn't, check the client logs first to tell node issues apart from local config issues; see the troubleshooting docs for the full process.
Clash is a community-driven family of open-source projects with publicly auditable code. The four sections below cover the project's history to help you decide which core and client to use.
Clash began as a community-maintained open-source rule-based proxy core, establishing this category of client with its YAML config format and "rules decide the route" design. The project didn't stop when the original repository was archived: the community kept evolving the protocol and config format, and the config syntax, rule-writing conventions, and proxy-group concepts carried over intact, so most old configs still run directly on newer cores.
The most actively maintained core branch today is mihomo (formerly Clash Meta). It extends the original with support for VLESS, Hysteria2, TUIC, and other protocols, plus a built-in TUN module and an enhanced rule set, and it's the core used by most clients recommended on this site. The core and the GUI client are two separate layers: the core handles proxy logic while the GUI handles config management and the interface, and understanding that split helps when tracking down a problem.
A cross-platform client ecosystem has grown around the core: projects like Clash Plus, Clash Verge Rev, and FlClash each cover desktop or mobile platforms with independent release cycles and maintainers. Clash for Windows and ClashX Meta, both no longer maintained, are marked as archived on the download page with suggested alternatives, so new users don't end up installing software that no longer gets updates.
This site tracks each client's official release channel, with version numbers shown dynamically on the download page; the tutorials, glossary, and technical reference docs are revised continuously as core features change. The core's source is available on GitHub, and anyone who wants to run the core directly on a server or router can grab every release from the repository.
Get the Core Source Code
git clone https://github.com/MetaCubeX/mihomo.git
One-line answers to four common questions; full answers and more questions are on the FAQ page.
Hands-on articles on reading logs, core differences, and troubleshooting, showing the three most recent posts by publish date.
Starting from log level configuration, this article walks through what frequent errors like DNS resolution failures, handshake timeouts, and rule misses actually mean, with a practical path for tracing each error type back to its source.
Explains exactly what the system proxy setting covers, then gives separate checklists for browsers not using the proxy and terminal commands ignoring it, covering the proxy toggle, environment variables, and when to switch to TUN mode.
Breaks down what mihomo (Clash Meta) adds on top of the classic core: support for VLESS, Hysteria2, and other protocols, built-in TUN, and an enhanced rule set, plus the compatibility points to watch when migrating an old config.