This page collects installers and setup documentation for Clash clients across every platform: clients are always free, the core and interface are open source, and the accompanying documentation covers the full path from subscription import to rule-based routing and TUN mode. Pick the right client for your platform and you can complete your first connection in under ten minutes.
Five capabilities that shape everyday usage. Click an item on the left to see its full explanation and matching config snippet — the panel auto-rotates on a timer and stops once you click manually.
Rule-based routing is what sets Clash apart from traditional proxy tools: the core matches every connection against the rules list from top to bottom, and once a connection hits a DOMAIN-SUFFIX, GEOIP, IP-CIDR, or similar condition, it's handed off to the specified proxy group; anything that doesn't match falls through to the MATCH catch-all rule. Paired with proxy-groups, you can send mainland China sites direct, route overseas sites through the proxy, and reject ad domains outright — all without manual switching. Rule sets support remote subscriptions and local overrides, so a configuration written once keeps working long-term.
rules:
- DOMAIN-SUFFIX,github.com,PROXY
- GEOIP,CN,DIRECT
- MATCH,PROXYmixed-port accepts both HTTP and SOCKS5 proxy traffic on the same port, so system proxy settings, browser extensions, and command-line tools only need to remember one port number. Turning on allow-lan makes the core listen on the LAN address as well — phones, tablets, and TVs on the same Wi-Fi can share the same exit by pointing their proxy server at this computer's local IP, without installing a client on every device. Before enabling it, allow inbound connections to that port in your system firewall, or other devices will time out trying to connect.
mixed-port: 7890
allow-lan: true
bind-address: "*"Most mainstream clients now bundle the mihomo core (the continuation of Clash.Meta), which stays compatible with the original Clash configuration syntax while adding broader protocol support: Shadowsocks, VMess, VLESS, Trojan, Hysteria2, TUIC, and more can all be mixed into a single configuration, so subscriptions don't need to be split by protocol. The core ships as a single binary, and desktop, mobile, and router deployments all share the same rule syntax — switching devices doesn't mean relearning configuration, and old configs can usually be migrated as-is.
proxies:
- name: "HK-01"
type: vless
server: example.com
port: 443A subscription packages the node list your provider issues into a single URL, and the client fetches it on a schedule to keep the node list current. Clients like Clash Verge Rev offer three related switches — update interval, auto-update on launch, and update through proxy — and if a fetch temporarily fails, the last working configuration is kept so your current connection isn't affected. Advanced users can merge several subscriptions into one configuration with proxy-providers, then inject their own routing rules uniformly through override files or global extension scripts.
proxy-providers:
main:
type: http
url: "https://example.com/sub"
interval: 86400System proxy settings only affect applications that respect them — command-line tools, game clients, and some desktop software bypass them entirely. TUN mode creates a virtual network adapter on the system, taking over all outbound traffic at the network layer and handing it to the core for rule-based processing, so even programs that ignore proxy settings get routed correctly. Enabling it requires granting the client administrator privileges or a system extension permission, and it's best to leave the DNS-hijacking-related settings at their defaults to avoid domain resolution issues.
tun:
enable: true
stack: system
auto-route: trueWhich clients are available for each of the five platforms and which version to install — the download page groups the full list, version numbers, and system requirements by platform. Jump straight to the section you need below.
Clash Verge Rev, Clash Plus, FlClash, and others all offer 64-bit installers supporting Windows 10 and later, with both system proxy and TUN mode available.
Go to DownloadsInstallers are provided separately for Intel and Apple Silicon — check "About This Mac" before downloading to confirm your chip type.
Go to DownloadsAPKs are split by ARM64 and ARMv7 architecture — most phones from the last few years should use the ARM64 build. Per-app proxy scoping is supported.
Go to DownloadsClash Plus is distributed normally through the App Store — just open the store page to install, and subscription import works the same way as on desktop.
Go to Downloadsdeb and rpm desktop installers are available; server and router users can grab the mihomo binary from the core section of the download page.
Go to DownloadsFrom the core to the graphical clients, every part of the Clash ecosystem has a public code repository and release history you can check — one reason it has earned long-term trust in the technical community.
Clash began as an open-source proxy core project on GitHub. After the original repository was archived, the community fork Clash.Meta continued development and was renamed mihomo in 2023, now maintained by the MetaCubeX organization. Nearly every mainstream client today bundles a core from this lineage, the configuration syntax has carried through consistently, and most instructions from older tutorials still work on the newer core.
From the mihomo core to graphical clients like Clash Verge Rev, FlClash, and ClashX Meta, all source code is publicly hosted on GitHub under open-source licenses such as GPL and MIT. Anyone can review the implementation, file issue reports, or build from source directly — release binaries map one-to-one to the code repositories, and the update cadence is fully transparent.
A graphical client is essentially a shell around the core: routing decisions, protocol handshakes, and DNS resolution are all handled by the core, while the client manages subscriptions, toggles, and the interface. Once you understand this division, switching clients just means switching interfaces — the same YAML configuration migrates directly between clients, so the learning curve only has to be paid once.
The download buttons on this site query a version manifest when the page loads and resolve the current latest installer for each client dynamically, rather than hard-coding version numbers into the page. Clients that are no longer maintained (such as Clash for Windows) are marked separately with their status and an archived installer, so users still relying on the old toolchain can transition smoothly.
git clone https://github.com/MetaCubeX/mihomo.git
Clone the core's source directly to browse or build it locally — build instructions are in the repository's README.
The four questions new users ask most, each answered directly up front — the full categorized Q&A and troubleshooting flow live on the FAQ page.
mihomo is the current name for the Clash.Meta core — think of it as the community continuation of the Clash core. It's what mainstream clients bundle today, and its configuration syntax remains backward compatible.
Your subscription link comes from the proxy service provider you use, available in their user dashboard — just copy the URL and import it into the client. This site only provides client software and documentation, not any node or proxy service.
Use Rule mode for everyday use — rules automatically decide direct vs. proxy. Global mode sends all traffic through the proxy and is only meant for temporary troubleshooting or special cases.
First confirm the system proxy toggle is on, the subscription imported successfully, and a working node is selected; then check whether another program is already using the proxy port. See the FAQ page for the full troubleshooting flow.
Practical notes on subscription management, rule-based routing, and troubleshooting — the three most recent posts, newest first.
Walks through the common triggers behind subscription update errors and explains how to correctly use the update interval, auto-update on launch, and update-through-proxy toggles in the client.
Uses the most common region-based routing scenario to explain how proxy-groups and rules work together, with real examples of DOMAIN-SUFFIX, GEOIP, and other rule types.
Collects the ten questions new users ask most often — core relationships, subscription sources, client choice, mode differences, icon color meanings, and more — with a direct answer to each.