x64Windows 10 / 11 64-bit installer and portable build

Clash for Windows 64-bit Downloads& Setup Guide

Download Clash View the Guide

Explore desktop clients, rule configuration, and documentation. The original project is discontinued, so compare alternatives before installing.

Installation and Portable Use YAML Configuration Reference Discontinuation and Migration

Downloads / Browse by OS

Client and System Architecture

Start with your device, then choose a client. Downloads for other systems are platform-specific software, not renamed Windows installers.

Windows

In Windows, go to Settings → System → About to check your system type. Most Intel and AMD desktop PCs use x64; for ARM devices, don't rely on “64-bit” alone to determine compatibility.

Go to Downloads

macOS

Open About This Mac and choose the build for your Apple silicon or Intel processor. ClashX Meta is an archived option; for a new setup, compare actively maintained clients and their system requirements.

Go to Downloads

Android

Choose a build for your processor architecture; most newer devices use ARM64. The first time you connect, the system will ask you to authorize the VPN configuration. If another VPN is running, check whether it is using the same connection channel.

Go to Downloads

iOS

Find Clash Plus on the App Store or visit clashplus.io. After importing a configuration, allow the system to add a VPN configuration. Check the client's current documentation for supported subscription protocols.

Go to Downloads

Linux

For desktop use, start by comparing Clash Verge Rev and FlClash. Check the package format for your distribution before installing. For servers or routers, see the core section and configure services, permissions, and network routing separately.

Go to Downloads

Installer or Portable Build?

An installer is a good fit for a computer you use regularly and usually includes installation and uninstallation steps. A portable build works well in a separate folder or for testing an older setup. Portable does not mean all data stays in the program folder: configurations, logs, and services may still use your user data directory or system locations. Before migrating, check where the client stores its configuration and back up your rules and subscription records.

Install the new client in a separate folder rather than overwriting the old one. Import your configuration first and confirm that policy groups, DNS, and rules load correctly before setting up launch at startup. During the switch, let only one client manage the system proxy; otherwise, ports, virtual adapters, and background services may conflict, leaving the proxy enabled while your browser cannot connect.

Browse all clients →

System Proxy and Rule Settings

Find each setting from General to Profiles. The examples below illustrate the interface and fields; they are not complete, connection-ready configurations.

System Proxy

General → System Proxy

On the General page, check Port, then enable System Proxy. This changes the Windows system proxy settings so browsers and apps that respect them connect through the local listening port. It is not a master switch for all application traffic: apps with their own proxy settings, some games, and command-line tools may not be affected. If only one app cannot connect, check its network settings first. Turn off the system proxy before closing the client to avoid leaving Windows pointed at a port that is no longer listening. Newer clients may use different labels, so verify the actual listener and system settings.

# Example listener fields
mixed-port: 7890
allow-lan: false
View details

Rule Routing

Rule → evaluated in order

In Rule mode, connections are checked from top to bottom. Once a rule matches, its policy is applied; the client does not keep looking for a “better” match. Put specific domain rules before broad ones, then use MATCH to handle anything left over. Policy names in rules must exactly match the groups defined in your configuration; even a missing space can cause loading errors. For everyday use, start with the rules included in your subscription and adjust individual domains based on logs. Don't switch to Global mode every time something fails: the cause could also be DNS, the node protocol, or the site itself. The snippet below illustrates syntax only; PROXY must be defined separately.

mode: rule
rules:
  - DOMAIN-SUFFIX,example.com,PROXY
  - GEOIP,CN,DIRECT
  - MATCH,PROXY
View details

TUN Mode

Virtual adapter → routing and DNS

TUN uses a virtual network adapter to capture traffic that meets its routing conditions, including traffic from some apps that ignore system proxy settings. Older versions of Clash for Windows typically require Service Mode to be set up before enabling TUN with the appropriate core. Other clients may place these controls elsewhere. Before enabling TUN, confirm that the regular proxy works and note your original DNS and VPN settings so you can roll back if connectivity fails. TUN does not guarantee that all traffic will use the proxy; routing exclusions, rules, and DNS settings still apply. When moving to a new core, rebuild your configuration using its current documentation rather than reusing outdated fields.

# Example General settings
Service Mode
TUN Mode

# Test the regular proxy before enabling TUN
View details

Configuration and Subscription

Profiles → import and update

A subscription link provides configuration; it is not an installer or a local proxy address. After importing it in Profiles, select the profile and confirm it loaded successfully. Then go to Proxies to choose a policy. Updates usually fetch the remote content again, so edits made directly to a subscription file may be overwritten next time. Manage persistent rules through the client's supported override or merge features. If an import fails, check whether the link is unreachable, the response is not YAML, or the core does not support a field. Subscription URLs often contain access credentials; hide the full link before sharing logs or screenshots to avoid exposing account details.

