Choose a Clash GUI client or the Mihomo core based on your operating system and CPU architecture. Version slots appear only when the manifest returns valid values. Before downloading, verify the OS, chip architecture, and package format.
A client’s package for one operating system cannot be used on another. After choosing a platform, read the system requirements and select the download that matches your device’s chip.
For standard Windows desktop environments. The Windows GUI packages listed here are primarily x64; no additional architecture entry is provided unless it appears in the release list.
A GUI client for everyday Windows use. Import configurations, switch policies, manage the system proxy, and inspect rule matches from the interface.
Uses a desktop GUI to manage Mihomo configurations. Suitable for Windows users who need rule modes, policy-group switching, configuration overrides, and system proxy control.
A cross-platform GUI client. On Windows, use the standard installer or run the ZIP archive from a separate directory to keep different local configuration environments isolated.
Provides desktop configuration management, policy-group controls, and proxy status management. Best suited to users familiar with subscriptions, rule modes, and system proxy behavior.
An archived client for restoring existing installations or running compatibility tests. For new environments, use a maintained client and back up configurations, scripts, and overrides before migrating.
For Apple M-series chips, choose ARM64 or Apple Silicon; for Intel processors, choose x64. On first launch, macOS may ask you to approve permissions related to networking and the system proxy.
Provides a macOS GUI for importing configurations and controlling policies. Check the chip type in About This Mac before downloading to avoid mixing Apple Silicon and Intel packages.
Manage Mihomo configurations, rule modes, and policy groups. Both architecture entries are maintained in the release manifest; still choose the one matching your Mac’s chip.
A cross-platform interface that keeps workflows familiar across desktop and mobile devices. You must still import a valid configuration and approve proxy permissions after installation.
An archived macOS menu bar client. It can restore an existing environment, but new installations should favor a maintained GUI client to reduce compatibility issues after system upgrades.
Most recent phones use arm64-v8a. Older 32-bit ARM devices use armeabi-v7a. If you cannot identify the architecture, check the device’s processor information or choose the available universal package.
A GUI client for Android mobile devices. Import a configuration after installation, grant local VPN access when prompted, then choose a policy group and connection mode.
An Android client in the Mihomo ecosystem with configuration import, policy-group selection, and local VPN takeover. Choose a smaller package for a known architecture or use the universal package.
A cross-platform interface for users who work across desktop and Android devices. Each APK targets a different CPU architecture; check your device information before installing.
An Android proxy client that imports compatible configurations and routes traffic through the system VPN interface. The universal package is suitable when the exact CPU architecture is unknown.
On iOS, get Clash Plus from its App Store page. Import a configuration after installation and approve VPN configuration access when prompted during the first connection.
A proxy tool for iPhone and iPad. After installation, import content from a subscription link or configuration file, choose a policy, and authorize a system VPN connection.
GUI clients work on Linux systems with a desktop environment. Choose deb for Debian and Ubuntu-based systems, rpm for Fedora and RHEL-based systems, or AppImage for a single-file option.
A Mihomo GUI client for Linux desktops, with subscription, override, rule-mode, and policy-group management. AMD64 deb and rpm packages are provided.
Provides multiple Linux AMD64 package formats. Prefer the format supported by your distribution’s package manager, or choose AppImage for single-file execution.
The Mihomo core is intended for servers, routers, containers, and environments where configuration files are maintained manually. Most desktop and mobile users should use the GUI clients above to manage subscriptions, policy groups, the system proxy, and connection status.
| System | Architecture | Format | Compatibility notes | Download |
|---|---|---|---|---|
| Windows | AMD64 | ZIP | 64-bit Intel / AMD desktop or server environments | Download AMD64 |
| Windows | ARM64 | ZIP | Windows on ARM devices and ARM64 servers | Download ARM64 |
| macOS | Intel | GZ | Macs with Intel processors | Download Intel |
| macOS | Apple Silicon | GZ | Macs with Apple M-series chips | Download Apple Silicon version |
| Linux | AMD64 | DEB | Debian, Ubuntu, and compatible package-management environments | Download DEB |
| Linux | AMD64 | GZ | Generic AMD64 servers, containers, or router environments | Download AMD64 |
| Linux | ARM64 | GZ | 64-bit ARM servers and router devices | Download ARM64 |
| Linux | ARMv7 | GZ | 32-bit ARMv7 routers and embedded devices | Download ARMv7 |
| Linux | MIPS soft-float | GZ | MIPS router devices using the soft-float ABI | Download MIPS |
Before starting the core, prepare a valid, parseable YAML configuration. At minimum, check the listening port, run mode, DNS, proxy nodes, policy groups, and rule fields to avoid indentation errors, duplicate ports, or references to missing policy names.
Server deployments usually need a system service to manage the process. Define the working directory, configuration path, log output, and restart policy. Router deployments should also verify storage, executable permissions, and device architecture.
Windows and Linux commonly use x64 or AMD64; Apple M-series chips use ARM64; Android commonly uses arm64-v8a. Choosing the wrong architecture may cause the installer to refuse to run or exit during startup.
Before upgrading or switching clients, export the subscription URL, override files, rule snippets, and necessary local settings. Data directories and field compatibility vary between clients, so review policy groups and DNS again after migration.
Running multiple proxy clients on one device can cause conflicts between system proxy ports, TUN interfaces, or local VPN connections. During installation and testing, enable only one client at a time and confirm that the previous process has exited.
After importing a configuration, do not check only the connection button. Also verify the current mode, default policy, DNS settings, and rule matches. Establishing a local proxy does not mean every request is assigned to the intended policy.
These answers cover package formats, architecture checks, and choosing between GUI clients and the core. For configuration imports and rule routing, continue with Getting Started and the configuration field documentation.
For regular desktop use, choose the installer. It creates a Start menu shortcut and deploys files through the client’s standard setup flow. Choose FlClash’s ZIP archive if you need a separate directory, multiple test environments, or isolated data directories for different configurations.
Fully extract the portable archive before launching it; do not run it from an archive preview window. Regardless of the format, back up subscriptions, override files, and rule snippets before switching clients.
Open System Settings and go to About This Mac, then check the chip or processor field. Choose ARM64 or Apple Silicon for an Apple M-series chip, and x64 or Intel for an Intel processor. A package mismatch may prevent the app from opening or require an additional translation environment.
When migrating from an older Intel Mac to an Apple Silicon device, do not reuse the old package. Configuration files can usually be migrated separately, but the application itself should be downloaded again for the correct architecture.
arm64-v8a targets most recent 64-bit Android phones and tablets; armeabi-v7a is for older 32-bit ARM devices; universal packages include broader architecture support and are therefore usually larger. A device that accepts a universal package may not support every architecture-specific package.
If you cannot identify the architecture, check the processor ABI in the device information. Emulators and some specialized devices may use x86_64; in that case, choose a package explicitly marked x86_64.
Debian, Ubuntu, Linux Mint, and compatible distributions generally use deb; Fedora, RHEL, Rocky Linux, AlmaLinux, and similar systems generally use rpm. Installing through the distribution package manager makes file locations and uninstallation easier to manage.
AppImage suits desktop environments that prefer a single-file application; after downloading, grant it executable permission. The GUI clients on this page primarily target AMD64 or x86_64. ARM Linux devices should consider the Mihomo core below and configure the runtime environment manually.
Most Windows, macOS, Android, iOS, and Linux desktop users should choose a GUI client. The interface handles configuration imports, policy-group switching, system proxy control, connection logs, and basic settings, reducing the need to maintain startup arguments manually.
The Mihomo core is suited to servers, routers, containers, and automated deployments. You must provide the YAML configuration, working directory, system service, and logging plan, while handling permissions, ports, and the process lifecycle yourself.
Archived packages can restore existing environments, read older configurations, or support compatibility testing, but they will not keep up with operating systems, core interfaces, or new configuration fields. For a fresh installation, choose a maintained client.
When migrating from Clash for Windows or ClashX Meta, first keep a copy of the original data directory, then import the subscription again in the new client. If you use scripts, override files, or custom rules, check field compatibility one by one instead of overwriting the new client’s data directory.