Client reviews and settings compared

Clash ReviewClient Downloads

Compare Clash Plus, Clash Verge Rev, and FlClash by platform, and review subscription imports and rule-based routing settings.

Open-Source Core Guides
mihomo core GPL-3.0 licensed Windows / macOS / Linux / Android / iOS YAML configuration

Proxy Modes
Rule, Global, and Direct

Proxy mode determines how connections are handled by the core. For everyday use, start with Rule mode to preserve the direct and proxied routes defined in your configuration. To check whether a rule is causing a problem, briefly switch to Global, confirm the selected outbound in the global policy group, then open a new connection to the same destination for comparison. Direct mode helps you check how a connection behaves without proxying. Clash Verge Rev and FlClash may place the mode selector in different locations. When comparing clients, check whether the Connections view shows both the matched rule and the final outbound.

  • Rule mode routes traffic according to the active configuration
  • In Global mode, check which policy is selected
  • Changing modes does not enable a traffic entry point

Rule-Based Routing
Match Order and Fallback

Rules are checked from top to bottom, and the first match determines the policy. To create an exception for a subdomain, place the exact domain before any broader suffix rule that would match it; otherwise, the exception will never apply. In this example, Proxy is a policy group name and must match the name in your configuration. Put MATCH last to catch connections that did not match an earlier rule. When choosing a client, distinguish interfaces that only display the rule list from those that support persistent overrides. The former make it easy to inspect current results; the latter let you keep local changes separate from your subscription.

  • Put specific rules before broader rules of the same type
  • Policy group names must match those in the configuration
  • Use a new connection to verify which rule actually matches

TUN and System Proxy
Traffic Entry Points and Permissions

System Proxy relies on apps honoring the proxy settings configured in the operating system. Apps with their own network stack may not appear in the connection list, even when System Proxy is enabled. TUN uses a virtual network interface and routing to capture a broader range of traffic; the actual coverage depends on exclusions and platform permissions. When comparing desktop clients, look beyond the toggle: check whether a service must be installed and whether the client explains permission errors. For initial troubleshooting, change just one entry point. Check LAN access, DNS resolution, and connection logs before deciding whether to leave it enabled.

  • System Proxy works with apps that follow system proxy settings
  • TUN coverage depends on routing and configured exclusions
  • Check for VPN conflicts before comparing the two entry points

Subscriptions and Configuration Files
Import, Switch, and Update

A remote subscription fetches a configuration from a URL; a local import reads a file on your device. A successful import only means the client accepted the input. Select the profile and confirm its proxy groups and rules have loaded. If you keep multiple profiles, name them by purpose and check the policy groups again after switching. Groups with the same name in different profiles may offer different outbounds. Clients vary in how they handle automatic updates and overrides. To keep custom rules, make sure they are saved in a separate override layer or save a local copy of the configuration, so a remote update does not overwrite your changes.

  • Importing a profile and activating it are separate steps
  • Review policy group options after updating a remote profile
  • Identify subscription URLs and other sensitive fields before backing up

Settings Troubleshooting Checklist

Start with the symptom, change one variable at a time, and keep comparisons reproducible.

The mode changed, but the connection log still shows the old policy

Check when the connection was made. Browsers, messaging apps, and file-sync tools may reuse existing connections, so old entries remain after you change modes. Close the test window in the app, reopen it, and make the same request again. Compare the destination, matched rule, and outbound in the new log entry. If no new entry appears, first check whether the app's traffic is reaching the client before investigating policy selection. After testing in Global mode, switch back to Rule mode so a temporary setting does not carry over into everyday use.

Clash Client Downloads by Platform

Check your operating system and processor architecture, then compare package types and maintenance status on the download page. Before using the same subscription across devices, check which configuration formats and rule types each client supports. Similar-looking interfaces do not mean settings transfer one-to-one. Import the profile on the new device and verify a connection before disabling the old client.

Windows

Compare Clash Plus, Clash Verge Rev, and FlClash. Before switching, back up your settings and disable System Proxy in the old app. Verify the active profile and policy groups in the new app.

macOS

Use About This Mac to choose the Apple silicon or Intel installer. Check the client’s permission requirements for TUN, and disable any other tool that manages System Proxy.

Android

Choose the package that matches your device and review the VPN permission prompt. If it disconnects, check for another VPN session or Android’s background activity restrictions.

iOS

Find Clash Plus on the App Store and check its iOS requirements. In the app, confirm how to import a profile and check whether VPN access is authorized.

Linux

Compare Clash Verge Rev and FlClash, then choose a package for your distribution and CPU. Test proxy settings in the browser and terminal separately. For headless systems, look for a standalone core.

