Client installers and core files

Clash Download and platform selection

Choose a GUI client for your operating system. The page covers Windows, macOS, Android, iOS, and Linux, with separate Mihomo core files for servers and routers.

5 operating systems GUI clients Multi-architecture cores
Confirm your platform and architecture Then choose the matching package
  1. 01
    Choose an operating system

    Use the tabs below to switch between Windows, macOS, Android, iOS, and Linux.

  2. 02
    Check the architecture

    Desktop builds distinguish x64, Apple Silicon, and Intel; Android builds distinguish arm64, ARM, and universal packages.

  3. 03
    Complete the initial setup

    After installation, import a subscription or local profile, then enable the system proxy or turn on TUN as needed.

Platform installers

Choose the client for your current device

Clients differ in interface, system integration, and supported architectures. For a first install, start with the first option for your platform; check the other clients when you need a specific interface or package format.

Windows clients

For everyday use, download the x64 installer. After installation, import a subscription, select Rule mode, and enable the system proxy. Choose FlClash's ZIP archive for portable use.

System Windows 10 / 11 Architecture x64 Permissions Authorization required the first time TUN is enabled
Clash Verge Rev

Clash Verge Rev

A desktop client with extensive configuration options for managing subscriptions, proxy groups, the system proxy, and TUN mode. The current download is a Windows x64 installer.

FlClash

FlClash

Available as an installer or ZIP archive. The installer is best for regular use; the ZIP version runs after extraction and suits portable directories or setups without an installation process.

Clash Nyanpasu

Clash Nyanpasu

A GUI client for desktop systems, with profile switching, proxy group selection, and system proxy controls. A Windows x64 installer is provided here.

No longer maintained

Clash for Windows

A classic desktop client retained for users who need to open legacy profiles or preserve an older setup. The project is no longer maintained; choose an actively updated client for new installations.

Command-line and embedded environments

Mihomo core architecture downloads

The Mihomo core is designed for servers, software routers, containers, and automated deployments, running through configuration files and the command line. Most desktop and mobile users should choose a GUI client above to manage subscriptions, proxy groups, and system network controls.

Operating system Architecture File format Use case Download
Windows amd64 ZIP Common 64-bit desktops and servers Download
Windows arm64 ZIP Windows on ARM devices Download
macOS amd64 GZ Intel-based Macs Download
macOS arm64 GZ Apple Silicon Macs Download
Linux amd64 DEB Debian, Ubuntu, and derivatives Download
Linux amd64 GZ Generic 64-bit Linux environments Download
Linux arm64 GZ 64-bit ARM servers and routers Download
Linux armv7 GZ 32-bit ARMv7 routers and embedded devices Download
Linux mips-softfloat GZ MIPS devices using the soft-float ABI Download

Configuration file entry point

The core does not provide a conventional desktop settings interface. Before running it, prepare config.yaml, which typically contains ports, DNS, proxies, proxy groups, and rules. When upgrading the core, keep the existing configuration and check new and deprecated fields first.

Architecture check

On Linux, use uname -m to check the architecture. The common output x86_64 corresponds to amd64, while aarch64 corresponds to arm64. For routers, also confirm the CPU architecture and floating-point ABI rather than choosing only by device brand.

How it runs

Server environments typically use systemd or a container to start and restart the service. After changing the configuration, run a configuration check before reloading the service. Desktop users who do not need command-line management will find the GUI clients above more direct.

Before and after installation

Installation, setup, and first-connection guide

An installer only provides the client. To connect, you also need a working subscription link or local profile, then choose system proxy or TUN mode based on your needs.

01

Confirm the system architecture

Windows and most Linux desktops use x64. Apple M-series Macs use arm64. Android devices most commonly use arm64-v8a, though older devices may still use 32-bit ARM. With a mismatched architecture, the installer may fail to open or report that it is incompatible.

02

Install and import a profile

Complete desktop installation through the wizard; for a DMG, drag the app into Applications. Install Android packages and open the client; install iOS builds from the App Store. Open the profile or subscription page, paste the subscription URL, and update it, or import an existing YAML file.

03

Choose a rule mode

Rule mode suits most profiles: rules determine whether requests use the proxy, connect directly, or are rejected. Global mode sends most traffic to one proxy group and is mainly useful for temporary troubleshooting. Direct mode bypasses the proxy and helps determine whether the proxy path is causing the issue.

04

Enable the system proxy or TUN

Start with the system proxy for browsers and apps that honor system proxy settings. Use TUN for applications that cannot read those settings, command-line tools, or scenarios requiring broader traffic capture. TUN uses a virtual network interface and system permissions, so complete authorization the first time you enable it.

Common download questions

Installer and architecture selection

These questions cover client selection, package formats, system architectures, and first-time connections. For the full configuration workflow, see the usage documentation.

View the usage documentation
Which Clash client should I download first?

For a consistent interface and workflow across platforms, start with Clash Plus. Windows, macOS, and Linux users can also choose Clash Verge Rev or FlClash based on system integration needs. If you have a legacy profile, first confirm that its rule fields and DNS options are supported by the new client before migrating.

What is the difference between the Windows installer and ZIP archive?

The installer places the program in an application directory and creates uninstall data and shortcuts for regular use. A ZIP archive usually runs after extraction and is easy to keep in a custom directory. For portable use, check the profile directory and system proxy status, and quit the client before moving the folder.

Should I choose the Apple Silicon or Intel macOS installer?

Open About This Mac from the Apple menu and check the Chip or Processor field. Choose the Apple Silicon build for an Apple M-series chip, or the Intel build when Intel is shown. If macOS blocks the first launch, approve the app-opening request under System Settings > Privacy & Security.

Which Android build should I choose if I do not know the processor architecture?

Most recent Android phones use arm64-v8a. If you cannot confirm the architecture, choose the universal Clash Meta for Android build first. armeabi-v7a is mainly for older 32-bit ARM devices, while x86_64 is more common in emulators and a small number of specific devices.

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

The Mihomo core runs through command-line arguments and YAML configuration rather than providing a conventional desktop management interface. It suits servers, routers, containers, and automated services. GUI clients typically bundle the core and add subscription updates, proxy group switching, log viewing, system proxy controls, and TUN switches, making management easier for most users.

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

Check the subscription update time and confirm that the profile is enabled, then make sure the running mode is not Direct. On desktop, check whether the system proxy or TUN is enabled; on mobile, check VPN authorization. If only some domains fail, inspect rule matches, DNS mode, and log messages such as timeout, connection refused, or resolution failures.