Choose a package by system and CPU architecture

Clash downloads and cross-platform client packages

Windows, macOS, Android, iOS, and Linux clients are listed in one place. Confirm your operating system first, then choose the file that matches your CPU architecture; server and router users can go directly to the Mihomo core section.

Graphical client System requirements CPU architecture Mihomo core

Choose a Clash client by platform

Switch platforms to view client order, package formats, and minimum system requirements. Version details appear only when the release list returns valid data.

Windows

Windows graphical clients

Most desktop PCs use the x64 package. After installation, import a subscription, choose a proxy group, and enable the system proxy. The legacy client is intended for existing configuration migration and compatibility scenarios.

Desktop

Clash Verge Rev

For Windows users who need configuration file management, rule inspection, proxy group switching, and system proxy control.

PackageWindows x64 · EXE
Cross-platform

FlClash

The same interface across desktop and mobile, suitable for users who want a similar workflow on multiple devices.

Available filesInstaller or portable ZIP
Configuration management

Clash Nyanpasu

Provides configuration switching, proxy group management, and runtime status viewing for desktop users familiar with Clash configuration structures.

PackageWindows x64 · EXE
Discontinued

Clash for Windows

An archived client for migrating existing configurations or supporting older environments. For new installations, prefer a maintained client higher in this section.

Archived formatWindows · EXE

Windows system requirements

CheckRecommendationDetails
SystemWindows 10 / 11Keep the system networking components and WebView runtime available and up to date.
Architecturex64The Windows graphical client packages on this page are primarily x64.
PermissionsStandard permissions; TUN may require elevated permissionsThe system proxy can usually be switched directly; follow system prompts when installing network components.

Command-line and embedded environments

Mihomo core downloads

The Mihomo core is intended for servers, software routers, containers, and users who maintain configuration files themselves. Core packages do not include a desktop GUI; you must prepare configuration files, startup arguments, service management, and log directories manually.

For ordinary Windows, macOS, Android, iOS, and Linux desktop users, the graphical clients above are recommended. They provide common controls for subscription updates, proxy group switching, system proxy, and runtime status.

System Architecture and format Download
Windows AMD64 · ZIP Download AMD64
Windows ARM64 · ZIP Download ARM64
macOS Intel · GZ Download Intel
macOS Apple Silicon · GZ Download Apple Silicon
Linux AMD64 · DEB Download DEB
Linux AMD64 · GZ Download AMD64
Linux ARM64 · GZ Download ARM64
Linux ARMv7 · GZ Download ARMv7
Linux MIPS soft-float · GZ Download MIPS
01

Confirm the CPU architecture

On Linux, use uname -m to check the architecture. Output x86_64 usually means AMD64; output aarch64 usually means ARM64.

02

Prepare the configuration file

Save the converted subscription or local configuration as a YAML file, then check proxy groups, rules, DNS, listen addresses, and the control port for the current environment.

03

Hand it over to the service manager

In server environments, use the system service manager to start the core, with explicit permissions for the configuration directory, log directory, and restart policy.

Installation and migration notes

After confirming the package type, handle the old client shutdown, configuration import, and system proxy switch.

Exit the old client before installing

Running multiple proxy clients at once can cause conflicts over listen ports, the system proxy, and the TUN network interface. Before installation or migration, exit the old client and make sure no leftover process remains in the taskbar, menu bar, or background processes.

Handle configuration separately from the client

The client package provides the runtime interface and core management only. Subscription links, proxy nodes, rule sets, and DNS settings are configuration content that must be imported separately after installation.

Update the subscription before choosing a proxy group

After importing a subscription, run an update first and confirm that the configuration loads correctly. Then open the proxy page to select a node or automatic group, and enable the system proxy or TUN mode as needed.

Keep a rollback path when upgrading

Before installing over an existing version, record the current configuration file, operating mode, and key settings. Clean up the old configuration directory only after the new version is stable, as field differences between clients can affect migration.

Clash download FAQ

Answers covering architecture choices, package formats, the Mihomo core, and first-connection issues.

Which Clash client should I download for Windows?

Clash Plus is the recommended choice. For a different configuration management interface, consider Clash Verge Rev, FlClash, or Clash Nyanpasu. Clash for Windows is discontinued and is mainly useful for migrating older configurations or compatibility scenarios.

Should I choose the Apple Silicon or Intel package for macOS?

Open “About This Mac” from the Apple menu to check the chip information. Choose Apple Silicon or ARM64 for an Apple M-series chip; choose Intel or x64 for an Intel processor. The wrong architecture usually prevents installation or startup.

How should I choose an Android package if I do not know the CPU architecture?

Recent Android phones and tablets usually use ARM64, so start with the ARM64 package. For older devices or an unknown architecture, choose the universal Clash Meta for Android package. ARMv7 is mainly for older 32-bit devices.

Should I download DEB, RPM, or AppImage for Linux?

Ubuntu, Debian, and Linux Mint generally use DEB; Fedora and RHEL-based distributions generally use RPM; AppImage suits x64 desktop environments where you want to run a standalone file. Servers and headless devices are better served by the Mihomo core.

What is the difference between the Mihomo core and a graphical client?

The Mihomo core provides low-level proxying, rule matching, DNS, and network listening, but no desktop management interface. Servers, routers, and automated environments can run the core directly; ordinary computer and mobile users will find a graphical client easier for importing subscriptions and changing settings.

What should I do if I still cannot connect after importing a subscription?

First confirm that the subscription update succeeded and choose an available proxy group on the proxy page. Then check the operating mode, system proxy switch, and port conflicts. If browsers and other apps behave differently, check the app's own proxy settings, DNS, and TUN mode. Follow the troubleshooting guide for a complete step-by-step process.