Choose your device’s operating system, then check its CPU architecture. For everyday use, choose a GUI client; for server and router setups, use the Mihomo core.
You’ll also need to import a valid configuration after installing. Have a subscription URL ready? Continue with the subscription import guide.
Choose a client that’s still maintained. The Windows downloads for the GUI clients below are x64 packages. For Windows on ARM, check Windows compatibility and client support separately.
A good choice for desktop users who want to start by importing a configuration. After installation, add a subscription or local configuration, then check your proxy mode and proxy group. Test the system proxy and TUN separately; you don’t need to enable both on first launch.
Manage configurations, proxy groups, and connections through a graphical interface. A good fit if you need more control over rules and traffic routing. Before using service-related features, check the permission prompts and installation status, then verify that TUN is actually routing traffic.
Includes common tools for managing configurations, proxies, and logs. The installer is suited to regular desktop use; the ZIP archive is for users who prefer to choose the program directory themselves. If you move the program, check where configurations are stored and update the startup path.
Manage Clash configurations and runtime status on your desktop. If you already use another client, quit it before launching this one to avoid mixed-port or controller-port conflicts. After migration, check the logs to confirm the configuration loaded correctly.
An archived download, mainly for migrating existing setups or reproducing older configurations. For new installations, choose a maintained client above. Older cores may not recognize newer protocols or configuration fields. If an import fails, check the logs instead of repeatedly reinstalling.
| Check | Requirements and steps |
|---|---|
| OS and architecture | Check your system type under Settings → System → About. This page mainly provides x64 packages. See each client’s release notes for its minimum supported Windows version. |
| Installation permissions | Launching the app normally and installing a service are separate tasks. Installing a service or virtual network adapter may require administrator approval. |
| Before connecting | Have a valid configuration ready. Make sure no other app is using the local proxy ports, and run only one proxy client during your initial test. |
If only Microsoft Store apps can’t connect, first check which traffic is covered by the system proxy. Then see Clash UWP loopback settings—you may not need a different installer.
Check your chip under About This Mac. Apple silicon uses ARM64; Intel uses x64. Some listings currently link to the same x64 package from both download buttons, so read the architecture notes below before downloading.
Separate installers are available for Apple silicon and Intel. Open the DMG and follow the installer to place the app, then launch it from Applications. Import a configuration on first launch. Once your proxy group is available, grant permission for any network features you need.
Manage subscriptions and rules through a desktop interface. The Apple silicon download listed here currently serves an x64 package, not a native ARM64 build. Before running it on an Apple silicon Mac, check that the translation environment is available and that the client is compatible.
Provides a configuration import and proxy management interface. Both macOS downloads currently serve amd64 packages. Apple silicon users should check the translation environment first. For a native ARM64 package, use the download above explicitly labeled ARM64.
An archived option for users who want to keep an existing menu bar workflow. Both downloads currently provide x86_64 packages; the button label does not mean the package is native ARM64. Before upgrading macOS or migrating your configuration, keep a restorable copy of the old setup.
| Check | Requirements and steps |
|---|---|
| Chip type | For Apple silicon, choose a package explicitly labeled ARM64. For Intel, choose x64 or amd64. Always check the package’s actual architecture. |
| OS version | Check the minimum macOS version in the selected client’s release notes. Being able to open a DMG doesn’t mean the app supports your current system. |
| Network permissions | Grant network permissions as needed. If using a service or TUN, confirm that the required component is installed and allowed to run. |
If macOS security blocks the app from launching, verify its source and review the system prompt. Use the official authorization flow in System Settings rather than disabling system security altogether.
Most recent phones use ARM64; older devices may require ARMv7. Check your device specifications before installing. The first connection usually triggers a system VPN permission prompt. After granting permission, test traffic in your browser and other apps.
An ARM64 APK is available here. After installation, import a configuration, choose a proxy group, then start the connection and accept the system VPN prompt. Background operation depends on the phone manufacturer’s policies, so check battery restrictions and persistent notification settings for your device.
For Android users who manage Clash Meta configurations. If you know your device’s architecture, download the matching package; if not, consider the universal package. Enable the configuration in the client after importing it—a configuration that’s imported but not activated won’t connect.
Includes common ARM64 and ARMv7 packages. If you use the client on multiple devices, import a configuration on each one as appropriate. Don’t assume all desktop network settings apply to phones. Retest the connection after switching between mobile data and Wi-Fi.
A universal Android package is available. Surfboard uses its own supported configuration formats; Clash YAML isn’t a universal format you can import directly. Check with your configuration provider which formats and protocols are supported before testing the connection.
| Check | Requirements and steps |
|---|---|
| CPU architecture | ARM64 corresponds to arm64-v8a; ARMv7 corresponds to armeabi-v7a. Check which app architectures your device supports. |
| OS and installation | Check the selected client’s minimum Android version. Follow the system prompt to grant the download source permission to install apps. |
| VPN and background use | Make sure no other app is using the VPN connection. For a persistent connection, adjust background activity and battery settings as needed for your device. |
If you see “App not installed,” check the architecture, available storage, and whether the existing app has a conflicting signature. Don’t uninstall the old version right away; export your configuration first to avoid losing custom settings.
Install Clash Plus from the App Store. Check the store listing for device and OS compatibility. After installation, add a configuration and grant the required network permissions.
Check the App Store listing for device compatibility and feature details. For first-time setup, import a valid configuration and choose a proxy group. When starting a connection, follow the system prompt to add a VPN configuration. Manage node changes and rules in the client.
| Check | Requirements and steps |
|---|---|
| Compatible devices | Check the App Store listing for compatible devices and the minimum OS version, then make sure your device meets the requirements. |
| Network permissions | Follow the prompt to add a VPN configuration on your first connection. If you have another VPN app, check which one is currently active. |
| Configuration source | Have a valid subscription or a configuration file supported by the client. After importing, check that usable proxy groups are available. |
On mobile, the OS handles traffic routing through its network interfaces. Don’t follow the desktop steps for a “system proxy port.” After granting permission, check both the connection status in the app and the results of an actual connection test.
For devices with a desktop environment, choose a GUI client. Check your distribution’s package format and CPU architecture before downloading. For headless servers, the Mihomo core is usually a better fit.
Includes amd64 DEB and x86_64 RPM packages. Choose DEB for Debian- and Ubuntu-based systems, or RPM for Fedora and other RPM-based distributions. Install through your distribution’s package manager to handle dependencies and make future removal easier.
An amd64 DEB desktop package is available here. Check the desktop environment and dependencies before installing. Import a configuration once the client launches. Command-line tools may not automatically use the desktop system proxy, so test them separately using the method each tool supports.
| Check | Requirements and steps |
|---|---|
| Architecture and distribution | Run uname -m to check your architecture. The GUI packages here are for amd64 / x86_64; don’t install them on ARM devices. |
| Desktop and dependencies | Make sure the desktop environment required by the client is installed. Check the client’s release notes and your package manager for dependency requirements. |
| Services and permissions | TUN and background services may require extra permissions. Test a regular proxy first, then configure services. Avoid starting the core through multiple managers at the same time. |
Don’t rename an RPM file to DEB and try to install it. Package formats, dependencies, and install scripts are distribution-specific. If installation fails, keep the full package manager error so you can investigate the cause.
For users running servers, routers, or self-managed environments. The core loads a configuration and processes traffic; it doesn’t provide a full desktop configuration interface. Most computer and phone users should choose one of the GUI clients above.
| OS | Architecture | Format and use | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP · x64 systems | Download AMD64 ZIP |
| Windows | ARM64 | ZIP · ARM64 systems | 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-based package managers | Download AMD64 DEB |
| Linux | AMD64 | GZ · standalone executable | Download AMD64 GZ |
| Linux | ARM64 | GZ · 64-bit ARM systems | Download ARM64 GZ |
| Linux | ARMv7 | GZ · 32-bit ARM systems | Download ARMv7 GZ |
| Linux | MIPS softfloat | GZ · soft-float systems | Download MIPS GZ |
| Check | Requirements and steps |
|---|---|
| Runtime files | Extract ZIP files; extract the executable from GZ files. On Unix-like systems, check that it has execute permission. Don’t try to run a compressed archive as a program. |
| Configuration and directories | Prepare a valid YAML configuration. Check the working directory, configuration path, and read/write permissions for the account running the core. |
| Network setup | Reserve listening ports and configure virtual network adapters, routes, and DNS as needed. On low-resource devices, check available storage and memory too. |
| Service management | Run the core in the foreground and check the logs first, then hand it over to the system service manager. The service account may differ from your interactive login account. |
Replacing the core and updating a client are not the same thing. A GUI client may manage its own core path and startup arguments; overwriting program files can disrupt future updates. Read the client’s core management documentation before making changes.
Installing a client only means the local app is ready. First, import a valid subscription or local configuration and confirm it’s enabled and has usable nodes. Start in rule mode, select an outbound in a proxy group, then enable the system proxy or mobile VPN. Open a known test site and check the connection log to see whether traffic went direct or through a proxy.
A speed test reflects only its specific test target and the network conditions at that moment. Lower latency doesn’t necessarily mean faster large downloads. If browsing works but one app doesn’t, check rule matching, DNS, and whether the app uses the system proxy. Don’t change nodes, modes, and clients all at once based on a single failure.
See the connection testing guide →When migrating from an old client, export your local configuration and custom rules first. Note your commonly used proxy groups and ports, then quit the old app. Keep the new client’s default settings on first launch and test a basic connection. Then migrate overrides, TUN, startup behavior, and other features one at a time, testing after each change so it’s easier to roll back if something goes wrong.
Updating a subscription may overwrite content from the remote configuration. For changes you need to keep, use the client’s override or merge feature rather than editing a remote configuration once and expecting the change to persist. Configuration files and screenshots may contain private subscription URLs. Remove credentials before sharing anything for troubleshooting.
See proxy groups and configuration management →For everyday use on computers and phones, choose a client with a graphical interface. Clients provide options for importing configurations, choosing proxy groups, and viewing logs. The Mihomo core is mainly for servers, routers, and users who manage their own services; you’ll need to provide a configuration file and set up how it runs.
Check your device’s CPU architecture rather than relying on its operating system name. On Windows, find the system type in Settings under System information. On macOS, check About This Mac to distinguish Apple silicon from Intel. For Android, check your device specifications. On Linux, run uname -m. Even if your system supports an architecture, not every client on this page necessarily offers a native package for it.
An installer doesn’t include a usable proxy configuration. Import a valid subscription or local configuration, enable it, and select an available proxy group. Then turn on the system proxy or configure TUN if needed. Finally, check the connection and logs to confirm requests are matching the expected rules.
Back up your local configuration, custom rules, overrides, and any essential client settings. Note the name of the configuration in use. Quit the old client before updating to avoid port conflicts. Since configurations may contain subscription URLs and credentials, store backups somewhere secure. After updating, check your configuration, proxy groups, and traffic-routing status.
Legacy clients are intended to keep existing setups working, not as the first choice for a new installation. Clash for Windows and ClashX Meta are no longer maintained and may not support future system changes or new configuration fields. For a new device, choose a client that’s still maintained. When migrating, check configuration syntax field by field rather than overwriting your existing setup.