Open-source core · Clients updated continuously
One page for Windows, macOS, Android, iOS, and Linux installers, plus setup guides for subscription import, rule-based routing, and TUN mode — from install to a verified connection.
DOWNLOADS
Each of the five platforms has an actively maintained client list. Pick your device below and the download page jumps straight to that tab.
Installer or portable build, with system proxy and TUN mode support for 64-bit Windows 10 and later.
Go to downloads →Separate installers for Apple Silicon and Intel, taking over system traffic once Network Extension access is granted.
Go to downloads →Install the arm64 or armv7 APK directly. Global proxying runs on VpnService, no root required.
Go to downloads →Install Clash Plus from the App Store. Subscription import and rule-based routing match the desktop experience, with updates through the store.
Go to downloads →Choose a deb or rpm desktop package, or run the core binary directly on servers and routers with systemd for persistent operation.
Go to downloads →FEATURES
Pick a setting on the left to see its purpose, usage, and matching config snippet on the right. All snippets use real, ready-to-use syntax.
Rules are the core of Clash. The rules list in the config file is matched top to bottom: requests hitting DOMAIN-SUFFIX, DOMAIN-KEYWORD, GEOIP, and similar conditions are routed to a proxy or direct connection as specified; anything unmatched falls through to MATCH. Domains and IPs in mainland China go direct while everything else is proxied, with no manual toggling back and forth. Unlike traditional proxy tools that only offer a global or direct mode, rule-based routing decides each connection individually — direct traffic never takes a detour, and proxied traffic is never missed. Rules can be managed through a subscription or appended and overridden locally in the client.
Some programs — command-line tools, games, certain client apps — ignore system proxy settings, so regular HTTP/SOCKS ports have no effect on them. TUN mode creates a virtual network adapter that pulls all outbound traffic from the device into the Clash core, then applies the same rule set, closing the gap the system proxy can't reach at the network layer. Enabling it requires administrator rights (Windows) or Network Extension permission (macOS); combined with dns-hijack, it can also intercept DNS queries to prevent tampered results. For everyday use, start with the system proxy and switch on TUN only when a program refuses to go through it.
A subscription is a URL pointing to a remote config. The client fetches it on the interval set in proxy-providers, so added or removed nodes and address changes sync locally without maintaining server details by hand. Multiple subscriptions can coexist, each updating independently, then get organized together through proxy groups. If a fetch fails, the client falls back to the last cached copy without breaking existing connections. Importing works the same way across clients: copy the subscription link and paste it into the config or subscription page; URL-based subscriptions can also be run through a conversion service to generate a full Clash config with complete rules.
A proxy group bundles multiple nodes into a single unit that rules can reference. url-test periodically pings every member and auto-selects the lowest latency; fallback guarantees availability in list order, switching to the next node if the preferred one fails; load-balance spreads connections across nodes; select keeps a manual entry point. All four types can nest inside each other — for example, a manual group whose candidates are several auto-test groups, balancing convenience with control. The tolerance parameter prevents nodes with similar latency from flip-flopping.
QUICKSTART
From install to a verified working proxy, the whole process usually takes under ten minutes. Here's the condensed version of the quick start guide.
Pick the client for your platform on the download page and follow the installer. On first launch, grant network permissions when prompted on Windows and macOS; on Android, allow the VPN connection after installing the APK; on iOS, install straight from the App Store.
Copy the subscription link from your provider and paste it into the client's "Config" or "Subscription" page, or import a local config.yaml file directly. Once imported, the node list and rules load together.
Switch on "System Proxy," pick a node in a proxy group on the Proxies page, and visit a site outside China to confirm connectivity; if a specific program still won't connect, turn on TUN mode to capture all traffic. The Connections page shows which rule each request hits in real time.
OPEN SOURCE
Clash isn't closed software — it's an open-source ecosystem of a core, rules, and multiple clients. The code is public, and anyone can review or build it.
Clash first appeared as an open-source project around 2018 and quickly became the de facto standard in its space thanks to its YAML config and rule-based routing design. After the original core repository was archived, the community took over maintenance while keeping config syntax and rule formats compatible, so years of accumulated subscriptions and rule sets still work.
The actively maintained core today is mihomo (the Clash Meta core), kept by the MetaCubeX team and released under the GPL open-source license. It stays compatible with the original config while adding more proxy protocols, DNS strategies, and TUN stack implementations. Most mainstream desktop and mobile clients ship with this core built in.
Clients such as Clash Plus, Clash Verge Rev, FlClash, and Clash Nyanpasu are built independently by different teams while sharing the same core and config format. Switching clients doesn't require changing configs — subscriptions and rules carry over directly, and your choice only affects the interface and platform support, not routing behavior.
This site tracks the release channels of every client and core; download links point to the current release, and version numbers on the page refresh as new versions ship. Discontinued clients (such as Clash for Windows and ClashX Meta) are clearly labeled, along with actively maintained alternatives.
git clone https://github.com/MetaCubeX/mihomo.git
FAQ
One-line answers to four common questions — see the glossary and full docs for details and more entries.
Where is the config file stored?
Every client's settings page has an "Open Config Folder" option; if you're browsing manually, it's usually under the client's data folder in your user directory on Windows, or in ~/.config or the app support folder on macOS.
System proxy or TUN mode — which one?
The system proxy is fine for everyday browsing; command-line tools, games, and other programs that ignore it need TUN mode instead. Avoid relying on the same port settings for both at once.
See the TUN mode entry →Nodes missing after importing a subscription?
First check that the subscription link hasn't expired and returns Clash-format data; then check the client logs for fetch failures, and if needed, open the subscription URL directly in a browser to inspect the response.
Follow the full troubleshooting guide →How do I enable launch at startup?
Desktop clients have a "Launch at Startup" toggle in general settings — turning on "Silent Start" too is recommended; on Windows, whitelist the client if security software blocks it.
See the steps in the quick start guide →BLOG
Troubleshooting logs, platform guides, and advanced config write-ups, updated by topic on an ongoing basis.
All nodes timing out doesn't mean they're all dead. Work through five layers — subscription validity, local port conflicts, system proxy toggle, protocol/core compatibility, and DNS tampering — to pin down whether it's a config or connection issue.
Read more →Launching a Clash client on macOS for the first time triggers a string of prompts for Network Extension, Keychain access, and Accessibility permissions. Here's what each one does, how to grant it correctly, and how to recover if authorization fails.
Read more →What each automatic proxy group type solves: url-test picks the fastest node, fallback preserves availability, and load-balance spreads traffic. Breaks down every parameter and includes ready-to-use YAML examples.
Read more →