Client Picks 8 min read

Best Clash Clients: Clash Plus, Clash Verge Rev, and FlClash Compared

Compare leading Clash clients by platform support, core version, usability, TUN support, and subscription management, with recommendations for different use cases.

Compare platforms: start with available downloads

For desktop subscription, rule group, and connection-log management, start with Clash Verge Rev. To use a similar interface on desktop and Android, try the FlClash family. For an iOS option listed on this site, see Clash Plus. The links below are the downloads offered on this site, not a complete list of each project's releases. In particular, distinguish FlClash from FlClashs, which this site lists separately. Check the package name and release notes before switching.

ClientPlatforms listed on this siteFirst workflows to tryWhat to check for traffic routing
Clash PlusWindows、macOS、Android、iOSImport a subscription, switch the active profile, and select a rule groupOn desktop, check system proxy and TUN settings; on mobile, check VPN permission and connection status
Clash Verge RevWindows、macOS、LinuxTroubleshoot across the subscription, proxy, connections, and settings screensCheck system proxy, virtual network adapter, and service permissions separately in settings
FlClash family (listed as FlClashs on this site)Windows、macOS、Linux、AndroidVerify profile switching and rule-group selection on both desktop and mobileCheck desktop TUN or Android VPN permissions for each platform

On macOS, open Apple menu → About This Mac and check Chip or Processor: choose ARM64 for Apple silicon or x64 for Intel. Among this site's Linux downloads, Verge Rev offers DEB and RPM packages, while FlClashs lists DEB. For Fedora, for example, look for RPM first rather than converting package formats. For Android, don't rely on the phone model alone: check which ABIs the OS supports on older devices, then choose an ARM64 or ARM package.

Core versions: a newer client doesn't guarantee support for every config field

The client imports configs, displays rules, and controls system traffic routing; the core parses YAML, handles connections, and matches rules. mihomo is the new name used by the Clash.Meta project, not a desktop client's version number. Clash Verge Rev and FlClash use mihomo, but bundled core versions can vary by release. For Clash Plus and FlClashs, check runtime details for the actual platform and package instead of extrapolating from a desktop build to a mobile one.

  1. In the client's Settings, look for About or Core information, and note the app and core versions separately. If the core version isn't shown, check the startup logs or release notes. Menu names vary by build.
  2. If a config won't load, start with the first parse error in the logs. An unknown proxy type, an invalid field value, and a rule referencing a nonexistent rule group are different problems; switching nodes repeatedly won't fix a parse error.
  3. Test with a copy of your own config. For example, if it includes type: hysteria2, confirm the running core can parse that type, then check whether a connection can be established. Seeing a node name in the subscription list isn't enough.

Interface and subscriptions: make sure updates still fit your workflow

A successful import only clears the first hurdle. Four everyday actions matter most: import, set as active, update, and roll back. In Clash Plus, check how many steps it takes to move from the profile list to a proxy group. In Verge Rev, select a profile under Subscriptions, then check under Proxies that its rule groups have refreshed. With the FlClash family, repeat the workflow on both devices; similar interfaces don't mean settings sync automatically.

Keep remote subscriptions separate from local edits

  • A remote subscription is usually a URL that returns config content. A local YAML is a file. If you need periodic updates, test refreshing the remote profile manually. If you want a snapshot you can roll back to, import a local copy.
  • Before adding rules, check whether the client supports separate overrides and whether they replace or append to the rule list. If you can only edit the local cache of a remote config, the next refresh may overwrite your changes.
  • After refreshing, check the active profile, rule-group members, and final fallback rule. Manual selections may not survive if nodes are renamed or removed. Put MATCH last and specific rules first so the logs make it clear which rule matched.
  • Subscription URLs often contain access tokens. Blur the full URL in screenshots, and keep subscription links separate from ordinary interface settings when making migration backups.

If you maintain multiple configs, rehearse a rollback: first establish a working setup with a local copy, then switch to the remote profile and update it. If the update fails, check whether the client kept the old config and whether you can switch back to the copy manually. Enable automatic updates only once this process is under control.

System proxy and TUN: test traffic routing app by app

A system proxy mainly serves apps that read the OS proxy settings. TUN routes IP traffic through a virtual network adapter, and may require administrator access or service permissions; on mobile, check the system VPN permission. UDP, IPv6, and DNS behavior also depends on routing, core configuration, and platform limitations. An enabled toggle doesn't mean every app is routed through the client.

Test the local proxy port, then the app's traffic path

Suppose the client's settings show a mixed port of 7890. You can explicitly set an HTTP proxy for a comparison test. If the port differs, use the actual value. In Windows PowerShell, use curl.exe to avoid interference from the legacy PowerShell alias.

curl --head --max-time 10 --proxy http://127.0.0.1:7890 https://example.com/

A successful command that appears in the connection log only proves that this request passed through the local proxy inbound. If the log shows DIRECT, the core received the connection but the rules selected a direct outbound. To test TUN, turn off the system proxy and start a new connection from an app that isn't configured to use an explicit proxy. Check the logs and matched rule; existing connections may be reused, so restart the app if needed.

If enabling TUN disrupts a work VPN, printer, or local file sharing, turn TUN off for comparison, then check for overlapping routes and DNS settings. On a managed device without authorization, use an approved per-app proxy option rather than making service installation your first troubleshooting step.

Choose by use case: desktop troubleshooting, cross-device use, and migration

  • Mostly browsing on Windows: Choose either Clash Plus or Verge Rev, then test the system proxy, tray controls, and behavior after a restart. If you regularly inspect matched rules and outbound connections, focus on Verge Rev's connection view. If the browser works as needed, there's no need to start with TUN.
  • Frequent connection checks on macOS or Linux: Filter by processor and package format first, then test a config update, log search, and system proxy restoration on exit. Linux desktop environments handle system proxy settings differently, so test with a terminal tool you actually use as well.
  • Desktop and Android: To keep workflows as similar as possible, try the FlClash family first. Test the phone's connection after locking the screen and switching between Wi-Fi and mobile data. A working desktop setup doesn't replace testing on the phone.
  • Need iOS: Check the installation requirements and supported subscription formats through the Clash Plus iOS link on this site. Test importing a profile, granting VPN permission, and restoring network access after disconnecting. Don't follow desktop service-mode steps.

When migrating from an older version of Clash for Windows or another client, keep the original YAML and subscription source. Exit the old client and turn off its system proxy and TUN before starting the new one. If both clients listen on 127.0.0.1:7890, they'll compete for the same port. If both change the system proxy, symptoms can also vary with startup order. Migration is complete when your regular apps connect, rules match correctly, subscriptions update, and the network works again after exit—not when both clients show the same number of nodes.

Download Clash