Choose a client · Download by OS and architecture

Clash Downloads & Installer Selection

Choose your operating system, then check your processor architecture. GUI clients are for everyday use; the standalone Mihomo core is for self-managed deployments.

How to configure after installation View the Mihomo core ↓

Get a client for your platform

Each platform lists a recommended client first, followed by alternatives. Buttons identify the installer type. Configuration menus can change between client versions; after installation, look for “Configuration” or “Profiles.” To compare workflows and features, see the client comparison.

Windows clients

The desktop installers below are primarily for x64. Check your system type under Settings → System → About. On an ARM PC, first confirm that Windows can run x64 apps; the computer’s brand doesn’t tell you its architecture.

Clash Plus

Clash Plus

Windows · x64
Top pick
Download Windows installer · EXE

A good starting point for your first installation. Run the installer and follow the setup wizard. On first launch, import a subscription or local configuration and check that its name appears in the list. Then choose an exit in the proxy group. Opening the app alone doesn’t mean your system traffic is routed through it.

If you need TUN, install or enable the required service when prompted. First verify a standard proxy connection to help distinguish configuration issues from permission issues. Official site: clashplus.io.

Clash Verge Rev

Clash Verge Rev

Windows · x64
Download Windows installer · EXE

A good fit for desktop users who need configuration management, rule-based routing, and service mode. After installation, add and enable a subscription on the configuration page, then check the system proxy status. If an older client is still running, turn off its system proxy first to prevent both apps from repeatedly changing the same setting.

This page provides the x64 installer. Before using service mode, confirm that administrator approval is requested by the client you just installed. When setup is complete, check the service status in the app.

FlClash

FlClash

Windows · AMD64
Download Windows installer · EXE Download ZIP archive · ZIP

A good fit if you want a similar workflow across desktop and mobile. For a standard installation, choose the EXE. If you choose the ZIP, extract it fully to a permanent folder before running the program. Don’t launch it from the archive viewer.

AMD64 usually refers to the same architecture as x64; it doesn’t indicate a specific processor brand. Back up your configuration before updating. A ZIP install doesn’t necessarily store service files or configuration data in the program folder.

Clash Nyanpasu

Clash Nyanpasu

Windows · x64
Download Windows installer · EXE

A good fit if you prefer to manage interface preferences and configuration entries separately. After importing an existing YAML file, check that it loads and that proxy group names match the rules that refer to them. Themes, system proxy settings, and core configuration are separate; avoid changing everything at once.

When migrating from another client, move the subscription URL or configuration file first rather than copying the old app’s entire data folder. Interface settings files aren’t necessarily compatible between clients.

Clash for Windows

Windows · Legacy client
Discontinued
Download archived installer · EXE

This archived download is for reproducing older tutorials, checking existing configurations, and migrating legacy setups—not for new devices. Newer subscription fields or protocols may not be supported by the older core. A successful installation doesn’t guarantee configuration compatibility.

Before migrating, export your subscription details and back up your configuration. Verify the rules and proxy groups in the new client before quitting the old one. Once the new client has taken over the system proxy, you can deal with the old installation folder.

Windows installation requirements

ItemRequirements and how to check
Operating system and architectureThe installers on this page are primarily for 64-bit Windows. Use a supported Windows version where possible. Minimum OS requirements vary by installer; older versions aren’t guaranteed to work.
Installation permissionsLaunching the app normally and installing a service require different permissions. Administrator approval may be needed to install a service or enable TUN.
First connectionEnable a configuration, then choose a proxy group and system proxy. Command-line tools may need proxy environment variables set separately.
Standalone deployment

Download the Mihomo core

For users managing servers, routers, or processes themselves. Most users should choose a GUI client above and don’t need to install the core separately. Files in the table are grouped by operating system and architecture and don’t include a graphical interface.

