Choose your operating system, then check the CPU architecture. Start with a GUI client for everyday use; server and router users can explore the Mihomo core downloads.
For common Windows 10 and 11 desktop setups. The Windows installers below are x64. Before downloading, check your system type under Settings > System > About.
Start with this option for a first-time install. Download the x64 installer and follow the prompts, then prepare a subscription link or local configuration file. The client manages configuration and connections; you'll need to configure a proxy service separately.
EXE installer · clashplus.io
For managing the Mihomo core, subscriptions, and rules through a GUI. System proxy and TUN handle traffic differently. Import your subscription first, then enable settings as needed by your apps instead of changing every network option at once.
EXE installer · Configure TUN and service mode as needed
A GUI client using the Mihomo core, suited to users who want a consistent experience across devices. For Windows, the installer is the easiest option. Use the ZIP to manage the program folder yourself; on first launch, check the configuration and permissions.
AMD64 and x64 refer to the same CPU architecture
Another GUI client option for Windows. If you already have a YAML configuration, check that its core and fields are supported—especially DNS, rule sets, and overrides. Being able to import a file doesn't mean every field will work as it did in your previous client.
EXE installer · Back up your existing configuration before migrating
Archived download for restoring older setups and comparing configurations. For a new device, use one of the clients above. The older core has limited support for newer protocols and some Mihomo fields. When migrating, check subscriptions, custom rules, and Parser overrides separately; don't overwrite the new client's configuration folder.
Archived installer · Not recommended for new installations
| Check | What to look for |
|---|---|
| System | Use a supported version of Windows 10 or 11 where possible. Check the selected installer's notes for its exact minimum requirements. |
| Processor | This section provides x64 builds. On ARM devices, check whether Windows can run x64 apps; an x64 build is not a native ARM64 build. |
| Runtime components | If prompted to install WebView2, install the runtime required by the client. Troubleshoot a blank window separately from configuration parsing errors. |
| Network permissions | Apps that follow Windows settings use the system proxy. TUN or service installation may require administrator approval. |
First check About This Mac to see whether your device has Apple silicon or an Intel processor. A platform label doesn't guarantee the file's architecture, so check both the filename and installer details before downloading.
Available for both Apple silicon and Intel Macs. Choose the DMG that matches your processor, open it, and follow the installer prompts. If another proxy client is running, quit it first to prevent multiple apps from repeatedly changing your system proxy settings.
DMG installer · clashplus.io
Manage subscriptions, policy groups, and Mihomo settings through a GUI. After the first launch, make sure the configuration loads before deciding whether to install the helper service. Both architecture links currently return x64 files; Apple silicon users should confirm compatibility first.
The Apple silicon link is not a native ARM64 build
For desktop users who prefer FlClash's workflow. After importing a subscription, select an outbound and choose how to route traffic. The current macOS listing returns an amd64 file. AMD64 and x64 are equivalent; neither is another name for Apple silicon architecture.
DMG installer · Check Apple silicon compatibility first
Archived download for older devices and existing configurations. For a new installation, choose one of the clients above. After a macOS upgrade, you may need to review permissions and reinstall older helper tools. Keep a copy of your configuration when migrating; don't rely on an outdated version to support fields for newer cores.
Archived DMG · File is x86_64
| Check | What to look for |
|---|---|
| macOS version | Minimum macOS requirements vary by client. Check the installer and app documentation; a DMG opening successfully doesn't mean the app supports an older macOS version. |
| Chip architecture | Apple silicon uses arm64; Intel Macs use x64 or x86_64. Some Apple silicon links in the current listings still return Intel builds. |
| Installation and permissions | Allow required network or helper-service permissions when prompted. If macOS blocks the app from opening, check the specific reason rather than disabling system security features. |
Most newer Android devices use ARM64; check older devices and emulators separately. After installing an APK, you'll usually need to approve the system VPN request to connect for the first time.
Recommended for a first Android installation; this link provides an arm64-v8a build. After installing, import a valid configuration and approve the system VPN request. If background connections drop, check the app's battery and background activity restrictions.
APK · clashplus.io
Clash Meta client for Android, available in ARM64, ARM, and universal builds. If you don't know your device's ABI, try the universal build; it typically includes multiple architectures and has a larger file size. After importing a configuration, select the one you want to use.
ARM 32-bit and ARM64 are different builds
Uses the Mihomo core, with ARM64, 32-bit ARM, and x86_64 builds. Most phones use ARM64; choose x86_64 only if it matches your device or emulator's ABI. If installation fails, check the architecture and Android version rather than renaming the APK and trying again.
armeabi-v7a is 32-bit ARM
Android universal APK. Surfboard uses a configuration format different from Clash YAML, so a Clash subscription can't be imported as if the formats were interchangeable. Before downloading, check that your provider offers a compatible configuration and that the required protocols and rule syntax are supported.
APK · Requires a Surfboard-compatible configuration
| Check | What to look for |
|---|---|
| System and ABI | Check the APK's minimum Android version. ARM64, 32-bit ARM, and x86_64 builds must match an ABI supported by your device. |
| Install permissions | Follow the system prompt to allow installs from your browser or file manager. You can revoke this permission afterward if you no longer need it. |
| VPN and background activity | Approve the system VPN request. If the connection drops, check for conflicts with other VPN apps, background restrictions, and battery optimization settings. |
Install Clash Plus from the App Store. Check the app's store listing for current device compatibility, system requirements, and other details.
After installing from the App Store, import a subscription or configuration file, then add a VPN configuration when prompted. Installing the app doesn't establish a proxy connection: first confirm the configuration is valid, a policy group has an available outbound, and you understand how rule mode routes traffic.
Official website: clashplus.io
| Check | What to look for |
|---|---|
| Device compatibility | Check the App Store listing for currently supported devices and the minimum iOS version. |
| System permission | Allow the VPN configuration when prompted on first connect. If another VPN is already connected, check for conflicts first. |
| Configuration | Use a valid subscription or local configuration in a supported format. Installing from the App Store does not provide a proxy service. |
For desktop use, start with a GUI client. The downloads here are for AMD64: Debian and Ubuntu-based distributions generally use DEB, while RPM-based distributions use the corresponding RPM package.
For Linux desktop users who want subscription management and proxy settings in a GUI. Choose DEB or RPM for your distribution and use its package manager to handle dependencies. TUN and system services require additional permissions; first confirm the configuration works in regular proxy mode, then route more traffic through the client as needed.
AMD64 desktop builds · Dependencies handled by your distribution's package manager
AMD64 DEB package for Debian-based desktops. After installation, make sure the window opens before importing your configuration. Command-line tools, browsers, and desktop apps may handle the system proxy differently, so test each one rather than relying on a single terminal request.
AMD64 package · For Linux desktops
| Check | What to look for |
|---|---|
| Check the architecture | Run uname -m to check your system architecture. x86_64 corresponds to the AMD64 packages here; these packages won't run directly on ARM devices. |
| Distribution | DEB and RPM are different package formats and can't be interchanged by changing the file extension. Check the package dependencies for runtime requirements. |
| Desktop and permissions | GUI clients require a compatible desktop environment. Servers typically use the standalone core, with permissions and services managed separately. |
For servers, routers, and command-line services you manage yourself. Desktop users can use one of the GUI clients above and usually don't need to download the core separately.
| System | Architecture | Package type and use | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP · 64-bit Intel / AMD | Download AMD64 ZIP |
| Windows | ARM64 | ZIP · 64-bit ARM | Download ARM64 ZIP |
| macOS | Intel AMD64 | GZ · Intel Mac | Download Intel GZ |
| macOS | Apple Silicon ARM64 | GZ · Apple silicon | Download ARM64 GZ |
| Linux | AMD64 | DEB · Debian package | Download AMD64 DEB |
| Linux | AMD64 | GZ · Standalone executable for manual deployment | Download AMD64 GZ |
| Linux | ARM64 | GZ · 64-bit ARM servers and devices | Download ARM64 GZ |
| Linux | ARMv7 | GZ · 32-bit ARM devices | Download ARMv7 GZ |
| Linux | MIPS softfloat | GZ · Match byte order and ABI | Download MIPS GZ |
On Linux, run uname -m to check the architecture. For routers, also check the firmware documentation for byte order, floating-point ABI, and system compatibility. MIPS and MIPSEL are not interchangeable; a device name containing MIPS alone isn't enough to choose a binary.
GZ archives usually need executable permissions after extraction. Check the configuration syntax before launching the core, then run it through a service manager. Keep the configuration directory, log location, and service account clear to avoid a manually started process and a background service competing for the same port.
mihomo -v
mihomo -t -f config.yaml
mihomo -f config.yamlThese commands assume the core is in your executable search path. If the file is in the current directory, use ./mihomo on Linux or macOS; on Windows, use .\mihomo.exe at the file's actual location. After the command checks pass, configure startup, TUN, and firewall settings.
Downloading is only the first step. Check separately that the configuration loads, outbound connections work, and app traffic is routed as expected.
Add a valid subscription link to the client or import a local configuration. If parsing fails, first check whether the response is in a supported format, then review YAML indentation, link expiration, and any required request headers.
Subscription import guide →For everyday split tunneling, start with rule mode. Select an outbound in the relevant policy group, then enable the system proxy. Configure TUN and its permissions only if an app ignores the system proxy or you have another specific need to route its traffic.
Understand rule matching order →Use client logs, connection records, and tests in the target app to verify the setup. DNS failures, incorrect rule matches, and port conflicts are different issues; troubleshoot the symptoms one at a time instead of reinstalling repeatedly and hiding the cause.
How to verify a connection →Check your system, architecture, and configuration source first, then troubleshoot installation or connection issues.
Choose your platform based on your device, then start with its featured Clash Plus client. For Windows system proxy, TUN, and subscription management settings, Clash Verge Rev is another option. One client is enough to configure your setup—there's no need to run several proxy clients at once.
On Windows, check Settings > System > About for your system type. On macOS, check About This Mac for your chip or processor. On Android, choose a build that matches an ABI supported by your device. x64 is the 64-bit Intel or AMD architecture; ARM64 is 64-bit ARM. If you can't confirm your Android architecture, choose a client that offers a universal build.
The client installer doesn't include a ready-to-use proxy service. Import a valid subscription or configuration file, select an outbound in a policy group, then enable the system proxy or TUN as needed by your apps. First check that the configuration loads, then check connectivity and rule matches. A toggle being on doesn't prove your traffic can connect.
Both clients are discontinued. Their download links remain available for migrating older setups and comparing configurations. For a new installation, choose a featured or recommended client for your platform. Archived versions may not support newer protocols or configuration fields, so back up your subscriptions, custom rules, and overrides before migrating.
A version label appears only when the version manifest returns valid data; empty values are not shown. The download button remains available and will try to refresh the URL when clicked. Before installing, check the filename, CPU architecture, and installer details. On macOS in particular, a platform key doesn't guarantee the file's actual architecture.
Usually not. The GUI client handles configuration, proxy controls, and core integration, so most users only need to install the client. The standalone Mihomo core is mainly for servers, routers, or command-line setups you manage yourself; you'll also need to provide a configuration file, launch options, and a way to manage the service.