CLIENT PACKAGES / MIHOMO CORE
Choose a client by operating system and processor architecture. GUI clients handle subscription imports, rule switching, and system proxy controls; the Mihomo core is intended for servers, routers, and command-line environments.
PLATFORM INDEX
Platform tabs update the URL hash. Each card records its use case, architecture, and installation method; version information appears only when the remote manifest returns a valid value.
WINDOWS / X64
For x64 computers running Windows 10 or Windows 11. Import a subscription after installation, then enable the system proxy or TUN as needed. Check client requirements before using an older Windows version.
A GUI client for everyday desktop use, with configuration import, proxy-group switching, connection history, and system proxy controls in one place. The Windows installer suits standard x64 computers.
A desktop client powered by the Mihomo core, with clearly separated configuration, proxy-group, connection, and log views. This listing provides the available Windows x64 installer.
A cross-platform GUI client with a similar workflow across desktop and mobile platforms. Choose the EXE for a standard installation or the ZIP package for a portable directory.
A desktop Clash client for managing configuration files, proxy groups, system proxy settings, and connection details. This listing provides the Windows x64 download from the remote manifest.
This client is archived. Its download is retained for migrating legacy configurations, restoring existing environments, and compatibility reference. For new installations, evaluate a maintained client first.
MACOS / ARM64 / X64
For M1, M2, M3, M4, and other M-series Macs, choose the Apple silicon download; choose x64 for Intel Macs. After opening the DMG, move the app to Applications, then approve system network permissions on first launch.
Provides separate installers for Apple silicon and Intel Macs. After installation, import a subscription, choose a proxy group, and grant any proxy or network-extension permissions requested by macOS.
The desktop management interface covers subscriptions, proxy groups, connections, and logs. The two architecture buttons are resolved separately from the release manifest; still check About This Mac before downloading.
A cross-platform client for users who want a similar workflow on computers and Android devices. Architecture-specific entries are preserved, and links update after the remote manifest loads.
A menu-bar macOS client retained as an archived option. It can restore older environments or migrate existing configurations; for new deployments, compare currently maintained clients first.
ANDROID / APK
Recent phones and tablets usually use ARM64. Older 32-bit devices can use ARM; when the architecture is unknown, Clash Meta for Android provides a Universal build. Grant VPN connection permission after installation.
For recent ARM64 Android devices. The client supports configuration import, proxy selection, and VPN connection control; ensure the system does not restrict its required background network activity.
An Android client built around the Meta core, offering ARM64, ARM, and Universal packages. Choose ARM64 for most newer devices, ARM only for older 32-bit hardware, and Universal when the architecture is unknown.
The cross-platform interface makes it easy to reuse familiar workflows across desktop and mobile. ARM64 suits most newer devices, while ARM targets older 32-bit hardware; choose based on the processor architecture.
An Android proxy client that imports compatible configurations and routes connections through the system VPN interface. This listing provides a Universal package for devices needing broad architecture compatibility.
IOS / APP STORE
On iOS, install Clash Plus through the App Store. Import a working configuration, allow the VPN configuration when prompted during the first connection, then choose rules and proxy groups in the client.
A Clash client for iPhone and iPad. Use the App Store page for installation and updates; product information is also available at clashplus.io.
LINUX / AMD64
The GUI section provides AMD64 packages available in the remote manifest. Choose DEB for Debian, Ubuntu, and derivatives; Fedora and RHEL-based systems can use RPM. For other architectures, use the Mihomo core section below.
A preferred option for Linux desktop environments, with AMD64 DEB and RPM installers. After installation, manage configurations, proxy groups, system proxy settings, and connection logs from the GUI.
A cross-platform Linux GUI client. This listing provides the fixed AMD64 DEB package, suitable for Debian, Ubuntu, and desktop distributions using the same package system.
MIHOMO CORE / COMMAND LINE
Core packages do not include a desktop management interface. They are intended for servers, routers, containers, transparent gateways, and automated deployments. Most computer and phone users should choose a GUI client above.
| System | Processor architecture | Format | Typical environment | File |
|---|---|---|---|---|
| Windows | AMD64 | ZIP | Windows x64 services and command line | Download AMD64 |
| Windows | ARM64 | ZIP | Windows on ARM devices | Download ARM64 |
| macOS | Intel x64 | GZ | Intel Mac command-line environments | Download Intel |
| macOS | Apple Silicon | GZ | M-series Mac command-line environments | Download Apple silicon version |
| Linux | AMD64 | DEB | Debian / Ubuntu servers | Download DEB |
| Linux | AMD64 | GZ | Generic x64 Linux environments | Download AMD64 GZ |
| Linux | ARM64 | GZ | 64-bit ARM servers and routers | Download ARM64 GZ |
| Linux | ARMv7 | GZ | 32-bit ARMv7 routers | Download ARMv7 GZ |
| Linux | MIPS softfloat | GZ | MIPS devices using a soft-float ABI | Download MIPS GZ |
Prepare a complete YAML configuration before starting the core. It typically includes listening ports, proxy nodes, proxy groups, rules, DNS, and log levels. For service deployments, use an absolute path and ensure the service account can read the directory.
Using only local HTTP or SOCKS ports usually requires no additional network-device permissions. TUN, transparent proxying, or routing rules may require network-management capabilities on Linux; configure permissions according to the features in use.
Stop the running service and preserve the current configuration before replacing the core. After starting the new core, check configuration parsing, listening ports, DNS initialization, and rule-loading logs. If field compatibility changes, use the logs to locate affected settings.
INSTALLATION NOTES
Downloading is only the first deployment step. System architecture, configuration source, proxy mode, and DNS handling together determine the final connection result; following a fixed order reduces repeated changes.
Windows desktop packages are mainly x64; macOS requires choosing between Apple silicon and Intel; Android requires ARM64, ARM, or Universal; Linux GUI packages are mainly AMD64. A downloadable file is not necessarily compatible—if the installer will not run, return to system information and verify the architecture.
After launching the client for the first time, open the configuration or subscription page and import a working link. Wait for the configuration to download and parse, then confirm that proxy nodes, groups, and rules appear. If nodes appear without rule groups, or parsing reports field errors, fix the configuration first.
Rule mode is the usual starting point for everyday use: domains, IPs, rule sets, and final matches determine the traffic route. Global mode is useful for briefly testing a proxy strategy, while Direct pauses the proxy path. Existing connections may keep their old route after a mode switch, so reconnect before checking the result.
Browsers and most applications that follow system settings can use the system proxy. Apps that ignore system proxy settings, some games, or scenarios requiring broader traffic capture can use TUN. Avoid stacking both repeatedly while the configuration is unclear; keeping one path active makes troubleshooting easier.
After creating a new connection, check the client connection list and logs to confirm that requests matched the expected rule and proxy group. If a page will not open, check the subscription update time, node availability, system proxy status, DNS resolution, and firewall restrictions in that order instead of repeatedly switching nodes.
DOWNLOAD FAQ
These questions cover client selection, installer architecture, and core use cases. See the user documentation and complete documentation for subscription formats, rule modes, and DNS configuration.
For standard desktop and mobile devices, start with the recommended client for the relevant platform. Clash Plus is available for Windows, macOS, Android, and iOS; Linux desktops can start with Clash Verge Rev. The main differences are interface organization, system integration, and update methods; rule-routing capability also depends on the core and configuration.
Download the Mihomo core separately only for servers, routers, containers, or automated services. Core packages provide no subscription-management interface, so configuration, service startup, and log collection must be handled manually.
Most Windows 10 and Windows 11 computers with Intel or AMD processors use the x64 architecture. Open “Settings → System → About” and check “System type”; if it shows a 64-bit operating system and an x64-based processor, choose the x64 installer listed here.
This page does not list a separate native Windows ARM64 package for Clash Verge Rev. Windows on ARM users can check other available clients above or use the Windows ARM64 file in the core section for their deployment needs.
Open “About This Mac” from the Apple menu and check the chip or processor field. Choose Apple silicon or ARM64 when an Apple M-series chip is shown, and Intel or x64 when an Intel processor is shown. Architecture labels match executable files and are unrelated to subscription contents.
After opening a DMG, drag the app into the Applications folder. When system proxy or network extensions are enabled for the first time, macOS may request permission; approve it, then return to the client and check its status.
ARM64 targets 64-bit ARM processors and is the most common choice for recent phones and tablets. ARM usually means 32-bit armeabi-v7a hardware, mainly found on older devices. Universal offers broader compatibility for unknown architectures but is typically larger.
Package architecture determines whether the app can run on the device; it does not change the nodes or rules in a subscription. If installation reports an incompatible package, switch architectures instead of changing the configuration.
A GUI client brings subscription import, configuration switching, proxy groups, connection history, logs, system proxy, and TUN controls into a visual interface for personal computers and phones. The Mihomo core is a command-line program usually controlled by configuration files, startup arguments, or a system service.
On servers and routers, the core integrates more easily with service managers and automation. On everyday desktops, a GUI client reduces configuration and permission overhead. They are different installation forms, so most users do not need both.
Install and launch the client, then open the configuration or subscription page and import a working Clash configuration. After parsing completes, check that nodes, proxy groups, and rules are present; choose the rule mode and target strategy, then enable the system proxy or configure TUN for the use case.
Once connected, use the connection list and logs to confirm that requests matched the expected rules. If the subscription will not update, configuration parsing fails, or DNS results are unexpected, follow the main steps in the user documentation; for complex platform issues, consult the complete documentation.