Clients for Windows, Mac, and mobile. Choose your operating system, then select a download.
Clash Plus is our first pick for Windows, macOS, Android, and iOS; for Linux, we recommend Clash Verge Rev. If you already have a preferred workflow, choose another client for the same platform. Import your own subscription or configuration after installation.
For desktop proxying, subscription management, and rule-based routing. The downloads below are for x64 devices. On Windows on ARM, first check compatibility with x64 apps and their drivers; an app launching successfully does not guarantee that TUN will work properly.
For first-time setup and everyday configuration
A good choice for managing subscriptions, proxy groups, and settings in one place. Import your configuration after installation, then enable the system proxy. If you need to route more apps, follow the guide to set up TUN separately rather than changing several network settings at once.
clashplus.io
Desktop subscriptions, rules, and overrides
For desktop users who want to keep subscription settings separate from local overrides. Before enabling service mode or TUN, review any permission prompts. Quit other proxy apps first to avoid system proxy or port conflicts.
View system proxy settings →
A familiar workflow across desktop and mobile
For users already using FlClash on mobile who want a similar setup on desktop. AMD64 and x64 refer to the same architecture here, regardless of processor brand. After importing a subscription, check that a proxy group is selected.
View subscription setup steps →
Desktop configuration and connection status
For users who prefer managing desktop proxy settings through a graphical interface. When migrating an existing setup, save your local rules and port settings, then restore them one at a time. Don’t overwrite the entire data folder with another client’s files.
Check for port conflicts →Reference for recreating or archiving a legacy setup
For reproducing an existing setup or migrating an old configuration only. The project is no longer maintained, and newer protocols, rule fields, or DNS options may not be recognized. For a new installation, choose one of the maintained clients above. This archived version is not recommended for long-term use.
View the post-migration setup guide →| Check | Requirements and notes |
|---|---|
| Operating system | Use a supported version of Windows 10 or 11 where possible. Check the installer prompt and the client’s release notes for the exact minimum version. |
| Processor | These are x64 installers and won’t work on 32-bit systems. Check compatibility separately for ARM devices. |
| Permissions and network | Standard proxy mode and TUN have different permission requirements. Follow prompts when installing a service or driver. On a work-managed device, check your organization’s policies first. |
Check About This Mac to identify your chip. For Apple Silicon, choose a native ARM64 build; for Intel, choose x64. Some download links currently provide x64 files, which are labeled on their cards. A selected architecture option does not guarantee the file uses that architecture.
Choose a native installer for your Mac’s chip
A good choice for setting up subscriptions and proxy settings on a Mac. Open the disk image, drag the app to Applications, and launch it from there. Then import your subscription. When prompted for network permissions, make sure the request is from the client you just installed.
clashplus.io
Subscription settings and local overrides
For Mac users who rely on configuration overrides. Both links currently point to the same x64 file. Apple Silicon users should check Rosetta compatibility; for a native ARM64 build, choose Clash Plus above.
View system proxy settings →
Keep your setup consistent across devices
For users running FlClash on both desktop and mobile. The Mac download listed here is AMD64 (x64); Apple Silicon users should check translation requirements before installing. You can reimport your subscription, but local overrides and app permissions must be set up separately.
View subscription setup steps →
Archived menu bar workflow
For recreating an existing menu bar workflow or using an old configuration. The project is no longer maintained, and all links currently provide x86_64 files. Check system compatibility before installing. If your configuration uses newer fields, migrate to a maintained client rather than repeatedly changing macOS security settings.
View compatibility troubleshooting →| Check | Requirements and notes |
|---|---|
| macOS version | Minimum macOS versions vary by client and build. Check the app’s compatibility notice, especially on older systems. |
| Chip architecture | M-series chips are Apple Silicon; choose ARM64 when available. Intel Macs use x64. Links to x64 builds are labeled. |
| Launch location | Move the app to Applications before launching it rather than running it from the disk image. Grant system proxy or network extension permissions only as needed. |
Most recent phones use ARM64; older devices may need ARMv7. If you’re unsure which architecture your device uses, try the universal build for Clash Meta for Android. The first connection requires VPN permission, and typically only one app can control the system VPN at a time.
Mobile subscriptions and proxy connections
For importing subscriptions and managing everyday connections on your phone. Grant install permission only to the browser or file manager you’re using to open the APK. After importing your configuration, select a proxy group and approve the system connection request.
clashplus.ioChoose an APK for your device’s architecture
For users with an existing Clash configuration who want to choose a build for their device’s architecture. The universal build is a convenient option if you’re unsure, but it’s usually larger. After importing a subscription, activate the configuration; seeing it in the list doesn’t mean proxying is enabled.
View import and activation steps →
A familiar interface on mobile and desktop
For users already running FlClash on desktop. Background behavior differs on mobile. If the connection drops when the screen locks, check battery optimization and background permissions before assuming the subscription or nodes are at fault.
View mobile troubleshooting →
Android client for compatible configuration formats
For users with a compatible configuration. Surfboard uses a different format from Clash YAML, so not all Clash configurations can be imported as-is. Check whether your subscription provider offers a compatible format before choosing this client.
Learn about subscription formats →| Check | Requirements and notes |
|---|---|
| System and architecture | Check that the client supports your version of Android. ARM64 and ARMv7 builds are not interchangeable; if you’re unsure, use a supported universal build. |
| Install permission | To install an APK, allow app installs from the source you’re using. If you get a parsing error, check that the file downloaded completely and is compatible with your system. |
| Connection permission | Approve the VPN request the first time you connect. Disconnect any other VPN app first. Background connections may be affected by system battery settings. |
Install Clash Plus from the App Store. Check the listed device compatibility and system requirements, then import your own subscription. The first time you connect, approve the system VPN configuration request.
Setup for iPhone and iPad
For managing subscriptions and rules on iPhone or iPad. Import your configuration first, then choose a proxy group. After allowing the VPN configuration, return to the app and check the connection status. If your device is managed by an organization, check its network policies first.
clashplus.io| Check | Requirements and notes |
|---|---|
| System compatibility | Check the App Store’s current compatibility listing for your device model and the minimum iOS version before installing. |
| Configuration source | Prepare a valid subscription or compatible configuration of your own. Installing the client and getting proxy service are separate steps. |
| VPN permission | Approve the request when prompted the first time you connect. Be aware of which app controls the connection when switching VPN apps. |
These AMD64 graphical clients are for desktop environments. Choose DEB for Debian, Ubuntu, and related distributions; choose RPM for distributions that use RPM packages. For headless servers and routers, see the Mihomo core section.
Linux desktop proxy and configuration management
For managing subscriptions and rules in one place on a Linux desktop. Install with your distribution’s package manager to handle dependencies. If the app opens but the system proxy isn’t working, check your desktop environment’s proxy settings and the app’s own proxy options.
View system proxy settings →
DEB installer for Debian-based desktops
For desktop users who want to keep their FlClash workflow. This AMD64 DEB package is not for ARM routers. If installation fails, check the package manager’s dependency messages instead of repeatedly rerunning the installer.
View installation and connection troubleshooting →| Check | Requirements and notes |
|---|---|
| Check your architecture | Run uname -m; x86_64 corresponds to the AMD64 desktop packages on this page. Do not install these files on ARM devices. |
| Distribution and dependencies | Choose DEB or RPM for your distribution. Check the package manager’s dependency requirements; the same file extension doesn’t guarantee full compatibility. |
| Runtime environment | A graphical desktop is required. TUN usually needs additional permissions. For server deployments, use the core with a standalone service configuration. |
For users managing servers, routers, and their own configurations. The core does not include a desktop subscription management interface. Before deploying, prepare a configuration file, runtime directory, and startup method. Most desktop and mobile users should choose a graphical client above.
| System | Architecture and format | Core downloads |
|---|---|---|
| Windows | AMD64 · ZIP | Download AMD64 ZIP |
| Windows | ARM64 · ZIP | Download ARM64 ZIP |
| macOS | Intel · GZ | Download Intel GZ |
| macOS | Apple Silicon · GZ | Download ARM64 GZ |
| Linux | AMD64 · DEB | Download AMD64 DEB |
| Linux | AMD64 · GZ | Download AMD64 GZ |
| Linux | ARM64 · GZ | Download ARM64 GZ |
| Linux | ARMv7 · GZ | Download ARMv7 GZ |
| Linux | MIPS-softfloat · GZ | Download MIPS GZ |
Extract ZIP and GZ files first. On Unix-like systems, make the file executable if needed. Install DEB packages with a compatible distribution’s package manager. Start the core in the foreground first and review any errors. Once the configuration loads successfully, set up a background service and startup behavior.
Don’t expose the external control interface directly to the public internet. To share access on a local network, first restrict the listening address and firewall rules, then configure client access. Troubleshoot port conflicts, DNS resolution, and permissions separately; see the port troubleshooting section for details.
Get one configuration working before changing advanced options. Downloading and installing are just the first steps; your connection also depends on your subscription, proxy group selection, and local network.
Paste the full URL into the client’s configuration or subscription page, or import a local file. Don’t use a regular webpage URL as a subscription link. After importing, check that proxy groups were created, then activate the configuration. Subscription links often contain access credentials, so hide the full URL in screenshots.
Subscription setup steps →For everyday use, start with rule mode, then enable the system proxy or mobile VPN connection. The system proxy only affects apps that follow that setting. If you need TUN, first confirm the basic connection works, then enable it separately to make permission or routing conflicts easier to diagnose.
System proxy settings →After selecting a proxy group, test the services you actually use and check the connection log to see which rules matched. The client’s speed test is only a guide, not a substitute for testing real apps. If something fails, note the error, current mode, and connection method, then consult the manual for that symptom. Avoid changing several settings at once.
Speed tests and connection checks →Check architecture, permissions, and configuration format separately. For connection problems, see the troubleshooting guide.
Start with Clash Plus on Windows, macOS, Android, and iOS, or Clash Verge Rev on Linux. If you want to keep your existing setup or workflow, choose another client for the same platform. The installer does not include a subscription.
On Windows, check System type in Settings > System > About. On a Mac, check the chip or processor in About This Mac. For Android, choose ARM64 or ARMv7 based on your device; if you’re unsure, use a supported universal build. On Linux, run uname -m to check the architecture. Make sure it matches the file name.
The client reads your configuration, applies rules, and connects through a proxy; the installer does not provide proxy service. Import a valid subscription or local configuration, select a proxy group, then enable the system proxy or VPN connection for your platform. See the subscription setup guide for details.
First, make sure the download is complete and the file extension matches your system. Then check the processor architecture and OS compatibility. If your system warns you about a risk, verify the file’s source and publisher instead of disabling security protections altogether. On a managed work device, check that you have permission to install software.
Export your local configuration, custom rules, and overrides. Note your subscription source, ports, and TUN status, then quit the old client before installing the update. Data folders and configuration formats vary between clients. When migrating, reimport your subscription rather than overwriting the entire configuration folder.
Mihomo is the core that handles proxy protocols, rules, and DNS settings. A graphical client adds subscription management, controls, and logs. Most desktop and mobile users should choose a graphical client; server and router users can deploy the core for their system architecture.