CLIENT PACKAGES / DOWNLOADS & ARCHITECTURES
GUI clients handle subscriptions, rule-based routing, and proxy settings. Choose your operating system first, then check the CPU architecture. For servers and routers, see the Mihomo core.
01 / CLIENTS
The main button links to the standard package for each platform. Choose another architecture from the same card.
For a first install, start with Clash Plus. The GUI installers below are for x64. Windows on ARM users should first confirm that their system can run x64 apps; the ARM64 core package is not a substitute for a GUI client installer.
For everyday desktop use, manage subscriptions, proxy groups, and network settings in one GUI.
After installation, import your configuration and select Rule mode. System Proxy and TUN route traffic differently, so test one first and enable the other only if needed. See clashplus.io for product details.
A desktop client based on mihomo, suited to users who want to manage configuration files and rule overrides.
If you need Service Mode or TUN, follow the client’s prompts to grant the required permissions. Subscription updates may overwrite the original configuration, so keep custom rules in a supported override location. Review the final configuration after making changes.
A mihomo client with a Flutter interface, for users who prefer a similar experience across desktop and mobile.
The amd64 package uses the same general architecture as x64. After importing an existing subscription, check your proxy group, DNS, and local listening ports. Don’t assume interface settings will transfer with the subscription from another client.
A desktop GUI client for users who want to manage configurations and check connection status through an interface.
Whether a configuration loads depends on the core in use and the fields it supports—not just the file extension. If parsing fails, check the field names in the logs and consult the technical reference instead of repeatedly reinstalling the client.
Archived downloads of legacy clients are kept mainly for migrating existing setups and comparing configurations.
An archived download does not mean the client is still maintained. Check compatibility with newer protocols, configuration fields, and operating systems separately. For a first install, choose a maintained client above. Back up your subscription URL and custom rules before migrating.
| Check | Requirements and guidance |
|---|---|
| System type | Check your system type under Settings → System → About. The desktop packages here are primarily x64. Refer to the selected client’s release notes and installer prompts for the minimum supported Windows version. |
| Permissions | Importing a regular configuration and running a TUN service require different permissions. Installing a service or virtual network adapter may require administrator approval. On a managed device, follow your organization’s policies. |
| Existing proxy clients | Before switching, turn off System Proxy and TUN in the old client, then quit it. Make sure the mixed port is available and avoid having multiple clients change system proxy settings at the same time. |
Check your chip under Apple menu → About This Mac. Apple Silicon uses arm64; Intel uses x64. Some current links provide x64 files, as noted on the cards. A platform label does not guarantee that the download is a native build for your processor.
Separate installers are available for Apple Silicon and Intel. Choose the DMG that matches your chip.
Open the disk image, move the app to Applications, then launch it and import your subscription. Follow macOS prompts to authorize System Proxy and network extensions. See clashplus.io for product details.
A mihomo desktop client; both current chip options fall back to an x64 DMG.
After downloading on Apple Silicon, check the actual file architecture. The current x64 package generally requires Rosetta. If you need a native arm64 build, choose a client on this page that explicitly offers one.
A cross-platform GUI client; both current macOS links fall back to an amd64 DMG.
amd64 is the same general architecture as x64, not native Apple Silicon. Compatibility depends on your macOS version. After the first launch, check System Proxy and DNS settings rather than assuming the client uses the same local addresses as your previous one.
An archived menu bar client for comparing existing setups; the current fallback file is an x86_64 DMG.
The Apple Silicon link also currently provides an x86_64 file, not a native arm64 build. Since this client is no longer maintained, choose one of the maintained options above for a new install. Verify archived configurations for compatibility before migrating.
| Check | Requirements and guidance |
|---|---|
| Chip architecture | For Apple Silicon, prefer native arm64. Intel Macs need x64 or amd64. A compatibility link to an x64 file is not a native ARM build. |
| macOS version | Minimum macOS requirements vary by client release. Check the app’s release notes and macOS installer prompts. The fact that an older system can mount a DMG does not mean it can run the app. |
| Compatibility and permissions | Running x64 apps on Apple Silicon usually requires Rosetta. TUN and related services may need additional permissions. If macOS displays a security warning, verify the app’s source and review the system guidance; don’t disable security features wholesale. |
Most recent phones use arm64, but a 64-bit-capable processor does not guarantee that the device runs a 64-bit OS. Check your system information before choosing an APK. If you’re unsure, see the universal Clash Meta for Android package below.
An Android GUI client with an arm64-v8a package.
After installing, import your subscription and allow the VPN connection when prompted. If you need the connection to stay active in the background, check your device’s battery management settings. See clashplus.io for product details.
An Android client in the Meta / mihomo ecosystem, with arm64, ARM, and universal package options.
The universal package supports multiple architectures and is usually larger, making it a good choice if you can’t identify your device’s architecture. App routing, background operation, and DNS are client settings; switching APK architectures won’t fix them.
Available as arm64-v8a and armeabi-v7a APKs. Choose the package that matches your device’s system architecture.
Users familiar with the Flutter desktop app can expect a similar interface. Once connected, check your proxy group and rule matches. The system VPN indicator only confirms that a tunnel is active—it doesn’t guarantee access to every destination.
An Android client with its own configuration syntax; a universal APK is available here.
Surfboard is not a drop-in replacement for loading arbitrary Clash YAML files. Before downloading, confirm that your provider’s subscription format, protocols, and rules are supported. Don’t assume proxy groups or overrides from Clash configurations will work unchanged.
| Check | Requirements and guidance |
|---|---|
| APK architecture | arm64-v8a is for 64-bit ARM systems; armeabi-v7a is for some 32-bit ARM systems. If you don’t know your system architecture, choose a universal package that supports multiple architectures. |
| Install permission | Grant install permission only to the browser or file manager performing this installation. If Android reports that the package is incompatible, first check the OS version, architecture, and whether an existing installation has a different signing key. |
| VPN and background operation | A connection requires Android VPN permission. Other apps using the VPN interface may conflict with the client. If Android stops it in the background, check battery optimization and auto-start settings. |
Install Clash Plus from the App Store. The store listing shows current system requirements and compatible devices. After installation, prepare a subscription or configuration, then authorize the first connection.
iOS client download and updates are provided through the App Store.
After importing, confirm that the configuration loaded successfully, choose a proxy group, and connect. When prompted the first time, allow iOS to add a VPN configuration. Check the connection status in Settings afterward. Other VPN apps may interfere, so test them separately.
| Check | Requirements and guidance |
|---|---|
| System and device | Refer to the compatibility details on the App Store listing, which shows the app’s current system version and device requirements. |
| First connection | Import a valid configuration and allow iOS to add a VPN configuration. After connecting, test actual requests rather than relying on the status bar indicator. |
| Subscription updates | Subscription updates and app updates are separate. Refresh an expired configuration in the client; get app updates through the App Store. |
The packages below are amd64 clients for graphical desktops. Debian- and Ubuntu-based distributions typically use DEB; Fedora and other RPM-based distributions use RPM. For headless servers, use a core package below.
Linux GUI client with amd64 DEB and x86_64 RPM packages.
Installing through your distribution’s package manager also handles dependencies. Desktop sessions, the WebView runtime, and TUN permissions affect the interface and traffic routing separately. Test them independently; don’t confuse an app that won’t open with a configuration error.
Linux desktop GUI client with an amd64 DEB package.
Use the GUI to switch configurations and proxy groups in a desktop environment. The desktop system proxy usually isn’t applied automatically to every terminal app. After installation, set proxy environment variables for commands that need them, or enable TUN if you have the required permissions.
| Check | Requirements and guidance |
|---|---|
| Desktop and architecture | These packages are for amd64 systems with a graphical desktop. Use uname -m to help check your architecture. Don’t install an amd64 desktop package on aarch64, armv7l, or other architectures. |
| Package format | DEB and RPM are different package formats. Choose the package for your distribution and use its package manager to handle dependencies. Don’t try to install a package by changing its file extension. |
| Permissions and networking | TUN requires permissions to manage a virtual network interface and routes. A desktop client launching successfully does not mean a regular user has those permissions. Server deployments also require you to configure startup services and log management. |
02 / CORE
The core reads configurations, establishes proxy connections, and applies routing rules. It does not include a GUI for subscription management. Choose it if you can manage configuration directories, startup options, and services yourself. For everyday desktop and mobile use, choose a GUI client above.
Check both your operating system and CPU architecture before downloading. amd64 and x86_64 are usually different names for the same architecture; arm64 commonly corresponds to aarch64. For routers, check the firmware architecture, endianness, and runtime environment. Don’t choose a MIPS package based on the device brand alone.
| Operating system | Architecture | File format | Download |
|---|---|---|---|
| Windows | AMD64 / x64 | ZIP | Download AMD64 |
| Windows | ARM64 | ZIP | Download ARM64 |
| macOS | Intel / AMD64 | GZ | Download Intel |
| macOS | Apple Silicon / ARM64 | GZ | Download Apple Silicon |
| 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 |
For core families, protocol support, and subscription compatibility, see the protocol and core reference. For Linux GUI desktops versus headless deployments, see the Linux deployment guide.
03 / FIRST RUN
Downloading the app is only the first step. Verify the configuration, traffic entry point, and requests in order to avoid port conflicts and mixing modes.
Import a subscription link from the client’s subscription or configuration page, or select a local YAML file. After saving, check that the configuration parses correctly. If an update fails, determine whether the link is unreachable, the response isn’t a configuration, or the core doesn’t recognize a field.
Subscription import guide →Start in Rule mode and check your proxy group, then enable System Proxy and test a browser. Use TUN only if you need to route apps that don’t read system proxy settings. Don’t let multiple clients manage System Proxy or virtual network interfaces at the same time.
Mode settings guide →Check connections and logs to confirm which rule and proxy group handle each request. A working browser doesn’t mean terminal traffic is proxied; terminals may need separate environment variables. If you change the mixed port, update every app with a manually configured proxy address.
Connection testing guide →04 / PACKAGE FAQ
For everyday use on a desktop or phone, start with a GUI client. Try Clash Plus on Windows, macOS, Android, or iOS, and Clash Verge Rev on Linux. The Mihomo core is for server and router users who can manage configuration files, startup options, and service permissions themselves; it does not include a subscription-management interface.
Check your processor and system type, then choose a matching package. x64 and amd64 usually refer to the same 64-bit desktop architecture; arm64 is 64-bit ARM, while ARMv7 is used by some 32-bit ARM devices. If you’re unsure which architecture your Android device uses, choose the universal Clash Meta for Android package. On Apple Silicon, check that the actual download is a native arm64 build—don’t rely on the platform label alone.
A version number appears only when the version manifest includes a non-empty value. A blank version field does not mean the download link is broken. The app version in the manifest may also differ from the package filename. Check the downloaded file and the client’s About page rather than treating an empty version label as an update status.
Archived downloads for these discontinued clients are kept for migrating existing setups and comparing configurations. Archived builds do not gain support for new protocols or operating systems. For a fresh install, choose a maintained client. Before migrating, back up your subscriptions, rules, and overrides, then check whether the new core can parse your existing fields.
The installer provides the client app, but you still need to import a subscription or configuration you’re authorized to use, choose a proxy group, and enable System Proxy or TUN as needed. First test browser traffic in Rule mode, then check your terminal’s environment variables and other apps’ proxy settings. See the quick start guide for the complete setup.
Turn off System Proxy and TUN in the old client before quitting it. This helps prevent clients from competing over listening ports, virtual network routes, or system proxy settings. After launching the new client, check its mixed port and proxy address. If you changed the port, update any manually configured proxy settings in browser extensions, terminals, and other apps.