Choose your operating system, then check your processor architecture. Use a graphical client for everyday setup and connections; use the Mihomo core for a self-managed deployment.
Check your OS and architecture
Download the right package
Import an existing configuration
Installers don’t include a subscription or proxy service. New users can follow the subscription import and connection guide. To compare interfaces and workflows, see the client comparison.
The first card on each platform is the recommended option; other clients follow in a consistent order. Use the main button on a card to download its installer.
All graphical client installers below are x64. Check your system type under Settings → System → About. On ARM devices, confirm x64 app compatibility separately; an x64 package is not a native ARM64 build.
A good choice for a first install or for users who want a similar workflow across desktop and mobile. After installation, import an existing configuration, then choose a policy and how to route traffic through the proxy.
EXE installer · Official site: clashplus.io
A Mihomo-based desktop client for managing configurations, rules, and TUN. Follow the client’s prompts to set up the required service or permissions before enabling TUN.
EXE installer · x64
A cross-platform client with a Flutter interface for importing configurations, choosing proxies, and using rule mode. When migrating, import the original subscription first, then check your proxy groups and local overrides.
EXE installer · AMD64 and x64 are equivalent architectures
An alternative desktop interface for users who prefer a different configuration workflow. Whether an existing configuration works depends on the core and configuration fields, not the interface’s appearance.
EXE installer · x64
An archived client for recreating legacy environments, reading existing configurations, and migrating settings. For new devices, choose a maintained client; don’t assume it supports newer proxy protocols or Mihomo fields.
EXE installer · Archived
| Requirement | Guidance |
|---|---|
| Operating system | Use a Windows 10 or 11 version that still receives security updates. Check the selected client’s installer for its minimum requirements. |
| Processor | The graphical installers on this page are x64 / AMD64; they don’t work on 32-bit Windows. |
| Proxy permissions | System proxy and TUN require different permissions. TUN may require administrator approval or a client service. |
Quit other proxy clients before installation to prevent them from changing the system proxy at the same time. After installing, test rule mode with a known-good configuration. If only your browser works, check whether other apps follow the system proxy; there’s no need to enable every networking option at once.
Open About This Mac from the Apple menu and check Chip or Processor. Choose a native ARM64 build for Apple Silicon or an x64 build for Intel. Some downloads currently use the same x64 file for both options; the relevant cards note this.
Separate installers are available for Apple Silicon and Intel. Choose the file for your chip, open the DMG, follow the installer, and then import your configuration.
DMG disk image · clashplus.io
For managing Mihomo configurations and desktop rules. Both architecture options currently provide the x64 DMG; Apple Silicon users need a compatible Rosetta 2 environment to run it.
DMG disk image · Not a native ARM64 build
For users who want a similar interface on desktop and mobile. Both macOS options currently link to the same AMD64 file; Apple Silicon needs compatibility support to run it.
DMG disk image · Both options use the same architecture
Kept for legacy menu bar workflows and configuration migration. Both options currently provide an x86_64 build. For new installs, choose a maintained client, then recheck DNS and proxy settings after migrating.
DMG disk image · Archived
| Requirement | Guidance |
|---|---|
| Chip architecture | Apple M-series chips are Apple Silicon. For Intel Macs, choose x64 / AMD64 / x86_64. |
| macOS version | Minimum requirements vary by client. If the installer says your system is too old, check the client’s requirements instead of trying to bypass the warning. |
| Compatibility | Running an x64 app on Apple Silicon requires Rosetta 2; compatibility mode is not the same as native ARM64. |
Move the app to a permanent location before opening it; don’t run it directly from the disk image. If macOS blocks it, check the source and read the system message, then look under System Settings → Privacy & Security for details. Don’t disable system-wide security protections.
Most newer phones use ARM64, but check the ABI your device actually supports. After downloading an APK, grant install permission only to the source you’re using. The first time you connect, Android will ask you to approve the VPN connection.
ARM64 APK for phones and tablets confirmed to support arm64-v8a. Import your subscription after installing, then approve the system VPN permission when you connect for the first time.
APK · arm64-v8a · clashplus.io
ARM64, 32-bit ARM, and universal packages are available. Choose the matching architecture if you know what your device uses; otherwise, use the universal build. Don’t infer processor architecture from the Android version alone.
APK · Choose by device ABI
ARM64 and ARM packages for users who also use FlClash on desktop. After importing the same subscription, configure app routing and background permissions separately on your phone.
APK · arm64-v8a / armeabi-v7a
Uses its own supported configuration formats; don’t assume Clash YAML will work. Before choosing this client, check whether your subscription provider offers a compatible format and verify which protocols it supports.
APK · Check configuration format compatibility
| Requirement | Guidance |
|---|---|
| Processor ABI | ARM64 corresponds to arm64-v8a; ARM usually corresponds to armeabi-v7a. Universal packages include multiple architectures. |
| Install permission | Follow the system prompt to allow app installs from your current browser or file manager. You can revoke this permission afterward. |
| Connection permission | Using Android’s VPN service to route traffic requires system approval; other VPN apps may conflict. |
If installation fails with an incompatibility warning, check the architecture, minimum system requirements, and signature of any existing app. Don’t repeatedly overwrite an app with the same name from an unknown source. If the connection drops when the screen locks, check battery optimization and background restrictions. Downloading, installing, and connecting through a proxy are separate steps.
Install Clash Plus from the App Store. Check the store listing for current compatibility, device requirements, and availability. Once installed, import a subscription you’re authorized to use.
Get the app from the App Store and receive updates through the store. The first time you connect, follow the iOS prompt to add a VPN configuration, then return to the client to check the selected configuration and connection status.
App Store · Installation and updates managed by Apple
| Requirement | Guidance |
|---|---|
| System and device | Check the Compatibility section on the App Store listing to confirm your device and iOS version meet the requirements. |
| Installation | Install using the App Store link above. Get future updates from the App Store. |
| VPN configuration | The first connection requires system approval. If you already use another VPN, check which one is currently active. |
Installing the client doesn’t create a subscription. After importing a configuration, check that a proxy is available in its groups, then test the service you want to access. If the connection switch turns off by itself, first confirm the system VPN configuration was created, then check the logs for configuration or connection errors.
For desktop use, choose DEB or RPM based on your distribution. All graphical client packages below are AMD64 / x86_64. For ARM servers and router deployments, see the Mihomo core section.
Graphical installers are available in DEB and RPM formats. Choose DEB for Debian- and Ubuntu-based distributions, or RPM for Fedora and other RPM-based distributions. Your package manager will check dependencies.
Desktop client · Choose a package for your distribution
AMD64 DEB package for compatible Debian-based desktop systems. On a headless server, use the core and a system service instead of installing a desktop client.
DEB package · AMD64
| Requirement | Guidance |
|---|---|
| Check your architecture | Run uname -m; x86_64 usually means an AMD64 package, while aarch64 means ARM64. |
| Distribution | Run cat /etc/os-release to identify your distribution, then choose DEB or RPM. |
| Desktop and permissions | Graphical clients need a working desktop environment and the required dependencies. TUN also requires the necessary network permissions. |
Use your system’s package installer to handle local packages, and keep the full output if dependencies fail. If the desktop app won’t start, check for an architecture mismatch, missing dependencies, or a graphics session issue. If it opens but doesn’t route traffic, check the system proxy, app proxy environment variables, and TUN settings.
For servers, routers, and users managing services themselves. The core parses configuration, listens on ports, and handles connections; it doesn’t include a full desktop interface. Most users should choose one of the graphical clients above.
| System | Processor architecture | Package and download |
|---|---|---|
| Windows | AMD64 | Download ZIP · AMD64 |
| Windows | ARM64 | Download ZIP · ARM64 |
| macOS | Intel / AMD64 | Download GZ · Intel |
| macOS | Apple Silicon / ARM64 | Download GZ · Apple Silicon |
| Linux | AMD64 | Download DEB · AMD64 |
| Linux | AMD64 | Download GZ · AMD64 |
| Linux | ARM64 | Download GZ · ARM64 |
| Linux | ARMv7 | Download GZ · ARMv7 |
| Linux | MIPS softfloat | Download GZ · MIPS softfloat |
ZIP files need to be extracted. GZ files are usually compressed single executables, not graphical installers. On Unix-like systems, the extracted file also needs execute permission. Check the service user, configuration path, and listening address before setting up a system service. Don’t expose proxy ports to the public internet without reviewing the security implications.
chmod +x ./mihomo
./mihomo -v
./mihomo -t -f ./config.yaml
./mihomo -f ./config.yamlUse -v to check the core version, -t to test a configuration, and -f to specify a configuration file. A successful test only confirms that the configuration parses; it doesn’t guarantee the remote proxy is reachable. If you see an exec format error, check the CPU architecture. If a port is already in use, stop the old instance or change the configured port.
EXE is a Windows installer, DMG is a macOS disk image, APK is an Android app package, and DEB and RPM are different Linux package formats. Similar file extensions don’t mean the architectures match; a single operating system can have multiple incompatible packages.
Read the specific reason behind any system security warning. Architecture incompatibility, an outdated OS, a signature conflict, and insufficient permissions all require different fixes; don’t assume every warning means the download is corrupted. Record the full message and look up the issue it describes instead of downloading the file repeatedly.
Manage the client app separately from its configuration files. Before updating, back up local rules, overrides, and essential settings, and make sure you can retrieve your subscription again. Subscription URLs may contain credentials; never share them in public screenshots, forums, or online conversion tools.
When switching clients, import an original configuration and confirm basic connectivity first. Then migrate rules, DNS, and TUN settings one at a time. Clients use different data directories and override mechanisms; copying an entire directory may also carry over old ports, controller addresses, and incompatible fields.
First confirm the configuration loaded, then check that a proxy is available in the proxy groups. Test a site in rule mode and check the connection log to see which rule it matched. Browser access doesn’t mean every app is using the proxy: the system proxy, app-level proxy settings, and TUN route traffic differently.
If an import fails, check whether the subscription returns a configuration format supported by the client, rather than a login page or error message. If only some sites fail, check rules, DNS, and restrictions on the destination service first. If all connections fail, check proxy service status, network reachability, and listening ports. See the getting started guide and FAQ for detailed steps.
For everyday use, start with a graphical client. Try Clash Plus for Windows, macOS, Android, or iOS, and Clash Verge Rev for Linux. The Mihomo core is for users who manage configuration files, system services, or router deployments themselves; it does not include a full desktop interface.
x64 and AMD64 usually refer to the same 64-bit x86 architecture, used by most Intel and AMD PCs. ARM64 is for compatible ARM devices. Android universal builds include multiple architectures and are a good choice if you’re unsure which one your device uses. Check your system information before downloading rather than relying on the device brand alone.
Choose a client that explicitly offers a native Apple Silicon build, such as the ARM64 version of Clash Plus on this page. Some clients currently link both architecture options to the same x64 installer, as noted on their cards. These builds require Rosetta 2 on Apple Silicon; an option labeled for Apple Silicon does not guarantee a native build.
The installer includes the client app, not a usable subscription or proxy service. Import a subscription or configuration you’re authorized to use, choose a proxy policy, and enable the system proxy or TUN if needed. If you’ve imported a subscription but still can’t connect, check the connection logs, configuration status, and system proxy settings first.
Back up local configuration, override rules, and any settings you want to keep, and note which subscription source you use. Quit the old client before updating to prevent multiple instances from competing for listening ports. Subscription URLs may contain credentials, so store backups privately. When switching clients, don’t overwrite another app’s data directory.
Archived downloads for Clash for Windows and ClashX Meta are available for recreating legacy environments and migrating configurations. They’re not recommended for new devices, and may not support newer protocols or Mihomo configuration fields. Keep a copy of your old configuration, then test it step by step in a maintained client.