# Example common fields
mixed-port: 7890
mode: rule
log-level: info
View details

First-time setup / 3-step overview

Import, Connect, and Verify

Get the regular proxy working first, then add TUN, custom DNS, or complex overrides. Change one thing at a time to make problems easier to diagnose.

Step 1

Import and select a profile

Open Profiles and paste a subscription URL from a trusted source, or import an existing local YAML file. Once the import finishes, select the profile to make it active. Installing the client alone is not enough for a complete connection: you also need working nodes and policy settings. This site does not provide subscription services.

If the client reports a parsing error, check the line number and field name first. Don't keep toggling the system proxy; until the configuration loads, the switch cannot add missing nodes or fix formatting.

Step 2

Choose a rule mode and policy

Open Proxies. For everyday use, start with Rule mode, then choose an exit from the groups provided by your configuration. Group names are set by the configuration author and may not be PROXY. Check that no other program is using the listening port shown in General, then enable System Proxy.

Enable Allow LAN only if other devices on your local network need to connect, and restrict access with the listening address and firewall rules. You don't need it for single-device use just because it appears in the example above; the screenshot shows the layout, not a recommended preset.

Step 3

Verify with real connections

Visit the target site in a browser while checking Connections or Logs to see whether the connection appears and which rule matched. Then test a site expected to connect directly and confirm the routing behaves as intended. A successful node test does not guarantee that every app will work.

If the browser works but one app doesn't, first check whether that app respects the system proxy. If nothing works, troubleshoot in this order: configuration loading, listening port, DNS, and upstream connection. When you're done testing, remember to turn off traffic capture before closing the client.

When migrating from an older client, also check that it has fully disconnected: quit the old program, confirm it is no longer running in the taskbar or background processes, and check that Windows proxy settings have been restored. Keeping two installation folders is fine; letting both programs change system proxy settings or install conflicting network services is what to avoid. The guide walks through tasks in order, while the reference is for looking up fields—you don't need to read every parameter to get started.

Read the full guide →

Project background / maintenance status

The Clash Ecosystem and Discontinuation

Distinguishing the desktop interface, proxy core, and configuration source is more useful for checking compatibility than memorizing software names.

Original project and archived builds

The original Clash for Windows project was discontinued in 2023. The old application may still run in some environments, but that does not mean it continues to receive security fixes, protocol support, or compatibility updates for new operating systems. The archived download is provided for preserving existing workflows, consulting older guides, or migrating configurations—not as a claim that the project is still maintained.

A repackaged, translated, or supposedly re-released app with the same name is not an official update just because its filename says so. Starting with a maintained client on a new computer makes troubleshooting easier. If you need to keep an older setup, limit its use and back up its configuration separately.

The client and core are separate layers

The client handles the interface, configuration management, system integration, and controls. The core parses configurations, establishes connections, handles DNS, and applies rules. Clash for Windows, Clash Verge Rev, and FlClash are separate projects; their names do not imply support for exactly the same configuration fields.

mihomo is one of the proxy cores continuing development in the Clash ecosystem. Its configuration capabilities differ from those of older cores, so check which core your client actually runs before following documentation for a newer one. Being able to import a file in the interface does not mean every advanced field in it is active.

Using open-source resources

Open-source repositories provide source code, configuration documentation, issue reports, and release notes. These resources can help you determine whether a behavior is a design limitation or a known issue. Open source does not guarantee that every build suits your current system or that any third-party subscription will work.

The mihomo core repository is linked below for readers who want to inspect the implementation and commit history. Cloning it only downloads source code; it does not install a desktop client or provide working nodes. For everyday desktop use, choose a graphical client for your operating system from the downloads page.

Evaluating updates and migration

When comparing alternatives, start with system architecture, configuration protocols, TUN requirements, and your everyday workflow; consider interface preferences after that. Our client guide highlights Clash Plus first and also compares other clients. Check each project's current release information for its maintenance status.

Application updates, core updates, and subscription updates are three different things. Updating a subscription fetches the remote configuration again; it does not patch the desktop application. Replacing the application will not fix nodes that your provider has taken offline. After migrating, recheck the listening port, policy group choices, rule matches, and DNS behavior—don't rely on an import-success message alone.

Read the mihomo source code

Git must be installed locally. This command retrieves source code from the public repository; review the project information there before running it.

git clone https://github.com/MetaCubeX/mihomo.git
View the core repository ↗
Compare alternatives now that the project is discontinued → Browse core and proxy terminology → Look up YAML configuration fields →

Field notes / Recent articles

Rules, TUN, and Client Selection

Choose a topic to explore. Start with the guide for hands-on steps, use the reference for parameter definitions, and read the articles for deeper explanations and trade-offs.

Browse all articles →

Download clients