CLIENT PACKAGES · GUI / CORE
Choose a graphical client for your operating system. For desktop and mobile devices, start with the first item in the list; for servers, routers, and automated environments, choose the Mihomo core below.
PLATFORM SELECTOR
Switching platforms updates the anchor in the address bar. When you share the current URL, the page can restore the corresponding system automatically. Version details appear only after the remote manifest returns a valid value.
WINDOWS PACKAGES
The installer suits standard desktop setups and can create a Start menu shortcut automatically. Use the archive to keep an independent directory or run temporary tests. For a first installation, start with Clash Plus, then compare other clients based on interface preferences.
A consistent desktop workflow for first-time installations and switching between devices. Import a subscription from the configuration page, then enable the system proxy or TUN mode.
A mihomo graphical client for Windows desktops, with configuration management, rule modes, system proxy, and TUN settings. Suitable for users who want access to more complete runtime options.
The interface stays broadly consistent across desktop and mobile platforms. Use the installer for standard deployment; extract the archive to an independent directory for easier portability and familiar settings across devices.
A desktop configuration-management client with access to subscriptions, proxy groups, rules, and connection details. Suitable for users familiar with Clash fundamentals who want to monitor runtime status in one place.
Archived client. The download remains available mainly for older devices, existing configuration migration, and interface checks. For new deployments, choose a currently maintained client higher in the list.
| Item | Recommendation | Selection criteria |
|---|---|---|
| System | Windows 10 / 11 | Keep the system networking components and WebView runtime available and operational |
| Architecture | x64 | The desktop packages on this page target common 64-bit Intel and AMD devices |
| Permissions | Standard user; confirm the system prompt when installing TUN | Changes to the virtual network adapter and system proxy may require permission confirmation |
platform: windows · package: exe / zip · recommended-arch: x64
MACOS PACKAGES
First check the chip in About This Mac. Choose Apple Silicon or ARM64 for an Apple M-series chip, and x64 for an Intel processor. When opening a downloaded app for the first time, follow the system security prompt to confirm its source and network permissions.
Provides installation options for Apple Silicon and Intel. Suitable for users who want a similar configuration workflow across Windows, macOS, Android, and iOS.
A mihomo graphical desktop client. The download manifest keeps separate architecture keys; choose the entry matching your Mac's chip before installation to avoid mixing architecture labels.
A broadly consistent cross-platform interface and configuration flow. The current manifest provides separate architecture keys; the version manifest returns the available file URL after selection.
An archived macOS menu bar client for migrating older configurations and restoring existing devices. For new installations, prefer a client above to use newer core and configuration capabilities.
| Item | Apple Silicon | Intel |
|---|---|---|
| Chip identifier | Apple M-series | Intel Core series |
| Package identifier | ARM64 / arm64 | x64 / x86_64 |
| System check | Check the chip in About This Mac; follow the system prompt on first launch to grant network configuration permission | |
platform: darwin · package: dmg · arch: arm64 / x86_64
ANDROID PACKAGES
Most recent phones use arm64-v8a. Older 32-bit devices use armeabi-v7a. When you start the proxy for the first time after installation, Android displays a system VPN connection request; confirm it to create the local VPN interface.
Suitable for current mainstream 64-bit Android phones and tablets. Its configuration flow is similar to the versions on other platforms, making it easier to compare subscriptions, proxy groups, and connection modes across devices.
An Android client built around Meta core capabilities, with architecture-specific and universal packages. Choose the matching package when the device architecture is known; otherwise use the universal package.
Suitable for users who want a similar interface between Android and desktop. Provides ARM64, 32-bit ARM, and x86_64 packages; choose according to the device processor.
An Android proxy client using a universal package. Suitable for users with compatible configurations who prefer a simple mobile workflow.
| Device type | Preferred architecture | How to identify it |
|---|---|---|
| Recent mainstream phones and tablets | arm64-v8a | 64-bit ARM processor; ARM64 is usually the right choice |
| Older 32-bit devices | armeabi-v7a | Device information tools or manufacturer specifications identify it as 32-bit ARM |
| Architecture unknown | universal | Use a package marked universal |
platform: android · service: VpnService · arch: arm64-v8a / armeabi-v7a / universal
IOS APP STORE
Install Clash Plus on iPhone and iPad through the App Store. After installation, import the subscription configuration; when starting a connection, follow the iOS prompt to approve VPN configuration access.
A Clash client for iPhone and iPad. Install it directly from the store page; product details and platform information are also available on the official website.
Official site: clashplus.io
| Item | Details |
|---|---|
| Device | iPhone or iPad |
| Installation method | Install from the App Store product page |
| First connection | Confirm the VPN configuration request shown by the system, then return to the client to check the connection status |
platform: ios / ipados · distribution: app-store · vpn: system-authorization
LINUX PACKAGES
Desktop users can choose DEB or RPM according to their distribution's package system. This section provides only AMD64 graphical client entries available in the manifest; use the Mihomo core below for routers, servers, and other architectures.
For common Linux desktop environments. Choose DEB for Debian, Ubuntu, and derivatives; choose RPM for Fedora, RHEL, and distributions using RPM package management.
Linux AMD64 desktop packages. DEB suits Debian-based distributions; choose RPM or AppImage according to your desktop environment and software-management preferences.
| Distribution family | Package type | Processor |
|---|---|---|
| Debian / Ubuntu and derivatives | DEB | AMD64 |
| Fedora / RHEL family | RPM | x86_64 |
| Other desktop distributions | AppImage or the format recommended by the distribution | AMD64 |
platform: linux · package: deb / rpm / appimage · gui-arch: amd64
MIHOMO CORE
The core package targets servers, routers, containers, and command-line environments. It has no graphical interface, so you must provide configuration files, startup parameters, and system services. Regular computer and phone users should prefer the GUI clients above.
| System | Architecture | Format | Supported environment | Download |
|---|---|---|---|---|
| Windows | amd64 |
ZIP | 64-bit Intel / AMD hosts | Download AMD64 |
| Windows | arm64 |
ZIP | Windows on ARM devices | Download ARM64 |
| macOS | amd64 |
GZ | Intel Mac | Download Intel |
| macOS | arm64 |
GZ | Apple Silicon Mac | Download Apple Silicon |
| Linux | amd64 |
DEB | Debian-based servers | Download AMD64 DEB |
| Linux | amd64 |
GZ | Generic 64-bit servers | Download AMD64 GZ |
| Linux | arm64 |
GZ | 64-bit ARM servers and router devices | Download ARM64 GZ |
| Linux | armv7 |
GZ | 32-bit ARMv7 router devices | Download ARMv7 GZ |
| Linux | mips-softfloat |
GZ | MIPS soft-float router devices | Download MIPS GZ |
CONFIG
Mihomo reads YAML configuration. Files typically contain proxy nodes, proxy groups, rules, DNS settings, and listening ports. Before deployment, confirm the file path and ensure the runtime user can read the configuration directory.
SERVICE
Server environments typically start the process through a system service manager, with restart-on-failure, log output, and startup loading configured. On routers, follow the firmware's package and service-management conventions.
ARCHITECTURE
amd64 is used for common 64-bit Intel and AMD devices, arm64 for 64-bit ARM, and armv7 for some older 32-bit ARM devices.
PACKAGE SELECTION
The same operating system does not guarantee the same processor architecture. Confirm these three items before downloading to reduce installation failures, startup errors, and system blocks.
For computers, distinguish Windows, macOS, and Linux; for phones and tablets, distinguish Android and iOS. If a server or router does not need a desktop interface, consider the Mihomo core.
Windows desktops commonly use x64. M-series Macs use ARM64, while Intel Macs use x64. Most Android devices use ARM64; older devices may use 32-bit ARM.
Use an installer or system package for standard desktop setups. Archives suit independent-directory deployments. On Linux, choose DEB, RPM, or AppImage according to the distribution; on mobile, use the entry for the corresponding platform.
Graphical clients bring subscription management, proxy-group selection, rule switching, system proxy, TUN, and log viewing into one interface for everyday computer and phone use. Clients may use different frontend technologies, but actual network handling usually depends on the integrated core version and the settings exposed by the client.
The Mihomo core provides only the core executable. It suits scripted startup, centrally managed configurations, and devices without a desktop environment. You must handle configuration paths, process permissions, port conflicts, service startup, and log rotation yourself. If you simply want to import a subscription and connect on a personal computer, a GUI client requires less setup.
The version slot on each client card is hidden by default. After the page loads, the shared download script reads the site's version manifest; version information appears only when a valid version is returned, and the button is updated to the matching file. If the manifest is temporarily unavailable, the button keeps the complete file URL built into the page, so the current download entry remains usable.
After installation, open the configuration or subscription page, paste the subscription URL, and import it. Then choose an available proxy group and enable the system proxy, TUN, or mobile VPN service as needed. Android and iOS show system-level connection authorization; Windows, macOS, and Linux may also request permission when installing virtual network components.
Once connected, check the client status and logs, then visit a familiar website in a browser to verify network access. If the client reports a connection but an app cannot reach the network, check the node status, rule mode, DNS settings, system time, and whether another proxy is using the same port—instead of repeatedly reinstalling.
DOWNLOAD FAQ
These answers cover architecture choices, archived clients, system authorization, and first-time setup. The content matches the page's structured data.
Start with the top-listed or recommended client for your current platform. Choose Clash Plus for a similar workflow across platforms; on Windows, macOS, and Linux desktops, you can also choose Clash Verge Rev or FlClash based on interface preferences. For first-time use, a clear interface, an obvious subscription entry point, and complete system-proxy controls usually matter more than the number of features.
Most recent Android phones use arm64-v8a. Older 32-bit devices can use armeabi-v7a. If you cannot confirm the processor architecture, use the universal package for Clash Meta for Android. The x86_64 package is mainly for matching emulators or a small number of devices, not the default choice for ordinary ARM phones.
Open About This Mac from the system menu. If it shows an Apple M-series chip, choose the Apple Silicon or ARM64 package; if it shows an Intel processor, choose the Intel, x64, or x86_64 package. Choosing the right architecture reduces reliance on translation layers and avoids downloads that cannot launch directly.
This client is archived, so its existing packages are mainly kept for compatibility with older configurations and devices. Archived does not mean the packages will be removed immediately, but new deployments should prefer Clash Plus, Clash Verge Rev, or FlClash for newer core, protocol, and system compatibility.
The Mihomo core is mainly intended for servers, routers, containers, and command-line environments. You must prepare the YAML configuration, startup parameters, and service-management setup yourself. Most desktop and phone users should choose a graphical client, where subscription imports, proxy switching, permission prompts, and log viewing are more direct.
Open the client's configuration, Profile, or subscription page, paste the subscription URL provided by your service provider, and import or update it. Then choose a proxy group, start the system proxy, TUN, or mobile VPN service, and verify the connection in a browser. For the complete sequence, continue with the Getting Started guide.