Cross-Platform Installers
Choose a graphical client by operating system. Windows, macOS, Android, iOS, and Linux are listed separately, with architecture, package format, and maintenance status shown clearly. For server or router deployments, open the Mihomo kernel section below.
Choose a platform
Click a platform tab to switch installer lists. The selected platform is added to the page URL, so you can copy the link to open the same list directly. The first solid button on each card is the client’s primary installer.
Windows
For everyday desktop proxying, rule switching, and subscription management. On a typical 64-bit PC, choose the x64 installer; for server deployments or command-line use, see the Mihomo section below.
A graphical client designed for common desktop environments, with settings organized in one place for importing subscriptions, selecting policies, and enabling the system proxy. A good first choice when you want a similar workflow across platforms.
A full desktop feature set covers configuration import, proxy-group switching, rule inspection, the system proxy, and TUN. A good fit for Windows users who frequently adjust settings and monitor connection status.
The same client runs on desktop and Android, with a largely consistent interface across systems. The installer suits most users, while the archive is useful if you prefer to manage the application folder yourself.
Provides a desktop graphical interface and common Clash configuration tools, ideal for Windows users who prefer a distinct interface and need to switch quickly between proxy groups and modes.
A classic Windows graphical client retained for opening legacy configuration environments or handling existing installations. For new setups, compare Clash Plus, Clash Verge Rev, and FlClash first.
| Check | Recommended | Details |
|---|---|---|
| System | Windows 10 / 11 64-bit | Modern clients generally target 64-bit desktop systems. |
| Architecture | x64 | Most Intel and AMD desktop processors use the x64 installer. |
| Permissions | Allow system proxy and network components | Enabling TUN or service mode may require administrator approval. |
macOS
Check the chip in About This Mac first. Choose Apple Silicon for Apple M-series Macs and x64 for Intel models. On first launch, follow the system prompts to allow the app and grant network-related permissions.
Provides Apple Silicon and Intel installers for macOS users who want a clear graphical interface for managing subscriptions, policies, and the system proxy. Confirm your Mac’s chip before downloading.
For desktop users who need to inspect rules, switch proxy groups, control the system proxy, and use TUN. If macOS displays a network-extension prompt after installation, complete the requested approval in System Settings.
A graphical client for desktop and mobile, suited to users who want a similar interface across devices. After importing a configuration, select policies and proxy modes in the client.
Retained for older macOS configuration environments and established workflows. For new devices, choose a maintained graphical client and recheck network-extension permissions after system upgrades.
| Check | Choose | Details |
|---|---|---|
| Apple chip | Apple Silicon / ARM64 | For Macs with Apple chips such as M1, M2, M3, and M4. |
| Intel chip | Intel / x64 | For devices that show an Intel processor in About This Mac. |
| First launch | Complete system authorization | Follow the system prompts to allow the app, network extension, or proxy configuration. |
Android
Most recent phones use ARM64. Older 32-bit devices use ARM32; when uncertain, choose the universal installer for Clash Meta for Android.
A graphical Android client for importing subscriptions, switching policies, and routing traffic through the system VPN interface. The current download is the standard ARM64 package.
Provides ARM64, ARM32, and universal installers for users who need a precise architecture match. Choose universal when the phone architecture is unknown; newer devices should generally use ARM64.
A good option for users who use both desktop and Android, with a largely consistent settings structure. ARM64 suits most newer phones; ARM32 targets older 32-bit devices.
An Android rule-based proxy client for users with a compatible configuration who understand proxy groups and rule modes. Import a valid configuration after installation, then allow the system to create a VPN connection.
| Installer | Supported devices | Recommendation |
|---|---|---|
| ARM64 | Recent mainstream Android phones and tablets | Choose this when device information shows arm64-v8a. |
| ARM32 | Older 32-bit ARM devices | Choose this when device information shows armeabi-v7a. |
| Universal | Devices with an unconfirmed architecture | Broader compatibility, but usually a larger installer. |
iOS
Clash Plus is available through the App Store. After installation, import a subscription or configuration, allow the system to add a VPN configuration, then select a policy and check the connection status.
A proxy tool for iPhone and iPad that routes network requests through the system VPN configuration. After installation, import a configuration, choose a proxy group, and connect in the app.
| Check | Requirement | Details |
|---|---|---|
| Device | iPhone or iPad | Check the App Store listing for current device compatibility requirements. |
| Network access | Allow VPN configuration | The system displays an authorization prompt on the first connection. |
| Configuration | Valid subscription or local configuration | Import a configuration after installation before establishing a proxy connection. |
Linux
The graphical clients target common x86_64 desktop distributions. Debian, Ubuntu, and derivatives generally use DEB; Fedora and RHEL-based systems can use RPM.
Suited to common x86_64 Linux desktops, with both DEB and RPM packages. A good first choice if you want a graphical interface for importing configurations, switching policies, and controlling the system proxy.
Provides a Linux desktop graphical interface for x86_64 users running Debian, Ubuntu, or derivatives. This page offers a DEB installer from the fixed download list.
| Package | Common distributions | Architecture |
|---|---|---|
| DEB | Debian, Ubuntu, Linux Mint, and derivatives | AMD64 / x86_64 |
| RPM | Fedora, RHEL-based, and compatible distributions | x86_64 |
| Desktop integration | A graphical session and tray environment are required | Tray behavior may vary between desktop environments. |
Core packages
Mihomo is a command-line kernel for servers, software routers, containers, and automated environments. It does not provide a complete desktop interface; prepare configuration files, startup arguments, and process management yourself. Desktop and mobile users should generally use the graphical clients above.
ZIP archive; extract it and run it from a terminal.
GZ archive; choose according to the chip type.
Supports common server, software-router, and embedded architectures.
| Environment | Common architectures | Package format | Key considerations |
|---|---|---|---|
| Windows server or terminal | AMD64 / ARM64 | Extract ZIP | Specify the configuration directory from a terminal and manage the process yourself. |
| macOS automation environment | Apple Silicon / Intel | Extract GZ | Grant execute permission, then run it from a terminal. |
| Debian-based server | AMD64 | DEB | Works well with system service management for startup and logs. |
| Software routers and embedded devices | ARM64 / ARMv7 / MIPS | GZ | Confirm the CPU instruction set and soft-float requirements first. |
Before you install
Downloading is only the first step. The right architecture, cleanup of old proxy settings, configuration import, and system permissions determine whether the client can route traffic reliably.
For desktop systems, check Windows x64, macOS Apple Silicon or Intel; on Android, check ARM64 or ARM32, or choose universal. A mismatched architecture may stop the installer from running or cause an immediate exit at startup.
Windows service mode, macOS network extensions, and VPN configurations on Android and iOS may trigger system confirmation. Approve them only in the authorization interface provided by the operating system, then return to the client to continue setup.
A newly installed client does not create proxy routes automatically. Import a valid subscription or local configuration, wait for the proxy groups to load, then choose rule, global, or direct mode. Rule mode is usually the best starting point.
Choose an available policy, enable the system proxy or VPN mode, and visit a familiar website to verify DNS resolution and connectivity. If the network becomes completely inaccessible, disable routing first, then check the subscription, DNS settings, port conflicts, and other proxy tools.
Download FAQ
This section covers frequent questions about client selection, architecture checks, first-run authorization, and connection problems after installation.
For a similar workflow across popular desktop and mobile platforms, start with Clash Plus. Windows and macOS users can also choose Clash Verge Rev or FlClash; Android users can select Clash Meta for Android based on their device architecture. Archived clients are mainly for existing setups and are not recommended as the default for new devices.
The graphical clients on this page mainly provide x64 installers for common 64-bit Windows devices. Most PCs with Intel or AMD desktop processors should use x64. Open the Mihomo section for an ARM64 archive only when you specifically need a command-line kernel and have confirmed ARM hardware.
Open the system menu in the top-left corner, select About This Mac, and check the chip or processor information. Choose Apple Silicon or ARM64 for an Apple M-series chip, and Intel or x64 for an Intel processor. If connection fails after installation, check network-extension and proxy permissions in System Settings.
Most recent Android phones use ARM64, corresponding to arm64-v8a. Older 32-bit devices can use ARM32, corresponding to armeabi-v7a. If the architecture is unknown, use the universal version of Clash Meta for Android; it supports more devices but is usually larger.
Mihomo is a command-line kernel for servers, routers, containers, and automated deployments. You must prepare configuration files, set startup arguments, and manage the runtime user and logs yourself. Graphical clients combine configuration management, system proxy controls, and visual tools, so most desktop and mobile users should choose one directly.
After installing the client, import a valid configuration or subscription, wait for proxy groups to load, select a policy, and enable the system proxy or VPN mode. If the switch says connected but websites remain unreachable, check the subscription expiry, node status, DNS resolution, proxy mode, system time, and port conflicts with other proxy programs.