Browse available clients by operating system. Each card lists its use case, package format, and CPU architecture. Desktop users should generally choose a GUI client, while server and router users can go straight to the Mihomo core section.
Platform tabs sync with the URL anchor, so refreshing or sharing a link returns you to the same section. Version fields appear only when the release list provides a valid value; package buttons always retain a complete fallback path.
Windows users will usually want the x64 installer. The installer creates a Start menu shortcut and handles standard upgrades; the portable archive is better for keeping the client in a separate folder. On first launch, install the client, import a subscription URL, choose a policy node, and enable the system proxy. Configure TUN mode only when you need to route applications that do not use the system proxy.
For quick installation and subscription management, start with Clash Plus. For detailed desktop controls, compare Clash Verge Rev, FlClash, and Clash Nyanpasu. Clash for Windows is retained as an archived client.
For Windows users who want one clear interface for installation, subscription import, policy switching, and system proxy settings. The package uses the familiar x64 installer format and offers a straightforward upgrade path.
Offers comprehensive desktop settings for managing configurations, policy groups, the system proxy, and TUN options. The current download is a Windows x64 installer.
The same client covers desktop and mobile platforms with a consistent interface and configuration workflow. On Windows, choose between an installer and an archive: the installer suits regular use, while the archive runs from a standalone folder.
Provides a desktop GUI and common proxy controls for users who prefer managing configurations independently. A Windows x64 installer is available here.
This client is archived. The installer remains available for migrating older configurations and specific compatibility cases. New installations should use a maintained client listed above.
| Check | Recommendation | Details |
|---|---|---|
| System version | 64-bit Windows 10 or Windows 11 | Newer system versions generally include more complete runtime libraries and networking components. |
| CPU architecture | x64 / AMD64 | The desktop packages on this page target common 64-bit Intel and AMD devices. |
| Installation permissions | Allow the installer to write to the application directory | Enabling network-layer features such as TUN may require administrator privileges. |
| Upgrade procedure | Quit the older version before installing | This helps prevent overwrite failures caused by locked files or two client processes running at once. |
Before downloading, check whether your Mac uses Apple silicon or an Intel processor. Apple Silicon packages support M1, M2, M3, M4, and later chips; Intel packages support older x86_64 Macs. After opening the DMG, drag the app to the Applications folder and launch it from there. The first time you enable the system proxy, network extension, or TUN, grant the permissions requested by macOS.
Open About This Mac or System Information from the Apple menu and check the Chip or Processor field. Select Apple Silicon when an Apple M-series chip is shown, or Intel when Intel is listed.
Provides Apple Silicon and Intel DMG packages for macOS users who want to import subscriptions, select policies, and configure the system proxy directly.
For desktop users who need configuration management, policy-group switching, system proxy controls, and TUN settings. Separate downloads are available for Apple Silicon and Intel.
For users who want a similar workflow across computers and Android devices. macOS downloads are separated by processor type, so verify the chip before installing.
This client is discontinued. The download remains available for legacy environment migration, existing configuration continuity, and compatibility needs. New users should choose a maintained macOS client above.
| Check | Recommendation | Details |
|---|---|---|
| Processor | Apple Silicon or Intel | The package architecture must match the Mac’s chip. |
| Installation method | Open the DMG and drag the app to Applications | Launching from Applications lets macOS manage the app consistently. |
| Network permissions | Allow proxy or network extensions when needed | TUN and enhanced traffic interception may require separate system approval. |
| Upgrade procedure | Quit the old version before replacing the app | Existing settings are usually stored in the user configuration directory, not inside the application bundle. |
Most recent Android phones and tablets use arm64-v8a, so the ARM64 package is usually the best choice. Older devices may use armeabi-v7a; when the architecture is unknown, Clash Meta for Android offers a universal build. After installation, import a subscription, choose a node in the policy group, and enable the connection. When Android displays a VPN confirmation dialog, allow the client to create a local virtual network interface.
For a device released in recent years with a mainstream 64-bit chip, choose ARM64. Older 32-bit devices should use ARM. The universal build supports a wider range but is usually larger.
For common 64-bit Android devices, with direct subscription import, policy selection, and connection controls. The current entry provides an arm64-v8a package.
Provides ARM64, 32-bit ARM, and universal packages for users who need an exact architecture match or compatibility with older devices. Choose the universal build when the device architecture is unknown.
For users already running FlClash on desktop who want a similar interface and configuration workflow on mobile. ARM64 and 32-bit ARM packages are available.
A rule-based proxy client for Android users familiar with configuration files, policy groups, and rule-based routing. A universal Android package is provided here.
| Check | Recommendation | Details |
|---|---|---|
| CPU architecture | Confirm ARM64 or ARM first | If the architecture does not match, Android may reject the installation outright. |
| Installation permissions | Allow the current browser or file manager to install apps | You can revoke this permission after installation if needed. |
| Connection permissions | Allow VPN connections | The client uses Android’s VPN interface to route traffic that requires a proxy. |
| Background operation | Adjust battery optimization settings if needed | Strict background restrictions may pause the connection service after the screen locks. |
Install Clash Plus on iOS through the App Store. After installation, copy your subscription URL, add it in the app, and update the configuration; then choose a policy node and allow iOS to add a VPN configuration. See the App Store listing and official website for app details, supported platforms, and further information.
Tap the App Store button to open the app listing, verify the app name, and install it. When connecting for the first time, iOS displays a VPN configuration permission prompt; approve it to establish the connection.
For iPhone and iPad, installed through the App Store. The app supports subscription adding, configuration updates, policy selection, and connection controls for everyday mobile use.
| Check | Recommendation | Details |
|---|---|---|
| Device | iPhone or iPad | Use the App Store on the device to open the app listing. |
| System permissions | Allow VPN configuration | The system displays the authorization prompt when the first connection is established. |
| Subscription import | Copy the complete subscription URL | After importing, update the configuration first, then check the policy groups and node list. |
| Connection verification | Check the system status bar and app status | Confirm that VPN is enabled, then test the target website or app. |
Linux desktop users can choose Clash Verge Rev or FlClash. DEB packages are primarily for Debian, Ubuntu, Linux Mint, and related distributions; RPM packages are mainly for Fedora, RHEL, openSUSE, and similar systems. After installation, launch the client from the desktop app menu, import a configuration, and set the system proxy for your desktop environment. Servers, containers, and software routers are generally better served by the Mihomo core below.
Choose DEB for Debian- and Ubuntu-based systems, and RPM for Fedora- and RHEL-based systems. If you only need a command-line service, skip the desktop client and switch to the Mihomo core section.
For Linux devices with a desktop environment, offering configuration management, policy selection, and system proxy controls. AMD64 DEB and RPM packages are currently available.
For users who want a similar interface across Linux, Windows, macOS, and Android. Linux currently provides an AMD64 DEB installer.
| Distribution type | Package | Installation instructions |
|---|---|---|
| Debian / Ubuntu family | AMD64 DEB | Use the system software installer or install the local DEB with a package-management command. |
| Fedora / RHEL family | x86_64 RPM | Clash Verge Rev provides an RPM package that can be installed with the appropriate package manager. |
| Desktop environment | Graphical session required | Desktop clients require a graphical environment; use Mihomo on headless servers. |
| Traffic interception | System proxy or TUN | TUN mode typically requires additional permissions and system network configuration. |
Mihomo is a core designed for configuration-file and command-line workflows, suitable for servers, software routers, bypass gateways, containers, and automated deployments. It does not provide a complete desktop GUI; before launching, prepare a YAML configuration and define the configuration directory, listening ports, log level, and runtime permissions. Most desktop and mobile users should choose a GUI client for their platform above.
AMD64 is common on 64-bit Intel and AMD computers and servers; ARM64 is common on 64-bit ARM devices; ARMv7 is used by some older 32-bit ARM devices; MIPS softfloat is mainly found on specific router platforms.
| System | Architecture | Format | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download AMD64 |
| Windows | ARM64 | ZIP | Download ARM64 |
| System | Architecture | Format | Download |
|---|---|---|---|
| macOS | Intel AMD64 | GZ | Download Intel version |
| macOS | Apple Silicon ARM64 | GZ | Download Apple Silicon version |
| System | Architecture | Format | Download |
|---|---|---|---|
| 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 |
| Check | What to verify |
|---|---|
| Architecture | Use system commands to confirm AMD64, ARM64, ARMv7, or MIPS so you do not download an incompatible binary. |
| Configuration file | Prepare a valid YAML configuration and check indentation, port conflicts, DNS settings, rule-set paths, and subscription-provider fields. |
| Execution permissions | After extracting the file, make it executable. For TUN, privileged ports, or routing changes, configure permissions as required by the system. |
| Background service | For long-running deployments, use systemd or another service manager and define the working directory, configuration path, restart policy, and log output. |
Manage subscriptions, policy groups, the system proxy, and logs from the interface for everyday computer and mobile use.
Runs through configuration files and the command line for servers, routers, containers, and automated deployments.
Dedicated entry points are available for Windows, macOS, Android, iOS, and Linux.
Client names may look similar, but packages are not interchangeable. Identify the platform, confirm the CPU architecture, then choose a GUI or command-line core to avoid most installation failures.
Windows EXE, macOS DMG, Android APK, and Linux DEB or RPM packages use different installation mechanisms and cannot be used interchangeably. Install iPhone and iPad apps through the App Store. A server may run Linux, but without a desktop environment it is better suited to the Mihomo core than a GUI client.
Windows and Linux desktop computers commonly use AMD64 or x86_64; Apple-silicon Macs use ARM64, while Intel Macs use x64; newer Android devices generally use arm64-v8a. Router architectures vary widely, so confirm them in the device dashboard or with system commands before downloading Mihomo rather than relying on the brand or appearance.
GUI clients suit users who want visual subscription import, manual policy-group switching, and connection and log views. Mihomo is better for users who understand configuration-file structure, need a service manager for long-running operation, or plan to deploy on a software router or in a container. The two may share similar configuration concepts, but installation, updates, and troubleshooting differ.
Here are answers to the download page’s most common selection questions. For more complete steps on subscription import, system proxy setup, and connection troubleshooting, continue to the Getting Started and FAQ pages.
For straightforward installation, subscription import, and everyday switching, start with Clash Plus. For more desktop settings, compare Clash Verge Rev, FlClash, and Clash Nyanpasu. Clash for Windows is archived and is better suited to migrating older configurations or specific compatibility cases, not as the first choice for a new setup.
Choose Apple Silicon or ARM64 for Macs with M1, M2, M3, M4, and other Apple chips; choose Intel or x64 for older Intel Macs. Open About This Mac or System Information from the Apple menu and check the Chip or Processor field. With the wrong architecture, the app may not open or may require an additional compatibility layer.
arm64-v8a is for mainstream 64-bit ARM devices and is usually right for recent phones and tablets. armeabi-v7a targets older 32-bit ARM devices. A universal build combines support for multiple architectures in one package, which helps when the architecture is unknown but usually makes the file larger. If Android reports that the package is incompatible, recheck the device architecture and Android version.
GUI clients provide subscription management, policy-group selection, a system proxy switch, connection views, and logs for everyday desktop and mobile use. The Mihomo core mainly runs with YAML configuration and the command line, often alongside systemd, containers, or router service managers. Most users should choose a GUI client; consider the core for servers and automated environments.
First verify the operating system, CPU architecture, and package format. For example, Intel Mac and Apple-silicon packages cannot be mixed freely, while Linux DEB and RPM packages target different distribution families. Then check whether an older version is still running, whether the system allows the app to launch, and whether network extensions or TUN have the required permissions. For upgrade conflicts, quit the old process before installing.
The page reads version text from the release list at runtime. If a project has no valid version field yet, that area stays hidden instead of showing an empty label or incomplete text. The download button retains the complete package address; if the network request fails, the browser continues using the fallback link embedded in the page.
Installing the client is only the first step. Next, add a subscription, update the configuration, choose a policy group, enable the system proxy, and verify the connection. The Getting Started page presents the complete workflow in this order.