CL-03.1
Windows
Includes installers for Clash Plus, Clash Verge Rev, FlClash, and Clash Nyanpasu, compatible with Windows 10 and later.
Go to DownloadsCARD CATALOG · CLASH LIBRARY
Clash Library Client Downloads·Subscription Setup·Protocol Picks
A catalog-numbered Clash resource library covering client installers for Windows, macOS, Android, iOS, and Linux, plus subscription setup guides, custom rule syntax, and protocol selection notes — every entry free to browse.
CL-01Rule Sets
CL-02Subscriptions
CLASH LIBRARY · CL-03
Clash Client Directory
Cataloged 2026-08-01
CL-03Clients
CL-04Configuration
CL-05Guides
CARD CATALOG · CLASHLIBRARY.COM
Catalog range CL-01–CL-05|Platforms covered Windows / macOS / Android / iOS / Linux|Cataloged 2026-08-01
CL-03Client Checkout Desk
Each of the five platforms gets its own drawer — click a card to jump straight to its section on the download page.
The download page groups entries by operating system, with several curated Clash clients listed side by side per platform: Clash Plus is the top pick on every platform, alongside entries like Clash Verge Rev and FlClash. Discontinued clients are archived separately so longtime users can still find them without misleading newcomers.
CL-03.2
macOS
Intel and Apple Silicon installers are listed separately, with the archived ClashX Meta entry kept on file for reference.
Go to DownloadsCL-03.3
Android
Install directly via APK — four picks: Clash Plus, Clash Meta for Android, FlClash, and Surfboard.
Go to DownloadsCL-03.4
iOS
Clash Plus is available on the App Store; the card links straight to the store listing plus the official clashplus.io site.
Go to DownloadsCL-03.5
Linux
Comes as a deb package with a desktop client — Clash Verge Rev is the recommended pick, with FlClash as a backup option.
Go to Downloads
View All Clients →
Server and router users should head straight to the mihomo core section →
CL-01Feature Card Index
Each of the five core capabilities has its own drawer — click a tab to pull out its reference card.
Ref. CL-01 · Custom Rules
Rule-Based Routing: Every Connection Takes Its Own Path
Clash decides whether each connection goes through the proxy or connects directly based on rules. Rules are written line by line using types like DOMAIN, DOMAIN-SUFFIX, IP-CIDR, and GEOSITE, matched from top to bottom, stopping at the first hit. When the rules bundled with a subscription don't fit your needs, you can add custom entries to the config file — for example, forcing direct connections for work-internal domains or pinning a specific service to nodes in a particular region. The mihomo core also supports rule-providers, letting you split rule sets into separate files maintained remotely, so rule updates don't require touching the main config. Rule syntax and priority details are covered in the protocol handbook and guide page.
Ref. CL-02 · Subscription Management
Subscription Links: The Remote Carrier for Nodes and Rules
A subscription link is how a provider delivers nodes and rules — essentially a remotely updatable YAML config. Paste the URL into the client's config page to import it, and set an auto-update interval so node changes don't require manual reconfiguration. If a subscription's format isn't compatible with your client, a subscription converter can transform the link into the target format; when running multiple subscriptions side by side, name each profile by purpose and update/switch between them individually to avoid overwriting one another. The full import steps and common error fixes are covered in the CL-05 drawer on the guide page.
Ref. CL-03 · Proxy Groups
Proxy Groups: Traffic Routing Organized by Purpose
Proxy groups organize nodes by purpose and determine where traffic actually exits. A select group lets you pick nodes manually; a url-test group periodically tests latency and auto-picks the fastest node; a fallback group switches to backup nodes in order if the primary fails; a load-balance group spreads connections across multiple nodes. Rules point to a proxy group rather than a specific node, so switching nodes just means switching within the group — no rule changes needed. The group panel in the client interface is the visual layer for proxy groups, supporting per-group speed tests and manual overrides, making it the layer you'll interact with most in daily use.
Ref. CL-04 · System Proxy & TUN
Two Ways to Take Over Traffic — Each With Its Own Scope
System proxy mode has the client register an HTTP/SOCKS proxy address with the OS; apps that respect system settings, like browsers, route through it automatically — but command-line tools and some apps ignore this setting. TUN mode instead creates a virtual network adapter and intercepts all traffic at the network layer, regardless of whether an app cooperates, giving fuller coverage at the cost of extra permissions (admin rights on Windows, network extension approval on macOS). System proxy is enough for everyday browsing; switch on TUN when you need full system-wide coverage. The underlying differences and setup steps are covered in a dedicated technical note.
Ref. CL-05 · mihomo Core
mihomo: The Actively Maintained Core
The Clash ecosystem has two layers: the core, which handles protocol handshakes, rule matching, and traffic forwarding, and the GUI client, which is just the interface wrapped around it. The original Clash core stopped receiving updates, and the community fork Clash Meta carried development forward, later renamed mihomo, adding support for newer protocols like VLESS, Hysteria2, and TUIC along with the GEOSITE database — making it the most actively maintained line today. The clients cataloged here, including Clash Plus, Clash Verge Rev, and FlClash, all run on the mihomo core, so config files are interchangeable between them. See the protocol handbook for the full core lineage.
CL-05Quick Start Excerpt
The full walkthrough is on the guide page; here are the three main steps.
Step 01 · Install the Client
Download and Install the Client for Your Platform
Grab the installer for your platform from the download page and follow the on-screen setup prompts; on macOS, you'll need to approve the network extension the first time it launches.
Step 02 · Import Your Subscription
Paste the Subscription Link to Generate Your Config
Paste the subscription URL your provider gave you into the config page — the client will automatically pull the node list and routing rules, with auto-update available if you want it.
Step 03 · Pick a Node and Connect
Turn On the System Proxy and Verify the Connection
Pick a node with good latency in the proxy group panel, switch on the system proxy toggle, and visit a target site in your browser to confirm traffic is being routed as expected.
CL-06Catalog Sourcing Notes
Here's where the cataloged entries come from, how the core lineage works, and how updates are handled — logged item by item below.
Project History
Clash started out as an open-source, rule-based proxy core written in Go, known for its flexible config and fine-grained rules, and a GUI client ecosystem grew up around it covering five desktop and mobile platforms. When the original author stopped updating it, community-maintained forks became the de facto mainline — the ecosystem never actually stalled.
Core Lineage
The Clash Meta fork carried the original core's development forward and was later renamed mihomo, adding support for more protocols while keeping the config format backward-compatible. Every actively maintained client cataloged here runs on the mihomo core, so the same YAML config can move between clients without any format lock-in.
Open-Source Ecosystem
Source code for the core and the major GUI clients is publicly hosted under permissive open-source licenses, so anyone can review the implementation, file issues, or contribute. The software itself is permanently free — this site only curates download links and documentation, and never modifies or repackages any installer.
How Updates Work
Version numbers and links on the download page are parsed live from a release manifest by a script when the page loads, so entries follow upstream releases automatically without manual rewrites; if the manifest is unreachable, preset fallback links are used instead. Each entry is logged with a catalog date, and discontinued clients are moved into the archive section and marked accordingly.
CHECKOUT · mihomo Core Source
git clone https://github.com/MetaCubeX/mihomo.git
CL-07FAQ Quick Reference
One-line answers to four common questions — see the guide page and protocol handbook for full details.
- What's the relationship between Clash and mihomo?mihomo is the community core fork that carries original Clash development forward; every actively maintained client today runs on it. See the protocol handbook for details.
- No nodes showing up after importing a subscription link?Usually caused by an incompatible subscription format or an expired link — work through the import checklist on the guide page to pinpoint the issue.
- Which client should I pick?Clash Plus is the top pick on every platform; if you want advanced desktop features, go with Clash Verge Rev. See the selection guide for a side-by-side comparison.
- Command-line tools not going through the proxy?System proxy mode can't reach apps that ignore system settings — turn on TUN mode to intercept traffic at the network layer instead. Steps are on the guide page.
CL-08Latest Technical Notes
The three most recent cataloged notes — see the technical notes section for the full list.