From importing subscriptions to routing rules, find configuration guides for Clash Verge Rev and mihomo, organized by task.
Import a working configuration first, then decide how to route traffic. Select an item on the left to view its settings and YAML structure.
RemoteThese interface labels are illustrative; wording varies by client.
mode: rule
rules:
- DOMAIN-SUFFIX,example.com,DIRECT
- IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
- MATCH,PROXYPROXY must refer to a node or proxy group defined in the configuration.
proxy-groups:
- name: PROXY
type: select
proxies:
- DIRECT
- Example nodeDefine Example node under proxies; this snippet only shows how to reference it.
tun:
enable: true
stack: mixed
auto-route: true
auto-detect-interface: true
dns-hijack:
- any:53Before enabling TUN, check permissions, DNS settings, and compatibility with other network tools.
# Subscription value
mixed-port: 7890
mode: global
# Override value
mode: rule
# Final result
mixed-port: 7890
mode: ruleCheck merge behavior separately for list fields; regular field rules do not necessarily apply.
Need to understand how the fields reference one another? Continue with the config.yaml reference. These examples explain the structure; they are not a complete configuration with real node details.
Check your operating system and processor architecture before comparing clients. Clients provide the interface and system integration; subscription services must be sourced separately.
New to Clash? Start by comparing Clash Plus and Clash Verge Rev. If you're replacing Clash for Windows, focus on subscription migration, service mode, and system proxy settings. You don't need to reproduce every setting from the old client.
Check your system architecture before installing, and export custom rules before migrating. Don't let old and new clients listen on the same local port at the same time.
Go to downloads →Check the chip listed under About This Mac to choose an Apple Silicon or Intel installer. Then compare how Clash Plus, Clash Verge Rev, and FlClash manage configurations.
When you first enable network features, follow the system prompts to grant permission. If you still can't connect after closing the client, check that the system proxy was restored and no proxy settings pointing to localhost were left behind.
Go to downloads →Compare Clash Plus, Clash Meta for Android, FlClash, and Surfboard. Check subscription format compatibility first—a link containing the word Clash is no guarantee.
After importing successfully, allow the client to create a VPN connection. If it needs to run in the background, check battery optimization and background permissions. If another VPN app is active, stop it before testing.
Go to downloads →The download page links to Clash Plus on the App Store and lists the official site, clashplus.io. After installation, add a compatible subscription, allow the VPN configuration when prompted, and select the policy you want to use.
After connecting, visit the target website in a browser to test access. If switching between Wi-Fi and cellular causes problems, reconnect first, then check the subscription and DNS. There's no need to delete all your configurations right away.
Go to downloads →For desktop Linux, choose Clash Verge Rev or FlClash and select the package format for your distribution. On servers, routers, or command-line-only systems, see the core section of the download page and use mihomo. You'll need to manage the configuration path, service startup, and permissions yourself.
A graphical client launching successfully does not mean system traffic is being proxied. Check the local listening port first, then verify desktop proxy settings or TUN routes. When managing a remote machine, keep a recovery path before changing routes.
Go to downloads →Use the system requirements on the download page to choose an installer. Similar client names don't imply the same maintenance status, protocol support, or configuration features. If your current setup works, back it up before migrating; changing one thing at a time makes problems easier to diagnose.
Once installation is complete, follow these steps in order. First make sure the configuration loads, then set the mode and test the connection. Avoid changing several variables at once.
Open the configuration page, add a remote profile, paste the full subscription URL, and save. Wait for the profile card to appear and check for download or parsing errors, then set it as the active profile. Seeing a card does not mean the profile is active; also check that its proxy groups appear on the proxy page. If parsing fails, verify the subscription format and URL.
For everyday use, select Rule mode, then open the proxy or proxy group page and choose an available member for the main groups in your configuration. On desktop, enable the system proxy; on mobile, allow the VPN connection when prompted. Leave TUN off unless you need it, so permissions, routing, and subscription issues stay easier to separate. Menu names vary by client.
Visit one website expected to connect directly and another expected to use the proxy. Then check the connection log for the matched rule and outbound policy. If both fail, check the network, configuration loading, and proxy toggle first. If only one fails, investigate its rules, DNS, or node. Test with a new connection; existing browser connections may keep using the old route.
Understand the core, interface, and subscription separately to get a clear starting point for choosing a client and troubleshooting. This site is a community resource, not the developer of these projects.
The Clash ecosystem includes proxy cores, graphical clients, and configuration tools. The original Clash project's history influenced the naming and configuration conventions of many clients, but that does not mean every similarly named app is maintained by the same team. When looking for a Clash for Windows replacement, check the target project's current maintenance status, configuration compatibility, and system integration instead of migrating based on a similar interface alone.
mihomo continues the technical direction of Clash Meta, parsing configurations, matching rules, and handling connections. Graphical clients such as Clash Verge Rev provide interfaces for managing subscriptions, toggling the proxy, and integrating with the system. If a field isn't recognized, first check which core is running and what it supports. For menu, tray, or permission issues, consult the client documentation. A client interface update is not the same as a core update.
Configuration examples explain individual fields or references; actual behavior depends on the runtime environment and the complete configuration. For DNS, TUN, or rule sets, consult project documentation for defaults and limitations. The mihomo repository command below is for users who want to read the source code and project documentation. Most users can simply install a graphical client—there's no need to compile the core or learn Git just to import a subscription.
Client updates change app features and compatibility. Subscription updates fetch content published by the configuration provider, and rule sets may have their own update schedule. Installing a new package won't renew an expired subscription, and updating a subscription won't upgrade the core. Keep a working configuration before making changes, read the release notes, and handle one type of change at a time. Afterwards, recheck the active profile, proxy mode, ports, and custom overrides.
A client does not provide a remote proxy service you can use out of the box. Use configurations from trusted sources with clear authorization, and follow the laws and network-use rules where you are. This site provides setup and configuration guides; connection results depend on your local network, subscription contents, and server status.
Explore topics beyond the quick start. Choose the article that matches your current question; there's no need to reset every network setting.
Starting with a complete configuration, this guide walks through general fields, dns, proxies, proxy-groups, rule-providers, and rules—explaining what each section does, how to order them, and how they reference one another.
Read article →A traffic-flow diagram explains how the three proxy modes work, where each is useful, and common misconceptions. Learn why Rule mode is usually the best choice for everyday use and when to switch to Global temporarily.
Read article →Troubleshoot node timeouts from local checks to remote services: subscription expiry, system time, DNS and fake-ip, port conflicts, system proxy, and TUN status. Each step includes what to check.
Read article →