Start by installing Clash Verge Rev, then learn about the system proxy and mihomo routing rules. Adjust subscriptions, DNS, and YAML configuration as needed.
System settings only determine where traffic enters. The client and core handle subscriptions, routing, and DNS resolution.
The Windows system proxy isn’t a universal switch. Some command-line tools, games, and apps with their own network stacks ignore it. Configure those apps separately or consider TUN mode.
If the proxy address isn’t restored before the client closes, your browser may keep trying to connect to a local port that’s no longer listening. When troubleshooting, distinguish network issues from a stopped local listener before considering a Windows reinstall.
When a remote configuration is downloaded again, locally added rules may disappear. Repeated edits are hard to track and can easily break YAML indentation or policy group names.
Manage the system proxy and TUN separately in Settings. Start with the system proxy to verify basic connectivity, then enable the virtual adapter if you need to cover more apps. Avoid changing too many variables at once.
Rule mode checks domains, addresses, or rule sets in order; policy groups determine the outbound route for a match. Use the Connections page and logs to confirm the actual route instead of relying on a toggle’s status.
Use the client’s override or merge features to save custom fields. Let the subscription provide the base configuration and the local layer add rules. After an update, check which settings are actually in effect.
Clash Verge Rev# Example configuration structure; no proxy nodes included
mixed-port: 7897
mode: rule
proxy-groups:
- name: Default
type: select
proxies:
- DIRECT
rules:
- MATCH,DefaultFirst identify how traffic enters, then decide which rules to match. These snippets explain individual fields; they aren’t complete subscriptions.
Rule mode doesn’t send every connection through the same route. mihomo checks rules from top to bottom and sends traffic to the corresponding policy group when a rule matches. Put specific domains before broader rules, and leave the catch-all rule at the end. The client can show policy groups and let you switch options, but it won’t fix an incorrect rule order. If a site takes an unexpected route, check the matched rule in the connection details, then make sure the policy group name matches the configuration. Unlike changing only the system proxy, rule-based routing lets you define exactly what should bypass the proxy on your LAN and how other traffic is handled.
rules:
- DOMAIN-SUFFIX,example.com,DIRECT
- IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
- MATCH,DefaultTUN mode routes traffic through a virtual network adapter and the routing table, making it useful when you need to cover more apps. It operates at a different layer from rule mode: TUN determines how traffic reaches the core, while rules determine where it goes next. On Windows, the client service typically needs appropriate permissions; make sure it’s installed before enabling TUN. If you use another VPN or virtual network adapter, check for routing conflicts first. TUN isn’t a universal fix for connection problems: expanding traffic capture won’t restore an unavailable remote connection or broken subscription.
tun:
enable: true
stack: mixed
auto-route: true
auto-detect-interface: true
dns-hijack:
- any:53Subscription management stores sources, fetches configurations, and switches the active profile. A successful import doesn’t mean every proxy node works, and a failed update doesn’t necessarily mean the link is dead. First confirm that the source returns a configuration the client supports—not a login page, error message, or a different subscription format. After updating, check whether the active profile changed and whether local overrides still apply. Subscription URLs may contain credentials, so remove them before sharing logs, screenshots, or configuration files. Clients may store subscriptions differently; back them up separately before migrating.
# Check that the configuration includes these top-level fields
# Nodes and policy groups are provided by the subscription source
proxies: []
proxy-groups: []
rules:
- MATCH,DIRECTThe system proxy writes a local listening address to Windows proxy settings for apps that respect them. Launch at startup only determines whether the client opens after sign-in; it doesn’t guarantee that the subscription works or the proxy is enabled. When setting things up, confirm the core is running, enable the system proxy, then test in a browser. If websites stop loading after the client exits unexpectedly, check whether Windows still points to a local port that is no longer listening. Allow LAN connections is a separate setting and usually isn’t needed on a single device. If you do need to share the proxy, consider firewall rules and limit who can access it.
# Core listener settings; the client controls the system proxy toggle
mixed-port: 7897
allow-lan: false
bind-address: "127.0.0.1"Enabling a DNS option alone can’t guarantee leak prevention. The system resolver, secure DNS in your browser, app-specific DNS, and TUN DNS hijacking can all change how requests are routed. mihomo supports configurable DNS modes and upstream servers, but you still need to test them with your current traffic entry method. With fake-IP enabled, watch for LAN services that require real IP addresses. If you run into compatibility issues, add domain-specific filters instead of copying an entire DNS configuration at random. During troubleshooting, track DNS resolution and outbound connections separately so you don’t mistake one issue for the other.
dns:
enable: true
enhanced-mode: fake-ip
fake-ip-range: 198.18.0.1/16
fake-ip-filter:
- "*.lan"Remote subscriptions are suited to maintaining proxy nodes and base policies; local overrides are better for ports, LAN options, and personal rules. Keeping the two layers separate means you won’t need to edit the original file after every update. Note that merge behavior varies by client: mapping fields may merge recursively, while lists may be replaced entirely. The example below shows fields to override, not a universal workflow shared by every client. Back up the original configuration before saving, then review the generated file and logs to see whether the fields took effect or were overwritten later. When migrating scripts from an older client, pay particular attention to when they run.
# Example local overrides
mixed-port: 7897
allow-lan: false
mode: rule
log-level: infoDesktop and mobile clients handle traffic differently. Choose your operating system first, then compare clients, processor architecture, and installation options.
The download page lists options such as Clash Plus and Clash Verge Rev. Before getting started, check the Windows requirements, import your configuration, and enable the system proxy. Set up service permissions for TUN only if you need it; there’s no need to enable every feature during installation.
Go to downloadsChoose the right installer for your Apple Silicon or Intel processor. Configure network extensions, the system proxy, and background permissions as prompted by the client. If you’re looking for a ClashX Meta download, compare maintenance status before deciding whether to use an archived client.
Go to downloadsCompare clients such as Clash Plus, Clash Meta for Android, and FlClash. Mobile clients typically use the system VPN permission to route traffic. Check that no other VPN is running, and note that background battery restrictions can interrupt long-running connections.
Go to downloadsThe Clash iOS client page links to Clash Plus on the App Store and lists the official site, clashplus.io. After importing a configuration, grant network access when prompted by iOS. Don’t assume desktop scripts or platform-specific fields will work the same way on a phone.
Go to downloadsFor desktop use, start with Clash Verge Rev or FlClash and choose a package for your Linux distribution. Server and router users should consult the core guides and plan service startup, listening addresses, and permissions separately. Don’t expose a local proxy port directly to the public internet.
Go to downloadsBefore migrating from Clash for Windows, keep a copy of your old configuration and rules. Then verify subscription parsing, policy group selection, and system proxy restoration in the new client. The same configuration file extension doesn’t mean different cores support exactly the same fields. For help choosing, read the client comparison, then return to the download page to pick an installer.
View all clients →Understanding what each layer does is more useful for troubleshooting than focusing on a single toggle. This site curates download links and configuration guides; software behavior depends on the project implementation and your actual configuration.
Graphical clients in the Clash ecosystem typically handle the window, tray menu, subscription storage, and system integration. The core handles proxy protocols, rule matching, and DNS resolution. mihomo continues the technical direction of Clash Meta and supports its corresponding configuration features. Clash Verge Rev is one client that uses mihomo; not every feature in its interface is a core configuration field. For example, launch at startup depends on the client and operating system working together. Copying generic YAML can’t guarantee it will work on every system.
To verify how something works, start with the project documentation, release notes, and issue tracker, then look at the source code. The mihomo public repository is under the MetaCubeX organization and is useful for checking supported fields, protocol handling, and known issues. Star counts and download numbers aren’t substitutes for technical evaluation; even accurate figures can’t tell you whether a setting suits your network. When reporting a problem, include your operating system, steps to reproduce it, and redacted logs so others can reproduce what you’re seeing.
The graphical interface and core may update separately. If your configuration breaks after a client update, check the logs for the field or line number, then consult the documentation for the corresponding core. Don’t migrate every old script, DNS setting, and override at once. Get the base subscription working first, then restore local changes one at a time and verify after each change. This makes it easier to pinpoint whether a problem comes from the subscription, merge order, or network environment.
A client is a tool for managing configuration and connections, not a network service. You choose and manage your own nodes, subscription URLs, and access permissions; this site doesn’t provide subscription accounts. Before downloading, distinguish software sources from subscription sources. Before changing a listening address, understand who will be able to connect. Follow the laws where you live and the rules of the networks you use. For work devices or shared networks, get the required authorization before changing system proxy, virtual adapter, or routing settings.
Find steps for issues ranging from subscription formats to migrating from older clients. Keep a working configuration, then track down changes one at a time.
Compare leading Windows clients by core version, interface and ease of use, TUN support, subscription management, and update activity, with recommendations for different needs.
Read the guide →Explore alternatives after the original client was discontinued, with step-by-step comparisons for moving subscriptions, custom rules, Parser overrides, and system proxy settings to a new client.
Read the guide →If a subscription fails to parse or imports no nodes, check for an expired link, unexpected response format, YAML indentation errors, or User-Agent filtering—one step at a time.
Read the guide →