DOWNLOAD DIRECTORY
Choose a platform by operating system first, then download the file matching your processor architecture. Desktop and mobile users should start with the GUI clients; server, router, and automation users can go straight to the Mihomo core section.
WINDOWS CLIENTS
Suitable for Windows 10 and Windows 11. Choose the installer for everyday use; use FlClash's compressed archive when you want to manage the program directory yourself.
A GUI client for everyday desktop use, with configuration import, proxy-group switching, system proxy controls, and TUN mode. Suitable for Windows users who prefer to manage core settings through a clear interface.
A Mihomo-based desktop client with a broad set of settings for managing subscriptions, rule modes, the system proxy, and TUN configuration. This page provides a Windows x64 installer.
Keeps a similar layout across multiple systems, making it suitable for users who work on both computers and Android devices. On Windows, choose the installer or download the archive and manage the extracted files yourself.
Provides desktop management for subscriptions, proxy groups, connections, and logs, for users who prefer an independent interface layout. The current Windows download targets common x64 systems.
A classic Windows GUI client retained for legacy environments, existing configuration compatibility, and historical workflows. For new installations, prefer a client that is still maintained.
| Item | Recommendation | Details |
|---|---|---|
| Operating system | Windows 10 / 11 | Keep system components and security updates current and functional. |
| Processor architecture | x64 | The Windows GUI downloads on this page primarily target common 64-bit systems. |
| Installation permissions | Permission to install desktop applications | Administrator privileges may be required to enable TUN or service mode, or to modify system network settings. |
| Configuration preparation | Subscription link or local YAML | A valid configuration must still be imported before the client can establish a connection. |
MACOS CLIENTS
Before downloading, check the chip type in About This Mac. Choose Apple Silicon for M1, M2, M3, M4, and other M-series Macs; choose Intel for older Macs with Intel processors.
Provides a macOS GUI and common proxy controls. Select the file matching your chip type; Apple Silicon and Intel installers should not be interchanged based only on the operating system name.
Suitable for users who want to manage subscriptions, proxy policies, rule modes, and network interception settings in one place on macOS. Download links follow the available release list.
Suitable for users who want similar workflows across macOS, Windows, Linux, and Android. Import a subscription from the configuration page, then choose a proxy policy on the proxy page.
Retained for existing macOS environments, legacy configuration migration, and historical workflows. Since the project is no longer maintained, new installations should use a maintained client above.
| Item | Selection method | Details |
|---|---|---|
| Apple Silicon | M-series chip | The Chip field in About This Mac shows the Apple M-series name. |
| Intel | Intel processor | Older Macs show an Intel model in the processor information. |
| First launch | Confirm the system security prompt | Move the app to the Applications folder, then follow the system prompts to open it for the first time. |
| Network permissions | Grant permissions as needed | When enabling the system proxy or TUN, macOS may ask you to approve a network extension or confirm an administrator action. |
ANDROID CLIENTS
Most recent phones and tablets use ARM64. Older 32-bit devices can try ARM; when the architecture is unclear, Clash Meta for Android also offers a universal build.
Designed for mainstream 64-bit Android phones and tablets, with mobile configuration import, policy selection, and connection controls. After downloading, open the file and follow Android's installation flow.
Offers ARM64, ARM, and universal installers for Android users who need to match a device architecture. Start with ARM64 on most newer devices and consider ARM for older hardware.
The mobile interface follows a workflow similar to the desktop version, making it suitable for managing multiple devices. Android builds are available for ARM64, ARM, and x86_64.
Another GUI client option for Android, suitable for users already familiar with its configuration workflow. A universal installer is provided for use across different Android devices.
| Installer | Compatible devices | Selection guidance |
|---|---|---|
| ARM64 | Most recent phones and tablets | Usually the first choice for modern Android devices. |
| ARM | Older 32-bit devices | Choose this only when ARM64 cannot be installed and the device is confirmed to be 32-bit. |
| x86_64 | Some emulators and specialized devices | Typical phones do not need this architecture. |
| Universal build | Devices with an unknown architecture | Offers broader compatibility, but the installer is usually larger. |
IOS CLIENT
Install Clash Plus on iPhone and iPad through the App Store. After installation, import a configuration in the app, follow the system prompt to allow the network configuration, then select the policy you want to use.
A GUI client for iPhone and iPad with configuration import, proxy-group switching, and connection controls. App details and further guidance are available alongside the official site at clashplus.io.
| Item | Requirement | Details |
|---|---|---|
| Compatible devices | iPhone / iPad | Check the current system requirements for your device on the App Store page. |
| Installation | App Store | Open the store page and complete installation through the standard system flow. |
| Network configuration | Allow system authorization | On the first connection, iOS asks you to confirm adding the network configuration. |
| Client configuration | Subscription or local configuration | After importing, update the content first, then select a proxy group and connect. |
LINUX CLIENTS
Choose deb or rpm according to your desktop distribution's package system. Linux GUI downloads target common AMD64 desktop environments; server and router users should see the Mihomo core section.
Suitable for Linux users who want a full desktop interface for managing subscriptions, proxy groups, and system network settings. Choose deb for Debian, Ubuntu, and similar distributions; rpm is suitable for Fedora, RHEL-based distributions, and similar systems.
Suitable for Linux desktop users who prefer a consistent cross-platform workflow. In addition to deb and rpm, an AppImage is available for distributions that support it and users who want to manage the application themselves.
| Format | Common distributions | Installation notes |
|---|---|---|
| deb | Debian、Ubuntu、Linux Mint | Install with the system software installer or your distribution's package manager command. |
| rpm | Fedora, RHEL-based systems, openSUSE | Choose the rpm file matching the system's package management system. |
| AppImage | Various desktop distributions | Make the file executable, then run it; the user manages updates and file location. |
| Desktop architecture | AMD64 / x86_64 | The GUI clients in this section primarily target common 64-bit desktop processors. |
MIHOMO CORE
Mihomo is intended for servers, routers, bypass routers, containers, and automated deployments. You must prepare the YAML configuration, startup command, directory permissions, and process management yourself. Most computer and phone users should choose a GUI client above.
| System | Architecture | Format | Use case | Download |
|---|---|---|---|---|
| Windows | AMD64 | zip | Common 64-bit Windows servers or command-line environments. | Download AMD64 |
| Windows | ARM64 | zip | Windows devices with ARM64 processors. | Download ARM64 |
| macOS | Intel | gz | Command-line deployment on Macs with Intel processors. | Download Intel |
| macOS | Apple Silicon | gz | Macs with Apple M-series chips. | Download Apple Silicon |
| Linux | AMD64 | deb | 64-bit Linux systems using the deb package system. | Download deb |
| Linux | AMD64 | gz | A generic compressed core for users who want to arrange directories and services themselves. | Download AMD64 |
| Linux | ARM64 | gz | Common 64-bit ARM servers, development boards, and router devices. | Download ARM64 |
| Linux | ARMv7 | gz | Some 32-bit ARMv7 devices and older router hardware. | Download ARMv7 |
| Linux | MIPS softfloat | gz | Specific MIPS router devices using software floating point. | Download MIPS |
Prepare a YAML file readable by the current core and check references among ports, DNS, proxy nodes, proxy groups, and rule sections.
Set stable directories for the core, configuration, cache, and logs, and ensure the running process has the required read and write permissions.
On servers, use the system service manager to configure startup, stopping, and automatic restarts; on routers, arrange startup scripts according to the firmware's capabilities.
System proxy, transparent proxy, and TUN operate at different interception layers. Choose based on the device role and network topology rather than stacking them all together.
BEFORE INSTALLATION
When filenames look similar, confirm the system, processor, and package format before installing. This helps prevent startup problems caused by architecture mismatches, incorrect package formats, or conflicts with older configurations.
Windows, macOS, Android, iOS, and Linux use different installation methods. Do not choose a file based only on the client name; open the matching platform tab and download from its listed entry.
AMD64 or x64 is common on Windows and Linux desktops; newer Macs generally use Apple Silicon; mainstream Android devices usually use ARM64. Servers and routers may also use ARMv7 or MIPS.
Windows installers generally use exe, macOS uses dmg, Android uses apk, and Linux desktops commonly use deb, rpm, and AppImage. Compressed cores must be extracted and run from the command line.
Before migrating from an older client, record the subscription URL, override rules, DNS settings, ports, and proxy preferences. Restoring items individually after installing the new client makes troubleshooting easier than overwriting the old directory.
DOWNLOAD FAQ
This section covers client selection, system architecture, configuration import, and core use cases. For a fuller first-time setup walkthrough, continue to Getting Started.