Open source project · Clients continuously updated·clashsupport.com

Clash Client Downloads & Config Docs for Every Platform

Download Clash View Setup Guide

This site collects client download links for the Clash ecosystem across Windows, macOS, Android, iOS, and Linux, along with step-by-step subscription import guides and a symptom-based troubleshooting handbook — every step is verified on real devices before publishing.

Free Forever Open Source English Docs core: mihomo

Got an error? Check the Troubleshooting Handbook →

clash/community
Star Fork
Public clash / community main
Code Issues Discussions

Get the Client by Platform

Each of the five platforms has an actively maintained GUI client — click a platform card to jump straight to its section on the download page. Not sure which to pick? Check the client comparison first.

Windows Installer and portable build available, with service mode and auto-start support Go to download → macOS Intel and Apple Silicon builds, managed from a persistent menu bar icon Go to download → Android Direct APK install, traffic handled via VpnService, no root required Go to download → iOS Official App Store listing, system-level traffic handling via Network Extension Go to download → Linux deb packages and binary releases, with both desktop and kernel-only options Go to download → All Clients Includes mihomo kernel releases and archived clients for every platform View all clients →

Core Capabilities

Six core capabilities of the Clash client, organized like an issue tracker — click a title to expand the full explanation. Each one links to a tutorial or handbook chapter on this site, not marketing copy.

Open 6 Closed 0 LabelsSort

Policy Groups

At the core of Clash is a rule engine: every connection is matched against a rule table by domain, IP range, process name, and similar conditions, then routed to the specified proxy or direct exit. Sites in mainland China connect directly while specific services route through a proxy, all decided automatically without manual switching. Subscription configs usually ship with a mature rule set built in, ready to use on import; advanced users can also write custom rules to override the defaults.

Rules are matched top to bottom, with common types including DOMAIN-SUFFIX, DOMAIN-KEYWORD, IP-CIDR, GEOIP (geographic database), and PROCESS-NAME (routing by process). This differs from traditional "global proxy" tools: Clash doesn't force all traffic through one exit — each connection takes its own path, saving bandwidth and avoiding services in mainland China getting flagged for traffic exiting through a proxy. Full details on rule syntax and match order are covered in the Troubleshooting Handbook and related Technical Notes articles.

Node Management

Policy groups organize multiple nodes into a selectable group: a select group is chosen manually, a url-test group periodically checks latency and auto-switches to the fastest node, and a fallback group falls back through nodes in order when the preferred one fails. With dozens or hundreds of nodes in a subscription, there's no need to test each one manually — opening a policy group in the client shows the measured latency for every node.

