Choose a client for your device, then import a subscription, configure routing rules, and verify the connection.
Start by separating three questions: Does the app send requests to the client? Which rules does the client use to handle them? Where are domain names resolved? System proxy and TUN determine how traffic enters; Rule mode determines the routing policy; DNS settings control the resolution path. Checking these layers separately makes issues easier to isolate than changing several switches at once.
Rule mode checks domains, destination addresses, or rule sets in the order defined in the configuration, then sends each request to a specified proxy group or direct connection. It works well when you need different network resources to use different routes, without changing the entire device's route for one site. First, make sure the referenced proxy groups exist. Put specific domain rules before broader ones, then use MATCH to handle anything left over. Unlike tools with a single proxy endpoint, the Clash ecosystem makes the matching process visible. If traffic takes an unexpected route, check the matched rule in the connection log instead of simply switching nodes.
mode: rule
rules:
- DOMAIN-SUFFIX,example.com,Proxy
- GEOIP,CN,DIRECT
- MATCH,ProxyIn this example, Proxy is the name of a proxy group; define it in your configuration. See the rule syntax →
Rule mode routes traffic using rules; Global mode sends requests that have reached the core through the global policy; Direct mode connects straight to the destination. Rule mode is usually the best starting point. Switch to Global temporarily when checking whether a rule affects a particular request. Global mode does not capture traffic from every app: programs that ignore the system proxy still need separate proxy settings or TUN. The controls may appear in different places across graphical clients, but these three modes serve broadly similar purposes. When testing is done, restore the previous mode and review the connection log so temporary troubleshooting settings do not become permanent.
# Route traffic by rules for everyday use
mode: rule
# Optional modes: global, directSubscription links usually come from your service provider. The client downloads and parses the configuration, then enables it; installing a client does not automatically provide working nodes. After importing, make sure the configuration is selected and check that its proxy groups contain options. If an update fails, distinguish between an invalid link, a network error, and a parsing error by checking the message and logs. Unlike tools that store only a single server address, Clash configurations may also include rules and DNS settings. Override and merge behavior varies by client. Manual edits to the original subscription file may be lost on update, so keep long-term changes in a supported override layer.
# Basic fields in a local configuration
mixed-port: 7890
mode: rule
log-level: infoDNS translates domain names into addresses. Fake-IP assigns domains virtual addresses that the core can map back to their names for later connections. Enabling it requires the right traffic-capture path; it does not automatically route every system DNS query through the core. If a LAN service or a particular app is incompatible, configure filters as needed instead of repeatedly swapping DNS servers. Compared with tools that offer only a system proxy switch, mihomo clients that support these fields let you shape the resolution path in more detail. Also check browser Secure DNS, the system cache, and IPv6.
dns:
enable: true
enhanced-mode: fake-ip
fake-ip-range: 198.18.0.1/16TUN routes traffic to the proxy core through a virtual network interface. It can help with some command-line tools and apps that ignore system proxy settings. Desktop clients may require administrator privileges or a service; mobile clients typically use the system VPN interface. Check your client's documentation for details. TUN covers more traffic than the system proxy, but is also more susceptible to conflicts with routes, other VPNs, and security software. For your first connection, verify the configuration with the system proxy before enabling TUN. If your connection drops afterward, check routing and DNS capture. The example below illustrates fields only; it is not a complete configuration for any particular system.
tun:
enable: true
stack: mixed
auto-route: true
auto-detect-interface: trueThe download center lists clients by operating system, processor architecture, and installation instructions. Start by identifying your device's OS, then choose between a graphical client and a standalone core. Most desktop and mobile users should choose a client with a graphical interface; cores are more suited to servers, routers, and devices where you manage services yourself. Similar client names do not guarantee the same supported fields, permission requirements, or configuration override behavior.
Start with Clash Plus, then compare options such as Clash Verge Rev and FlClash by interface and workflow. Check your processor architecture and system requirements. If you're replacing Clash for Windows, review service mode, configuration migration, and startup settings rather than simply copying the old program folder.
Go to downloadsFirst check whether your Mac uses Apple silicon or an Intel processor, then choose the matching package. After installation, grant the permissions requested by macOS. Before switching clients, turn off the old client's proxy and background services to avoid a menu bar that looks normal while the system still uses the previous proxy.
Go to downloadsCompare clients such as Clash Plus, Clash Meta for Android, and FlClash. Match the package architecture to your device. On the first connection, approve the system VPN prompt. If the connection drops in the background, check battery optimization and background activity restrictions before repeatedly reinstalling the app.
Go to downloadsThe download center links to Clash Plus on the App Store and the official site, clashplus.io. After installing, import a supported configuration and allow the app to add a VPN configuration. Some system-specific fields in desktop configurations cannot be copied over as-is; follow the mobile client's import feedback.
Go to downloadsFor a desktop environment, consider Clash Verge Rev or FlClash and choose a package format for your distribution. For a service-only setup, use the mihomo core and configure the service and access permissions separately. Terminal programs may not use the desktop system proxy, so check their environment variables.
Go to downloadsBefore installing a new client, export your current configuration and note any local overrides. For the first test, run only one proxy client. Once the connection works, enable automatic updates or startup launch; this helps avoid port conflicts and routing issues.
Browse all clients →For your first setup, establish a connection you can verify before adding more rules or enabling TUN. A successful installation, an imported configuration, and a request actually routed through the proxy are three different outcomes. This section covers the sequence; the full guide explains each screen and permission in detail.
On the configuration or subscription page, add the link from your service provider or import a local YAML file. Once parsing is complete, select the configuration and check that its proxy groups show available options. If the import fails, keep the original error message. Do not expose subscription links in screenshots or logs.
Start in Rule mode, select an available route in the relevant proxy group, then enable the traffic entry point that suits your system. On desktop, try the system proxy first; on mobile, approve the VPN connection prompt. Do not enable traffic capture in multiple clients at once, and do not use Global mode as a substitute for checking the entry point.
Visit the destination you want to test, then open the Connections or Logs page and check the domain, matched rule, and selected policy. If the browser works but the terminal does not, check their proxy settings separately. When testing is complete, restore any temporary mode changes and confirm that frequently used apps and LAN resources remain accessible.
If a configuration update fails but existing connections still work, troubleshoot the update itself first instead of resetting every setting. When asking for help, include your operating system, client name, proxy mode, and when the error occurred. Redact subscription links, credentials, and the full configuration before sharing.
Read the full guide →Clash is a common name for an ecosystem of proxy tools; not every platform runs the same program. Understanding how the core and client work together helps you judge whether a guide applies and avoids treating one client's interface options as universal settings.
Early Clash projects established a workflow built around YAML configuration, proxy groups, and ordered rules. The community later developed different core forks and graphical clients, and mihomo continued and expanded some of those configuration capabilities. When you find an older article, first check which core and client it covers and whether that client is still maintained. Fields that look identical may differ in support or default behavior. If parsing fails, refer to the current core documentation and the actual error message rather than relying on old screenshots.
Open-source repositories let you browse code, read release notes, and follow issue discussions. Downloads, stars, and comments cannot replace compatibility testing on your own device, so this site does not use those numbers to recommend a client. To check whether a feature is supported, consult the upstream documentation for the field and then look for known limitations in the issue tracker. This site collects download links and Chinese-language setup references; it is not an official organization for any upstream project. Licensing, distribution, and features are determined by each client project's own documentation.
The core handles protocol connections, rule matching, DNS, and other network tasks. The graphical client manages configuration imports, mode switches, system integration, and log display. Two clients built on similar cores may still have different interfaces and override workflows. Likewise, a client starting successfully does not prove that the underlying configuration loaded correctly. When troubleshooting, note which configuration is active, then check the core logs. Before migrating, move subscription sources, local overrides, and system settings separately; do not assume one configuration file contains all your preferences.
App updates fix or improve the client or core itself; subscription updates fetch nodes, proxy groups, or rules. They are not the same thing. Before updating the app, read the release notes and back up local changes. After updating a subscription, check whether your customizations remain. Some clients merge subscription content with local overrides before passing it to the core, so the effective configuration may differ from the original subscription file. If something breaks after an update, compare what changed before deciding whether to roll back the configuration or adjust client settings. Avoid changing the app, subscription, and DNS all at once, or you will lose useful troubleshooting clues.
These articles focus on specific issues and are useful once installation is complete and you need to verify how something behaves. Save the log for a failed request, then troubleshoot each layer in order: proxy entry point, resolution path, rule matching, and outbound connection. Similar symptoms can have different causes, so don't reset the entire configuration based on a single error message.
A practical guide to reading latency tests, calculating traffic multipliers, matching locations to your needs, and comparing protocols.
Read the node selection guide →A breakdown of common log messages such as dial timeouts, DNS resolution failures, and unmatched rules, with steps for setting log levels and tracing an error to the relevant configuration section.
Read the log troubleshooting guide →A practical setup sequence for Windows, macOS, Android, and other platforms, covering permissions, port conflicts, configuration imports, startup launch, and more.
Read the first-install guide →Not sure which layer is causing the problem? Start by comparing the symptoms with the FAQ. When troubleshooting, change one setting at a time and retry the request. This makes the cause easier to identify, helps you undo changes, and preserves your existing setup.
Browse all articles →