Choose a client by operating system, processor architecture, and installer format. Use a GUI client first on desktops and phones; servers, transparent gateways, and automated environments can use the Mihomo core directly.
Platform tabs are synced to the page URL. Copy a link with a platform anchor and reopening it will show the corresponding system. Each card lists the primary installer first, followed by architecture-specific or alternate formats.
Users on Windows 10 or Windows 11 should generally choose a 64-bit installer. After installation, import a subscription and choose between system proxy and TUN mode based on the applications you need to route.
A GUI client for everyday desktop use, combining subscription imports, policy-group switching, system proxy controls, and connection logs. The Windows installer suits users who prefer a standard setup process.
A mihomo-based desktop client with configuration management, proxy-mode switching, rule inspection, and TUN settings. Suited to Windows users who need finer control over core parameters and multiple configurations.
Its cross-platform interface stays consistent, making it useful for users who manage both computers and Android devices. The installer handles standard deployment, while the ZIP package makes it easy to choose a directory and keep a separate configuration.
Provides desktop configuration management, proxy-group controls, and core management. Its information-dense interface suits users who already understand rule modes, policy groups, and system proxy behavior.
Kept for devices that need compatibility with older configurations and established workflows. This client is archived and is not recommended as the default for new installations; before migrating, export the current configuration and record port settings.
| Item | Recommendation | Details |
|---|---|---|
| System | Windows 10 / 11 64-bit | Newer system components provide more complete support for desktop interfaces, service mode, and TUN drivers. |
| Processor | x86-64 | The Windows GUI installers on this page target common 64-bit Intel and AMD devices. |
| Permissions | Grant administrator access when needed | Confirmation may be required to install services, enable TUN, or change certain system network settings. |
| Migration | Back up your configuration first | Before switching clients, record your subscription, override rules, listening ports, and DNS settings. |
First check the chip type in About This Mac. Choose the Apple silicon build for Apple M-series chips and the Intel build for Intel Macs. On first launch, follow the system prompts to approve app and network-extension permissions.
Provides subscription management, policy switching, and system network routing. The two DMG files correspond to Apple silicon and Intel processors; use the chip information shown by the system when choosing a download.
A desktop environment for inspecting rules, switching run modes, and tuning mihomo parameters. The current list provides entries for both architectures; download links are updated from the version manifest.
Its cross-platform layout makes familiar workflows easy to reuse across macOS and other devices. After downloading the DMG, drag the app to Applications and follow the system prompts on first launch.
An older menu-bar macOS client retained for existing configurations and workflows. On new devices, consider a maintained client first; save subscriptions and local overrides before migrating an older setup.
| Item | How to choose | Details |
|---|---|---|
| Apple silicon | M1, M2, M3, and M4 series | Choose arm64 or a download button labeled Apple silicon. |
| Intel | Intel Core series | Choose x64, x86_64, or a download button labeled Intel. |
| Installation format | DMG | Open the disk image and drag the app into Applications. |
| First run | Confirm system prompts | Network extensions, system proxy access, and background services require explicit user approval. |
Most recent phones use arm64-v8a. Older 32-bit devices can use armeabi-v7a; if the architecture is unknown, prefer a client that offers a universal package.
For common 64-bit Android phones and tablets. The client combines subscription imports, node selection, policy-group switching, and VPN takeover status management.
A mihomo GUI client for Android. It offers 64-bit ARM, 32-bit ARM, and universal packages for users who need to select an installer precisely for their device architecture.
It uses a layout similar to the desktop version, helping maintain consistent workflows across devices. Choose the 64-bit ARM, 32-bit ARM, or x86_64 package for your processor.
An Android network proxy client supporting common rules and configuration workflows. The universal package here is a convenient installation option for existing Surfboard configuration users.
| Architecture | Common devices | Recommendation |
|---|---|---|
arm64-v8a | Recent mainstream phones and tablets | If you are unsure but the device is fairly new, choose this version first. |
armeabi-v7a | Older 32-bit ARM devices | Use only when the 64-bit package cannot be installed and the device is confirmed to be 32-bit. |
x86_64 | Some emulators and specialized devices | Physical phones generally do not need this version. |
| Universal build | Devices with unknown architecture | The file is usually larger, but it reduces the chance of choosing the wrong architecture. |
Clash Plus is available from the App Store. After installation, import a subscription or configuration in the app, then follow the system prompts to add the network configuration.
A GUI client for iPhone and iPad that routes selected traffic through the system network extension. It provides subscription, policy-group, and connection-status management; system approval is required the first time it is enabled.
Official site: clashplus.io
| Item | Requirement | Details |
|---|---|---|
| Device | iPhone or iPad | Check the App Store listing for current system compatibility information. |
| Installation | App Store | Use the system store to download, install, and receive future updates. |
| Network permissions | Confirm on first enable | The system will request permission to add a network configuration; the client cannot route traffic until it is approved. |
| Configuration | Subscription link or configuration file | After installing the client, you still need to import a valid configuration before establishing a connection. |
This section targets amd64 desktop systems. Debian, Ubuntu, and derivatives generally use DEB; Fedora and RHEL-based systems can use RPM. For other architectures, see the Mihomo core section below.
A mihomo GUI client for common Linux desktop environments. It provides DEB and RPM packages that fit into the distribution's existing package-management workflow.
A cross-platform desktop client for users who want a workflow similar to Windows, macOS, or Android. The Linux section provides DEB as the primary package.
| Package | Suitable environment | Pre-installation checks |
|---|---|---|
| DEB | Debian, Ubuntu, and derivatives | Confirm the system architecture is amd64 and be ready to address desktop dependency prompts. |
| RPM | Fedora and RHEL-based systems | Confirm the system architecture is x86_64 and install using the distribution's package tool. |
| Desktop environment | Common graphical desktops | The GUI client requires an available desktop session and system-tray support. |
| Server | Command-line environment | Use the Mihomo core below directly; a desktop client is usually unnecessary. |
The Mihomo core is intended for servers, routers, containers, and command-line environments. It reads YAML configuration, opens listening ports, matches rules, handles DNS, and establishes protocol connections.
Most computer and phone users should choose a GUI client above. GUI clients combine subscription updates, policy-group selection, system proxy controls, logs, and core lifecycle management in a visual interface.
| System | Architecture | Format | Use case | Download |
|---|---|---|---|---|
| Windows | amd64 |
ZIP | Common 64-bit Intel and AMD computers and server environments | Download |
| Windows | arm64 |
ZIP | Windows on ARM devices | Download |
| macOS | amd64 |
GZ | Intel Macs and corresponding automation environments | Download |
| macOS | arm64 |
GZ | Devices with Apple M-series chips | Download |
| Linux | amd64 |
DEB | 64-bit systems using Debian package management | Download |
| Linux | amd64 |
GZ | Generic 64-bit servers, containers, and custom deployments | Download |
| Linux | arm64 |
GZ | 64-bit ARM servers, development boards, and routers | Download |
| Linux | armv7 |
GZ | 32-bit ARMv7 routers and embedded devices | Download |
| Linux | mips-softfloat |
GZ | MIPS routers using a soft-float ABI | Download |
A single client may offer several processor architectures and installation formats. Confirm the operating system first, then the processor, and finally the installation method to avoid discovering after download that the file cannot run.
Windows and macOS use desktop installers; Android uses APK files; iPhone and iPad apps are installed through the App Store. Linux requires checking whether the distribution uses DEB or RPM packages. Servers and routers usually do not need a GUI, so check the Mihomo core table directly.
Apple M-series chips use arm64, while Intel Macs use x86_64. Most newer Android devices use arm64-v8a, while older devices may use armeabi-v7a. On Linux, run uname -m to check the architecture: x86_64 corresponds to amd64, and aarch64 corresponds to arm64.
EXE, DMG, DEB, and RPM integrate with system installation workflows and suit everyday desktops. ZIP and GZ usually require manual extraction, configuration placement, and startup management, making them better for portable directories, server scripts, or router environments.
Client interfaces differ, but core settings usually center on subscriptions, policy groups, rules, DNS, and ports. Recording these details before migrating reduces reconfiguration time.
These questions cover the most common decisions during download. For subscription imports, node selection, and proxy modes, continue to the Getting Started guide.
Most desktop and mobile users should start with a GUI client. For Windows, macOS, Android, and iOS, check Clash Plus first; on the Linux desktop, start with Clash Verge Rev. GUI clients integrate subscription management, policy selection, system proxy controls, and logs, providing a more complete workflow than running the core alone.
Servers and routers typically use the Mihomo core directly. These environments require you to prepare configuration files, startup arguments, and process management yourself, so they are better suited to users comfortable with the command line and network configuration.
Choose the EXE when you want a standard installation, system shortcuts, and installer-managed files. Choose FlClash's ZIP package when you need a custom program directory, a separate copy, or a portable setup.
The main difference is deployment, not proxy capability. After extracting the ZIP, place it in a directory with reliable read/write access; do not run the program from the archive preview window.
Open About This Mac from the system menu and check the chip or processor field. Choose Apple silicon for Apple M1, M2, M3, M4, and similar models; choose Intel for Intel Core processors.
A mismatched architecture may prevent the app from launching or require an additional compatibility layer. Confirming it before downloading is more straightforward than troubleshooting launch problems afterward.
Most recent Android phones use arm64-v8a. If you are unsure, choose the universal build of Clash Meta for Android. Select armeabi-v7a only when the device is confirmed to be an older 32-bit ARM platform.
The x86_64 package mainly targets some emulators and specialized devices. A physical phone generally does not need it unless it explicitly identifies itself as x86_64.
Mihomo is the core program that handles connections: it reads configuration, listens on local ports, matches rules, resolves DNS, and establishes proxy connections. It can run independently, but configuration, updates, and process management usually require the command line or another control panel.
A GUI client adds subscription updates, policy-group switching, system proxy controls, logs, and configuration editing around the core. GUI clients suit everyday computers and phones, while automated deployments and embedded devices more often run the core directly.
The package contains only the client. After installation, import a working subscription or configuration, choose a node and proxy mode, and enable the system proxy or TUN. Installing the app alone does not create a usable connection.
If all nodes time out, first check whether the subscription has expired, whether the system clock is accurate, and whether the configuration updated successfully. Then check DNS, the local firewall, and port conflicts. If only some websites fail, review the rule mode and DNS configuration.