Latency testing works by sending a timed HTTP request to the url specified in the config (commonly Google's generate_204 endpoint); the value reflects the full round-trip latency of reaching that address through the node, not a raw ping. The interval parameter on a url-test group controls the testing cycle, while tolerance prevents flapping between two nodes with similar latency. Which group type fits which use case, and how to nest them, is discussed further on the client comparison page and in the Technical Notes.

Subscription Import

A proxy subscription is essentially a downloadable YAML config URL. Every mainstream client supports pasting a subscription link for one-click import, plus scheduled auto-updates so node changes and rule revisions sync locally with each refresh. Multiple subscriptions can coexist, and switching configs swaps the entire set of nodes and rules at once.

Import failures are the most common issue for newcomers, usually falling into three categories: the subscription URL itself needs a proxy to reach (update via direct connection or a temporary node first), the subscription returns a base64-encoded format the client can't parse directly (needs client-side conversion support or a conversion service), or the subscription has run out of traffic or expired (the server returns an error page instead of YAML). Step-by-step troubleshooting is covered in the "Subscription Failures" section of the Troubleshooting Handbook, with a dedicated analysis also available on the FAQ page.

Advanced

System proxy settings only cover apps that honor them — command-line tools, game clients, and UWP apps often bypass them entirely. TUN mode creates a virtual network adapter at the network layer and routes all outbound device traffic through Clash, matching VPN-level coverage while routing rules still apply. It's the standard fix for "some apps won't go through the proxy."

Enabling TUN requires administrator privileges (on Windows this usually pairs with a service-mode install), and enabling DNS hijacking alongside it is recommended — otherwise system DNS queries may bypass the virtual adapter and cause rule mismatches. TUN doesn't conflict with the system proxy and both can run together; the performance overhead is slightly higher but barely noticeable for everyday browsing and downloads. A dedicated Technical Notes article compares the two modes and offers guidance on choosing between them, and handling Windows UWP loopback restrictions is covered in the Troubleshooting Handbook.

Kernel

Current clients generally run on the mihomo kernel (often called Clash Meta in the community), which extends the original protocol set with newer additions like VLESS, Hysteria2, and TUIC — mixing nodes of different protocols in a single config works without issue. The kernel is open source under GPL-3.0, with releases covering desktop, server, and router architectures.

Development of the original Clash kernel stopped in 2023, and mihomo took over protocol evolution as the community successor project: older protocols like Shadowsocks, Trojan, and VMess remain fully compatible, and new protocols get added as upstream implementations mature. For most users, picking a client "built on the mihomo kernel" guarantees the widest protocol coverage — every actively maintained client listed on this site's download page meets that bar. When a subscription contains a node using a protocol the client doesn't recognize, upgrading the kernel version usually resolves it.

Advanced

With allow-lan enabled, a computer running Clash becomes a proxy server for the whole local network: phones, TVs, and game consoles just need to point their network proxy at that computer's IP and mixed port to share the same nodes and rules, with no need to configure every device separately.

Three config points matter here: mixed-port specifies a single port handling both HTTP and SOCKS; allow-lan is set to true with bind-address confirmed to allow outside access; and the OS firewall permits inbound connections on that port. With those three in place, other devices just enter the computer's local IP and port in their Wi-Fi proxy settings. Taking it further, this machine can be turned into a bypass gateway so the whole subnet routes through Clash by default. Full steps with firewall configuration screenshots are covered in the Technical Notes article on LAN sharing.

Three Steps to Your First Connection

1

Install the Client & Import a Subscription

Pick the installer for your platform on the download page, open the client after installing, and paste the subscription link from your proxy provider into the "Profiles/Subscription" field — then wait for the config to download.

2

Choose Rule Mode & a Node

Leave the proxy mode on the default "Rule" setting, then open the policy group screen and pick a low-latency node for the main group — or just let an auto-test group handle it.

3

Enable the System Proxy & Verify

Turn on the "System Proxy" toggle (or start the VPN on mobile), visit a site outside China to confirm the connection works, then visit a site in mainland China to confirm direct connections still work.

For detailed steps, screenshots, and common sticking points, see the full tutorial →

Open Source Ecosystem & Maintenance

Clash first launched in 2018 as an open source rule-based proxy kernel. Its clear YAML config format and rule-routing design made it the de facto configuration standard in this space — today, the vast majority of subscription services output Clash-format configs. After the original author stopped development in 2023, the community project mihomo (Clash Meta) fully took over kernel development, keeping protocol support and bug fixes actively updated ever since.

A multi-client ecosystem has grown around the kernel: GUI clients like Clash Verge Rev, FlClash, and Clash Nyanpasu are independently maintained by different teams, each making its own tradeoffs on interface and platform coverage, but all sharing the same kernel and config format. That means switching clients doesn't require switching subscriptions — one config works across all five platforms. Both the kernel and the mainstream clients are developed in public repositories, so anyone can review the code, commit history, and release artifacts.

This site is a community-maintained documentation and download hub: download links follow each client's official release channel, tutorials and handbook content are published only after verification on real devices, and relevant sections are revised whenever a client has a significant update. The site itself doesn't provide proxy nodes and isn't affiliated with any subscription provider.

To build the kernel directly from source, clone the repository:

git clone https://github.com/MetaCubeX/mihomo.git

facts.yaml

  • kernel: mihomo
  • license: GPL-3.0
  • config: YAML
  • platforms: Windows / macOS / Android / iOS / Linux
  • since: 2018

note

The kernel, clients, and rule sets are maintained in separate repositories, so upgrades don't block each other; the kernel version bundled with a client can be checked on its settings page — if a protocol isn't recognized, check the kernel version first.

Featured FAQs

Subscription updates keep failing?First check whether the subscription URL opens directly in a browser, then see if the client needs to temporarily switch to direct connection to fetch it — details in the FAQ.

Proxy is on but some apps aren't using it?Command-line tools and UWP apps often bypass the system proxy — switch to TUN mode to capture them, see the setup guide.

All nodes timing out — how to troubleshoot?Work through it in order: local network → subscription validity → node availability → rule matching. The full process is in the Troubleshooting Handbook.

Do configs work across different clients?Yes — mainstream clients share the same YAML config format, so switching clients just means re-importing the subscription. See the client comparison for picking one.

Technical Notes · Recently Updated

Browse everything by tag: View all articles →

Download Clash