Clash Plus: A simple start across devices
Clash Plus is our top pick for users who want to import a subscription, choose a policy, and connect before exploring rules. It is available for Windows, macOS, Android, and iOS, so you can start with one product on your computer and phone without learning different interfaces at once.
Cross-platform availability does not mean every feature works the same way. System proxies on desktop, VPN permissions on mobile, and background behavior vary by operating system. Support for a YAML setting on one platform does not guarantee support on another. Check platform-specific documentation before migrating configurations that use complex scripts, custom DNS, or less common protocols.
If you want a reliable everyday setup rather than a core to experiment with, follow the Quick Start Guide to get connected. Visit the official site at clashplus.io for product details, or find installers in the Download Center.
Clash Verge Rev: Desktop configuration and overrides
Clash Verge Rev is a desktop client powered by mihomo, suited to users who manage multiple subscriptions, keep local overrides, or configure TUN. Rather than focusing only on a connect toggle, it lets you manage subscription content, client settings, and local changes as separate layers.
Basic imports and policy selection are straightforward. Advanced use requires knowing where the active configuration comes from. Subscription updates may rebuild the original file, so direct edits to generated content may not persist. Check the scope of your overrides, inspect the live configuration and logs, then troubleshoot rules or DNS.
TUN involves services, routing, and system permissions; it is not a universal speed boost. Consider enabling it only when the system proxy cannot cover a target app or you need more complete traffic routing. Downloads: Windows, macOS, and Linux.
FlClash: A familiar workflow across desktop and Android
FlClash uses mihomo and is available here for desktop platforms and Android. If you switch often between a computer and phone, its similar interface can make configurations, policies, and connection status easier to recognize. It does not automatically sync subscriptions or policy selections between devices.
For multi-device use, share reusable subscription sources and rule logic—not entire configurations containing device-specific paths, listen addresses, or interface names. Desktop permissions differ from Android VPN access, and background restrictions need to be configured separately. If a setup fails only on your phone, check its permissions and logs before changing settings shared by all devices.
FlClash suits users who want a familiar workflow with mihomo configuration support. When installing, choose the correct processor architecture and do not confuse desktop packages with Android packages. Find the right option under platform downloads in the Download Center.
Clash Nyanpasu: A configurable desktop workflow
Clash Nyanpasu suits users who want to understand how desktop configuration processing works. We offer a Windows download; this guide does not cover builds for other platforms. Its interface and configuration management follow their own conventions, so do not assume that every button is in the same place as in another client's tutorials.
When choosing a core, keep the client name separate from the core actually in use. Whether a setting works or a protocol is supported depends on the selected core and the bundled build—not simply on whether the client is actively maintained. Before migrating, import a basic configuration and check proxy groups, DNS, and rule matching, then restore existing changes one at a time.
If you just want to import a configuration and get connected, consider Clash Plus first. To organize a desktop configuration workflow, compare Nyanpasu and Verge Rev. Download Windows clients.
Clash for Windows: Archived setups and migration
Clash for Windows, often abbreviated to CFW, appears in many older tutorials. Later builds commonly used Clash Premium, not current mihomo. Familiar steps for Profiles, Proxies, or the system proxy are not, by themselves, a reason to keep using archived software.
Archived clients no longer receive ongoing updates for new operating systems and protocols. An old configuration may still run, but that does not mean newer settings will work—or that every connection issue is caused by your subscription. For a new installation, choose an actively maintained client. To reproduce an existing setup, use the archived download option and keep a record of the original configuration.
When switching from CFW to Clash Plus, Verge Rev, or FlClash, first save your subscription sources and note any manual rules. Then disable the old client's system proxy and background services. Simply closing its window before launching the new client can leave ports occupied, proxy settings behind, or traffic routing in conflict—all of which make troubleshooting harder.
Clash Meta for Android: Fine-grained mobile traffic rules
Clash Meta for Android, often abbreviated to CMFA, uses a Meta/mihomo-family core. It suits users who want to inspect proxy groups, edit configurations, and manage app traffic on Android. Rather than copying a desktop system proxy toggle to a phone, it routes traffic through Android's VPN interface.
The first connection requires system permission. If another app is using the same VPN interface, you will usually need to choose between them. Per-app routing, bypass lists, and battery settings can also affect behavior. If the connection drops after the screen locks, check background restrictions and logs before assuming the node has failed.
CMFA is worth considering if you have a Clash YAML subscription and want to keep using Meta-family rules on Android. Actual field support depends on the core bundled with your download. Check the package type and architecture in the Android downloads.
Surfboard: Check the configuration format first
The key difference between Surfboard and the other clients listed here is that it is not a graphical interface for a Clash core. It has its own proxy implementation and uses Surge-style configuration. Even where node protocols overlap, configuration sections, policy syntax, and available features are not directly interchangeable.
If you already have a configuration adapted for Surfboard, you can evaluate it for everyday Android use. If you only have a Clash YAML link, Surfboard should not be the default next step. Conversion tools can change some formatting, but cannot add settings the target app does not support. Check node parameters, policy references, and rule order after conversion.
Surfboard is best for Android users who have a compatible configuration and understand the format differences—not every Clash beginner. If you want to keep using an existing YAML subscription, compare Clash Plus, CMFA, and FlClash first; they are generally more likely to preserve the configuration's meaning.
ClashX Meta: Archived macOS menu bar client
ClashX Meta uses a Meta-family core and runs from the macOS menu bar. It can help identify an existing installation, review legacy configurations, or plan a migration. A simpler menu does not mean it is more stable on every recent system.
The menu bar interface differs from a full management window in how it organizes tasks; it says nothing about core performance. Compatibility depends on processor architecture, macOS version, permissions, and the bundled core. For new installs, compare Clash Plus, Verge Rev, and FlClash. If you already use ClashX Meta, back up your subscription sources and local rules before migrating.
During migration, check for leftover startup items, system proxy settings, and background processes. Remove the old setup only after confirming that the new client routes the traffic you expect. This helps prevent confusing the behavior of two programs with the results of one configuration.
Choose a client by use case
Before switching clients
- Keep track of configuration sources. Note where subscription URLs are stored and how local changes are made. Keep sensitive links in a trusted environment. Do not rely only on temporary runtime files generated by the client.
- Check formats and fields. Distinguish Clash YAML from the format required by Surfboard, then verify protocols, proxy groups, DNS, and rule references. For core differences, see the Quick Reference and YAML Handbook.
- Stop the old traffic routing. Before exiting the old client, disable its system proxy or TUN and check for background services and startup items. On mobile, make sure another VPN app is not still using the interface.
- Start by verifying a basic connection. Confirm the configuration loads, policies can be selected, and logs show no persistent errors. Then restore overrides and per-app routing. Change one thing at a time.
- Keep a rollback option. Remove old files only after confirming that your usual apps and direct-connection rules work as expected. If problems persist, check the Help Center with details about your operating system, client, core, and error logs.
The right choice depends on your device and configuration needs. Beginners should start with Clash Plus; users who rely on desktop overrides or specific mihomo settings should compare the relevant clients. Keep CFW and ClashX Meta as references for legacy setups. Find installers, architecture details, and archived versions in the Download Center.