127.0.0.1 / Client installers

Clash downloads

Choose your operating system, then check the CPU architecture and package format. For everyday use, choose a desktop client. For managing configs yourself on a server or router, choose the standalone core.

ARCH / Platform index

Choose an installer by platform

Find the package for your platform. Archived builds are useful for checking older setups; for a first install, start with a client that's still maintained.

Windows clients

Most desktop packages here are x64. Check Settings → System → About to confirm your system type. If a client offers both EXE and ZIP packages, choose based on whether you want a standard install or to manage the program folder yourself.

Clash Verge Rev

For users who want to manage config overrides or inspect connection details in the interface. On first use, make sure the config loads before enabling TUN if needed.

FlClash

Use the EXE for a standard install. Choose ZIP if you want to manage the program folder yourself; extract the files fully before running the app. Don't launch it from the archive preview.

Clash Nyanpasu

A desktop client with a graphical interface. When migrating, import your existing config first; check the old client's UI preferences, ports, and system proxy settings separately.

Clash for Windows

Discontinued

Kept for reference with older setups. Newer config fields and protocols may not load. If you run into parse errors, consider switching to a currently maintained client.

Windows requirements and permissions
CheckWhat to look for
OS and architectureUse a supported 64-bit version of Windows where possible; check each client's release notes. The x64 packages listed here are not native ARM64 builds.
Installation and servicesCheck your system's installation policies. TUN may require a separate service or virtual network adapter.

Opening the app and routing traffic through it are two different things. For a first test, quit any old client, import a config into the new one, and enable system proxy only. Then check the browser and connection logs. If the result changes in a terminal, check whether the terminal reads the system proxy instead of reinstalling the app.

MIXED-PORT / Setup handoff

From install to connection test

Test one layer at a time: first make sure the app starts, then check that the config loads, and finally confirm that app requests are routed through the proxy.

Keep your old config when migrating

Before switching clients, save the original config, custom rules, and overrides separately. Store subscription URLs somewhere secure; don't include them in screenshots or public logs. Menus, service settings, and subscription refresh behavior vary between clients. Import one config and test it before migrating the rest.

Check ports and proxy mode

mixed-port is the local proxy listening port, not the subscription service URL. If the port is already in use, quit the old client and check whether its background process has stopped. If you switch ports, update any apps with manually configured proxy settings too. To see whether rules are matching, test in rule mode rather than relying on the connection toggle.

Know who provides the config and who publishes the app

Clash Open Source Hub organizes links and usage notes for these projects; it doesn't publish the clients. Installers, subscriptions, and local client settings are separate: updating the app doesn't update a subscription, and refreshing a subscription may replace remotely synced content. For custom rules you need to keep, use the client's local override feature when available.

DIRECT / Download FAQ

Download and installation FAQ

Can I use Windows x64 and ARM64 installers interchangeably?

Check Settings → System → About to see your system type. x64 is the package type used by most Windows desktop clients listed here. Some Windows on Arm devices can emulate x64 apps, but virtual network adapter and service driver support must be checked separately. An app opening successfully doesn't mean TUN will work.

Which macOS version should I choose: Apple silicon or Intel?

Open About This Mac from the Apple menu. Choose arm64 for Apple silicon or x64 for an Intel processor. If a listing only offers an Intel build, Apple silicon devices may need Rosetta. For system extensions or helper services, prefer a client with a native build.

Android says there's a package conflict. What should I check first?

Check whether the phone already has an app with the same name. Updating an existing app usually requires the same application ID and a compatible signing certificate; an older version may also be rejected. Back up your config, then decide whether to update from the original source or migrate. A universal package may solve some architecture mismatches, but it won't fix a signing conflict.

Why are there no nodes to choose from after installing a Clash client?

The installer provides the client app. Nodes, proxy groups, and rules come from a separately imported config file or subscription. After importing, make sure the config is selected, then check the proxy groups for available entries. Don't enter an installer URL as a subscription URL.

Do I need to install Mihomo separately after downloading a desktop client?

Usually not if the client includes or can manage the required core. A standalone Mihomo install is better suited to servers, routers, or command-line setups where you manage the config, process, and logs yourself. If two instances run on the same device, check their listening ports and traffic interception scope separately.

Already installed, but having trouble starting the app, using the system proxy, or connecting? See Troubleshooting.