Client and core downloads

Clash Download: Choose a client by platform

Confirm your operating system and CPU architecture first, then choose the matching installer. For everyday use, choose a client with a graphical interface; servers, routers, and automated environments can use the Mihomo core directly.

GUI clients System requirements CPU architecture Mihomo core
Choose a platform Switching platforms also updates the URL hash, making the current platform easy to save or share.

Windows clients

Windows GUI clients

For Windows 11 and supported Windows 10 devices, use the 64-bit installer. After installation, import a subscription and enable the system proxy or TUN mode as needed.

Clash Verge Rev

Alternative

A full desktop interface for subscriptions, proxy groups, rules, logs, and system proxy settings—well suited to users who need detailed runtime information.

  • Install type: x64 installer
  • Processor: 64-bit Intel or AMD

FlClash

A cross-platform GUI client with a consistent interface and workflow across operating systems, suitable for users managing both computers and mobile devices.

  • Primary: x64 installer
  • Portable use: ZIP archive

Clash Nyanpasu

Provides a desktop GUI and common proxy controls as another Windows client option.

  • Install type: x64 installer
  • Processor: 64-bit Intel or AMD

Clash for Windows

No longer maintained

A classic desktop client with an archived installer for older configurations or migrating an existing setup. For new installations, choose a client that is still being updated.

  • Status: Archived version
  • Install type: Windows installer

Windows system requirements

ItemRecommendationDetails
Operating systemWindows 10 / 11 64-bitKeep system patches and the WebView runtime components available and up to date.
Processorx86-64The primary Windows GUI installers on this page target 64-bit Intel and AMD processors.
PermissionsInstalls with standard permissions; some modes require elevationWindows may request administrator approval when enabling TUN or service mode, or changing certain network settings.

Command-line and service environments

Mihomo core downloads

The Mihomo core is intended for servers, software routers, containers, and environments with an existing management panel. It does not provide a complete desktop GUI, so prepare a configuration file and start it through the command line, systemd, or a device management panel. Everyday computer and phone users should choose a GUI client above.

Operating system Architecture Format Use case Download
Windows AMD64 ZIP Common 64-bit Intel or AMD computers and servers Download AMD64
Windows ARM64 ZIP Windows on ARM devices Download ARM64
macOS Intel GZ Intel-based Macs Download Intel
macOS Apple Silicon GZ Apple Silicon Macs, including M1, M2, M3, and M4 Download ARM64
Linux AMD64 DEB Debian, Ubuntu servers or desktop systems Download DEB
Linux AMD64 GZ General 64-bit server deployments Download AMD64
Linux ARM64 GZ 64-bit ARM servers, development boards, or routers Download ARM64
Linux ARMv7 GZ Some 32-bit ARM development boards and embedded devices Download ARMv7
Linux MIPS softfloat GZ Specific routers using soft-float MIPS architecture Download MIPS

How the core runs

After extracting it, start the core from the command line with a configuration directory or file. For long-running deployments, Linux commonly uses systemd to manage the process, with configuration, logs, and executables stored in stable paths. Router environments are usually handled by the device management panel or startup scripts.

Preparing configuration files

The core requires parseable YAML, typically containing ports, mode, DNS, proxy nodes, proxy groups, and rules. Keep a known-good configuration before updating; after changes, review startup logs before routing system traffic through it.

Choosing an installer

How to identify the architecture and package format

A single client may offer several files with the same general features. The main differences are the operating system, CPU architecture, and installation method. Choosing incorrectly may cause the system to reject the installation or fail to launch.

AMD64 / x64 / x86-64
These names generally refer to the same 64-bit desktop and server architecture. Most Windows and Linux computers with Intel or AMD processors use this type of package.
ARM64 / AArch64
Common on Apple Silicon Macs, recent Android phones, ARM servers, and some development boards. Android filenames may also use arm64-v8a.
DEB / RPM
DEB is mainly used by Debian, Ubuntu, and derivatives; RPM is common on Fedora and RHEL-family distributions. The system package manager handles their installation.
DMG / APK / AppImage
DMG is a common macOS distribution format; APK is used for Android installation; AppImage runs as a single file on many Linux desktop distributions.

Download questions

Common decisions before and after installation

These questions focus on client selection, CPU architecture, core usage, and first-time connections. For fuller configuration and troubleshooting, continue to the tutorials and troubleshooting guides on this site.

Which Clash client should I download first?

Choose the GUI client marked as a top pick or recommendation in the section for your operating system. GUI clients include subscription import, system proxy, proxy groups, and logs, making them better suited to everyday desktop and mobile use. Download the Mihomo core directly only when running on a server, router, or existing management panel.

How do I tell Apple Silicon and Intel macOS installers apart?

For Macs with M1, M2, M3, or M4 chips, choose Apple Silicon or ARM64; for older Intel Macs, choose Intel or x64. Open About This Mac from the Apple menu to check the chip or processor name. If the app installs but will not launch, verify the selected architecture again.

Should I choose ARM64, ARM, or universal for Android?

Most recent Android phones use ARM64, usually shown as arm64-v8a in filenames. Older 32-bit devices can use ARM or armeabi-v7a; when the architecture is unknown, choose the universal installer. x86-64 is mainly for a small number of specific devices or emulated environments.

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

GUI clients combine the core, subscription management, policy selection, system proxy controls, and log viewing in one interface. The Mihomo core mainly runs through configuration files, the command line, or a service manager, making it suitable for servers, routers, and automated environments. Most computer and phone users do not need to manage core files separately.

Why can’t I connect immediately after downloading?

Client installers do not include a working subscription. After installation, import the subscription URL provided by your service provider or a local configuration file, wait for it to parse successfully, then choose a proxy group and enable the system proxy, VPN connection, or appropriate interception mode. If loading fails, check the specific message in the client logs first.