Downloads · Architecture · Configuration
Check your device’s architecture before choosing an installer.
Use a graphical client on desktop and mobile devices, and the Mihomo core on servers and routers. Find installers organized by platform below, with maintenance status noted for archived clients.
Browse platform downloads ↓Downloads by platform
Buttons show the file format and architecture. Version details appear on cards when available; choose files based on the actual installer.
Most Intel and AMD PCs should use the x64 installer. Quit any running proxy client before installing and launching another one to avoid both apps controlling the system proxy or using the same port.
A good choice for first-time setup and everyday use. Start with a graphical client to import a subscription, choose a proxy mode, and configure the system proxy. It’s easier to check the status than with a command-line core. After installation, select a configuration and check that a proxy group has an available outbound.
clashplus.io
For desktop users who want to manage subscriptions, rules, and TUN settings. First test the connection with the system proxy, then enable service mode or TUN only if needed. These options use different permissions and routing, so avoid changing everything at once when troubleshooting.
For users who want a similar experience on desktop and mobile. Compatible subscription configurations may carry over, but check keyboard shortcuts, system proxy settings, and startup options on each device. Similar interfaces don’t mean the operating systems handle permissions the same way.
An alternative desktop interface for users familiar with configuration files and proxy groups. After importing a configuration, check that it loads successfully. If a field isn’t recognized, check whether the core supports it instead of repeatedly reinstalling the same app.
Kept for reproducing older setups, migrating configurations, and comparing interfaces. For new installations, choose a client above that’s still maintained. The archived core has limited support for newer protocols and fields. If a configuration fails to parse, check compatibility first; updating the subscription alone may not help.
| Check | What to check |
|---|---|
| System and architecture | This section offers common x64 desktop installers. Go to Settings → System → About to check your system type. On Windows on ARM devices, also verify app compatibility. |
| Windows version | Use a Windows version that’s still supported where possible. Minimum version requirements vary by client; check the installer prompt and release notes for the client you’re installing. |
| Runtime dependencies | Clients built with WebView may require WebView2. If the window is blank or the app crashes on startup, record the error and check the runtime dependencies before deleting your configuration. |
| Permissions and traffic routing | The system proxy and TUN have different permission requirements. Before enabling TUN, check whether you need administrator access or service mode, and quit any other client before testing. |
Check the chip type in Apple menu → About This Mac. Choose the native or x64 file for Apple Silicon or Intel, respectively. Some clients currently offer the same x64 installer for both; the card will say so.
Choose the file for your chip, open the disk image, and move the app to Applications. Don’t run it from the mounted DMG long-term. After launching it for the first time, import a configuration and check that the system proxy turns on. Set the app to launch at login if needed.
clashplus.io
For users who need subscription and override management. Both links currently point to the same x64 file, not a native ARM64 build. Apple Silicon users should check whether Rosetta is supported. Before switching clients, turn off the old app’s system proxy to avoid a stale proxy address.
A good fit if you want a consistent experience across platforms. The available file is amd64 (x64), and both chip options currently link to the same file. Once the app launches, check that the right configuration is selected, then verify the proxy group and system proxy. An open interface doesn’t mean you’re connected.
For maintaining an existing menu bar workflow or comparing migration options. Both links provide an x86_64 file. Check permissions, compatibility, and configuration support on newer systems. Before switching clients, save your YAML file and custom rules, then migrate them one at a time.
| Check | What to check |
|---|---|
| Processor | If About This Mac lists an Apple chip, choose a native ARM64 file. If it lists an Intel processor, choose x64. If only x64 is available, check Rosetta support first. |
| Windows version | Minimum macOS versions vary by app. If you see a message that the app can’t run on this version, check the release notes. Changing the file extension won’t resolve compatibility issues. |
| Install location | Move the app to Applications before launching it. If macOS shows a security alert, verify the file’s source and follow the options provided by the system. |
| Network permissions | The system proxy, service mode, and TUN may require different permissions. Enable only what you need, then expand the scope of traffic routing after confirming the connection works. |
Most recent phones use arm64-v8a. Older devices or systems that support only 32-bit apps need armeabi-v7a. A 64-bit processor doesn’t guarantee that the OS supports 64-bit apps, so check your device’s system information before choosing.
For Android devices that support 64-bit ARM apps. After installing, import a subscription and approve the system VPN prompt when connecting for the first time. If the connection stops when the screen locks, check background restrictions in your battery settings before changing your configuration.
clashplus.ioFor users familiar with configuration files and proxy rules. If you know your device’s architecture, choose the matching installer. If not, consider the universal build, which is usually larger. Before connecting, check that the configuration is selected. Rule mode and per-app routing settings also affect which traffic is routed.
For users who want a similar configuration workflow on mobile and desktop. Android’s VPN service works differently from a desktop system proxy. If only certain apps have connection issues, check per-app routing and bypass settings, then review the rules and DNS.
For Android users with existing configurations that support the Surge format. Surfboard isn’t a drop-in replacement for importing Clash YAML; check protocol, rule, and subscription format compatibility separately. If you only have a Clash configuration, use one of the clients above that supports its format.
| Check | What to check |
|---|---|
| App architecture | arm64-v8a is for 64-bit ARM apps; armeabi-v7a is for 32-bit ARM apps. Check the app’s packaging details to see which architectures a universal build supports. |
| Windows version | Minimum Android versions vary by app. If the installer is incompatible, check your OS version and architecture. Avoid repeatedly trying modified packages from unknown sources. |
| Install permission | Follow the system prompt to allow installs from your current browser or file manager. If the installer conflicts with an existing app, back up your configuration and verify the signing source before deciding whether to uninstall the old app. |
| Background activity | The first connection requires VPN permission. Most devices allow only one standard VPN service at a time; check compatibility before using another VPN app simultaneously. |
Check Clash Plus’s current compatibility requirements and app details on the App Store. After installing, add a valid configuration, then follow the system prompt to add a VPN configuration. Once authorized, check the connection status in the app.
For managing configurations and proxy connections on iPhone and compatible devices. The App Store listing has current system requirements and release notes. After installing, import a subscription and check the selected configuration and proxy group. If the connection fails when switching between Wi-Fi and cellular, reconnect and check network permissions first.
clashplus.io| Check | What to check |
|---|---|
| System compatibility | Check the minimum OS version and supported devices listed under Compatibility on the App Store. Review the listing before updating your system. |
| Configuration source | Prepare a valid subscription or compatible configuration. Installing the app doesn’t automatically provide a working proxy connection. |
| Connection permission | Follow the system prompt to add a VPN configuration the first time you connect. If another VPN is active, check which app is currently routing traffic. |
| Troubleshooting details | Note your network type, the exact error message, and the steps that triggered it. Hide subscription links and credentials in configurations before sharing screenshots. |
The graphical clients here are for AMD64 / x86_64 desktop systems. Debian- and Ubuntu-based distributions generally use DEB; Fedora and other RPM-based distributions use RPM. For servers or other processor architectures, see the Mihomo core section.
For users who want a desktop interface to manage subscriptions, rules, and connection status. Install with your distribution’s package manager to handle dependencies. If the app launches but the system proxy doesn’t work, check your desktop environment’s proxy settings, not just the core’s port.
For desktop users on DEB-based distributions. Before installing, confirm that your processor is AMD64 and that your system has a graphical session and the required app dependencies. Command-line tools may not use the desktop system proxy. For terminal traffic, check proxy environment variables or configure routing separately.
| Check | What to check |
|---|---|
| Processor | Run uname -m to check. The output x86_64 corresponds to the AMD64 files in this section; ARM devices can’t install these desktop packages directly. |
| Distribution | DEB and RPM use different package management systems. Don’t change a file extension to convert formats; choose the package made for your distribution. |
| Desktop dependencies | Graphical clients need an available desktop session and the required runtime libraries. If dependencies are missing, review the package manager output before installing them. |
| Network permissions | TUN uses a virtual network interface and routing permissions. Desktop users should test the system proxy first. For servers, configure services and permissions based on how the core is deployed. |
For users managing servers, routers, or services themselves. The core has no desktop settings window and doesn’t include a subscription configuration. Most users should choose a graphical client above; download a core here only if you need a command-line deployment.
AMD64 and x86_64 usually refer to the same 64-bit architecture; ARM64 and ARMv7 are not interchangeable. For routers, also check the instruction set, endianness, and floating-point ABI. For MIPS in particular, the device brand alone isn’t enough to identify the right file.
| System | Architecture and format | Installer |
|---|---|---|
| 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 softfloat GZ |
These commands are for Linux: rename the extracted core to mihomo, save your configuration as config.yaml in the current directory, then run the test. A successful test means the configuration can be loaded; it doesn’t guarantee that every outbound connection will work.
chmod +x ./mihomo
./mihomo -t -f ./config.yaml| Check | Before deployment |
|---|---|
| System and ABI | Check the CPU architecture, OS bitness, and supported file formats. If you see Exec format error, check the architecture first rather than changing the configuration. |
| Configuration and directories | Prepare a loadable YAML configuration and check the paths to rule sets and database files. The service account needs read access to the relevant directories. |
| Ports and permissions | Check that the listening port is available before starting. Enabling TUN, changing routes, or listening on a privileged port requires additional permissions and a clear rollback plan. |
| Remote maintenance | Keep your current session open before changing routes on a remote server. Don’t expose the control interface to the public internet, and protect credentials in logs and configuration files. |
Clash download FAQs
For Windows, macOS, Android, and iOS, start with Clash Plus for your platform. For Linux, consider Clash Verge Rev. Choose a client card if you need a graphical interface; Mihomo is a command-line core, not a desktop installer.
Check your device’s processor and operating system architecture in system settings, then match them to the download button. Windows x64 is for most 64-bit Intel and AMD devices. Android arm64-v8a is for devices that support 64-bit ARM apps. If you’re unsure of your Android architecture, try the universal build, which is usually larger. Mac download buttons show the architecture of the available installer; don’t infer the file contents from the processor name alone.
Installing the client doesn’t set up a proxy configuration. Import a valid configuration from the subscription or configuration page, select it, then check the rule mode, proxy groups, and system proxy settings. You’ll need to obtain a subscription separately. Don’t post subscription links in public comments or screenshots.
Make sure the download is complete and the file extension is correct, then check your OS version and processor architecture. If a Windows desktop client won’t start, check its runtime dependencies. On macOS, verify the app’s source using the system’s security prompts; don’t disable security protections across the board. If the problem persists, note the full error and follow the Troubleshooting guide.
Export or back up your current configuration, custom rules, overrides, and any client settings you need. Then quit the old client and install the update. When switching clients, use a standard YAML configuration where possible; don’t overwrite the entire application data directory.
Both clients are no longer maintained. Their download links remain available for migrating older setups and checking compatibility. For new devices, choose a client that’s still maintained. Older cores may not support newer protocols or configuration fields; if parsing fails, check core compatibility first.
Already installed, but subscription updates fail, the system proxy doesn’t work, or the client crashes? Troubleshoot by symptom →