DOWNLOAD DEVICE ENUMERATION
Find a client by operating system, CPU architecture, and package format. Prefer GUI clients that are still maintained; use the Mihomo core section for servers, routers, and command-line environments.
[01] Confirm your operating system
[02] Confirm your CPU architecture
[03] Choose a package format
[04] Import your configuration after installation
PLATFORM SELECTOR
Choose a platform first, then select the file that matches your chip architecture and installation method. Version details appear only when the manifest returns valid data.
DEVICE 01 / WINDOWS
The current downloads target 64-bit Windows. Use the installer for a standard desktop setup; choose the FlClash ZIP package to run from a separate folder. Before installing, exit older clients that occupy proxy ports. During upgrades, keep the configuration folder and close running processes.
Suitable for standard Windows desktop environments. The installer adds the application directory and shortcuts; after the first launch, you can import a subscription URL or local YAML configuration.
A desktop GUI client with system proxy, TUN, subscription management, proxy group selection, and rule viewing. This link provides the Windows x64 installer.
Both installer and portable ZIP packages are available. The installer suits a fixed device; extract the ZIP package to run it and manage the program and configuration from a chosen folder.
A desktop GUI client for managing configurations, proxy modes, and proxy groups. This link provides the Windows x64 installer.
The archived link is provided for restoring existing environments, migrating older configurations, and compatibility work. For new installations, choose a Windows client that is still maintained.
| Check | Requirements and selection | Installation notes |
|---|---|---|
| Processor | x86-64 / AMD64 | The Windows GUI clients currently listed here are provided as x64 packages. |
| System | Supported 64-bit Windows desktop system | If system components are outdated, complete Windows updates before installing. |
| Permissions | Standard use; TUN installation may require administrator approval | Confirm the system authorization prompt only when enabling network-driver features. |
| Upgrade | Close the old process before reinstalling | Record the current configuration folder and subscription URL before upgrading. |
DEVICE 02 / MACOS
Before downloading, open “About This Mac” or “System Information” to check the chip type. Choose Apple Silicon for Apple M-series chips and Intel for Intel processors. When opening the downloaded app for the first time, follow the system prompts to confirm its source and network permissions.
Separate installers are provided for Apple Silicon and Intel. After confirming the chip, download the matching DMG, drag the app to the Applications folder, and launch it from there.
A macOS GUI client with system proxy controls and configuration management. Select the link matching your chip, then launch the app from the Applications folder after installation.
A desktop GUI client for managing configuration files, proxy groups, and proxy toggles. The two chip links are resolved separately from the download manifest; choose the entry matching your device.
The archived link is kept for older devices and existing configuration migrations. For new deployments, use a macOS client that is still maintained to reduce compatibility issues after system upgrades.
| Device information | Download choice | Installation step |
|---|---|---|
| Apple M-series | Apple Silicon / ARM64 | Open the DMG and drag the app to Applications. |
| Intel processor | Intel / x64 | Use the Intel link to avoid selecting the wrong architecture. |
| First launch | Confirm the system security prompt | Follow the system prompts to open the app and grant network permissions. |
| System proxy | Requires changes to network proxy settings | Turn off the system proxy before quitting the client to prevent leftover settings. |
DEVICE 03 / ANDROID
Most recent Android phones and tablets use arm64-v8a. Choose armeabi-v7a for older 32-bit ARM devices; if you cannot confirm the architecture, use the universal package for Clash Meta for Android. Keep your subscription URL and any required local override configuration before upgrading.
The current download is an arm64-v8a package for most recent Android devices. After installation, approve the VPN connection in the system authorization dialog, then import your configuration.
ARM64, 32-bit ARM, and universal packages are available. Choose a dedicated package when the architecture is known; use the universal package when device information is unclear.
ARM64, 32-bit ARM, and x86_64 packages are available. Phones and tablets usually use ARM64; older ARM devices use the 32-bit package, while some emulators use x86_64.
A general Android client option for devices that need a universal package. After installation, import a subscription or local configuration in a format supported by the client.
| Architecture | Common devices | How to choose |
|---|---|---|
| arm64-v8a | Most recent phones and tablets | Choose this first when the device uses 64-bit ARM. |
| armeabi-v7a | Older 32-bit ARM devices | Choose this only when the system or hardware is confirmed to be 32-bit. |
| x86_64 | Some emulators and specialized devices | Choose according to the emulator’s virtual CPU architecture. |
| universal | Devices with unclear architecture information | The file is usually larger, but reduces the chance of choosing the wrong architecture. |
DEVICE 04 / IOS
Install Clash Plus through the App Store on iPhone or iPad. After installation, add a subscription or configuration in the app and approve the system VPN permission when connecting for the first time.
A client for iPhone and iPad. View the app details and install it through the App Store; product and platform information is available at clashplus.io.
| Check | Process |
|---|---|
| Device | Open the app’s details page in the App Store on your iPhone or iPad. |
| System permissions | When connecting for the first time, follow the system prompt to approve VPN configuration access. |
| Import configuration | Copy the complete subscription URL, or import a configuration file using the method supported by the client. |
| Connection check | Choose a proxy node, start the connection, and check access to the target website. |
DEVICE 05 / LINUX
For graphical desktops, choose Clash Verge Rev or FlClash. Debian, Ubuntu, and derivatives generally use DEB; Fedora and RHEL-based distributions generally use RPM. The current GUI downloads target AMD64 desktop devices.
AMD64 DEB and RPM packages are available. Choose the file matching your distribution’s package system, then launch the client from the desktop menu or terminal.
This link provides an AMD64 DEB package for graphical desktop distributions using the Debian package system. Confirm that the system architecture is AMD64 before installing.
| Distribution type | Package | Notes |
|---|---|---|
| Debian / Ubuntu based | AMD64 DEB | Install through the system package manager, which can also create the desktop entry. |
| Fedora / RHEL based | x86_64 RPM | Clash Verge Rev provides a matching RPM option. |
| CPU architecture | AMD64 / x86_64 | The current GUI section does not provide a Linux ARM download. |
| Servers and routers | Standalone Mihomo core | Go to the core section below and choose the compressed file matching the device architecture. |
CORE PACKAGE TABLE
The standalone core is intended for servers, routers, containers, and command-line deployments. Desktop and mobile users should prefer the GUI clients above.
| System | Architecture | Format | Environment | Download |
|---|---|---|---|---|
| Windows | AMD64 | ZIP | 64-bit Windows command-line environment | [Download] |
| Windows | ARM64 | ZIP | Windows on ARM devices | [Download] |
| macOS | Intel / AMD64 | GZ | Intel Mac command-line environment | [Download] |
| macOS | Apple Silicon / ARM64 | GZ | Apple M-series devices | [Download] |
| Linux | AMD64 | DEB | Debian-based servers | [Download] |
| Linux | AMD64 | GZ | Generic x86-64 servers | [Download] |
| Linux | ARM64 | GZ | 64-bit ARM servers and routers | [Download] |
| Linux | ARMv7 | GZ | 32-bit ARMv7 routers | [Download] |
| Linux | MIPS soft-float | GZ | MIPS devices using the soft-float ABI | [Download] |
ARCH CHECK
On Linux, use uname -m to check the architecture. Common results include x86_64 for AMD64 and aarch64 for ARM64. Routers also require checking the ABI used by the firmware.
CONFIG PATH
Before starting a standalone core, define the configuration path, Geo data location, log output location, and external control port. Use spaces for YAML indentation and keep list levels consistent.
PROCESS CONTROL
For long-running deployments, use the system service manager to handle startup, stopping, and restarts. Before updating the core, stop the old process, confirm that the configuration parses correctly, and then restore the service.
PACKAGE DECISION TABLE
Whether a file installs depends mainly on the operating system, CPU architecture, and package format. Similar names do not mean packages can be used across platforms.
First distinguish Windows, macOS, and Linux. Each system uses different executable formats, permission models, and installation processes, so do not choose solely by client name.
AMD64 is common on Windows and Linux, Apple M-series chips use ARM64, and Intel Macs use x64. The wrong architecture typically causes startup failures or installation rejection.
Use the Windows installer for a fixed setup and ZIP for a separate folder; macOS uses DMG; Linux uses DEB or RPM according to the distribution.
A running client may lock files and proxy ports. Before upgrading, disable the system proxy and close the old process while keeping the subscription URL, local rules, and override configuration.
Recent devices generally use arm64-v8a, while older 32-bit devices use armeabi-v7a. Check an emulator’s virtual device settings rather than inferring the architecture from the computer’s processor.
Clash Meta for Android provides a universal option. Its broader architecture coverage suits devices whose ABI cannot be confirmed from system information.
Open the Clash Plus listing in the App Store and install it. When connecting for the first time, follow the system prompt to approve VPN configuration access.
Importing a subscription does not establish a connection by itself. Select a policy or node, start the connection, and check the client log and target website access.
DOWNLOAD FAQ
Common guidance for package formats, chip architectures, archived clients, and standalone cores.
Choose the installer for Start menu shortcuts, uninstall records, and standard upgrades. Choose the FlClash portable ZIP to keep the program in a specified folder, maintain multiple independent environments, or control file locations manually. Whichever format you choose, exit the old process before upgrading to prevent files from being locked.
Open the Apple menu in the top-left corner of the screen, then select “About This Mac” or “System Information.” Choose Apple Silicon when the chip field shows an Apple M-series chip, and Intel when the processor field shows Intel. The wrong architecture may prevent the app from launching, so checking the chip is faster than reinstalling repeatedly.
arm64-v8a targets 64-bit ARM devices and is the most common choice for recent phones and tablets. armeabi-v7a targets older 32-bit ARM devices. The universal package supports a broader range of architectures and suits devices whose ABI cannot be confirmed. Some Android emulators use x86_64, so choose according to the emulator settings.
Clash Plus offers clients for Windows, macOS, Android, and iOS, making it suitable for users who want a similar workflow across desktop and mobile devices. Still check the system and architecture: Windows uses the x64 installer, macOS distinguishes Apple Silicon from Intel, Android currently offers an ARM64 package, and iOS installs through the App Store.
Archived links for both are retained for restoring older environments, migrating existing configurations, and specific compatibility cases. Both are no longer maintained, so choose a client that is still updated for new devices. During migration, import the base subscription first, then verify that rules, DNS, the external control port, and TUN settings are recognized correctly.
Usually not. GUI clients manage their required core and provide interfaces for importing configurations, selecting policies, controlling the system proxy, and viewing logs. Standalone Mihomo files are mainly for servers, routers, containers, and command-line deployments, where you manage configuration paths, startup arguments, process permissions, and autostart yourself.
NEXT BOOT STAGE
After launching the client, import the subscription, update the configuration, select a proxy node, enable the system proxy or TUN, then verify the connection through logs and actual access results. If configuration parsing fails, check YAML indentation and field nesting first instead of changing several network settings at once.