Choosing a Client · Windows Setup Checklist
Choose a client, import a subscription, and connect. Follow the checklist to configure Clash Verge Rev, routing rules, and TUN mode.
Clash Verge Rev · Setup Checklist
Download the Clash Verge Rev x64 installer (.exe)
Install the core as a service
Paste the subscription link and click Import
Set the proxy mode to Rule
Enable the system proxy
Enable launch at startup
Settings / System Settings
System Proxy
Proxy port 7897
Settings / Clash Settings
TUN Mode
Install service mode first
stack: mixed
Windows / App Network
UWP Loopback Exemption
CheckNetIsolation LoopbackExempt -a -n=…
First connection / Complete these three tasks first
Open the download center and check your operating system and processor architecture first. Windows users can start with Clash Plus or Clash Verge Rev; the setup examples on this page use Clash Verge Rev. After installing, open Settings and confirm the core starts before importing a configuration.
Get a link from your subscription provider, open the Configuration page, paste the link, and click Import. Once the configuration appears, select it to enable it. Return to Proxies and check that the proxy groups have loaded. Saving a link without enabling its configuration will not establish a connection.
Set the proxy mode to Rule, choose an available node in a proxy group, then enable System Proxy. Visit the site you want to reach and check the matched rule and outbound policy on the Connections page. Get the browser working first, then configure TUN if your apps need it; avoid changing several settings at once.
Install, import, connect, and verify—in that order. If something fails, stop and check the logs at the current step.
Downloads / Choose a device
Installers are client apps; subscriptions come from your provider. Choose a device, then check the architecture and system requirements.
Whether you can use the same subscription across devices depends on its configuration format, protocol support, and your provider’s device limits. Don’t copy a Windows installer to a phone, or assume clients with similar names share every setting. The download center lists available clients, maintenance status, and setup notes for each platform.
A good fit for desktop browsers, developer tools, and everyday work apps. First check the system type under Settings → System → About, then choose the matching installer. The download center lists Clash Plus first, alongside Clash Verge Rev, FlClash, and other options. The discontinued Clash for Windows is clearly marked as an archived release.
Go to downloadsChoose the right installer for Apple Silicon or Intel. Check the chip listed in About This Mac, then pick a client. Clash Plus, Clash Verge Rev, and FlClash each have a download option; ClashX Meta is archived and no longer maintained. Follow your chosen client’s prompts for first launch and network extension permissions.
Go to downloadsOptions include Clash Plus, Clash Meta for Android, FlClash, and Surfboard. Your first connection requires Android VPN permission; that does not provide a working subscription. If the connection drops when the screen turns off, check battery optimization and background activity restrictions. Verify the configuration and node first, then adjust power-saving settings.
Go to downloadsUse the download center to open the Clash Plus App Store page. The project website is clashplus.io. After installing, follow the prompts to add a VPN configuration, then import your subscription. Desktop features such as service mode and UWP settings do not apply to iPhone; use the options provided by the mobile client.
Go to downloadsFor desktop use, start with Clash Verge Rev or FlClash and choose the package format for your distribution. Server and router users can find the mihomo core in the download center, but will need to manage configuration files, service permissions, and startup themselves. New desktop users will find a GUI client easier for checking the active configuration and connection history.
Go to downloadsSettings at a glance / From traffic entry to routing decision
System proxy determines how apps connect; proxy mode and rules determine where connections go.
When you enable System Proxy, the client points Windows’ proxy address to its local listening port. Browsers and other apps that follow system proxy settings can then send traffic through the core, which handles it according to the current mode. For your first setup, choose Rule mode, make sure a configuration is enabled and a proxy group has an available node, then turn on the switch. This does not force every program to use the proxy: some games, command-line tools, and apps with their own network settings may connect directly. Compared with TUN, this changes less and is a good way to check that your subscription and nodes work. Turn off System Proxy before closing the client.
mixed-portmodeLocal proxy address 127.0.0.1
mixed-port: 7897
mode: rule
allow-lan: falseTUN routes traffic through a virtual network adapter and routing settings. It can handle traffic from some apps that ignore the system proxy. On Windows, install service mode and confirm it is working before enabling TUN mode. Afterward, check the target app’s connection records rather than relying on the switch’s appearance. TUN is not the same as Global mode: TUN handles how traffic enters, while rules can still decide whether it goes direct or through a proxy. If it conflicts with another VPN, virtual adapter, or corporate network, disable other traffic-routing tools first, then check routes and DNS. You don’t need every networking feature enabled just to browse.
tun.enabletun.stacktun.auto-routetun:
enable: true
stack: mixed
auto-route: true
auto-detect-interface: trueRule mode matches domains, addresses, and other conditions in configuration order, then applies the corresponding policy. Start with the rules included in your subscription, then check the matched rule and policy group on the Connections page. Unlike Global mode, rules can send different destinations through different routes, but the result depends on the rule content and order. To customize, add rules using the client’s supported override method; avoid editing files that subscription updates may overwrite. Proxy group names must match exactly. Put the fallback rule last, or more specific rules below it may never run.
moderulesrule-providersmode: rule
rules:
- DOMAIN-SUFFIX,example.com,DIRECT
- IP-CIDR,192.168.0.0/16,DIRECT
- MATCH,DIRECTShows rule order only; every example uses DIRECT.
A subscription link fetches configuration data such as nodes, proxy groups, and rules; the client itself does not provide working nodes. Open the Configuration page, paste the link, and import it. Once it appears, set it as the active configuration. A successful import only means the file was retrieved; check the proxy groups and test an actual connection too. Subscriptions make it easier to update nodes than maintaining a single configuration file by hand, but updates may overwrite direct edits. Keep personal changes in an override layer supported by the client. Subscription links often contain credentials, so hide the full address when troubleshooting and never post screenshots or raw configuration publicly.
proxiesproxy-groupsproxy-providersHide subscription links and credentials before sharing screenshots.
Service mode lets a Windows service handle some operations required to run the core, which is useful when elevated network permissions are needed. Find Service Mode in Settings, install it, approve the Windows prompt, and check its status. It is different from launch at startup: service mode handles background operation and permissions, while startup determines whether the client interface opens after you sign in. Installing the service does not enable TUN or guarantee that your configuration and nodes work. If installation fails, check the logs and Windows security prompts instead of toggling settings repeatedly. When switching clients or uninstalling, follow the service removal steps provided by the original client.
tun.enableService mode is managed by the client; it is not a universal YAML switch.Service mode, launch at startup, and TUN are separate settings.
Open-source ecosystem / Know what each project does
The client manages configurations and provides the interface; the core handles protocols, matches rules, and routes network traffic. When updating, check the release notes for both rather than relying on the app’s name alone.
Clash originally provided a rule-based proxy core. GUI clients in its ecosystem built on it with features such as a system tray, configuration management, and platform settings. Since the original project and Clash for Windows are no longer maintained, download links, screenshots, and option names in older guides may not match current clients. Check maintenance status first, then consider your operating system and required features. A Clash name alone does not mean a project is actively maintained. Archived software can help with legacy configurations; for a new device, start with a maintained option.
mihomo is an open-source core continuing the Clash Meta lineage. It reads configurations, handles connections, and applies rules. Clash Verge Rev provides a graphical interface for importing subscriptions, choosing policy groups, viewing logs, and adjusting the system proxy. They are separate projects, and GUI menu items should not be mistaken for universal configuration keys. When following a guide, first determine whether it describes client actions or core configuration to see if it applies to your device.
Open source lets you inspect how a project works and what changes between releases. For questions about protocols, DNS options, or routing behavior, check the core documentation first, then consult the client’s release notes to confirm what it supports. This site collects client downloads and setup guides; it does not develop these independent projects. Subscription providers are responsible for node quality, account status, and device limits. Whether the client starts, the subscription imports, and a destination connects are three separate things to verify.
Client updates and subscription updates serve different purposes: the former changes the interface, dependencies, or core integration; the latter refreshes nodes and configuration data. Before updating, save personal overrides, rules, and essential settings, and read the release notes. Afterward, check the active configuration, system proxy, service mode, and TUN settings. If the network stops working, note what triggered the issue and when the logs were recorded, then return to a known-working basic setup. Don’t keep adding complex rules and multiple traffic-routing tools before confirming the connection works.
Browse source / mihomo
Use this when you need to read or build the core from source. For everyday use, choose a GUI client from the download center; you don’t need to install Git or build tools first.
git clone https://github.com/MetaCubeX/mihomo.gitPaste the command into a terminal after copying; it will not run automatically.
A client processes network traffic on your device; it does not come with working nodes. Subscriptions typically provide servers, proxy groups, and rules, and must be obtained from a service provider. Check that the subscription is valid and uses a compatible format before importing it. A link opening in your browser does not necessarily mean it returned a usable configuration file.
See how to import a subscriptionGlobal mode sends connections that have reached the core through the global policy; it does not take over all system traffic. For everyday use, start with Rule mode so different destinations can be routed according to rules. You can temporarily switch to Global mode to compare results while troubleshooting, but still check which node is selected. Changing modes won’t fix an expired subscription or an app that bypasses the proxy.
Understand proxy modes and traffic entryFirst check whether the app follows the system proxy. If it’s a UWP app affected by loopback restrictions, check its loopback exemption. If it does not use the system proxy at all, consider TUN if needed. Loopback exemption only addresses a local connection restriction in certain sandboxed apps; it is not a general fix for network issues and should not be enabled indiscriminately.
Read about UWP loopback exemptionsOpen Windows Settings → Network & Internet → Proxy and check that a manual proxy is not still pointing to a local port that is no longer listening. If you enabled TUN, check the status of other VPNs and virtual network adapters too. Whenever possible, exit through the client’s menu so it can clean up properly. Record the original settings while troubleshooting; don’t reset all network settings right away.
Visit the help centerUpdates / Recent setup notes
Once your basic connection is working, look up guides for specific issues. The interface overview helps you find menus; the UWP article covers a particular local loopback restriction; the Fake-IP article explains DNS mapping in more depth. Before changing network stack settings, save the current configuration and test each change separately.
Learn how Fake-IP maps domains to reserved addresses and reduces DNS round trips, what fake-ip-filter does, and how to handle conflicts with local network devices.
Read the full articleLearn why the UWP sandbox blocks access to 127.0.0.1, and how to add a loopback exemption for Store apps using the client’s built-in tool or the CheckNetIsolation command.
Read the full articleA page-by-page guide to the sidebar: switching proxy groups, managing subscription configurations, checking connections and logs, and using common settings to get familiar with the interface.
Read the full article