Clash Plus
Top pickOur top pick for a new Windows installation, with a GUI for managing subscriptions and proxy settings. After installation, check that your configuration has loaded before choosing a routing mode. Official site: clashplus.io.
Client installers · Choose by system and architecture
Download Clash
Download Clash
Platforms and installers
Choose separately for desktop, mobile and server use. Check the operating system and CPU architecture first, then compare subscription management, routing rules and TUN options.
Choose a client by platform
Clients for each platform are listed in a consistent order. Read the architecture notes before downloading. Archived clients are listed for older setups; for new installations, choose a maintained option.
Windows installers
This section provides x64 installers for GUI clients. Find your system type under “Settings → System → About.” For a first install, import your subscription without elevated permissions. If you need TUN, install the service or grant permissions as prompted by the client.
Clash Verge Rev
For users who want the mihomo core and desktop configuration management. Before enabling service mode or TUN, quit any other client currently managing network traffic. Back up subscriptions and overrides before upgrading to avoid overwriting local changes.
FlClash
For users who want a similar interface across desktop and mobile. After importing a configuration, check that proxy groups have selectable options before enabling the system proxy. A consistent interface does not mean every platform has the same system-level permissions.
Clash Nyanpasu
An alternative interface for managing desktop configurations. When migrating, check the GUI settings and core configuration separately, especially listening ports, local file paths and rule overrides. Don’t copy another client’s entire data directory as-is.
Clash for Windows
DiscontinuedKept for reproducing older configurations and reference during migration. This project is no longer maintained and is not recommended as the default for new setups. For newer protocols or rule fields, check core compatibility before migrating to a client such as Clash Plus.
Windows requirements and checks
| Item | What to check |
|---|---|
| Operating system | Use a 64-bit Windows version that still receives security updates. Check the installer for the specific minimum version required. |
| Processor | This section mainly offers x64 packages. On Windows ARM devices, check whether the system supports x64 apps. |
| Traffic routing | System proxy and TUN are configured separately. Installing the service and routing traffic through a virtual adapter may require administrator permissions. |
If installation succeeds but your browser isn’t using the proxy, check the system proxy setting and listening port first. Avoid running two clients that compete for the same port.
macOS installers
Check your chip under “About This Mac.” Clash Plus offers separate Apple Silicon and Intel builds. The two architecture links for other clients in this download list currently point to the same x64 package. On Apple Silicon, check Rosetta and client compatibility; the link label does not guarantee a native ARM build.
Clash Plus
Top pickTop pick for macOS. Choose the DMG that matches your chip, open it and follow the installer prompts to move the app into place, then launch it from Applications. Official site: clashplus.io. Grant permissions for network routing features after the first launch, as needed.
Clash Verge Rev
For users who need desktop subscription management and mihomo configuration. The Apple Silicon compatibility link does not currently point to a separate ARM build. If the service fails to start after installation, check system permissions and existing proxy processes, then review the logs.
FlClash
For users who want a similar configuration workflow across devices. The current file is named amd64; check compatibility before installing on Apple Silicon. Subscriptions may be reused, but review local paths, ports and permissions on this Mac.
ClashX Meta
DiscontinuedArchived downloads are kept for older setups, migration and reference. Both links currently point to the same x86_64 file. The project is no longer maintained; for new installations, consider another client instead of relying on archived builds to support newer fields.
macOS requirements and checks
| Item | What to check |
|---|---|
| Chip | For Apple M-series Macs, choose native ARM64 where available. For Intel processors, choose x64 or amd64. |
| macOS version | Minimum requirements vary by client; check the installer details. Back up your configuration before updating macOS. |
| Permissions | Grant system proxy or service permissions as needed. If macOS blocks startup, check the specific reason shown by the system. |
If the installer’s architecture label doesn’t match what you expect, pause and check the filename. Don’t disable system-wide security protections just to run an app.
Android installers
Most recent phones use ARM64. Older devices may need a 32-bit ARM build; check your device’s hardware information if you’re unsure. The first time you connect, Android will request VPN permission. This system prompt enables local traffic routing; it does not provide a working proxy node.
Clash Plus
Top pickTop pick for Android. After installation, import a subscription, select a proxy group, then connect and approve the system permission prompt. Official site: clashplus.io. For extended background use, check your device’s battery and background activity settings.
Clash Meta for Android
For Android users familiar with Clash configuration files. Choose the package for your device architecture where possible; use the universal build when you need broader device support. Back up local settings before updating. After restoring, check that rule providers loaded successfully—not just that the subscription name appears.
FlClash
Offers a configuration workflow similar to the desktop version. If the connection drops when the screen turns off, check background restrictions and Android’s VPN status before checking the node. Switching mobile networks may trigger a reconnect; a single timeout doesn’t mean the configuration is broken.
Surfboard
For Android users with configurations compatible with Surge-style syntax. It is not a direct replacement for importing Clash YAML. Before downloading, confirm that your configuration provider supports the format to avoid parsing failures from simply changing the file extension.
Android requirements and checks
| Item | What to check |
|---|---|
| Architecture | arm64-v8a is 64-bit ARM; armeabi-v7a is 32-bit ARM. Make sure your Android version supports the package too. |
| Install permissions | Allow installation only for the app you’re actually using to download or open the APK. Revoke permission afterward if you no longer need it. |
| VPN and background activity | Check whether another VPN app is using the connection. Background restrictions may stop the connection when the screen turns off. |
If Android says “App not installed,” check the architecture, available storage and signature of any existing app. If an update fails, don’t delete old data right away; export any configuration you need to keep first.
iOS client
Install Clash Plus from the App Store. Check the store listing for current compatibility, availability and pricing. Prepare a valid configuration after installation, then add the VPN configuration when prompted by iOS. Having the app icon does not mean network routing is active.
Clash Plus
Top pickFor managing proxy configurations on iPhone and iPad. After importing a subscription, check the current mode, proxy groups and system connection status. If the connection has issues, check whether another VPN configuration is active before reviewing the subscription and logs.
iOS requirements and checks
| Item | What to check |
|---|---|
| Compatibility | Check the Compatibility section of the App Store listing and confirm your device’s iOS version before installing. |
| Install and update | Use the App Store link above to install and update the app. Review the developer’s notes and current listing details. |
| Connection permissions | Add the VPN configuration when prompted by iOS. After importing a valid subscription, check your rules and policy selection. |
You can reuse a compatible subscription across devices, but system permissions and local settings must be configured on each one. Check the connection again after switching between Wi-Fi and cellular.
Linux desktop installers
Choose a package format for your distribution, then check your CPU architecture. Debian and Ubuntu typically use DEB; Fedora typically uses RPM. This section provides amd64 / x86_64 GUI clients. For headless servers and other architectures, see the Mihomo core section.
Clash Verge Rev
RecommendedRecommended for Linux desktops. Installing through your distribution’s package manager can also resolve dependencies. After launch, check whether your desktop environment honors the system proxy settings; command-line tools usually need proxy environment variables configured separately.
FlClash
For Debian-based desktop users who want a consistent configuration workflow across devices. First confirm that the GUI launches, then configure TUN permissions. On a headless remote system, use the standalone core instead of installing a desktop environment.
Linux requirements and checks
| Item | What to check |
|---|---|
| Architecture | Check the architecture with uname -m; x86_64 generally uses the amd64 package. |
| Runtime environment | GUI clients require a compatible desktop environment and runtime libraries. Check package manager output for dependency requirements. |
| Permissions and routing | TUN uses a virtual network interface and requires routing permissions. Before making changes remotely, keep a backup management connection and recovery path. |
Don’t mix DEB and RPM installation methods. If you hit a dependency error, read the package manager’s message instead of repeatedly reinstalling over the same package. The system proxy also won’t automatically cover every terminal app.
Standalone Mihomo core
For users managing servers, routers or self-hosted services. For everyday desktop and mobile use, choose a GUI client above. The core has no subscription management interface, so you’ll need to prepare the YAML configuration, data directory, process management and log retention yourself.
| Operating system | Architecture | Formats and downloads |
|---|---|---|
| Windows | AMD64 / x64 | Download AMD64 ZIP |
| Windows | ARM64 | Download ARM64 ZIP |
| macOS | Intel / AMD64 | Download Intel GZ |
| macOS | Apple Silicon / ARM64 | Download ARM64 GZ |
| Linux | AMD64 | |
| Linux | ARM64 | Download ARM64 GZ |
| Linux | ARMv7 | Download ARMv7 GZ |
| Linux | MIPS softfloat | Download MIPS GZ |
Core deployment requirements
| Item | Deployment checks |
|---|---|
| Configuration | Prepare a compatible YAML file. Check proxy group references, rule order and DNS settings, then validate the configuration syntax before starting the core. |
| Service | Set a clear working directory and service account. Ensure the configuration and rule data are readable, and prevent multiple processes from competing for the same port. |
| Management API | Restrict the API’s listening address and access permissions. Don’t expose a local management port directly to an untrusted network. |
DEB fits package manager workflows; GZ usually contains a compressed executable. Before upgrading, note the current service arguments and file locations. After replacing the core, check the logs and confirm that rules and DNS behave as expected.
Installers, configuration and proxy service
Three separate layers
Downloading the client only takes care of installation. Proxy traffic also depends on the configuration format, service status and whether the app is routed through the proxy.
The client manages settings
GUI clients provide controls for importing subscriptions, selecting proxy groups and configuring system settings. The GUI and core may have different versions, so the client name alone doesn’t tell you which protocols are supported. For a newer protocol or specific DNS features, check the current core capabilities and configuration parsing results.
Configuration controls routing
Rules in YAML are matched in order, and traffic is sent to the policy for the first matching rule. A subscription update may replace the remote configuration, so save local overrides separately. During migration, verify policy names and rule references, then check the MATCH fallback. This helps avoid mistaking a network issue for an installation failure.
Connections require a working service
Clients don’t include a ready-to-use proxy service. Import a valid configuration, select an available policy and test the connection. Node latency tests are only a snapshot of your current network; a single result can’t guarantee throughput, stability or connectivity in every app.
Post-install checks
Change one thing at a time. Validate the configuration first, enable traffic routing next, then set up startup and background behavior.
-
Back up settings and quit the old process
Note the old client’s subscription, ports and local overrides. Turn off its system proxy and TUN, then quit the process; closing the window alone may leave a background service running. Once network access is back to a known state, start the new client. Avoid running two programs that change system settings at the same time.
-
Import and verify the configuration
Import a valid subscription URL or local YAML file. Wait for it to load, then check that proxy groups and rules appear. If parsing fails, inspect the specific field. Subscription URLs may contain credentials; don’t include the full URL in public screenshots, support requests or shared logs.
-
Choose a mode and test the connection
Rule mode is usually a good starting point for everyday use. Enable the system proxy, connect from the target app, then check the matched rule and outbound policy in the logs. If an app ignores system proxy settings, consider TUN. Don’t change DNS, routes and nodes all at once, or it’ll be harder to isolate the issue.
-
Configure startup and recovery
Once the configuration is stable, enable Clash at startup or allow it to run in the background. After restarting, check that the proxy setting and service status match. Keep a way to disable the proxy and restore the original routes, especially on remote servers. See the Clash setup guide for installation help, and protocol details for differences between protocols and cores.
Download and installation FAQs
These answers cover installer selection and first launch. For rule matching, DNS and TUN conflicts, see the FAQ.
Which Clash client should I download first?
For Windows, macOS, Android and iOS, start with Clash Plus; for Linux, start with Clash Verge Rev. Choose an installer by operating system and CPU architecture, then check subscription format and required features. Clients do not include a ready-to-use proxy service.
What’s the difference between ARM64, x64 and universal builds?
ARM64 and x64 use different CPU instruction sets; amd64 generally means x64. On Android, armeabi-v7a is 32-bit ARM, while universal builds typically support multiple architectures. Check your device’s system information rather than relying on its name to determine compatibility.
Why can’t I access a website after downloading the client?
The installer only provides the client. You also need to import a valid configuration, select an available proxy group, and enable the system proxy or TUN if needed. Then check the connection log for matched rules and outbound policies. DNS issues, node status or an app bypassing the proxy can also prevent pages from loading.
Can I migrate my old client configuration as-is?
Back up your existing configuration and local overrides first, then import the subscription or YAML into the new client. Compatibility for protocols, rule fields and DNS settings depends on the core and its version. Check proxy groups, rule providers and local paths individually; a successful import does not guarantee that every feature is compatible.
Should I download a GUI client or the Mihomo core?
Choose a GUI client for everyday desktop and mobile use, with subscription, proxy group and system proxy management. The Mihomo core suits servers, routers and self-managed services, but you’ll need to prepare the configuration, startup method, permissions and log management yourself. The standalone core does not include a GUI.
Should I quit my old client before installing a new one?
Turn off the old client’s system proxy and TUN, then quit the process to avoid conflicts involving listening ports, virtual adapters and route management. Once the new client is working, configure it to start at boot. Keep a backup of the original configuration so you can restore it if needed.