Client Downloads · Platforms and Architectures
Find Clash Plus, Clash Nyanpasu, and other Clash ecosystem clients by operating system. Choose a graphical client first, then check your CPU architecture. Server and router users can go straight to the mihomo core.
First-time setup
Start with the recommended client for your platform, then import a subscription using the guide.
Existing configuration
Keep your local rules and policy groups, and make sure the new core can read your configuration.
Choose the right architecture
x64 / amd64 and arm64 are different package types. Check the filename before downloading.
The desktop installers below are for x64 systems. Exit any running proxy client before installing and launching another app, so multiple programs don't compete to control the system proxy.
A good fit for Windows users who want to get started by importing a subscription. Install the client, then add your own configuration; you don't need to run a separate command-line core to switch modes in everyday use.
After the first launch, check that the right profile is selected, then choose an outbound proxy in its policy group. Official site: clashplus.io.
For desktop users who want to manage profiles, rules, and proxy settings in one place. When moving from another Clash client, check local overrides instead of copying only the subscription name.
For TUN or service components, follow the client's permission prompts. Keep the default network settings until you've verified a basic connection.
A desktop client for managing configurations, with a familiar workflow across devices. Choose an installer or ZIP that matches your CPU architecture.
Extract the ZIP completely before running the app; don't launch it from within an archive utility. A portable ZIP doesn't necessarily mean the configuration folder is stored alongside the program.
An open-source desktop client built with Tauri, offering configuration management, Rule Routing, and core options. To use mihomo features, first check which core is enabled.
The client interface and core have different roles: the interface manages configurations, while the core handles connections and rules. After installation, follow the user guide to verify each step.
Archived download for migrating older configurations or reproducing issues in existing setups. For a new installation, consider one of the clients above. Don't assume features described in older guides are supported by current cores.
Without ongoing maintenance, this client may not adapt to future system changes or new protocols. Back up your configuration before migrating, then recheck DNS and rule behavior.
| Check | Before installing |
|---|---|
| System and architecture | Use a Windows version that is still supported by Microsoft. The packages listed here are for x64 / amd64; check System type under Settings > System > About. On ARM devices, verify app compatibility separately. |
| Runtime | Tauri clients require a working WebView2 runtime. If startup reports a missing component, install it as prompted by the installer or system. Minimum Windows versions vary by client; check the requirements for the specific app. |
| Permissions and network | Managing configurations normally requires different permissions from installing a network service. Before enabling TUN, check the service component and administrator permissions, and make sure another proxy app isn't also changing routes. |
Check About This Mac for your chip: Apple M-series chips are Apple Silicon; Intel Macs typically use x64. Some download buttons currently provide an Intel-compatible build, clearly labeled on the button.
Choose a DMG for your chip. Apple Silicon users should prefer the arm64 build, while Intel users should choose x64. Don't rely on file size or download order to identify the right package.
After installation, launch the app from Applications and grant network permissions if needed. Official product site: clashplus.io.
For desktop configuration and rule management. The Apple Silicon and Intel download buttons currently point to the same x64 file; this is not a native ARM installer.
Running on Apple Silicon depends on Rosetta 2 and client compatibility. If you need a native ARM build, choose a client on this page with an explicitly listed arm64 file.
A good fit for Mac users who want a graphical interface for managing subscriptions and proxy modes. Both chip options currently provide an amd64 file; check the actual package architecture before downloading.
Before using the Intel-compatible build, make sure your system supports Rosetta 2. When migrating a configuration, keep the subscription source; don't overwrite the app's settings with another client's interface settings file.
Archived option for older Mac setups and compatibility testing. The available build is x86_64; for newer devices or fresh configurations, prefer a maintained client.
An archived package may still run, but that doesn't mean it will keep up with system changes. Back up your old configuration, then check the current core's rules and DNS documentation after migrating.
| Check | Before installing |
|---|---|
| macOS version | Use a macOS version supported by the client. Minimum requirements vary between projects. If the installer says your system is incompatible, don't try to bypass the check by renaming the file. |
| Chip and package format | arm64 is the native architecture for Apple Silicon; x64 / amd64 / x86_64 are for Intel. A DMG is a disk image. Mount it, then follow the prompts to install the app in Applications. |
| System permissions | Follow system prompts to confirm the app's source and grant network permissions. Test a standard proxy first, then enable network features that require extra permissions; change one thing at a time. |
Most recent Android phones use arm64, but check your device specifications. The first time you connect through a proxy, Android will usually ask you to authorize the VPN connection.
For importing subscriptions and managing everyday connections on an Android phone. This arm64-v8a package requires a device that supports 64-bit ARM apps.
Allow installs from the source you used to download the app before continuing. You'll need to provide your own subscription; installing the app doesn't provide a proxy service. Official site: clashplus.io.
An Android app for managing configurations and connections. Choose an APK for your device's architecture if known. If you're not sure, try the universal package, but check that your system meets the app's requirements.
After importing a configuration, select it before starting a connection. If Android stops the app in the background, check battery optimization and background activity settings instead of repeatedly trying different installers.
Available for arm64 and 32-bit ARM. A newer phone doesn't automatically mean every system environment supports the same architecture; emulator users should check the ABI in particular.
When switching from another client, disconnect its VPN first. Android typically allows only one standard VPN connection at a time.
For Android users with a compatible configuration. Surfboard uses a different configuration syntax from Clash YAML; changing the file extension alone does not convert it.
Before importing, check which formats your subscription provider supports, along with protocol and rule compatibility. If parsing fails, check the configuration format first rather than granting additional permissions.
| Check | Before installing |
|---|---|
| System and ABI | Check your device manufacturer's specifications and the app's requirements. arm64-v8a is 64-bit ARM; armeabi-v7a is 32-bit ARM. Universal packages include multiple architectures but aren't guaranteed to work with every system version. |
| Install permission | Allow app installs only for the browser or file manager you used to download the APK. If parsing fails, check that the download is complete, your Android version is supported, and the package matches your device's architecture. |
| Connection and background activity | Approve the system VPN prompt on the first connection. For long-running background use, check battery restrictions. Stop other VPN apps before diagnosing a connection issue with this client. |
Open the app's listing in the App Store and check device compatibility before installing. Import subscriptions and configure rules in the app using formats it supports.
Install through the App Store. Manage your own subscriptions and network connections on an iPhone or compatible device; check the store listing for supported devices.
Product details: clashplus.io. After the first launch, import a configuration as prompted and approve the system network permission when connecting.
| Check | Before installing |
|---|---|
| Device compatibility | Check the Compatibility section on the App Store listing for minimum iOS requirements and supported devices. Store information is more reliable than assumptions based on older guides. |
| Configuration source | Prepare a subscription or configuration link you're authorized to use. Installing a client doesn't create a proxy service, and the configuration format must be supported by the app. |
| Connection permission | When connecting for the first time, follow the system prompt to add a VPN configuration. Disconnect other VPNs before troubleshooting so you can identify which network route is active. |
After installation, import a configuration, select an outbound proxy, and verify that it works before changing rules or DNS. Making changes one at a time makes it easier to find what affected the connection. See the subscription import guide for steps.
Desktop users should start with a graphical client. The packages below are for amd64 / x86_64. Match DEB or RPM to your distribution's package system; don't choose by file size alone.
DEB and RPM packages are available. Debian and Ubuntu systems typically use DEB, while Fedora and other RPM-based distributions use RPM. Check system dependencies before installing.
Install with your distribution's package manager to handle dependencies. System proxy settings affect different apps in different ways; command-line tools may need proxy environment variables configured separately.
This Linux amd64 DEB package is for desktop systems that support the format. A successful installation doesn't automatically route every app through the proxy; check each app's settings.
If startup fails, check the terminal output and missing dependency messages first. Servers without a graphical desktop are usually better served by the standalone core below than a GUI package.
| Check | Before installing |
|---|---|
| Distribution and architecture | Check your architecture with uname -m; x86_64 usually corresponds to an amd64 package. The desktop downloads don't include ARM packages. ARM server users can check the core downloads below. |
| Desktop and dependencies | Graphical clients need a desktop session and the appropriate runtime libraries. Minimum distribution requirements vary by client. If the package manager reports missing dependencies, resolve them first rather than forcing the installation. |
| Permissions and services | TUN requires permissions to create network devices and configure routes. Get a standard proxy working before setting up services or extra permissions. Don't use elevated privileges for the entire desktop app as a substitute for troubleshooting. |
Standalone Core · Servers and Routers
The standalone core reads configurations, listens on ports, and applies rules; it doesn't include a desktop management interface. Most users can use a GUI client above. Server, router, and self-hosted service users can choose a core based on their operating system and CPU architecture.
The core and client are separate choices. Clients usually manage their bundled core; don't replace files in the installation directory with the standalone executable here. Before a standalone deployment, prepare a configuration file and check ports, DNS, the service account, and startup method. For technical background, see the protocol and core technical reference.
| System | CPU architecture | File and usage notes | Download |
|---|---|---|---|
| Windows | AMD64 / x64 | ZIP archive. Extract and run from the command line; for 64-bit Intel / AMD systems. | Download AMD64 ZIP |
| Windows | ARM64 | ZIP archive for Windows on ARM64; not for standard x64 systems. | Download ARM64 ZIP |
| macOS | Intel / AMD64 | GZ archive. Extract the executable and set its permissions as required by your system. | Download Intel GZ |
| macOS | Apple Silicon / ARM64 | GZ archive for standalone use on Apple M-series systems; not a graphical DMG client. | Download ARM64 GZ |
| Linux | AMD64 | DEB package for distributions that support this format. Configure how it runs after installation. | Download AMD64 DEB |
| Linux | AMD64 | GZ archive for systems where you manage binaries and services manually. | Download AMD64 GZ |
| Linux | ARM64 | GZ archive for 64-bit ARM servers and compatible devices. Check the architecture of your operating system's user space first. | Download ARM64 GZ |
| Linux | ARMv7 | GZ archive for devices compatible with ARMv7 32-bit. Don't choose it based on processor brand alone. | Download ARMv7 GZ |
| Linux | MIPS softfloat | GZ archive for devices matching this architecture and floating-point ABI. Check byte order too; this isn't suitable for every MIPS router. | Download MIPS GZ |
GZ is just a compression format; extracting it won't create a service, configuration directory, or startup entry. Before deploying on a router, check the firmware environment and available storage. If a firmware plugin manages the core, follow its update process.
Import a subscription or local configuration, then select the active profile. Make sure the rules reference existing policy groups and choose an actual outbound proxy in each group. Saving a subscription URL to a list doesn't necessarily activate its profile. If an update fails, check the response format and parsing logs; don't post subscription links publicly.
Next, test the connection in Rule mode and enable the system proxy if your apps need it. System proxy and TUN cover different traffic; TUN also involves extra permissions, DNS, and routing, so there's no need to enable everything at once. Make changes one at a time after confirming access works. If something breaks, keep the logs and a record of your changes to make troubleshooting easier.
Before upgrading or switching clients, back up your subscription source and custom local rules, close the old app, and check that the system proxy has been restored. Client settings folders and subscription YAML files aren't always the same kind of file, so don't copy an entire old folder over the new app. See the user guide for the full process, and the glossary for terminology.
For your first setup, choose a client with a graphical interface. Clients support subscription imports, mode switching, and log viewing. The standalone mihomo core is intended for server and router users who manage configuration files, startup parameters, and system services themselves.
On Windows, check System type under Settings > System > About. On Mac, check the chip or processor under About This Mac. On Android, consult your device manufacturer's specifications. x64 and amd64 usually refer to the same 64-bit architecture; arm64 is a different architecture. Check both the download button and the actual filename—don't choose a package based on the operating system name alone.
Some clients currently link to the same x64 or amd64 file from both their Apple Silicon and Intel download buttons. These are labeled as compatibility builds on this page; they are not native ARM builds. Whether they run depends on system and client support for Rosetta 2. For a native build, choose a file explicitly labeled arm64.
The installer doesn't include a ready-to-use subscription service. Import a subscription or configuration you've obtained and are authorized to use, select the profile and an outbound proxy in its policy group, then check the rule mode, system proxy, and app proxy support. TUN mode also requires permissions and routing configuration, so enable it only after a basic connection works.
Archived clients may still run, but they won't receive support for new protocols or fixes for system compatibility. Clash for Windows and ClashX Meta are listed only for migration from older setups or reproducing compatibility issues. For a new installation, choose a maintained alternative. Back up your configuration and check core compatibility before migrating.
Back up your subscription source, custom rules, policy group names, and local configuration, and note your system proxy and TUN settings. Close the old client before installing or starting the new one to prevent both apps from changing system proxy and routing settings at once. After upgrading, check that the configuration loads and review the connection logs before removing old files.
For other connection and subscription issues, see the FAQs. If installation fails, note your operating system, package architecture, and the full error message; that's more useful for troubleshooting than simply saying it "won't open."