Clients / Platforms & Configuration

Clash ClientComparison Guide

Start with your operating system, then check subscription compatibility. Clash Plus is a good starting point for beginners. Choose Clash Verge Rev for desktop configuration management, or FlClash for a similar experience across Android and desktop.

Download Clash View the setup guide

A client loads your configuration and routes traffic; it does not include a usable subscription. Similar-looking interfaces do not guarantee the same core, permissions, or config format. Save your original configuration before switching clients.

Quick pick / Clash Plus

Start with your operating system

Top pick: Clash Plus

If you just need to install a client, import a subscription, pick a node, and connect, start with Clash Plus. It’s listed first in our Windows, macOS, Android, and iOS download sections to make it easy to find the right version for your device. Official site: clashplus.io. Permissions and features can vary by operating system, so don’t assume desktop settings work the same way on a phone.

On Linux, start with Clash Verge Rev, then compare it with FlClash. Android users who often adjust per-app routing can also consider Clash Meta for Android. Surfboard follows a different configuration approach, so check that your provider supports its format before installing it.

Browse clients and setup requirements by operating system →

Platform, Core & Feature Comparison

Platforms shown reflect the download options listed here, not every release the projects have ever offered. Scroll horizontally to view the table. Ease of use reflects the steps needed to import a config and connect for the first time—not performance.

Eight clients compared by platform, core, maintenance, ease of use, key features, and ideal users
Client	Platforms listed here	Core	Maintenance	Ease of use	Key features and workflow	Best for
Clash Plus	Windows、macOS、Android、iOS	Varies by platform and implementation	Actively maintained	Easy	Import a config, choose a policy, and connect	Beginners and multi-device users
Clash Verge Rev	Windows、macOS、Linux	mihomo, from the Meta lineage	Actively maintained	Moderate	Subscription management, system proxy, TUN, and config merging	Users who want finer control over desktop networking
FlClash	Windows、macOS、Android、Linux	mihomo	Actively maintained	Easy to moderate	Cross-platform interface, policy group management, and connection monitoring	People using both Android and desktop
Clash Nyanpasu	Windows	Supports core options including mihomo, depending on the release	Actively maintained	Moderate to advanced	Desktop config management, core options, and interface customization	Users familiar with YAML and desktop proxies
Clash for Windows	Windows, archived	Original Clash / Clash Premium lineage	No longer maintained	Easy for existing users; not recommended for beginners	Legacy Profiles, Proxies, and system proxy workflow	Migrating older setups and following legacy guides
Clash Meta for Android	Android	Clash.Meta / mihomo lineage	Check recent project announcements	Moderate	VPN routing, per-app access controls, and config overrides	Users who need per-app routing on Android
Surfboard	Android	Independent implementation; not a Clash core	Check recent project announcements	Depends on the configuration source	Its own supported config format and Android VPN routing	Android users with a compatible config
ClashX Meta	macOS, archived	Clash.Meta lineage	No longer maintained	Easy for existing users	Menu bar policy switching and system proxy	Reference for migrating older macOS setups

Eight Clash Clients Reviewed

Start with the section for your device. This guide compares configuration workflows and limitations—not interface-driven speed claims or core names in isolation.

Clash Plus: Best for a First Install

Windows / macOS / Android / iOS

Clash Plus is a solid starting point for your first install. Download the version for your device, import the config from your provider, select it, then connect. If you use multiple devices, sticking with one client name makes it easier to find relevant guides and avoid mixing instructions with screenshots from other apps.

Keep in mind that the same client may use different cores and offer different settings on different operating systems. Check platform-specific instructions for TUN, per-app routing, and background operation. Get a basic connection working first, then enable advanced settings one at a time to make troubleshooting easier.

View Clash Plus downloads by platform →

Clash Verge Rev: Desktop Config Management

Windows / macOS / Linux · mihomo

Clash Verge Rev suits users who rely on a proxy as part of their desktop workflow. Subscriptions, policy groups, connection details, and traffic-routing options are managed in one interface, making it easier to inspect how a config behaves. For regular browser use, start with the system proxy. Consider TUN only if an app ignores the system proxy.

Its flexibility also means you need to understand how the configuration layers fit together. Subscription content, client-side merge rules, and system permissions are separate things. Before making changes, check whether a subscription update could overwrite them. If TUN fails to start, check permissions and logs before assuming the node is unavailable.

Browse desktop client downloads →

FlClash: A Consistent Workflow Across Android and Desktop

Android / Windows / macOS / Linux · mihomo

FlClash works well for people who switch between phone and computer. Its similar interface makes it easier to find configs and policy settings on both, while its mihomo lineage helps with modern Clash configurations. But a similar cross-platform interface does not mean configs sync automatically or system permissions work the same way.

On Android, the first launch usually requires approval for system VPN access. On desktop, learn the difference between the system proxy and TUN. If you copy a config to another device, check local file paths, listen addresses, and ports so you don’t carry over settings that only work on the original device.

View FlClash for Android →

Clash Nyanpasu: Advanced Desktop Workflow

Windows build listed here

Clash Nyanpasu is better suited to users who already understand subscriptions, policy groups, and config merging. It offers desktop config management and core-related options for users who want to organize their proxy workflow their own way. We list a Windows download here; that does not imply the project releases builds for other systems.