Browse all clients

Quick Start: Import a Profile and Verify a Connection

  1. Import and Activate a Profile

    Open the client's profile or subscription page and choose Remote Subscription or Local File, depending on the source. For a remote subscription, enter the full URL provided by its source. For a local profile, select the saved YAML file. Wait for the profile to appear in the list, set it as active, then open Proxy Groups to confirm its contents have loaded.

    If saving fails with a parse error, first check whether the URL returned a configuration at all or whether the returned file uses an unsupported format. If the profile saves but has no policy groups, confirm that the imported profile is active rather than the previous default. When reporting an error, include only the relevant details and avoid showing the full subscription URL in screenshots.

  2. Choose a Policy and Traffic Entry Point

    Choose the option you plan to use in Proxy Groups, then set the mode to Rule. On desktop, start by testing an app that follows system proxy settings. On mobile, complete the VPN authorization requested by the operating system. Enable only one traffic entry point at first, and do not run two clients with the same profile just to compare them.

    If the interface offers a latency test, use the same test destination to compare whether candidate outbounds respond. A single result depends on the test address and current network conditions; it is not a download speed test and does not prove that the target app is using that outbound. Keep your chosen policy, then verify it with a real request.

  3. Verify Routing with a New Connection

    Choose a destination expected to use the proxy, then send a new request from the test app. Open Connections, find the entry by domain or request time, and check the matched rule, selected policy group, and final outbound. Repeat with a destination expected to connect directly and confirm neither connection is falling through to the same fallback rule.

    A page loading successfully does not prove that routing is correct. If there is no matching connection entry, check the traffic entry point first. If there is an entry but the policy is wrong, inspect the rules. If the policy is right but the request fails, check whether the current outbound can reach the destination. Following this order avoids repeatedly changing configuration before the entry point is working.

Read the full guide

Clash Open-Source Projects and Maintenance

Clash Review gathers selection guides for third-party clients; it is not affiliated with the core projects or client developers. Projects with similar names may be maintained by different teams. When reading project documentation, identify whether it covers the core, a GUI, or subscription and rule data, then apply its guidance to the right layer.

Project History: Clash, Clash.Meta, and mihomo

The Clash ecosystem uses YAML to define proxy groups and rules. mihomo's history traces back to Clash.Meta. In older guides, these names may refer to a core from a particular period or, more broadly, to clients that use the same configuration approach. The name alone does not guarantee that current features match. For example, instructions for setting up System Proxy in an older guide may not apply to a current GUI client. When a guide mentions rule data files, check whether the target core supports that data format. Before comparing documentation, identify which core is running and check the meaning of fields in the current project docs.

Community Resources: License, Issues, and Releases

mihomo's source code is published under the GPL-3.0 license. The repository's license explains the terms for using the code, release notes document changes, and issues track reported behavior and discussion. These resources are not interchangeable: a bug report does not mean the issue occurs on every platform, and a change in the codebase does not mean it is included in a client installer yet. If a GUI behaves differently from the core documentation, check the client's own docs and issues before looking for related reports in the core repository.

How the Core and GUI Client Work Together

The core handles connections and rule matching; the GUI presents tasks such as importing profiles, choosing policies, and viewing connection status. Even when two clients use the same core, they may differ in default DNS settings, configuration override order, how they set System Proxy, and whether they restore the original settings on exit. Before switching, note your current entry point, profile source, and any rules you need to keep, then compare them one by one rather than assuming compatibility from similar-looking menus. For more on how the core, rules, and traffic entry points fit together, see the complete reference.

Update Paths: App, Core, Subscription, and Rule Data

App updates mainly affect the client interface and packaged contents. Core updates may change configuration parsing and traffic handling. Subscription updates replace remote profiles, while GeoIP or GeoSite data updates may change classification results. When troubleshooting, identify what actually changed first. If the app was not updated and only classification data changed, start by checking the matched rule and data source instead of reinstalling the client. If several components are updated, back up the current configuration and overrides, update one component at a time, then repeat the same test to pinpoint which layer caused the change.

Clash Configuration and Troubleshooting Articles

Choose an article based on the issue: check the traffic entry point first, then investigate import errors or routing differences caused by rule data.

Deep Dive

Clash TUN Mode vs. System Proxy: Coverage and Use Cases

Understand the two modes by how they handle traffic: System Proxy relies on apps honoring proxy settings, while TUN uses a virtual network interface to route traffic from the entire device. Includes permission requirements, compatibility issues, and guidance on when to use each.

Browse all articles