DOWNLOAD DIRECTORY
Confirm your operating system and CPU architecture, then choose the matching package. Use a GUI client on desktops and mobile devices; deploy the Mihomo core directly on servers, routers, and automated environments.
PLATFORM PACKAGES
Platform tabs sync with URL anchors, so you can save or share the current selection. The first solid button on each client card is the primary package for that device; other architectures and archive formats appear as additional options.
WINDOWS
For x64 desktop environments running Windows 10 or Windows 11. Use a GUI client for everyday use; after installation, import a subscription, choose a policy group, and enable the system proxy or TUN mode as needed. On company-managed devices, confirm that your account can run the installer and create a network adapter.
Provides subscription imports, policy switching, system proxy controls, and common settings in one place for Windows users who want to manage everyday connections through a unified interface.
A Mihomo-based desktop GUI with settings for subscriptions, rules, system proxy, TUN, overrides, and external control.
A cross-platform GUI that keeps its interface and workflow similar across desktop and mobile, suited to users who want a consistent setup on multiple devices.
A desktop Clash client for configuration management, proxy-group switching, and Mihomo settings. Best for users who understand the difference between rule mode and the system proxy.
An archived client kept available for older-device migration, configuration export, and restoring existing workflows. New installations should use a maintained client instead.
MACOS
Before downloading, open About This Mac from the Apple menu and check whether the device has an Apple M-series chip or an Intel processor. Choose ARM64 for Apple M1, M2, M3, M4, and newer Macs; choose x64 for older Intel Macs. On first launch, macOS may ask you to approve network extensions, VPN configuration, or background-item permissions.
Provides installers for Apple Silicon and Intel processors, with subscription imports, policy switching, system proxy controls, and common network settings for macOS.
A Mihomo-based desktop client with subscription configuration, rule overrides, system proxy, and TUN support for users who need to inspect rules and logs.
A cross-platform client for setups that include macOS and Android. Subscriptions, policy groups, and connection controls follow a consistent interface.
An archived macOS menu-bar client kept for existing users restoring an older environment or migrating configurations. New installations should favor a maintained client.
ANDROID
Most recent Android phones and tablets use ARM64, so start with the ARM64 package. Older 32-bit devices use the ARM version; if you cannot identify the architecture, the Universal build of Clash Meta for Android offers broader coverage. After installation, accept the system VpnService permission; a VPN indicator appears in the status bar while connected.
For mainstream 64-bit Android devices, with subscription imports, policy switching, and a system VPN connection entry point. Grant VPN permission when prompted to create the local tunnel.
An Android client powered by Mihomo, offering ARM64, ARM, and Universal packages. Choose Universal for older devices or when the architecture is unknown.
A cross-platform GUI for users who want a similar interface on Android and desktop. Check the device architecture before downloading; most current devices use ARM64.
An Android network proxy client that imports compatible configurations and routes traffic through the system VPN interface. Best for users familiar with its configuration format and rules.
IOS
On iOS, get Clash Plus from the App Store. After installation, import a subscription link or local configuration; on the first connection, follow the system prompt to allow adding a VPN configuration. Once connected, Control Center or the status bar shows the system VPN status. Switch policies and update subscriptions in the client.
A Clash-style client for iPhone and iPad with subscription imports, policy-group switching, rule processing, and system VPN connectivity. On first launch, import a configuration, choose a policy, and approve VPN access.
LINUX
Linux desktop users can choose DEB or RPM based on their distribution’s package system. Ubuntu, Debian, Linux Mint, and similar distributions typically use DEB; Fedora, RHEL, and related distributions typically use RPM. For a standalone file, choose FlClash AppImage. The graphical packages below target AMD64 desktops.
A Mihomo GUI for Linux desktops. DEB and RPM packages integrate with the distribution’s installation workflow, making it easier to add an application menu entry and manage desktop integration.
Provides DEB, RPM, and AppImage formats for Linux desktops. AppImage is suitable for users who do not want to modify the system package database and prefer to manage the file and execute permissions themselves.
MIHOMO CORE
Mihomo is a command-line core for servers, software routers, containers, gateway devices, and environments where you maintain YAML configuration yourself. It does not provide a full desktop interface; users manage startup arguments, configuration paths, logs, and the service process. Most desktop and mobile users should choose a GUI client above.
The operating system and CPU architecture must both match. AMD64 corresponds to common x86_64 computers and servers; ARM64 is common on 64-bit ARM devices; ARMv7 is used by some 32-bit ARM devices; MIPS soft-float is only for matching MIPS soft-float environments.
| System | Architecture | Format | Use case | Download |
|---|---|---|---|---|
| Windows | AMD64 | ZIP | Common 64-bit Intel / AMD computers | Download |
| Windows | ARM64 | ZIP | Windows on ARM devices | Download |
| macOS | Intel | GZ | Macs with Intel processors | Download |
| macOS | Apple Silicon | GZ | Macs with Apple M-series chips | Download |
| Linux | AMD64 | DEB | Package-managed Debian and Ubuntu installations | Download |
| Linux | AMD64 | GZ | Manual deployment with a standalone binary | Download |
| Linux | ARM64 | GZ | 64-bit ARM servers and router devices | Download |
| Linux | ARMv7 | GZ | Some 32-bit ARM devices | Download |
| Linux | MIPS soft-float | GZ | Matching MIPS soft-float router environments | Download |
SELECTION GUIDE
If a download fails or the app will not start after installation, the usual cause is not the configuration itself but a mismatch in operating system, CPU architecture, or package format. The three checks below explain how to narrow it down.
A GUI client brings subscription management, policy-group selection, system proxy controls, logs, and core settings together for personal computers and phones. Mihomo runs from the command line, with configuration files and service status managed separately, making it better suited to servers, routers, containers, and automation scripts.
If you want to import a subscription and connect immediately, download the GUI for your platform. If you want a gateway to run continuously under file-based control, choose the Mihomo core instead.
Common Windows and Linux desktop labels include x64, x86_64, and AMD64; in this download context, they generally refer to the same 64-bit platform. Apple M-series Macs use ARM64, Intel Macs use x64, and most Android devices use ARM64, while older devices may use 32-bit ARM.
Architecture is separate from the operating system version. Windows 11 does not necessarily mean x64, and macOS runs on both Intel and Apple Silicon, so read the processor name in system information.
Windows EXE, macOS DMG, and Android APK are standard installation formats for their platforms. Linux DEB targets Debian-based distributions, RPM targets Fedora, RHEL, and similar distributions, while AppImage runs as a single file. ZIP and GZ packages usually require manual extraction and placement.
Package formats integrate more easily with the desktop; archives are better for manual deployment. Choose based on your system’s software management workflow and maintenance habits.
| Architecture label | Common devices | Choose this label | How to check when unsure |
|---|---|---|---|
| x64 / x86_64 / AMD64 | Most Windows PCs, Intel Macs, and common cloud servers | x64 or AMD64 | Check “System type” in system information or run uname -m |
| ARM64 / aarch64 | Apple M-series Macs, ARM servers, and mainstream Android devices | ARM64 | Check the chip name or run uname -m |
| ARMv7 / armeabi-v7a | Some older Android and embedded devices | ARM or ARMv7 | Use a device-information tool to check the ABI |
| MIPS soft-float | Specific legacy routers and embedded systems | MIPS soft-float | Check the device firmware and CPU architecture documentation |
AFTER INSTALL
A client launching successfully only confirms that the program is compatible with the system. A working connection still requires a valid configuration, the correct policy, and network permissions.
Copy the complete subscription URL and add a remote configuration from the client’s configuration or subscription page; you can also import a local YAML file. Run one manual update after importing and confirm that the configuration appears without format errors. Subscription URLs are sensitive and should not be shared on public pages or in log screenshots.
Rule mode decides whether traffic goes direct or through a proxy according to the configured rule order. Global mode usually sends traffic through one proxy policy, while direct mode temporarily bypasses the proxy. In rule mode, open the policy group and select a working node or automatic selection group.
Common desktop options include the system proxy and TUN. The system proxy mainly affects apps that follow system settings; TUN covers more traffic but requires the appropriate permissions. Android and iOS create a local tunnel through the system VPN interface and show an authorization prompt on first connection.
If a webpage will not open, check the client log for subscription parsing, DNS, rule matching, or connection errors. If a rule matches DIRECT, inspect the routing logic; if a proxy policy matches but the connection fails, check the node, network conditions, and system time. Following the log stages is more effective than repeatedly reinstalling the client.
DOWNLOAD FAQ
These answers cover client selection, device architecture, first connections, and archived-software migration. For configuration syntax, DNS, and rules and routing, continue to the advanced configuration guide.
Start by choosing a GUI for your operating system. For Windows, macOS, Android, and iOS, check Clash Plus first; Linux desktop users can choose Clash Verge Rev or FlClash. GUI clients provide subscription imports, policy-group selection, connection controls, and logs for most everyday devices.
The Mihomo core has no full desktop management interface and runs mainly through YAML configuration, command-line arguments, and an external control panel. Download the core directly only for servers, routers, containers, or automated deployments.
Open About This Mac from the Apple menu. If the Chip field shows Apple M1, M2, M3, M4, or a later Apple chip, choose an Apple Silicon or ARM64 installer; if the Processor field shows Intel, choose an Intel or x64 installer.
CPU architecture and the macOS version are separate details. Two Macs can run the same system version but require different installers because their chips differ.
ARM64 targets 64-bit ARM devices and is the most common architecture on recent Android phones and tablets. ARM packages generally target older 32-bit devices. Universal builds include the components needed for multiple architectures, offering broader compatibility but usually a larger file size.
For a newer device, start with ARM64. If installation reports an architecture mismatch, check the device ABI and try another version. The Universal build of Clash Meta for Android is available when the architecture cannot be confirmed.
First confirm that the subscription updated successfully and that a working policy is selected in the policy group. Then check whether the system proxy, TUN, or mobile VPN permission is enabled. Importing a configuration alone does not ensure that the client intercepts all traffic.
If it still fails, identify the stage shown in the logs: subscription parsing errors point to the configuration; DNS errors point to resolution settings; a DIRECT match points to routing order; proxy connection errors require checking the node, network conditions, and system time.
The page keeps archived entries for restoring older environments and migrating existing configurations, but neither is recommended for new installations. Long-term clients must adapt to operating-system changes, core updates, and network-permission changes, so new deployments should use a maintained client.
Back up subscription URLs, local configurations, rule overrides, and necessary interface settings before migrating. After migration, verify more than whether the client launches: test policy groups, rule matches, and system proxy status.
The Mihomo core is best for users comfortable with the command line, YAML configuration, and service management. Operators must specify the configuration path, listen port, log location, and service account, then configure a daemon or startup task for the operating system.
If your main goal is to import a subscription, switch nodes, and click Connect on a computer or phone, a GUI client is a better fit. GUI clients generally include or manage the required core while providing visual logs, configuration updates, and system proxy controls.