Check your operating system and configuration format first, then compare cores and management features. For a fresh install, start with Clash Plus. For desktop rule management or Linux, compare the relevant alternatives.
Platforms listed here reflect the download options on this site; they do not claim to cover every platform supported by each project. Maintenance status describes the project, not whether an installer has been tested on your system.
Swipe horizontally to view the table on narrow screens. Ease of use reflects the effort involved in importing a config, routing system traffic, and managing settings day to day—not performance.
Choosing a client: check platform support, then configuration compatibility and management needs
Familiar to existing users; not recommended for new installs
Menu bar controls and legacy config management; suited to reviewing existing setups during migration
CLIENT NOTES
Client-by-client reviews
Start with what each client is designed for, then review configuration and migration details. The key questions are whether it can manage your subscription and how much setup it requires.
Clash Plus: Best for first-time setup and multiple devices
Top pick
If you don’t already have a desktop workflow, start with Clash Plus. This site provides download options for Windows, macOS, Android, and iOS, making it easy to set up each device separately. It’s recommended for its straightforward onboarding—not because every platform has the same underlying implementation. Linux users should compare Clash Verge Rev and FlClash directly.
Show configuration and usage notes
After installing, import a compatible config from your provider and confirm it’s enabled. Then check your proxy groups and connection settings. If the config uses core-specific fields, consult the client documentation for that platform; don’t assume every mihomo option is supported based on the app’s name. System proxy settings on desktop and VPN permissions on mobile are separate, and connection status isn’t shared between devices.
For multiple devices, save the subscription link supported by each platform and check your provider’s simultaneous connection limits. On iOS, use the download page to open the App Store. See product information at clashplus.io. If you rely on complex rules or specific override features, check whether the client preserves those settings.
Clash Verge Rev: Desktop configuration and rule management
Clash Verge Rev uses the mihomo core and helps manage subscriptions, proxy groups, and traffic routing on Windows, macOS, and Linux desktops. It suits users who regularly refine rules: remote subscriptions provide nodes and base configuration, while local overrides handle custom changes. If you just need to import and connect, start with the default configuration.
Show override and migration notes
Updating a subscription fetches its remote content again, so direct edits to the subscription file may be lost. Use the client’s override features for persistent rules, DNS changes, or proxy group selections, then confirm the resulting configuration is active. When troubleshooting, check both the source config and the merged result—you may have changed one file while the core is reading another.
When migrating from an older client, import the original subscription first instead of moving every script and network setting at once. Verify the system proxy, then test TUN, rule sets, and startup behavior. Linux users should choose the installer for their distribution; a desktop client is not the same as a server deployment.
FlClash uses the mihomo core, with downloads for Windows, macOS, Android, and Linux on this site. It suits users who want a similar approach to configuration management across devices. Familiar interfaces and core behavior can make proxy groups easier to learn, but permissions, background operation, and traffic routing vary by platform—don’t copy desktop settings straight to mobile.
Show cross-device usage notes
You can import the same subscription on multiple devices, but configs containing local paths, listening addresses, or system interface names usually need adjustments. On desktop, check system proxy settings and service permissions; on Android, check VPN permissions, battery optimization, and background activity. Before choosing, confirm the installer architecture and system requirements.
When migrating from another mihomo client, move the subscription and essential rules first; there’s no need to copy every app setting. Similar feature names don’t guarantee the same merge order, especially for DNS overrides and TUN options. After importing, check connection logs to confirm the expected proxy group is being used before restoring advanced settings.
Clash Nyanpasu suits users who care about organizing desktop configurations and are comfortable checking core and merge settings. This page lists a Windows download from our catalog; that does not mean the project supports only Windows. Choose it based on whether its configuration workflow fits your habits—not assumptions about node speed or system resource use based on its interface.
Show core selection notes
Before importing a configuration, check which core is actually running. The client and core names are not interchangeable. Check the installed package for available cores, whether switching is supported, and which core is enabled by default. If a subscription requires mihomo, don’t try to fix import errors by using another core that lacks the required fields.
If you have complex rules, test them in a separate config first and confirm the merge order and local changes are preserved. After switching cores, recheck DNS, proxy protocols, and proxy group behavior; a working interface isn’t enough. Beginners looking to avoid these extra checks can start with Clash Plus.
Clash for Windows: Archived client and legacy configs
No longer maintained
Clash for Windows, or CFW, is the desktop client found in many older tutorials. Archived builds can be useful for reviewing legacy configurations, but they aren’t recommended for new installs. The original Clash-family core differs from current mihomo; if an older build can parse a config, that doesn’t mean it supports newer protocols or fields added by your provider.
Show archived client migration notes
Before migrating, record your subscription, any essential custom rules, and the system proxy port. Quit the old client and confirm the system proxy has been restored before starting the new one. This prevents conflicts between listening ports, proxy switches, or virtual adapters. Once the new client is working, migrate local settings one at a time instead of overwriting its application data directory.
An archived app launching successfully doesn’t make it a good long-term choice. If you run into compatibility, certificate, or protocol issues on a newer system, switch to an actively maintained client rather than hunting for an even older installer. The download page retains archived builds for reference; their status doesn’t change just because they’re still available.
Clash Meta for Android: Android configuration management
Clash Meta for Android, or CMFA, is an Android client for Clash configurations that uses a Meta/mihomo-family core. It’s worth considering if you already have a compatible YAML subscription and want to manage proxy groups and connection details on your phone. It routes traffic through Android’s VPN interface, which works differently from a desktop system proxy.
Show mobile permissions and background activity notes
The first connection requires Android VPN permission. If another VPN app is running, stop it first to avoid conflicts. If it connects in the foreground but disconnects when the screen locks, check battery optimization, background restrictions, and system keep-alive settings before changing DNS. Settings vary by device manufacturer, so follow the options on your phone.
Choose the package architecture that matches your device’s processor; package size alone isn’t a reliable guide. Older configs may contain ports or routing settings that no longer suit your setup, so verify them after importing. Speed tests only show response times to specific test targets; check that the apps you actually use work too.
Surfboard is an Android proxy client, but it doesn’t use the Clash, Meta, or mihomo core. Its presence in the same download catalog doesn’t mean it can read every Clash config. If you already have a config that Surfboard supports and know its rule syntax, it may fit your workflow. With only a Clash YAML subscription, check whether your provider can supply a compatible format first.
Show compatibility notes
Converting a config means more than changing its file extension. Proxy protocols, proxy group types, DNS behavior, and rule syntax may all differ, and conversion tools may not preserve every detail. After importing, verify the nodes, routing rules, and default policy. If key fields were ignored, a successful connection may still route traffic differently than expected.
Using Android’s VPN interface doesn’t mean clients handle background activity and per-app routing the same way. If your Surfboard setup works well, there’s no need to switch just for a consistent name. To continue using the mihomo configuration ecosystem, compare actual compatibility in Clash Plus, CMFA, and FlClash.
ClashX Meta is a macOS menu bar client using a Meta-family core, suited to reviewing configurations and migrating existing setups. It’s no longer maintained, so don’t choose it for a new install just because an old tutorial recommends it. Check the installer and test the results to confirm compatibility with your current macOS permissions, traffic routing, and processor architecture.
Show macOS migration notes
Before migrating, save your subscription and local rules, and note your current system proxy settings. Quit the menu bar client and confirm the proxy is actually off before installing a replacement. Choose the Apple Silicon or Intel installer to match your Mac; launching through a compatibility layer doesn’t make an Intel build the best fit for your machine.
For an alternative, start with Clash Plus. If you need fuller desktop configuration management, compare Clash Verge Rev and FlClash. After migrating, test your browser, terminal, and apps that rely on traffic routing separately—a connected menu bar icon isn’t proof that everything works. For related issues, see our Troubleshooting page.
Don’t compare every feature at once. Start with a client that handles your main task, then verify its configuration support and traffic routing.
DECISION / VALIDATION
Recommendation and pre-install checks
Clash Plus is the default recommendation for users who haven’t built a complex configuration workflow and want to get connected. For desktop rule management, compare Clash Verge Rev; for desktop and Android, compare FlClash. If you already have an Android Clash config, CMFA is another option. Check format compatibility before choosing Surfboard. CFW and ClashX Meta are mainly for reference and migration from archived setups.
Choose based on platform, configuration compatibility, and how you need to route traffic—not the client’s name. The original Clash, Meta, and mihomo aren’t interchangeable labels. A graphical client is more than a skin over the core: it also determines permission handling, config merging, and system integration. Understanding these differences helps explain why the same nodes can behave differently after migration.
Check platform and architecture. Confirm your system meets the requirements and choose the right build for Apple Silicon, Intel, or your Android architecture. The download page lists options by platform.
Check the configuration source. Make sure you have a subscription format the client supports. Don’t use a provider dashboard webpage as a subscription URL, and don’t share links containing personal parameters.
Check how traffic is routed. Test the system proxy with a browser first, then consider TUN for other apps. On mobile, check VPN permissions. Quit the old client before switching.
Check that it works. Test the apps you use and review connection logs and matched proxy groups. Troubleshoot node timeouts, DNS failures, and inactive system proxy settings separately; don’t switch clients to hide a configuration problem.