Client downloads / processor architectures / core
Choose a client for your operating system, then check the installer architecture. Graphical clients manage subscriptions and provide the interface; the Mihomo core handles rules and connections.
Platform downloads
Featured downloads appear first in each platform list. Check the filename to confirm the actual package architecture. Archived clients include a separate maintenance-status note.
This section provides x64 desktop installers. Check Settings → System → About to find your system type. On ARM devices, also confirm compatibility with x64 apps and their drivers.
A good starting point for a first Windows installation. After installing, import your configuration and select a proxy group before enabling the system proxy. If you need to route more app traffic, check the permissions required for TUN. Don't let multiple clients change system proxy settings at the same time.
A desktop client for managing configurations and monitoring core status in one place. After installation, check core startup, system proxy, and service mode separately. Service permissions enable system integration; they don't mean a subscription has been imported or a node is ready to use.
A good fit if you want a similar workflow across desktop and mobile. This is the Windows AMD64 installer. On other devices, authorize network routing separately and check any local file paths referenced by your configuration.
Another graphical client for Windows. Before migrating, keep a copy of your current configuration, then import your subscription and check the proxy group names. Interface settings, port preferences, and client-specific extensions may not transfer with the YAML configuration.
Archived download for migrating older setups and comparing legacy configurations. The old core may not recognize newer protocols or fields, or work with future system changes. For a new installation, choose a maintained client from the options above. Back up your subscription, local rules, and port settings before migrating.
| Check | Requirements and notes |
|---|---|
| Processor | These builds are primarily x64 / AMD64; native ARM64 driver support is not guaranteed. |
| System compatibility | Check the minimum system requirements stated by the installer. Older Windows versions may also need specific UI runtime dependencies. |
| Permissions | Standard configuration management and TUN or service installation require different permissions. Grant administrator access only when needed. |
| Network | Use a valid configuration and an available proxy port. Don't let multiple clients control the system proxy or virtual network adapter at the same time. |
Check the chip type under Apple menu → About This Mac. Apple Silicon and Intel use different architectures. The notes below identify the actual files in this list; don't rely on the download button label alone to determine native support.
ARM64 and x64 disk images are available. Choose ARM64 for Apple Silicon and x64 for Intel. Open the DMG and follow the installer prompts, then grant the required network permissions and import your configuration.
For managing desktop subscriptions and checking core status. Both macOS downloads currently point to x64 files. Apple Silicon users should confirm Rosetta compatibility before using them. For a native ARM64 build, choose the option above that is explicitly labeled ARM64.
Offers configuration management similar to the other platforms. The listed macOS build is AMD64, and both download options point to the same file. Apple's translation layer doesn't guarantee that all network extensions will work; check compatibility separately before enabling TUN.
An archived menu bar client, mainly for continuing an older workflow or comparing configurations before migration. The current listing is an x86_64 file, and both download options point to it. A legacy client running successfully doesn't guarantee support for newer protocols or systems.
| Check | Requirements and notes |
|---|---|
| Chip | Use native ARM64 on Apple M-series Macs. Intel uses x64 / AMD64 / x86_64. |
| System compatibility | Check the individual installer for the minimum macOS version. Older systems may have additional runtime requirements. |
| Translation support | Apple Silicon may need Rosetta to run x64 apps. Network components still need to be compatible separately. |
| Installation and permissions | Install the app first, then approve the network extension when prompted. Keep your system security settings enabled. |
Most recent phones use ARM64, but processor support and the app architectures supported by the OS may differ. Check your device information before choosing an APK. Older devices may need ARMv7 or the universal build.
ARM64 Android installer. On first launch, import a subscription. When connecting, allow the VPN connection when prompted by Android. This permission routes device traffic; it is separate from your subscription account or server authentication.
An Android configuration management client with ARM64, ARMv7, and universal builds. The universal APK includes code for multiple architectures and is useful if you're unsure which one your device supports. If you know the architecture, choose the matching build to avoid downloading extra files.
ARM64 and ARMv7 Android installers. If the connection drops on mobile, check Android's background restrictions and battery settings as well as your configuration. Allowing background activity doesn't change the rule mode or fix an expired subscription.
Universal Android installer. Surfboard uses a configuration format different from Clash YAML, so don't assume your existing subscription can be imported directly. Before downloading, check that your configuration provider offers a Surfboard-compatible format and that your protocols are supported.
| Check | Requirements and notes |
|---|---|
| App architecture | ARM64 corresponds to arm64-v8a; ARMv7 corresponds to armeabi-v7a. Use the universal build if you don't know your device's architecture. |
| OS version | Check the compatibility notice from the package installer. If the app is incompatible, first check your Android version and device architecture. |
| Installation permissions | Grant install permissions only to the browser or file manager used to download the APK. Revoke them afterward if you wish. |
| Traffic routing | A VPN permission is required to connect. Another VPN app may already be using the system VPN slot. |
Get Clash Plus from the App Store. Check the store listing for system compatibility, then install the app, import your configuration, and authorize its VPN connection.
On iOS, install through the App Store. Add a valid subscription or configuration, check your proxy groups, then allow iOS to establish a VPN connection. The VPN icon means the tunnel is active; it doesn't mean every request is routed through the proxy. Actual routing depends on the rules and selected policies.
| Check | Requirements and notes |
|---|---|
| Device compatibility | Check the App Store listing for supported devices and minimum iOS / iPadOS versions. |
| Get the app | Install using the App Store link above. The App Store manages future app updates. |
| Network permissions | When connecting for the first time, follow the system prompt to add a VPN configuration. Other VPN configurations may affect connection status. |
| Configuration setup | Have a valid subscription ready. After importing it, check that nodes, rules, and proxy groups have loaded correctly. |
Check your Linux distribution and processor architecture first. DEB and RPM are different package formats and can't be swapped by changing the file extension. The desktop installers below are for AMD64 / x86_64.
DEB packages are commonly used on Debian-based distributions; RPM packages are for RPM-based distributions. Install dependencies with your system package manager before launching the desktop app. Check permissions separately for TUN and service installation; an app that opens doesn't mean it has taken over routing.
AMD64 DEB desktop installer. Designed for Linux systems with a graphical desktop; headless servers are better suited to the core downloads below. If startup reports a missing shared library, resolve it using your package manager's dependency information rather than copying libraries from another system.
| Check | Requirements and notes |
|---|---|
| Processor | Check the architecture with uname -m; x86_64 matches the AMD64 builds listed here. |
| Package format | Debian / Ubuntu-based distributions usually use DEB; Fedora and other RPM-based distributions use a compatible RPM. |
| Runtime dependencies | Requires a graphical desktop session and the runtime libraries declared by the package. Check the installer and startup logs for distribution-specific compatibility. |
| Permissions and routing | System proxy support depends on the desktop environment and app. TUN also requires device permissions, firewall access, and routing rules. |
For servers, routers, and manually managed configurations
The core doesn't include a subscription management interface. Desktop and mobile users should start with a GUI client above. Install the core separately only if you need to manage configuration files, listen addresses, and service processes yourself.
| System | Processor architecture | File format | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download AMD64 ZIP |
| Windows | ARM64 | ZIP | Download ARM64 ZIP |
| macOS | Intel / AMD64 | GZ | Download Intel GZ |
| macOS | Apple Silicon / ARM64 | GZ | Download ARM64 GZ |
| Linux | AMD64 | DEB | Download AMD64 DEB |
| Linux | AMD64 | GZ | Download AMD64 GZ |
| Linux | ARM64 | GZ | Download ARM64 GZ |
| Linux | ARMv7 | GZ | Download ARMv7 GZ |
| Linux | MIPS softfloat | GZ | Download MIPS GZ |
| Check | Requirements and notes |
|---|---|
| Architecture and ABI | The CPU, operating system, and binary build target must be compatible. For embedded firmware, check the floating-point ABI and byte order in particular. |
| Configuration directory | Prepare readable configuration files and any rule sets, databases, or provider resources they reference. |
| Network permissions | Proxy listeners and TUN require different permissions. Use the least privilege necessary and don't expose the management interface directly to the public internet. |
| Service management | First check startup logs and listening ports in the foreground, then run the core under a system service manager. This helps catch configuration errors before they get hidden by the service. |
Before deployment, see Mihomo Configuration Basics →. For protocol support and configuration compatibility, see Protocol Reference →.
After downloading
A successful download only means the file is on your device. Follow these steps to separate installation issues from configuration and traffic-routing problems.
Before changing clients, note your subscription URL, selected proxy group, and local rules. Store subscription URLs containing credentials somewhere secure; don't post them in public screenshots or support threads. A new client may import the same YAML, but that doesn't mean it will inherit the old client's service mode, system proxy settings, or startup items.
After installing the new client, keep the old one stopped to avoid port conflicts. Subscription updates may overwrite rules in the remote configuration. Put persistent local changes in the client's supported override or merge mechanism, then check the effective configuration after each update.
Import and update subscription links →First check the logs to confirm the configuration loaded and proxy ports are listening, then enable the system proxy. System proxy settings only affect apps that follow the operating system's settings; command-line tools and some games may use different network paths. TUN routes traffic through a virtual network adapter and requires additional permissions and routing configuration.
Don't treat a “connected” status in the interface as proof that rules are working. Check whether test requests appear in the connection log, which rule matched, and which policy was selected. If no requests appear, troubleshoot the traffic-routing path before switching nodes repeatedly.
First connection and verification steps →CLIENT / CORE / PROFILE
The client provides the interface and system integrations, the core parses protocols and handles connections, and the subscription supplies remote configuration. They update on different schedules. A client's name alone doesn't guarantee support for a particular protocol or field.
Keep a working configuration before updating the installer. After updating, check that the core starts, the subscription loads, and all referenced proxy groups are present. For unknown fields or unsupported protocols, check the actual core version rather than relying on the client interface alone.
Clash for Windows and ClashX Meta are discontinued. Their archived downloads remain available to help with migration. Older workflows can be a reference, but verify new configurations against the current core's capabilities. Installers, core files, and remote configurations each have their own compatibility limits.
Check core versions and protocol compatibility →Download and installation FAQ
These answers cover choosing and installing packages. For connection, DNS, and app routing issues, see the FAQ →.
For your first setup, choose a graphical client. Clients provide subscription import, proxy group selection, system proxy controls, and logs. The Mihomo core handles connections directly and is better suited to server or router users who manage configuration, startup options, and services themselves.
Check your system information to confirm the processor architecture, then verify the download button and filename. x64, AMD64, and x86_64 usually refer to the same 64-bit architecture; ARM64 is different. For Android, choose the matching ARM64 or ARMv7 build when possible, or use the universal build if unsure. Some macOS listings currently point to the same x64 file, so Apple Silicon users should choose a client with a clearly labeled ARM64 download.
The client installer does not include a ready-to-use proxy service. Import a valid subscription or local configuration, select a proxy group, then enable the system proxy or TUN as needed. Finally, check connection logs and rule matches to confirm how traffic is routed.
Both clients are discontinued. Their downloads remain available for migrating older setups and comparing configurations. Legacy cores may not support newer protocols, fields, or operating system changes. For a new installation, choose a maintained client. Back up your configuration and local rules before migrating.
These are separate updates. Client updates affect the interface and integrations, core updates affect protocol and connection handling, and subscription updates change remote configuration. Whether a client installer also updates the core depends on how that client is packaged. After updating, check the core version, configuration load status, and subscription update time separately.
Confirm the operating system, processor architecture, and installer format, then check system prompts, disk space, and installation permissions. If an Android update fails, check the previous build's signing key and the installation source. On Linux, verify the distribution's package format and dependencies. Don't disable system security just to bypass a warning.