Find client download links for Windows, macOS, Android, iOS, and Linux, with guidance on subscription imports, routing rules, and protocol selection, plus configuration references for the mihomo core.
Clash is not a single switch. It is a processing chain built from rules, proxy groups, DNS, and system network entry points. The sections below explain what each part does and where its boundaries lie using real configuration concepts.
Rule mode checks domains, IPs, processes, or rule sets in the order defined by the configuration. Once a rule matches, the connection is handed to the specified proxy group. This determines how different traffic is handled, rather than sending every connection through the same exit. A common approach is to define the most specific domain rules first, handle IP geolocation rules next, and use MATCH for anything left unmatched. Compared with global mode, rule mode offers finer control and is better suited to long-term use.
Proxy groups sit between rules and individual proxies. Rules only need to point to a stable group name; users can select a member manually, or the group can choose automatically based on health checks. url-test generally selects the candidate with the best test result; fallback uses the first available candidate in order; load-balance distributes different connections across multiple candidates. These are not simply rankings by speed: they handle automatic selection, ordered failover, and connection distribution respectively. Choose the group type after deciding whether stability, failover order, or distribution is the primary goal.
mihomo
proxy-groups:
- name: Auto
type: url-test
proxies: [Node-A, Node-B]
- name: Backup
type: fallback
proxies: [Node-A, Node-B]System proxy mode sends requests from applications that follow the operating system's proxy settings to Clash. It is straightforward and works well for browsers and most desktop software. TUN mode uses a virtual network interface to capture a wider range of connections, including traffic from applications that ignore system proxy settings, some command-line tools, and scenarios requiring UDP. These modes determine how traffic enters the core; they do not change the rules themselves. For a first setup, verify that system proxy mode works before enabling TUN as needed, and pay attention to administrator permissions, routing, and firewall settings.
For domain rules to work reliably, the core must preserve domain information that can be used during connection handling. Fake-IP mode returns mapped addresses for DNS queries, then uses its internal mapping to recover the original domain for subsequent connections, improving the consistency of domain-rule matching. It is not the same thing as the real destination address. Check the listen address, upstream resolvers, enhanced mode, and filter lists together. If LAN devices, specific applications, or local domains have resolution issues, add the relevant domains to the filter range instead of disabling DNS entirely.
dns:
enable: true
enhanced-mode: fake-ip
fake-ip-range: 198.18.0.1/16
respect-rules: trueThe same subscription can work across different operating systems, but installation formats, permission models, and network entry points vary. Start with the download page for your current device, then compare graphical clients with core tools instead of using another platform's package on your system.
For users who need a desktop graphical interface, system proxy support, TUN mode, and startup management. The download page lists Clash Plus, Clash Verge Rev, FlClash, and Clash Nyanpasu, with archived clients identified separately.
Go to DownloadsFirst distinguish between Apple Silicon and Intel processor architectures. Graphical clients can manage menu bar status, system proxy settings, and configuration updates. When enabling a network extension or TUN for the first time, grant the required permissions when prompted by the system.
Go to DownloadsIdeal for phones and tablets. Clients typically use the system VPN interface to capture app traffic, import subscriptions, switch proxy groups, and view connection logs. Confirm the device architecture before installing; if unsure, choose a universal build on the download page.
Go to DownloadsClash Plus is available through the App Store, and product information is available at clashplus.io. iOS network extensions are managed by the system. After importing a configuration, select a proxy group in the client and confirm the VPN status.
Go to DownloadsDesktop users can choose a graphical client, while servers, routers, and automated environments typically use the mihomo core directly. On the download page, choose files based on the distribution, CPU architecture, and whether a desktop interface is required.
Go to DownloadsClient names may differ, but compatibility depends on distinguishing three layers: the graphical interface, the core, and the configuration format. The interface handles interaction, the core processes connections, and the configuration file describes proxies, policies, and rules.
Clash established a workflow centered on YAML configuration, proxy groups, and rule-based routing. Although the original project is no longer maintained, its configuration concepts did not disappear; community clients and subsequent cores continue to use many foundational fields. Structures such as proxies, proxy-groups, and rules found in older guides remain an entry point for understanding configurations. However, support for a field in an older client does not mean every newer core uses exactly the same default behavior, so always consult the current documentation when migrating.
mihomo is a widely used rule-based proxy core in the current Clash ecosystem and extends the capabilities of Clash Meta. Graphical clients such as Clash Verge Rev and FlClash can bring configuration editing, subscription updates, system proxy settings, and core startup into one interface, but the core usually handles the actual connections. When protocol support, DNS behavior, or configuration-field errors differ, first confirm which core the client uses, then determine whether the issue belongs to the interface layer or the core layer.
mihomo is released under the GPL-3.0 open-source license. Its source code, commit history, issue discussions, and release notes are available in the public repository. Open-source visibility is valuable not only because it provides source access, but also because it makes configuration changes, compatibility discussions, and bug fixes traceable. Most users do not need to compile the core themselves, but when choosing a client or investigating a specific protocol issue, public records are usually closer to the implementation than second-hand summaries.
Graphical clients, cores, and rule data each follow their own update cycle. Client updates usually involve the interface, system integration, and bundled core; core updates may change protocol support, DNS handling, or configuration fields; GeoIP, GeoSite, and rule sets are independently updateable data. If the client is updated but the rules are still old, or a subscription imports successfully but new fields are not recognized, check these three layers separately rather than treating all update states as one.
Rule mode evaluates each connection against the configuration to determine where it goes; global mode sends all connections to the current proxy group. For everyday use, start with rule mode and adjust rules for unmatched traffic or specific applications.
View Mode-Related QuestionsFirst confirm that the link is still accessible, that its response uses a format supported by the client, and that the subscription update shows no errors. If the configuration downloads but parsing fails, also check core compatibility and the subscription conversion process.
View Subscription Troubleshooting StepsSome clients allow both to be enabled, but their coverage differs. When troubleshooting connection issues, verify system proxy mode on its own first, then enable TUN. This makes it easier to identify whether the problem lies in application proxy handling or the virtual network interface path.
View the First-Connection WorkflowNo. Fake-IP addresses are used by the DNS module to maintain domain mappings. Subsequent connections use those mappings to recover the domain and apply rules. Continue to the concept reference for more on the resolution flow and filtering scope.
View the Fake-IP Terminology GuideThese articles cover proxy-group selection, subscription parsing, and node connection issues with checks you can perform in order. They focus on concrete decision points instead of mixing different failure types into one generic troubleshooting process.
Breaks down how three automatic proxy groups make decisions, compares latency-based selection, ordered failover, and connection distribution, and explains how common parameters affect switching results.
Read the Full Article →When subscription imports show errors, the proxy list is empty, or updates fail, check link validity, response format, client identification, core compatibility, and the local network layer by layer.
Read the Full Article →First separate client configuration, an individual proxy node, and local network issues. Then check system proxy settings, DNS, protocol parameters, firewall rules, and time settings to avoid aimless repeated changes.
Read the Full Article →