DOWNLOAD / PLATFORM ROUTING
Confirm your operating system first, then check the CPU architecture. Desktop and phone users should choose a GUI client; servers and routers should continue to the Mihomo core section.
CLIENT PACKAGES
The platform label is synced to the page URL. When you share a platform-specific link, the page opens directly at the matching download section. Version details appear only when the manifest returns valid data.
OS / WINDOWS
Most devices use 64-bit Windows 10 or Windows 11. For a first installation, start with Clash Plus; if you need a different interface or configuration workflow, compare the clients below. Run the installer after downloading. If Windows asks you to confirm the source, check that the filename matches the selected client.
A good choice for first-time installation and everyday use. Includes a graphical interface, subscription import, policy-group switching, and system proxy controls. The Windows download is an x64 installer.
A Mihomo-based desktop client for users who need to inspect rules, connections, and configuration overrides. The current Windows download provides an x64 installer.
A cross-platform GUI client. The installer places the app in the standard application directory; the archive is useful when you want to choose the location yourself or keep a portable folder.
Provides subscription, proxy-group, and configuration management interfaces. A good fit for users who understand the difference between rule and global modes and want to maintain configuration centrally on the desktop.
The archived package is intended for migrating existing environments or maintaining compatibility with older configurations. Since the project is no longer maintained, choose an actively updated client for new devices.
| Check | Recommendation | Where to check |
|---|---|---|
| Windows version | Windows 10 or Windows 11 | Settings → System → About |
| System type | 64-bit operating system, x64 processor | About → System type |
| Installation permissions | The current account can install desktop applications | For managed devices, confirm administrator policies |
| First connection | Enable the system proxy after importing a configuration | Client home page or system proxy settings |
OS / MACOS
First check the chip in About This Mac. Apple M1, M2, M3, and M4 chips are Apple Silicon; choose ARM64. For Intel devices, choose x64. When opening a downloaded app for the first time, macOS may ask you to approve network extensions, proxy access, or VPN configuration permissions. Grant only the permissions required by the client.
Provides separate Apple Silicon and Intel downloads. Confirm the chip first, then download the matching DMG. During installation, drag the app to the Applications folder.
A desktop option for users who need configuration overrides, rule inspection, and Mihomo features. The two architecture downloads are managed separately in the release manifest, so confirm the chip type before downloading.
The interface is similar to versions on other platforms, making it suitable for users who switch between desktop and Android devices. After installation, allow the required network permissions in System Settings.
The archived version is intended for existing users restoring an older environment. Because the project is no longer maintained, it will not keep up with new system changes; choose one of the clients above for a new installation.
| Check | Apple Silicon | Intel |
|---|---|---|
| Chip identifier | Apple M series | Intel Core series |
| Package identifier | ARM64 / Apple Silicon | x64 / x86_64 / Intel |
| Installation method | Open the DMG and drag it to Applications | Open the DMG and drag it to Applications |
| Initial permissions | Allow network configuration when prompted | Allow network configuration when prompted |
OS / ANDROID
Most recent phones and tablets use ARM64. Older 32-bit devices may require the ARM version; if you are unsure, the universal package for Clash Meta for Android supports a wider range. On the first connection, Android displays a VPN permission prompt, which is required to create the local traffic-forwarding interface.
A GUI client for common 64-bit Android devices. After installation, import a subscription, choose a policy node, and authorize the VPN connection to get started.
Provides ARM64, 32-bit ARM, and universal packages. Choose ARM64 for most newer devices; choose the universal package when you cannot confirm the architecture.
Suitable for users who want a similar interface and configuration workflow on desktop and Android. Choose ARM64 for mainstream phones and ARM for older 32-bit devices.
Use the Android GUI to manage configurations and proxy connections. This universal package is suitable for users who want to avoid choosing an architecture.
| Package identifier | Supported devices | Recommendation |
|---|---|---|
| arm64-v8a | Recent mainstream Android phones and tablets | Preferred choice |
| armeabi-v7a | Older 32-bit ARM devices | Consider only if ARM64 cannot be installed |
| universal | Devices with an unknown architecture | Wider compatibility; the file is usually larger |
| x86_64 | Some emulators or specialized devices | Not the default choice for regular phones on this page |
OS / IOS
Get Clash Plus from the App Store on iPhone or iPad. After installation, import a subscription link or configuration file and allow the system to add a VPN configuration on the first connection. Then choose a policy group in the client and check the connection status in the system status bar.
For iPhone and iPad. Install it through the App Store, import a subscription, choose a proxy policy, and use the system VPN configuration to route selected traffic.
| Step | Where to find it | Completion signal |
|---|---|---|
| Install the app | App Store | Clash Plus appears on the Home Screen |
| Import configuration | Client subscription or configuration entry | Policy groups and node list appear |
| Authorize the connection | System VPN configuration prompt | The system accepts the network configuration |
| Choose a policy | Client policy group | The target policy is selected |
OS / LINUX
Desktop Linux users can use Clash Verge Rev or FlClash. Debian, Ubuntu, Linux Mint, and similar systems typically use DEB; Fedora, RHEL, and their derivatives typically use RPM. The current GUI packages target AMD64; for other architectures, see the Mihomo core section below.
Provides DEB and RPM packages for common AMD64 Linux desktops. After installation, launch it from the application menu, import a subscription, and configure the system proxy.
This AMD64 DEB package is intended for Debian, Ubuntu, and desktop distributions compatible with DEB package management.
| Distribution family | Common format | Installation method |
|---|---|---|
| Debian / Ubuntu / Linux Mint | DEB | Software installer or dpkg / apt |
| Fedora / RHEL family | RPM | Software center or rpm / dnf |
| Other desktop distributions | Check package-manager compatibility first | Follow the distribution documentation |
| ARM routers or servers | Standalone core archive | Go to the Mihomo section below |
CORE / MIHOMO
The standalone core is intended for servers, routers, containers, and users who maintain YAML configuration themselves. Regular desktop and mobile users should download a GUI client above; those clients already provide configuration import, policy switching, and system proxy controls.
| System | Architecture | Format | Use case | Download |
|---|---|---|---|---|
| Windows | amd64 |
ZIP | 64-bit Windows command-line environment | Download AMD64 |
| Windows | arm64 |
ZIP | Windows on ARM device | Download ARM64 |
| macOS | amd64 |
GZ | Intel Mac command-line environment | Download Intel |
| macOS | arm64 |
GZ | Apple Silicon Mac | Download Apple Silicon |
| Linux | amd64 |
DEB | Debian-family server | Download DEB |
| Linux | amd64 |
GZ | Generic 64-bit Linux | Download AMD64 |
| Linux | arm64 |
GZ | ARM64 servers and routers | Download ARM64 |
| Linux | armv7 |
GZ | 32-bit ARMv7 devices | Download ARMv7 |
| Linux | mips-softfloat |
GZ | MIPS routers using soft-float | Download MIPS |
On Linux and macOS, run uname -m in a terminal. Among common results, x86_64 maps to AMD64, while aarch64 or arm64 maps to ARM64. For routers, also confirm the firmware ABI and floating-point type.
The standalone core has no conventional desktop settings interface. Before running it, prepare a configuration file, working directory, and startup arguments. When running it as a system service, configure permissions, log paths, and startup behavior separately.
DOWNLOAD TRIAGE
First determine whether the issue occurs at the download, installation, configuration import, or system proxy layer. Do not troubleshoot different layers as if they were the same problem.
Most devices running 64-bit Windows 10 or Windows 11 can start with Clash Plus. It includes common subscription import, policy-group, and system proxy controls. For more configuration override options, compare Clash Verge Rev; for a consistent interface across platforms, consider FlClash.
If you are migrating an older environment, the Clash for Windows archive can still restore existing configurations, but a discontinued client is not recommended as a long-term solution for new devices. Before installation, check the system type under “Settings → System → About.”
Click the Apple menu in the top-left corner of the screen and open About This Mac. If the Chip field shows an Apple M series, choose a package marked Apple Silicon, ARM64, or arm64; if the Processor field shows Intel, choose Intel, x64, or x86_64.
Choosing the wrong architecture may cause the app not to launch, trigger an unsupported-system warning, or require an additional translation layer. The safest fix is not repeated reinstallation, but returning to the system information page and checking the chip again.
arm64-v8a targets mainstream 64-bit Android phones and tablets and should usually be the first choice. armeabi-v7a targets older 32-bit ARM devices. The universal package supports a wider range of architectures and is useful when you cannot yet identify the device type.
If the ARM64 package reports incompatibility during installation, check the device architecture and Android version. Do not mistake subscription-import failures or node timeouts for package-architecture issues; if the app installs and launches normally, the installation layer has passed.
Installing the client does not complete its configuration. After the first launch, import a valid subscription link or local configuration file, wait for it to finish parsing, choose an available node in a policy group, and enable the system proxy, TUN, or VPN permission required by the system.
If no policy groups appear, fix the subscription import first. If policy groups exist but the browser still connects directly, check the system proxy. If only some domains fail, inspect rule matching and DNS. Layer-by-layer diagnosis is more effective than reinstalling the client repeatedly.
Usually not. GUI clients such as Clash Plus, Clash Verge Rev, and FlClash integrate core management, configuration import, and system proxy controls into the interface. Regular desktop and mobile users can simply choose the client for their platform.
Standalone Mihomo is suited to servers, software routers, containers, bypass gateways, and environments where configuration files are orchestrated manually. Users should be able to identify the system architecture and understand startup arguments, working directories, listening ports, and service permissions.
The archived package can still migrate existing environments and restore older configurations, but the project is no longer maintained. As operating systems, cores, and configuration formats continue to change, the archived client will not receive ongoing compatibility updates.
For new devices, prefer actively maintained clients such as Clash Plus, Clash Verge Rev, FlClash, or Clash Nyanpasu. Before migrating, record the subscription URL, policy choices, and local overrides, then restore them one by one in the new client rather than assuming every field is fully compatible.