Platform support: narrow down your options by device
Start with the devices you use, not a feature checklist. If you only need Windows, all three are worth considering. For iPhone support, start with Clash Plus and check its iOS availability. If you need Linux and Android, look at the FlClash family. Sticking with one product family can make workflows easier to learn, but core details, traffic interception, and local settings may differ between desktop and mobile versions.
| Client | Platforms to compare | Features to check first |
|---|---|---|
| Clash Plus | Windows、macOS、Android、iOS | Import subscriptions, enable configurations, and switch proxies. On iOS, check VPN permissions and configuration compatibility separately. |
| Clash Verge Rev | Windows、macOS、Linux | Desktop configuration management, service mode, TUN, and local rules maintained through configuration extensions. |
| FlClash family | Windows、macOS、Linux、Android | Compare configuration workflows on desktop and Android, and check each platform's traffic interception method and diagnostic tools. |
Check FlClash and the FlClashs releases listed on this site's download page separately. Before following a FlClash guide, make sure its app name, release, and interface match the package you installed. For macOS, distinguish Apple silicon from Intel. On Linux, choose a package for your distribution and the files actually provided—for example, check for a .deb on Debian-based systems and a .rpm on Fedora-based systems. Don't assume both projects use the same package formats.
Core versions: importing a subscription doesn't mean every field will work
The client manages configurations and the interface, and handles system-level traffic; the core parses configurations and processes connections. Clash Verge Rev and FlClash use mihomo, but the client release number doesn't tell you which core version is actually running. For Clash Plus, check the version details for the platform you're using. Don't assume that core versions or supported fields on desktop also apply to mobile.
- Check both version numbers. Record the app version and core version from the client's About or core information page. If only the app version is shown, check the startup entries in the logs. If you can't find core details, mark the version as unconfirmed.
- Check configuration dependencies. If your subscription uses
type: vlessandreality-opts, test a node that uses that combination rather than just checking whether nodes appear in the list. If your rules referenceRULE-SET, make sure the corresponding names are defined underrule-providersand that remote rule sets load successfully. - Verify the results. Enable the configuration and check the startup logs. Then visit a domain that should match a specific rule and check the matching rule, proxy group, and outbound in the connection log. A successful subscription download, a loaded configuration, and correctly routed traffic are three separate outcomes.
Usability: run the same four tasks in each client
Counting buttons won't tell you much about day-to-day usability. Use the same subscription you're authorized to use and complete these steps in each client: import and enable the configuration, switch to the same proxy group, refresh the subscription, and inspect a connection log. Run only one client at a time to avoid local port conflicts and competing changes to the system proxy. Menus change between versions, so compare the tasks and results—not the location of a button in a screenshot.
- Clash Plus: If you mainly refresh subscriptions and switch proxies, check that the active configuration is easy to identify and that refresh failures are clearly reported. On iOS, complete the initial VPN permission flow, then return to the app and confirm the connection status.
- Clash Verge Rev: If you manage several desktop configurations, distinguish the active configuration in the profile list from the active proxy on the proxy page. Switching proxies doesn't switch subscriptions. After refreshing a subscription, confirm that the intended configuration is still active.
- FlClash: If you'll switch between desktop and Android, test the import and refresh workflow on both. Even with the same subscription, don't assume the selected proxy group, LAN settings, or traffic interception toggles sync across devices.
System proxy and TUN: test with the apps you use
For browsers and other apps that honor the system proxy, start there. Command-line tools configured with an explicit local proxy don't need TUN for a single request. Check the client's TUN or mobile VPN traffic interception if an app ignores the system proxy or needs certain UDP traffic routed through the client. A switch turning on only confirms that initialization got partway through; verify routing, DNS, and app exclusions separately.
Desktop: verify the proxy listener before testing traffic interception
These commands are for Windows PowerShell. Use them as written only if the client's mixed-port or HTTP proxy listener is actually 7890; otherwise, substitute the configured port. The command explicitly sends a request through the local HTTP proxy, so success only confirms that this request used that port—not that the system proxy or TUN is working.
Get-NetTCPConnection -LocalPort 7890 -State Listen
curl.exe --proxy http://127.0.0.1:7890 --head https://example.org/
Next, turn off the system proxy, retry with the target app, then enable TUN separately and test again. Check the connection log to confirm that the request reached the core. On Windows with Clash Verge Rev, if the client reports that TUN needs a service or additional permissions, check the service mode status and follow the interface prompts to install or authorize it. For WSL, virtual machines, and other VPNs, don't treat a working browser on the host as proof that they can connect; test each environment directly.
Mobile: check VPN permissions and traffic interception
Android and iOS use their own system VPN mechanisms, so Windows service mode steps don't apply. On Android, if you need per-app traffic interception, check whether your release provides an app list and confirm that the target app is included. On iOS, test with the target app after granting permission. A VPN-connected status doesn't guarantee that every connection uses the same outbound policy as your subscription.
Configuration overrides: make sure changes survive a refresh
Overrides keep local changes separate from remote subscriptions. Direct edits to a downloaded subscription YAML file may be overwritten on the next refresh. In Clash Verge Rev, start by checking the configuration page for extension options and distinguish merge-based configuration from script processing. With Clash Plus or the FlClash family, check on your target platform whether the current version supports field overrides, adding rules, or only editing a configuration copy. These approaches don't have the same scope.
- Make a copy of a working configuration for comparison. Change just one thing—for example, add
DOMAIN,example.org,DIRECTfor a test domain—and make sure the client is in Rule mode. - Make sure the new rule comes before any rule that could match first, especially a trailing
MATCH. Clash evaluates rules in order; adding a rule after the catch-all usually won't give you the result you expect. - Reconnect and check which rule actually matched. Then refresh the remote subscription, restart the client, and repeat the test. Treat the change as a reliable long-term configuration only if it still works after all these steps.
When migrating, distinguish configuration files from local device state. Proxy groups defined in a subscription can move with the configuration; the last selected proxy, system proxy toggle, and service permissions may be stored locally. Before switching clients, note any DNS settings, rule extensions, and app exclusions you depend on, then restore them one by one.
Choose a client for your setup
- Need iPhone and desktop support: Start with Clash Plus and verify subscription import, proxy connections, and VPN permissions on iOS. If you also need advanced overrides on desktop, choose a separate desktop client; there's no need to use the same app on both.
- Frequently edit rules on Windows or macOS: Start with Clash Verge Rev. Test extension configuration, rule matching, and whether changes survive a refresh using your actual subscription. Test TUN only if the apps you use need it.
- Need both Android and Linux: Start by checking the FlClash releases for your platforms. Test mobile traffic interception, desktop rule logs, and whether the core supports your subscription on each platform before deciding whether to migrate both.
If you only need browser access and your current client reliably refreshes subscriptions, switches proxies, and restores the system proxy, there may be no reason to switch just for more toggles. If you do need to move, keep your old configuration and don't retire the old client until the new one passes three checks: subscription refresh, rule matching, and connectivity from the apps you need.