Before choosing it, check which core is included in your build and which fields your subscription requires. Switching cores is not a universal fix: if a config uses unsupported features, adjust its format or choose a compatible core before testing the connection again.

Browse Windows clients →

Clash for Windows: Archive and Migration

Windows · No longer maintained

Clash for Windows still appears in many older guides, and users may recognize pages such as Profiles, Proxies, and General. It is no longer maintained, so new users shouldn’t start with it just because a guide’s screenshots look familiar. The original Clash and Clash Premium lineages are also not interchangeable with the current feature set of mihomo.

If you’re migrating an existing setup, keep your subscription URL, essential local rules, and policy group choices, then recreate the configuration in your new client. Don’t copy the entire application folder. If modern protocols or config fields aren’t recognized, switch to a compatible client instead of repeatedly importing the same file.

View Windows setup and migration instructions →

Clash Meta for Android: Per-App Routing

Android · Meta / mihomo lineage

Clash Meta for Android is often shortened to CMFA. It builds on the Clash for Android workflow and suits users who want direct control over Android VPN routing, per-app access, and config overrides. After importing a subscription, select the config and return to the home screen to connect. An import success message alone doesn’t mean traffic is being routed.

Per-app access controls decide which apps are routed through the proxy; rule mode decides where those connections go. They serve different purposes. For reliable background connections, check your system’s battery restrictions too. A client’s Meta name doesn’t guarantee every build includes the latest features, so check the release notes for its actual support and maintenance status.

View Android routing and permissions guide →

Surfboard: Check the Config Format First

Android · Independent implementation

Surfboard may be on your shortlist of Android proxy clients, but it isn’t Clash with a different interface. It has its own implementation, so check its config syntax, rules, and protocol support separately. If your only subscription is in Clash YAML format, don’t assume you can simply paste the link and connect.

Surfboard is a better fit when your provider confirms the config is compatible or you’re already familiar with its format. Before converting a config, check whether node types, policy groups, and rules will retain their intended behavior. Never paste a private subscription URL into an unknown conversion site. Once you’ve confirmed the format, grant Android VPN access and test the connection.

View Android config options and downloads →

ClashX Meta: Legacy macOS Menu Bar Workflow

macOS · No longer maintained

ClashX Meta is a useful reference for the classic macOS menu bar workflow: switch policies, choose a config, and set the system proxy from the menu. It is no longer maintained, and a simple menu doesn’t mean it supports newer systems and protocols. New users should consider Clash Plus, Clash Verge Rev, or FlClash instead.

If you’re keeping an older setup, first check that the system version and chip architecture are compatible, then confirm your config is supported. After migrating to another client, disable the old client’s system proxy and auto-start options. Otherwise, both apps may try to change proxy settings, causing intermittent connections or leaving you offline after closing an app.

Browse current macOS client options →

Choose by Use Case

Four Checks Before Switching Clients

Keep your config source and custom rules

Save your original subscription URL, local config files, and any rules you added yourself. Subscription URLs may contain private access credentials, so don’t include them in public screenshots. Import the original config into the new client first, then reapply local changes one at a time to make errors easier to track down.

Check protocol and syntax compatibility

Meta is the name of a core branch, and mihomo continues that lineage. Original Clash, Premium, and independent implementations are not interchangeable. Successfully parsing a file is only the first step—also check that nodes, policy groups, and rules work as expected.

Use only one traffic-routing entry point at a time

Stop the old client before starting the new one. On desktop, check whether the system proxy still points to the old port. On Android, check whether another app is already using the VPN. TUN, system proxy, and LAN sharing are separate features; you don’t need to enable all of them.

Test connectivity and routing separately

First confirm your regular internet connection works, then check that a node connects, and finally test apps that should use the proxy and apps that should connect directly. A successful speed test doesn’t prove every app is routed. If something goes wrong, check connection logs, per-app access controls, and DNS settings one at a time.

View setup, routing, and config guides for all platforms →

Frequently Asked Questions

Will switching clients make the same subscription faster?

Not necessarily. Node routes, your current network, protocol support, and DNS all affect connectivity. For a fair comparison, use the same node, config, and test conditions, and first confirm both clients are routing the same traffic. A newer interface or a different name doesn’t prove better performance.

System proxy or TUN: which should beginners use?

On desktop, start with the system proxy and test in a browser; it’s easier to check how traffic is routed. If an app ignores the system proxy, consider TUN and confirm the required service permissions. Android usually routes traffic through the system VPN, so the desktop choices don’t apply directly.

What’s the best Clash for Windows alternative?

Start with Clash Plus. If you want desktop-focused subscription management, system proxy, and TUN controls, compare it with Clash Verge Rev. FlClash is a good fit if you use both Android and a computer. Keep your subscription and local rules when migrating; don’t overwrite the new app with the old client’s entire config folder.

Can I use the same subscription on my phone and computer?

That depends on your provider’s device limits and supported config formats. Two clients supporting the same YAML format doesn’t mean your provider allows simultaneous connections, or that local paths and routing settings can be shared. Check the subscription’s usage limits, then import it on each device. Policy selections may not sync automatically.

Should I download the Mihomo core if I’m not familiar with config files?

Usually not. Core packages are better suited to servers, routers, or users who manage processes themselves; they also require setting up config paths, services, and traffic routing. For a regular phone or computer, use a graphical client. Follow the quick start guide to import a config and connect.