Clash downloads

Choose your operating system, then check the CPU architecture and installer format. Archived clients are marked separately.

Compare client features · Installation and setup guides

Windows clients

Clash Plus

Top pick

A desktop client installed through a setup wizard. If you're new to the app, import a subscription first, then check the active configuration and proxy mode. clashplus.io

Clash Verge Rev

Configurations, proxy groups, and connection logs are shown separately. When troubleshooting routing, use the connection log to check which rule matched and which policy was used.

FlClash

The installer and ZIP target the same AMD64 architecture; they differ in how they're deployed. If you choose the ZIP, extract it to a writable folder before launching the app.

Clash Nyanpasu

Switch configurations and proxy groups in the GUI. When moving from another client, import the original subscription or local YAML instead of copying the app's internal database.

Clash for Windows

Discontinued

This archived download is for reference and migrating old configurations. Support for newer syntax may differ from current clients. For a fresh install, choose a client that's still maintained.

Windows requirements and pre-install checks
CheckWhat to look for
System typeOpen Settings → System → About and check System type. Choose an x64 installer based on the processor architecture; don't rely on the words “64-bit” alone.
Windows versionNote the Windows version and OS build on the About page, then check the selected client's release requirements. Minimum supported versions vary by project.
Proxy permissionsA successful install doesn't guarantee that TUN will work. First test connectivity with the system proxy, then check the client's requirements for a virtual network adapter, services, and elevated permissions.

Standalone Mihomo core

The standalone core is for servers, routers, and users who want to manage the process themselves. Most desktop and mobile users should choose a GUI client above. The standalone package has no GUI; configure its paths, startup options, and background process separately.

Choose a package by operating system and architecture
SystemArchitectureDownload
WindowsAMD64ZIP
WindowsARM64ZIP
macOSIntel / AMD64GZ
macOSApple Silicon / ARM64GZ
LinuxAMD64DEB · GZ
LinuxARM64GZ
LinuxARMv7GZ
LinuxMIPS softfloatGZ

Installation and migration checklist

Identify the system before choosing a file

Don't choose a package based only on the device's product name. A product line may use different processors, and a device may run an OS whose bitness differs from its processor. On Windows, check System type; on macOS, check the chip; on Android, check the app architectures supported by the OS; on Linux, also check the package format and distribution. AMD64 and x86_64 in desktop filenames refer to the same target architecture and don't require an AMD processor. Once the architecture matches, check the client's release notes for the minimum OS version. Compatibility with newer and older systems should be assessed separately.

Keep a reusable copy of your configuration

Before migrating, record your subscription URL, local YAML, custom rules, and any proxy group names you need to keep. Subscription URLs may include account access tokens, so don't post them in public support tickets or screenshots. Remote updates may overwrite direct edits; keep local changes in a separate copy. When switching clients, import one configuration first and confirm that proxy group names and rule references match. If parsing fails, note the line number and check the syntax and core support before considering a different installer.

Test startup, configuration, and traffic separately

If the app opens, installation is complete—but you still need to confirm that a configuration is enabled, a proxy group is selected, and app traffic is reaching the client. When migrating, quit the old client first to prevent both apps from competing for the local proxy port or changing system proxy settings. Test with an app that follows the system proxy, then check the destination, matched rule, and active policy on the connection page before deciding whether to enable TUN. If the client can test a connection but the target app has no connection log, first check whether the system proxy is enabled and whether the app uses it; don't rush to reinstall.

View the full reference

Download FAQs

How do I choose between x64 and ARM64?

Check the processor and system type shown by your device. x64 may be listed as AMD64 or x86_64; ARM64 as AArch64. Android packages commonly use the arm64-v8a label.

What's the difference between an installer and a ZIP?

Installers typically guide you through setup. For a ZIP, extract all files first, then launch the app as directed in the release notes. Don't run apps from the archive preview.

What should I back up when switching from an older client?

Keep your subscription URL, local YAML files, and custom rules. After importing them into the new client, check the active configuration, proxy groups, and proxy settings. Don't overwrite the entire old client directory.

Do I need to import a subscription after installing?

The client and its configuration are separate. Import a subscription or local config in a format the client supports, then select a valid configuration and proxy mode. The installer doesn't include a subscription.

Do I need to download the Mihomo core separately for a regular PC?

Usually not if you're using a GUI client that includes the core. A standalone core is for users who want to manage the configuration, launch process, and update workflow themselves.