GUI clients and the mihomo core are provided in separate sections
After the legacy Clash core line ended, mihomo (Clash Meta) carried forward protocol, rules, DNS, and TUN capabilities. This page lists maintained graphical clients by operating system, while retaining archived clients and standalone core packages so you can choose by device and processor architecture.
Choose by device
Confirm your operating system first, then check the processor architecture. GUI clients suit everyday desktops and mobile devices; core packages are for servers, routers, containers, or environments where you manage processes yourself.
Windows clients
The installer is best for straightforward deployment; the portable archive suits users who manage the application directory themselves. Current clients primarily target 64-bit Windows, so check the system type on older devices.
A graphical client for everyday desktop use, ideal for managing subscriptions, proxy groups, the system proxy, and connection status in one place. The Windows installer creates a standard application directory, making future updates and uninstalling easier to manage.
A mihomo-based desktop client with built-in configuration import, proxy mode switching, policy selection, system proxy, and TUN controls. A good fit for users who need comprehensive configuration access and regularly inspect rule matches.
A consistent cross-platform interface for users who manage Windows and mobile devices together. The installer handles standard deployment, while the ZIP archive can be extracted to a custom directory; both use the same type of configuration and subscription data.
Another mihomo desktop interface with common controls for subscriptions, proxy groups, connections, and logs. Suited to users familiar with Clash configuration who want to choose between different desktop front ends.
This classic desktop client is now archived and no longer receives ongoing support for new core capabilities or system changes. The installer remains available for migrating old configurations and restoring existing setups; for new installations, choose a maintained client above.
| Check | Recommendation | How to choose |
|---|---|---|
| System | Windows 10 or Windows 11 | Provides broader compatibility with modern system proxy, TUN drivers, and WebView runtimes. |
| Processor | x64 / AMD64 | Open “Settings → System → About” and check the system type. |
| Permissions | Allow administrator approval when installing and enabling TUN | The standard system proxy generally does not require running as administrator continuously. |
macOS clients
Choose Apple Silicon for M-series Macs and x64 for Intel models. If unsure, open “About This Mac” to view the chip or processor name.
Apple Silicon and Intel packages are available. Open the DMG after downloading, move the app to the “Applications” folder, then grant network-related permissions when prompted. You must still import a configuration and choose a policy before first use.
The desktop client offers comprehensive controls for subscriptions, proxy modes, policy groups, DNS, and TUN. The two architecture links in this list are maintained by the same release service; still select the button matching your Mac chip before downloading.
Its cross-platform workflow is close to the Windows and Android versions, making it suitable for users who want a consistent setup across devices. Move the app to the standard Applications folder after installation and approve macOS security prompts on first launch.
An older menu-bar macOS client retained as an archive option. It can help restore an existing workflow or migrate legacy configurations; for long-term use, assess compatibility with newer macOS releases and core capabilities.
| Check | Recommendation | How to choose |
|---|---|---|
| Chip | Apple Silicon or Intel | When “About This Mac” shows an Apple M-series chip, choose ARM64; when it shows Intel, choose x64. |
| Installation | Move the app to the “Applications” folder | Running the app long-term from a temporarily mounted DMG can interfere with updates and permission management. |
| Network permissions | Confirm when prompted by the system | Authorization may be required to enable the system proxy, network extension, or TUN. |
Android clients
Recent phones and tablets usually use ARM64. Older 32-bit devices can use ARM; if you cannot identify the architecture, choose the universal package.
For mainstream 64-bit Android devices, with mobile controls for subscription import, policy selection, and connection management. After installation, approve the connection request in the system VPN permission dialog.
A Clash Meta client for Android that uses mihomo ecosystem configurations directly. ARM64, ARM, and universal packages are available for users who need an architecture-specific download or support for older Android devices.
Its interface closely follows the desktop version, making workflows consistent across systems. Use ARM64 for mainstream devices, ARM for 32-bit devices, and x86_64 mainly for certain tablets or emulated environments.
An Android rule-based proxy client for users familiar with configuration files and policy groups. This site provides the universal package; after installation, import a working configuration and complete VPN authorization yourself.
| Check | Recommendation | How to choose |
|---|---|---|
| Architecture | ARM64 preferred | Most recent Qualcomm, MediaTek, and Samsung mobile platforms use 64-bit ARM. |
| Installation permissions | Grant permission to the current browser or file manager only during installation | After installation, you can disable installation permission for that source in system settings. |
| VPN permission | Confirm on first connection | The Android client uses the system VPN interface to route traffic that requires a proxy. |
iPhone and iPad
Clash Plus is installed through the App Store. After installation, import a configuration and approve the VPN permission prompt to switch connection status and policies from the client.
A graphical client for iPhone and iPad, installed and updated through the system store. It imports configurations, selects policies, and uses the iOS network extension to connect, with clear controls and system permission boundaries.
Official site: clashplus.io
| Check | Recommendation | Details |
|---|---|---|
| Device | iPhone or iPad | Check the App Store listing for the exact iOS version required by the current release. |
| Account | The Apple Account on the device | The App Store manages installation and updates. |
| Permissions | Allow VPN configuration on first connection | Without authorization, the client cannot establish a system-level network connection. |
Linux desktop clients
Debian, Ubuntu, and derivatives usually use DEB; Fedora and RHEL-based distributions can use RPM. For portable operation, consider FlClash’s AppImage.
A mihomo graphical front end for Linux desktops, with in-app configuration, policy, and system proxy management. DEB targets Debian-based distributions; RPM targets Fedora, RHEL, and systems using compatible package formats.
Three desktop package formats are available: DEB, RPM, and AppImage. Standard packages work well with system package managers; AppImage suits users who prefer running from a home directory without writing to system software locations.
| Distribution type | Recommended package | Installation method |
|---|---|---|
| Debian、Ubuntu、Linux Mint | AMD64 DEB | Use a graphical software installer or apt to install the local package. |
| Fedora and RHEL-based systems | x86_64 RPM | Use dnf or a compatible package manager to install it. |
| Other desktop distributions | AppImage | Grant execute permission, run it from a user directory, and manage the desktop entry yourself. |
Standalone core
Mihomo is the successor core to Clash Meta, suited to servers, routers, gateway devices, containers, and environments where you write your own service scripts. Regular desktop and mobile users should prefer the GUI clients above.
| System | Architecture | Format | Use cases | Download |
|---|---|---|---|---|
| Windows | amd64 |
ZIP | 64-bit Windows command line or service wrapper | Download |
| Windows | arm64 |
ZIP | Windows on ARM devices | Download |
| macOS | amd64 |
GZ | Intel processor Macs | Download |
| macOS | arm64 |
GZ | Apple Silicon Mac | Download |
| Linux | amd64 |
DEB | Debian and Ubuntu servers | Download |
| Linux | amd64 |
GZ | Generic 64-bit Linux | Download |
| Linux | arm64 |
GZ | ARM64 servers and routers | Download |
| Linux | armv7 |
GZ | 32-bit ARMv7 router devices | Download |
| Linux | mips-softfloat |
GZ | MIPS devices using the soft-float ABI | Download |
Configuration path
Place the core, configuration files, and runtime data in a directory with clearly defined permissions. Point startup arguments to the actual configuration file instead of relying on the current terminal directory; for service deployments, ensure the service user can read the configuration and write to the cache.
mihomo -d /etc/mihomo -f /etc/mihomo/config.yamlArchitecture check
On servers, x86_64 commonly maps to amd64, while Raspberry Pi and newer routers commonly use aarch64, which maps to arm64. MIPS devices also require the correct endianness and floating-point ABI; the wrong choice usually prevents startup.
uname -m
dpkg --print-architecturePackage selection order
The client name is not the only criterion. Match the operating system, processor, and package format together to avoid downloads that cannot be installed or launched.
Windows, macOS, Android, iOS, and Linux use different package formats. Do not download a mobile package for a desktop, and Linux packages cannot be used directly on Windows.
AMD64 is common on Windows and Linux desktops; Apple M-series Macs and most newer Android devices use ARM64. Older Android devices and some routers may use ARMv7 or MIPS.
EXE, DMG, DEB, and RPM use the system installation workflow; ZIP, GZ, and AppImage are more suited to manual deployment. For automatic updates and desktop entries, prefer a standard installer.
After-install handoff
A completed download only means the program is in place. To route traffic according to rules, import a configuration, choose a mode, and enable the appropriate system-level traffic interception method.
Follow the standard installation process for your system. Run the Windows installer wizard; move the macOS app to “Applications”; open the client after installing the Android APK; on Linux, use the package manager for your distribution.
The configuration defines proxy nodes, policy groups, DNS, and rule order. After importing, verify that it loaded successfully and that the policy groups contain selectable options. The client does not generate usable nodes automatically.
Browsers and most desktop applications can use the system proxy; apps that ignore system proxy settings may require TUN. Understand the permission requirements before enabling it, and avoid having another VPN or proxy app intercept traffic at the same time.
After connecting, visit a familiar site and review the client’s connection records and rule matches. If only some applications fail, check the system proxy, TUN, DNS, and the app’s own proxy settings separately instead of repeatedly changing packages.
Download FAQs
These questions cover the most common branches during downloading. For configuration imports, rule modes, and DNS fields, continue to the guides and configuration reference.
Desktop and mobile users usually choose a graphical client. It combines configuration import, policy group selection, system proxy, TUN, logs, and update controls, so everyday use does not require process maintenance. The Mihomo core is mainly for servers, routers, gateway devices, and users who manage configuration files and service scripts themselves.
Choose EXE when you want an installation wizard and the system to manage the application directory and uninstall entry. ZIP suits users who choose the program location themselves; after extraction, preserve the directory structure and manage shortcuts, updates, configuration, and permissions manually. For most users, the installer takes fewer steps.
Choose Apple Silicon or ARM64 for Macs with M-series chips such as M1, M2, M3, or M4, and x64 for older Intel models. Open “About This Mac” from the Apple menu in the top-left to see the chip or processor name. A wrong architecture may prevent launch or require an additional compatibility layer.
Recent Android phones and tablets usually use arm64, so download ARM64-v8a first. Older 32-bit devices use armeabi-v7a, shown as the ARM version on this page. If you cannot confirm the architecture, choose the client’s universal package; it is usually larger but supports more devices.
The package only provides the client application. After first launch, import a valid configuration or subscription, verify that it parsed successfully, choose a policy group and proxy mode, then enable the system proxy or TUN. If the configuration has no usable nodes or refers to a missing policy group, the client cannot establish the expected connection even when installation succeeded.
Archived clients may still run on some systems with older configurations, which is why the download page retains migration links. However, they will not keep adapting to operating-system changes, new protocol capabilities, or core fields. After restoring a legacy environment, gradually migrate subscriptions, override rules, and local configuration to a maintained client.