Open-source ecosystem · Multi-platform clients, continuously updated
One subscription works across all five platforms — completely free, open source, backed by step-by-step documentation and troubleshooting guides.
All Platforms · One-Stop Setup
From installer downloads to configuration docs, every step is organized by platform: download first, import your subscription, then adjust the mode as needed. Scroll down for a five-minute overview of the whole site.
Clash isn't a single app — it's an open-source ecosystem built around one core and several client interfaces. The five cards below walk through it in order: how subscriptions work, how traffic gets routed, what powers the core, how to pick a client, and where to find the docs.
Once you get a subscription link from your provider, paste it into a client on any platform to pull in all nodes and rules — proxy groups you fine-tuned on Windows carry over exactly to your phone. Configs live as YAML files, so you can export backups or move them between devices. Clients refresh subscriptions on a schedule automatically, so node changes don't need manual updates on every device, and switching devices doesn't mean starting over.
In Rule mode, every connection is matched against the rule table first: traffic that matches a direct rule goes straight over the local network, while traffic matching a proxy rule goes to the selected node — the two never interfere with each other. Rules can be written by domain, IP range, or geographic location, or you can just use the rule sets bundled with your subscription. Compared to blanket global proxying, rule-based routing saves node bandwidth and keeps local sites and LAN services from being routed the long way around.
Every client recommended on this site is built on the actively maintained Mihomo core, the continuation of the Clash Meta project. It supports mainstream protocols like VMess, VLESS, Trojan, Hysteria2, and Shadowsocks, plus a TUN mode that captures all system traffic for apps that ignore the system proxy. The core is open source under GPL-3.0 with a steady release schedule, and protocol compatibility issues are usually fixed quickly in follow-up releases.
Several graphical clients run on the same core: Clash Plus covers all five platforms and is currently the top recommendation; Clash Verge Rev and FlClash each have their own strengths for heavier desktop use; the once-popular Clash for Windows is no longer maintained, and migrating away sooner rather than later is advised. The download page lists each client's focus, system requirements, and installation notes by platform, with full migration steps covered in the tutorials.
The site's documentation is layered by stage of use: Quick Start covers only the core three-step import flow; the multi-platform guide walks through installation, subscription import, system proxy, and TUN configuration system by system; the glossary and FAQ handle terminology and edge cases. If you run into connection failures or slow speeds, the blog's layered troubleshooting method helps pin down the cause step by step — swap nodes to compare, test a direct-connection baseline, then check local settings, instead of guessing.
Each of the five platforms has its own list of installers and clients. Click a platform below and the download page jumps straight to its recommended list.
Going from a clean system to a working browser takes just three steps. Each one is explained in detail, screenshots included, on the tutorial page.
Pick a recommended client for your platform on the download page and follow the installer prompts. Desktop clients may ask for network permissions on first launch — just allow it.
Copy the subscription link from your provider and paste it into the client's subscription or config screen, then wait for the node and rule lists to load.
Stay in Rule mode, turn on the system proxy, choose a node with normal latency, then open a browser and visit a target site to confirm the connection works.
The original Clash project launched in 2018 and defined this category of tool with its rule-based routing engine and YAML config format. After the original repository was archived, the community continued development on the Clash Meta fork, which was later renamed Mihomo and remains active today. Every client recommended here is built on that continuously maintained core lineage, and the config format stays compatible with the original — old config files can generally be migrated as-is.
The Mihomo core and mainstream graphical clients are released under open-source licenses such as GPL-3.0, so anyone can read the source, reproduce the build, and submit issues or patches. Protocol implementation details and rule-matching logic are all in the public repositories — when something behaves unexpectedly, you can check the source and issue history directly instead of just guessing.
The core ships new releases on a steady cadence, with protocol compatibility fixes and rule-engine improvements landing along the way; each graphical client tracks core updates while maintaining its own interface and platform support. Geo databases like GeoIP and GeoSite can be updated independently inside the client, so rule data stays current without needing a full client upgrade. Download links on this site are refreshed in step with each project's releases.
If you prefer building it yourself or deploying on a server or router, clone the Mihomo core repository directly:
git clone https://github.com/MetaCubeX/mihomo.git
Most users don't need to build anything — just pick a graphical client from the download page.
Is Clash for Windows still usable now that it's discontinued? Older versions still run, but no longer get protocol or security updates. Migrating to Clash Plus or Clash Verge Rev is recommended, and configs import smoothly. See the FAQ for details.
Rule mode or Global mode — which should I use? Stick with Rule mode by default and let the rule table decide routing; only switch to Global temporarily when troubleshooting or if rules stop working. See the multi-platform guide for details.
Are a subscription link and a config file the same thing? A subscription link is a remote address pointing to a config file — the client periodically fetches the latest config from it. The content is the same; only the form differs. See the glossary for details.
Does the latency shown in the panel reflect actual speed? No. Latency measures the handshake time to a test URL, which is unrelated to real bandwidth — a low-latency node can still buffer when streaming video. See the FAQ for details.
In-depth articles on troubleshooting, advanced settings, and core concepts, updated regularly.