PACKAGESClients & Core

Clash Download

Choose your operating system first, then match the CPU architecture and package format. Use a desktop or mobile app for everyday use, or run Mihomo directly on a server or router.

Package guide

Choose a Clash client by platform

Windows installers

Open Settings → System → About to check your system type. Choose the x64 package if it says “64-bit operating system, x64-based processor.” If you have an ARM device, don’t rely on the “64-bit operating system” line alone.

Clash Plus

Top pick

For your first setup, import a config in the app, choose a policy group, then enable the system proxy. Check that traffic appears in the client using a browser before deciding whether you need TUN mode.

Clash Verge Rev

A good fit if you want to inspect rules, connections, and core logs in one place. For standard proxy use, start with the current-user settings. Check the client’s service-mode guidance if you later need system-wide traffic handling.

FlClash

The installer is best for everyday use. Choose the ZIP package if you want to keep the app in its own folder. Extract it fully before launching; don’t run it from your archive utility’s preview.

Clash Nyanpasu

A good option for managing local configs and subscriptions separately on desktop. If you’re testing it alongside an older client, quit the old process first, then check the system proxy address and port.

Clash for Windows

Discontinued

Archived packages are for migrating old configs or recreating a legacy setup. For a new installation, choose a maintained client. Before migrating, keep your original YAML and custom rules, then uninstall the old version.

Windows system requirements and installation notes
CheckWhat to look for
Windows versionUse a Windows version that still receives security updates. Minimum version and runtime requirements vary by client release.
ProcessorDesktop packages in this section are primarily for x64. On Windows on ARM, check separately whether the app UI, core, and service components work under emulation.
Installation permissionsInstalling a service or virtual network adapter may require administrator approval. If you’re only testing browser proxying, start with the standard system proxy setup.

Mihomo command-line core

The standalone core is for servers, routers, and users who manage their own configs. It reads configs, listens on ports, and applies rules; graphical clients handle subscriptions, system proxy toggles, and tray interfaces. For everyday desktop or mobile use, start with a client above.

Core downloads by operating system and architecture
Operating systemArchitecturePackage formatDownload
WindowsAMD64ZIPDownload ZIP
WindowsARM64ZIPDownload ZIP
macOSIntel / AMD64GZDownload GZ
macOSApple Silicon / ARM64GZDownload GZ
LinuxAMD64DEB / GZ
LinuxARM64GZDownload GZ
LinuxARMv7GZDownload GZ
LinuxMIPS softfloatGZDownload GZ

Start the core for the first time

Place the extracted binary and config in a directory the current user can read and write. Use the config reference to check listening ports, DNS, and rules, then start the core in the foreground and watch for errors. If a port is already in use, identify the process listening on it. If it’s another client, quit that app and try again; don’t expose the listening address to your entire network by changing it blindly.

Once it runs correctly in the foreground, consider setting it to start at boot. When moving it to a service account, check the working directory: a config readable from an interactive terminal may not be accessible to the service account, and relative paths to rule files may resolve differently.

Installation checks, step by step

For a fresh setup, choose an app; for a migration, back up your config

For your first setup, choose one client for your operating system; there’s no need to install several versions at once. If you’re already using an older client, note the active config, routing mode, and selected policy group, then back up any locally edited rule files. A subscription URL is not the same as a config file: the URL fetches updates, while the file contains the result of a particular download or edit. Keeping only one may leave you without the other when you migrate.

To compare clients, check platform support and workflow differences in the Client Picks. You can keep two apps installed, but before testing the new one, disable the old app’s system proxy or VPN and quit its background process. Then launch the new app. This ensures its logs show the connections it actually handled, rather than making old settings look like the new rules are working.

Test installation, config import, and traffic handling separately

If the installer won’t open the main window, check the architecture, OS version, disk space, and runtime dependencies first. If the app opens but can’t import a config, check whether the subscription URL is reachable and the format is supported. If the config is enabled but the app can’t connect, check the listening port, system proxy, or VPN status. Troubleshoot each stage separately instead of repeatedly blaming the installer.

For a basic check, open a webpage and confirm its domain appears in the client’s connection list. Then inspect the matched rule and outbound policy. If your browser works but one app doesn’t, check whether that app uses the system proxy. For a more thorough walkthrough, follow the Getting Started guide to repeat the import, connection, and verification steps.

Common download and installation questions

Can x64 and ARM64 installers be used interchangeably if both are 64-bit?

No. They are different architectures: x64 is used by most Intel and AMD PCs, while ARM64 is for 64-bit ARM devices. Some apps can run across architectures when the operating system supports translation, but native builds are still the best choice.

Do I need to install Mihomo separately if I already have a desktop client?

For everyday use, check the client’s core options first; you usually don’t need to run Mihomo separately. The standalone core is intended for servers, routers, or setups with manually managed configs. Running both at once may also cause a port conflict.

Moving from Clash for Windows to a new client: what settings can I keep?

Back up your working YAML files and local rules, then import your subscription or local config into the new client. UI preferences, service settings, and override scripts from the old client may not carry over, so check them individually.

Will updating the client reset my subscriptions or rules?

An in-place update usually keeps the app’s data, but installed and portable versions may use different directories. Back up your subscriptions and local changes before updating, then check the active config, selected policy group, and traffic-handling mode.

The client opens, but importing a subscription fails. What should I check first?

Make sure you copied the subscription URL, not the account page, then check the client’s error summary. If the download fails, check your connection and subscription status. If it downloads but won’t parse, check that the config format is supported. Don’t include the full subscription URL when sharing troubleshooting details.

Confirm package

Continue to download