PACKAGE ROUTING / PLATFORM INDEX
Enter the list for your operating system and check the processor architecture, installer format, and maintenance status. Prefer graphical clients on desktop and mobile devices; choose the Mihomo kernel for servers and routers.
BEFORE DOWNLOAD
Clients may have similar names, but their supported platforms, package formats, and maintenance status differ. Checking your system and architecture first helps prevent installing the wrong package, launch failures, and configuration import errors.
On Windows, first check whether the system is 64-bit. On macOS, distinguish Apple Silicon from Intel. On Android, check the OS version and processor architecture. On Linux, confirm whether the distribution uses DEB, RPM, or manual deployment. If the system is too old, the installer may download successfully but fail to launch because of incompatible runtimes or system APIs.
Clash Plus, Clash Verge Rev, FlClash, and Clash Nyanpasu are graphical clients with configuration import, proxy switching, and system integration controls. Mihomo is a standalone kernel that must be started with a configuration file, command-line arguments, or a service manager. Most desktop users should choose a graphical client under their platform instead of deploying the kernel directly.
Clients marked “No longer maintained” are intended for legacy environments or reading older configurations, not as the default choice for new installations. Archived packages may still help migrate existing configuration structures, but long-term use should account for OS updates, kernel compatibility, and rule syntax changes. For new devices, choose a maintained client and then compare its interface and platform capabilities.
CLIENT PACKAGES
After switching platforms, the download buttons point to the corresponding installers. Version details appear only when the remote manifest provides valid values; if the manifest is temporarily unavailable, the buttons retain the complete fallback paths defined on this page.
For a standard desktop installation, choose the x64 installer. After installation, import your configuration first, then enable the system proxy or configure TUN as needed. Before migrating from an older client, keep the original configuration file and subscription URL.
A graphical client for everyday desktop use. It guides you through installation, configuration import, and system-proxy integration in sequence, with an x64 installer for Windows.
A Mihomo-based desktop client with configuration management, proxy-group switching, and system-proxy controls. Suitable for Windows users who need more kernel options.
A cross-platform client for desktop and Android. Windows users can choose an installer or archive, making it suitable for those who want a consistent workflow across devices.
A desktop configuration-management client for users familiar with Profiles, proxy groups, and basic Mihomo settings. The current Windows download is an x64 installer.
Kept for legacy-environment migration and reading historical configurations. For new installations, prefer a maintained client; before continuing to use this one, assess compatibility with the newer OS and existing configuration.
| Check | Recommendation | Where to check |
|---|---|---|
| System architecture | 64-bit Windows; choose an x64 or AMD64 package | Settings → System → About → System type |
| Installation permissions | Allow administrator approval when installing drivers or service components | Windows security confirmation dialog |
| Port status | Before enabling the client, confirm that the listening port is not in use by another proxy program | Client logs or a system port inspection tool |
Check the chip type in About This Mac first. Choose an ARM64 or Apple Silicon package for Apple M series chips, and an x64 or Intel package for Intel processors. Complete the app permissions requested by macOS on first launch.
Provides separate macOS installers for Apple Silicon and Intel. Designed for configuration import, proxy switching, and system-proxy control through a graphical interface.
Provides a Mihomo-based desktop interface for configuration and proxy-group management. Select the correct processor-specific download before installation, then grant the permissions required for system-proxy integration.
A cross-platform graphical client for workflows shared between desktop and Android devices. The macOS downloads distinguish Apple Silicon and Intel processors.
Retained as an archive entry for older macOS environments and existing configurations. For new devices, evaluate maintained clients first and avoid long-term reliance on legacy system APIs.
| Check | Apple Silicon | Intel processor |
|---|---|---|
| Installer identifier | ARM64、arm64、Apple Silicon | x64、x86_64、Intel |
| How to check | Apple menu → About This Mac → Check the chip or processor field | |
| First launch | Follow the system prompts to approve app permissions, then check proxy status in network settings | |
Most current Android phones use ARM64. Older 32-bit devices can use an ARM package; when the architecture is unknown, choose a client with a Universal build. After installation, Android will ask you to approve VPN connection permission.
A graphical client for Android ARM64 devices, with configuration import, proxy selection, and system connection authorization. Confirm that your device uses 64-bit ARM before downloading.
An Android Mihomo-based client offering ARM64, ARM, and Universal packages. Suitable when you need to match the device architecture precisely or prefer a Universal package.
Provides Android packages for ARM64, 32-bit ARM, and x86_64. Most phones should use ARM64; older devices can use ARM, while some emulators and specialized devices use x86_64.
An Android network-proxy client with its own configuration and rule-management workflow. Suitable for users familiar with subscriptions, proxy groups, and rule matching who are ready to adjust settings according to the client documentation.
| Architecture | Common devices | Selection advice |
|---|---|---|
| ARM64-v8a | Recent mainstream Android phones and tablets | Preferred choice; usually offers the best architecture match |
| armeabi-v7a | Older 32-bit ARM devices | Choose only when the device does not support 64-bit apps |
| x86_64 | Some emulators and specialized Android devices | Confirm the processor architecture before installing |
| Universal | Devices with an unknown architecture | The package is usually larger but simplifies compatibility decisions |
Install Clash Plus on iPhone and iPad through the App Store. Check system compatibility on the store page, complete the installation, then import your configuration in the client and approve the required network permissions.
An App Store client for iPhone and iPad. After installation, manage configurations and select proxies in the app, then approve network connection permissions when prompted by iOS.
| Check | Details |
|---|---|
| Device type | iPhone or iPad; see the App Store listing for the exact compatible versions |
| Installation method | Open the App Store listing and complete installation through Apple's standard flow |
| First connection | Approve network permissions when prompted, then check the active proxy and configuration status |
First identify your distribution's package system. Debian and Ubuntu-based systems typically use DEB; Fedora, RHEL, and Rocky Linux typically use RPM. Choose a graphical client for desktop environments, or continue to the Mihomo kernel section for servers.
A graphical client for Linux desktops, with AMD64 DEB and RPM packages. Suitable for users who need configuration management, proxy switching, and desktop proxy controls.
Provides AMD64 DEB, RPM, and AppImage packages. Use DEB or RPM with a standard package manager; consider AppImage when you need a self-contained application.
| Distribution type | Package format | Pre-installation checks |
|---|---|---|
| Debian / Ubuntu / Linux Mint | DEB | Confirm the system is AMD64 and check the desktop environment and runtime libraries |
| Fedora / RHEL / Rocky Linux / openSUSE | RPM | Confirm that the package manager supports RPM and review dependency notices |
| Other desktop distributions | AppImage | Grant execute permission before launching, then check how system-proxy integration is handled |
MIHOMO CORE
The Mihomo kernel is intended mainly for servers, routers, containers, and users who maintain service processes themselves. Desktop and mobile users should prefer the graphical clients above for managing configurations, proxy groups, and system-proxy status.
Suitable for command-line execution, script control, or use as the backend kernel for another management interface.
Choose AMD64 for Intel processors and ARM64 for Apple M series chips. Extract the archive and run it from a terminal.
Choose according to the CPU architecture. AMD64 and ARM64 are common on servers; embedded devices also require checking for ARMv7 or MIPS soft-float instruction sets.
| Platform | Architecture | File format | Typical environment |
|---|---|---|---|
| Windows | AMD64 / ARM64 | ZIP | Command line, scripts, and service processes |
| macOS | Intel AMD64 / Apple ARM64 | GZ | Terminal execution and custom management tools |
| Linux | AMD64 | DEB / GZ | Servers, desktop services, and container hosts |
| Linux / Router | ARM64 / ARMv7 / MIPS softfloat | GZ | ARM servers, development boards, and routers |
INSTALL SEQUENCE
Downloading is only the first step. The recommended sequence is to install the client, import a configuration, choose a proxy mode, verify proxy groups, then enable system integration and test the resulting traffic path.
Follow the installer on desktop systems; approve app permissions through the system flow on Android and iOS; use the appropriate package manager on Linux. After the first launch, check the client logs for startup errors and avoid enabling multiple proxy clients at once.
On the Configuration or Profiles page, import a valid configuration file or subscription URL. Importing does not enable it automatically; switch the target profile to active. For YAML parsing errors, check indentation, field names, and kernel compatibility.
Rule mode routes traffic according to the rule order in the configuration; Global mode sends requests to the selected proxy policy; Direct mode helps isolate network issues outside the client. In Rule mode, also inspect the proxy group to verify the selected node or sub-policy.
Enable the system proxy on desktop when needed; evaluate TUN when more application traffic must be covered. Mobile clients typically connect through the system VPN interface. Avoid running other proxies, VPNs, or network filters that may create routing conflicts.
After connecting, check the client logs for recurring errors and confirm that HTTP, SOCKS, or mixed-port is not already in use. If some domains remain unreachable, inspect DNS mode, rule-match order, and proxy-group status instead of repeatedly reinstalling the client.
DOWNLOAD FAQ
These questions cover platform selection, processor architecture, package formats, and basic post-installation troubleshooting. For full guidance on configuration syntax, rule routing, and TUN, continue to the system tutorial.
For a standard graphical installation and setup, start with Clash Plus. For finer kernel and configuration control, compare Clash Verge Rev, FlClash, and Clash Nyanpasu. Clash for Windows is no longer maintained and is available only as an archive, so it is not recommended for new devices.
Open About This Mac from the Apple menu and check the Chip or Processor field. If it shows an Apple M series chip, choose an Apple Silicon or ARM64 installer; if it shows Intel, choose an Intel or x64 installer. A mismatched architecture may prevent the app from launching or require an additional compatibility layer.
Most recent Android phones use ARM64. Older 32-bit devices can use ARM, while some emulators use x86_64. If you cannot confirm the architecture, choose the Universal build of Clash Meta for Android. Also confirm that the Android version meets the client requirements before installing.
Debian, Ubuntu, Linux Mint, and similar systems typically use DEB; Fedora, RHEL, Rocky Linux, and openSUSE typically use RPM. FlClash also offers AppImage for desktop environments that need a self-contained package. If dependencies are missing, follow the package manager's instructions to install the required components.
Graphical clients provide configuration management, proxy selection, and system-proxy controls for everyday desktop and mobile use. Mihomo is a command-line kernel intended mainly for servers, routers, containers, and users who manage service processes themselves. Direct kernel use requires a separate configuration and startup method.
First confirm that the configuration loaded successfully and is active, then check proxy mode, proxy-group selection, system proxy, and TUN status. If there is a port conflict, stop the process using the port or change the listening port. If only some domains fail, inspect DNS and rule-match results.