Clash Downloads

Choose your device’s operating system, then select the right package architecture. For everyday use, choose a graphical client. Servers and routers can use the standalone Mihomo core.

Browse Mihomo core downloads ↓

Downloads by platform

Windows downloads

This section offers x64 installers. To check your system type, search for “System Information” in Settings. Choose an x64 package if it says “x64-based processor” and you’re running 64-bit Windows. If it lists an ARM processor, first check whether the client and its networking components support your device.

Clash Plus

Clash Plus

Top pick

A good starting point for importing a subscription on Windows. Enable your configuration, turn on the system proxy, then test the connection in a browser.

Clash Verge Rev

Clash Verge Rev

Manage subscriptions and inspect rule matches in the graphical interface. To route traffic from apps that don’t use the system proxy, configure TUN as prompted by the client.

FlClash

FlClash

A good fit if you already use FlClash on another device. Reimport your subscription, then check the system proxy and local listening port on this device.

Clash Nyanpasu

Clash Nyanpasu

Manage multiple configurations in the graphical interface. Before switching, check which configuration is active so you don’t mistake rules from an old one for the results of a new one.

Clash for Windows

No longer maintained

Kept for reference on older systems and configuration migration. For everyday use on a new device, choose a client that’s still maintained.

Windows system requirements
CheckWhat to choose or do
Operating system and architectureThe x64 installers in this section require 64-bit Windows. Check the selected client’s release notes for its Windows version requirements. 32-bit Windows cannot run x64 installers.
Installation and permissionsYou need write access to the installation folder. If you enable TUN features that rely on a service or driver, grant the permissions requested by Windows.

Mihomo core downloads

The standalone core is for servers, routers, or users who want to manage processes manually. For everyday use, choose a graphical client above. With a core package, you’ll need to provide your own configuration file and decide which user runs it, where it reads the configuration, and where to find its logs.

Choose a core file for your environment
Operating systemArchitectureFile
WindowsAMD64Download Windows AMD64 ZIP
WindowsARM64Download Windows ARM64 ZIP
macOSIntelDownload macOS Intel GZ
macOSApple siliconDownload macOS ARM64 GZ
LinuxAMD64Download Linux AMD64 DEB · Download Linux AMD64 GZ
LinuxARM64Download Linux ARM64 GZ
LinuxARMv7Download Linux ARMv7 GZ
LinuxMIPS softfloatDownload Linux MIPS softfloat GZ

Install, update, and migrate

First-time setup

Choose one client per device. After launching it, import and enable a configuration, then turn on the system proxy, TUN, or Android VPN. For your first test, avoid changing the routing mode, proxy groups, and DNS all at once; otherwise, it’ll be hard to tell what caused a problem. See the quick-start guide for detailed instructions.

Update an existing client

Stick with the original download source and architecture when possible. Save your subscription URL and local configuration, then quit the old client. On desktop, make sure it has also exited from the system tray or menu bar. After updating, check which configuration is enabled before testing the connection, so configuration changes aren’t mistaken for an installation failure.

Switch clients

First, make sure the new client supports your configuration format before importing the old file. Quit the old client and disconnect before starting another to avoid conflicts over ports or the system VPN. If you’re choosing between clients, see the client comparison and narrow down your options by operating system, configuration source, and traffic routing method.

Download and installation FAQs

Which Android package should I choose: ARM64, ARM, or universal?

Choose ARM64 if your system supports arm64-v8a; choose ARM if it only supports armeabi-v7a. If both are supported, prefer ARM64. If you’re unsure, try the universal package offered by the same client. Supported architectures vary by publisher, and a universal package does not lower the client’s minimum Android version.

Android says the app wasn’t installed. Should I uninstall the old version first?

Don’t uninstall it yet. Make sure the package matches your Android version and device architecture, and check that you have enough free storage. If Android reports a signature mismatch, verify the new package’s source, back up your configuration, and save your subscription URL before deciding whether to switch download sources. Uninstalling may erase configurations, proxy group selections, and update settings.

Why did my Apple silicon Mac download an x64 file?

Some client download buttons currently point to the same Intel installer. Treat files named x64, amd64, or x86_64 as Intel builds. Apple silicon Macs may need Rosetta to run these clients, and you should still check that the client supports your macOS version. For native performance, choose a file explicitly labeled arm64.

Do I need to download the graphical client and Mihomo core together?

Usually, you only need one graphical client. Clients that include a core manage its startup and configuration loading for you. The standalone Mihomo core is for servers and routers where you want to manage configuration files, permissions, and logs yourself. Before replacing a graphical client’s core, check that the client supports it.

Does the installer include a ready-to-use subscription?

Installers only install the client. To route traffic through a proxy, provide your own subscription URL or configuration file, then import and enable it in the client. If no proxy groups appear in the preview, first check whether the imported content uses a format supported by your client instead of reinstalling it repeatedly.

Can I use an archived version to restore an old configuration?

Archived versions can help you check an old interface or read an older configuration, but for everyday use, choose a client that’s still maintained. Keep a copy of your configuration before migrating. After importing it into the new client, check your proxy groups, rules, and ports. The exported configuration may not include interface preferences or saved group selections from the old client.

View installation and configuration guides for each platform →