Platform downloads · Architecture · Before you install
Choose your operating system, then check your processor architecture. Use a GUI client on desktop or mobile; choose the Mihomo core for servers and routers.
The client and connection service are separate. Import a valid subscription or local configuration after installation.
Desktop client / EXE
For a first install, start with Clash Plus. The GUI clients below are x64 packages for compatible Windows devices. ARM devices require a separate compatibility check; these are not native ARM64 builds.
A good fit for everyday use, starting with package selection and subscription import. Quit any existing proxy client before installation to prevent conflicting system proxy settings. After installing, import your configuration and check the proxy mode and traffic-routing switches.
A good fit for desktop users who want to manage configurations, rules, and traffic-routing settings. System proxy and TUN route traffic differently. Test the system proxy first, then configure the permissions and services TUN requires if needed.
A good fit if you want a similar interface across desktop and mobile. Choose the installer for a first install. If you use the ZIP package, extract it to a permanent folder; don’t run it from inside the archive or move its data files while it’s in use.
Another desktop interface for managing configurations. Back up your existing Clash configuration, then import it separately into the new client. Settings may not map one-to-one, so review overrides, ports, and startup options in particular.
Kept for reference in legacy environments and configuration migrations—not recommended for a first install. This archived client uses an older core that may not recognize newer protocols or configuration fields. If configuration parsing fails, consider switching to a maintained client.
| Check | Requirements and recommendations |
|---|---|
| Operating system | Use a supported version of Windows 10 or Windows 11. Check the installer for the specific minimum version required. |
| Processor | Check Settings → System → About for your system type. Packages in this section are x64 / AMD64. |
| Permissions and ports | For everyday use, start with the system proxy. TUN or background services may require administrator approval. If a port is already in use, quit the old client first. |
Desktop client / DMG
Check About This Mac for your chip. Choose a package explicitly labeled ARM64 for Apple silicon, or x64 for Intel. Some downloads listed here are x64 files; they’re labeled by file architecture and are not native ARM64 builds.
Separate packages are available for Apple silicon and Intel. Open the disk image and move the app to Applications, then launch it from there. After importing a configuration, grant any network permissions macOS requests. Don’t keep running the app from the disk image.
A good fit for managing desktop configurations and rules. The macOS file listed here is x64; Apple silicon users should check Rosetta compatibility. After installation, check that system proxy access and any helper services are authorized.
A good fit if you want a consistent cross-platform interface. The filename identifies this as an AMD64, or x64, build; check compatibility before using it on Apple silicon. When switching platforms, import your configuration again rather than reusing another system’s application data directory.
Kept for legacy environments and migration reference. The listed file is x86_64; archived status does not imply support for newer configuration fields. Before migrating, save your local rules, then check DNS, routing, and port settings in the new client.
| Check | Requirements and recommendations |
|---|---|
| macOS version | Check About This Mac for your macOS version. Minimum requirements vary by client; check the installer for details. |
| Chip architecture | Apple M-series chips use ARM64; Intel Macs typically use x64. Running x64 apps on Apple silicon requires Rosetta compatibility. |
| First launch | Launch the app from Applications and check any prompts under Privacy & Security. Don’t disable system security protections across the board to resolve an issue with one app. |
Mobile client / APK
For newer phones, start by checking the ARM64 package. Older devices may need ARMv7; if you’re unsure of the architecture, choose a client that offers a Universal package. Installing the app and granting VPN access are separate steps—the system will ask for authorization when you first connect.
A good fit for importing subscriptions and switching modes on your phone. This is an ARM64 package. Approve the system VPN prompt on first connection. If the connection drops when the screen locks, check background activity and battery optimization settings.
A good fit for Android users who want to manage Clash configurations. Choose a package based on your device ABI; if you can’t confirm it, use the Universal version. After importing an existing configuration, check that it parses successfully before connecting so a format issue isn’t mistaken for an installation problem.
A good fit if you already use FlClash on desktop and want a similar experience on Android. ARM64 and ARMv7 packages target different ABIs. The x86_64 package is mainly for devices with that architecture; don’t choose it just because your phone runs a 64-bit system.
A good fit if you already have a Surfboard-compatible configuration. Its format differs from Clash YAML, so a generic Clash subscription won’t necessarily work. Before downloading, check whether your provider offers a compatible format, then import it.
| Check | Requirements and recommendations |
|---|---|
| System and ABI | Check your Android version and supported app architectures. A 64-bit processor does not necessarily mean the system can install every 64-bit app. |
| Install permissions | Follow the system prompt to temporarily allow app installs from your browser or file manager. You can revoke permission for that source afterward. |
| Network access | Approve the VPN prompt the first time you connect. On most devices, only one VPN connection can be active per user at a time. |
Mobile client / App Store
Check the app’s compatibility and installation details in the App Store. After installing, add a configuration and follow the system prompt to allow a VPN configuration. Check the client and system settings for the actual connection status.
iPhone and iPad users can install from the App Store listing. System requirements, availability, and pricing are subject to change; check the current listing. When importing a subscription, use the configuration URL rather than a website login URL. After updating the subscription, make sure the configuration is enabled.
| Check | Requirements and recommendations |
|---|---|
| Device compatibility | Check the App Store listing’s compatibility section for your device and the minimum iOS version. |
| Where to install | Use the App Store link in this section. Refer to the store listing for app details and installation status. |
| Configuration permissions | Prepare a valid configuration and approve the VPN configuration prompt on first connection. If you already have another VPN configured, check which one is active. |
Desktop client / DEB · RPM · AppImage
These are desktop clients with a graphical interface, not for minimal, command-line-only systems. Check your distribution’s package format and CPU architecture first. The desktop packages below are AMD64; for servers and other architectures, see the Mihomo core section.
Choose DEB or RPM based on your distribution. Installing through your system’s package manager helps keep dependencies consistent. If the app won’t launch, check terminal errors and desktop environment dependencies before troubleshooting proxy settings.
Available in DEB and other package formats. AppImage doesn’t work on every distribution; a compatible desktop environment and runtime dependencies are still required, and you may need to make the file executable. After installation, check whether your desktop and apps are using the system proxy.
| Check | Requirements and recommendations |
|---|---|
| Package format | Debian and Ubuntu typically use DEB; Fedora typically uses RPM. Check compatibility before installing on other distributions. |
| Architecture and desktop | Run uname -m to check your architecture. x86_64 matches the AMD64 packages in this section. GUI clients require a working desktop session. |
| Services and permissions | TUN requires the appropriate device and network permissions. Don’t let multiple clients create routes or repeatedly change system proxy settings at the same time. |
Servers / routers / command-line setups
Mihomo is a core for handling proxy protocols and rules, not a desktop client with a configuration management interface. Most users should choose one of the GUI clients above. Choose the standalone core only if you need to manage startup options, services, and runtime permissions yourself.
| Platform | Architecture and format | Use case | Local download |
|---|---|---|---|
| Windows | AMD64 · ZIP | 64-bit x86 command-line systems | Download AMD64 ZIP |
| Windows | ARM64 · ZIP | ARM64 Windows systems | Download ARM64 ZIP |
| macOS | Intel · GZ | Intel x64 command-line systems | Download Intel GZ |
| macOS | Apple Silicon · GZ | Apple M-series ARM64 systems | Download ARM64 GZ |
| Linux | AMD64 · DEB | Systems using DEB packages | Download AMD64 DEB |
| Linux | AMD64 · GZ | Manage the binary and service yourself | Download AMD64 GZ |
| Linux | ARM64 · GZ | 64-bit ARM servers or compatible devices | Download ARM64 GZ |
| Linux | ARMv7 · GZ | 32-bit systems compatible with ARMv7 | Download ARMv7 GZ |
| Linux | MIPS-softfloat · GZ | Check byte order and firmware requirements separately | Download MIPS GZ |
| Check | Requirements and recommendations |
|---|---|
| Executable file | Extract ZIP and GZ files first. On Unix-like systems, grant execute permission if needed. You can’t run the compressed archive itself as a program. |
| Configuration directory | Prepare a valid configuration, rule resources, and a writable data directory. Use the core’s configuration test feature to check syntax before starting it. |
| Service management | Set the run user, log location, and restart policy. Bind the external control interface to loopback by default; configure access restrictions separately if remote management is needed. |
GUI clients may bundle a specific core version and supporting services. Don’t overwrite files inside the app with a standalone core; first check whether the client offers a supported core update method.
View protocol and core compatibility notes →Before and after installation
Get the app running first, then handle configuration and connectivity. Troubleshooting one issue at a time makes it easier to find the cause.
Installers, disk images, archives, and core binaries serve different purposes. On Windows, an EXE usually starts an installer; on macOS, a DMG is a disk image that contains an app; on Android, an APK is installed by the system installer. On Linux, both the distribution’s package format and the architecture must match. The file extension alone doesn’t tell you whether a package will work.
Don’t keep opening a file while your browser is still downloading it. If the system says the package isn’t compatible, note the full message and check your system type instead of repeatedly switching clients. Installation failures and invalid subscriptions happen at different stages and should be troubleshot separately.
Before upgrading, save your subscription URL, local YAML, custom rules, and overrides. Note your ports, DNS mode, and whether TUN is enabled. Subscription URLs may contain credentials, so don’t post them on public forums or include them in screenshots. When switching clients, rebuild the configuration using the import feature, then check any local changes manually.
Automatic subscription updates may overwrite directly edited settings. For changes you need to keep, use the client’s supported override or extension mechanism. A new client may not recognize the old client’s database, cache, or service state. Copying the entire directory can carry old problems over too.
The system proxy affects apps that read the system proxy settings. TUN uses a virtual network interface to handle matching traffic and involves additional permissions, routes, and DNS settings. Start by testing the system proxy. Once the configuration works, decide whether to enable TUN based on the needs of your apps.
Fully quit the old client before switching, including any background process in the system tray or menu bar. Two clients changing proxy settings at the same time can leave the switch enabled while traffic still goes through the old port. If installation requires permission, check which app and action the prompt refers to first.
If the client opens, the app is running—but that doesn’t mean you’re connected. Next, check that the subscription updates, the configuration is enabled, the proxy mode is right, and the system or app is using the selected traffic-routing method. Rule mode routes traffic based on rule order; it doesn’t send every connection through the proxy.
When something goes wrong, check the error type in the logs first. Configuration parsing, port conflicts, permission failures, and remote connection failures call for different fixes. Note the relevant error, then change one setting at a time. Changing DNS, mode, and routing together makes it harder to identify the cause.
Download FAQs
How to choose an architecture, upgrade, and get started.
For Windows, macOS, Android, and iOS, start with Clash Plus. For Linux, start with Clash Verge Rev. Check your device architecture before choosing a package. Clients do not include a subscription service, so you’ll need to import a working configuration after installation.
AMD64 and x64 usually refer to the same 64-bit x86 architecture; ARM64 is a different 64-bit architecture. Android Universal packages include multiple architectures and are usually larger. Check your system or device specifications before downloading—don’t choose based on the device brand alone.
Don’t choose based on the section heading alone. Clash Plus has a dedicated ARM64 package. The listed macOS downloads for Clash Verge Rev, FlClash, and ClashX Meta are x64 or x86_64. On Apple silicon, check Rosetta compatibility before using these packages, or choose a native ARM64 build when available.
The installer includes the client, not a connection service. Import a valid subscription or local configuration, make sure it’s enabled, then turn on the system proxy or TUN as needed. Verify one traffic-routing method first to avoid running multiple proxy clients at once.
Export or back up your subscription URL, local configuration, custom rules, and override settings. Note your ports and traffic-routing method. Fully quit the old client before installing the new version, then check that your configuration migrated on first launch. Don’t overwrite the entire data directory when switching clients.
For everyday desktop and mobile use, choose a GUI client for configuration imports, mode switching, and logs. The Mihomo core is mainly for servers, routers, and command-line setups; you’ll need to manage the configuration, startup process, permissions, and service yourself.