Operating systemProcessor architectureFile typeDownload
WindowsAMD64 / x64ZIPDownload Windows AMD64
WindowsARM64ZIPDownload Windows ARM64
macOSIntel / AMD64GZDownload macOS Intel
macOSApple Silicon / ARM64GZDownload macOS ARM64
LinuxAMD64DEBDownload Linux AMD64 DEB
LinuxAMD64GZDownload Linux AMD64 GZ
LinuxARM64GZDownload Linux ARM64
LinuxARMv7GZDownload Linux ARMv7
LinuxMIPS softfloatGZDownload Linux MIPS softfloat

Extract the archive and test your configuration first

Extract ZIP files before use. GZ files are usually compressed single executables; extract them and, on Unix-like systems, make them executable. Set up your configuration directory, then test in the foreground to confirm the configuration loads before running it under a service manager. After installing a DEB, check the installed file locations and service status.

For example, if you’ve named the executable mihomo and the current directory contains config.yaml, run the syntax test command below first. Passing the test only confirms that the configuration can be read; it doesn’t guarantee a working remote connection.

./mihomo -t -f ./config.yaml

Post-installation checks

A successful download is only the first step. Check the configuration, proxy groups, and system traffic routing separately to avoid wasting time reinstalling the client.

Configuration

Import and enable a configuration

Open the configuration page, paste a subscription link or select a local file, save it, and wait for the result. A configuration appearing by name doesn’t mean it’s enabled. Check which one is selected, then open the proxy groups and confirm they’re populated. Subscription links may contain access credentials; don’t share them in screenshots or public forums.

See how to import a subscription →

Traffic routing

Choose a mode and traffic entry point

For everyday use, start by testing rule mode. On desktop, begin with the system proxy; on mobile, grant VPN permission when prompted. If you need to route traffic from more apps through the client, check TUN settings. The system proxy and TUN are separate options—you don’t need to enable both for your first connection.

Compare proxy modes →

Verification

Check requests and error logs

Make a specific network request, then check the client’s connections or logs page for an entry. Review the matching rule and exit. If there’s no entry, check whether traffic is reaching the client. If there is an entry but the connection fails, check the proxy group, subscription status, and remote network. Don’t assume every problem is caused by the installer.

See routine maintenance tips →

Common download and installation questions

First check that the installer matches your system, then troubleshoot configuration and connectivity. Expand a question below for details.

Which Clash client should I download first?
For Windows, macOS, Android, and iOS, start with the recommended Clash Plus client. For Linux, start with Clash Verge Rev. Check your device architecture and installer requirements, then choose using the client comparison. You’ll also need to provide your own working subscription or configuration file after installation.
What’s the difference between ARM64, x64, and universal builds?
These labels indicate the processor architecture supported by an installer. x64 and AMD64 usually refer to the same 64-bit architecture. ARM64 is common on phones, Apple Silicon Macs, and some PCs. Universal builds include files for multiple architectures and are usually larger. Check your device’s system information and the architecture listed for the installer.
Why might both macOS architecture buttons download the same file?
Some clients’ current distribution manifests map both architecture options to the same x64 installer. The page keeps both options to match the manifest and notes this on the card. Apple Silicon users should choose a build explicitly labeled native ARM64 when available. Before using an x64 build, make sure Rosetta is available for compatibility.
Does the installation include a working proxy connection?
The client installer and subscription are separate. After installation, import a subscription you’ve obtained and are authorized to use, or a local configuration file. Enable the configuration, then choose a proxy group and connection mode. Check the configuration name, node list, and any error messages after importing; a toggled switch alone doesn’t confirm a successful connection. See the user guide for detailed steps.
Can I use a discontinued client for a new installation?
Clash for Windows and ClashX Meta are listed for compatibility with legacy setups and migration reference. For a new installation, choose a client that’s still maintained. Back up old configurations before migrating, and check protocol, rule-field, and core compatibility. Don’t overwrite your only working configuration.
Do regular desktop users need to download the Mihomo core separately?
Usually not. GUI clients generally include or manage the core they need. Standalone Mihomo builds are mainly for users managing servers, routers, or service processes themselves; you’ll need to handle configuration, permissions, and service management. For everyday desktop use, start with the GUI client for your platform.