Clash - Rule-based Network Proxy Core

Efficient, stable, cross-platform. Built for developers and power users.

Latest News

Track Clash releases, security advisories, and community tutorials

Release

Clash Meta v1.18.0 Released

New Vless protocol support, improved rule engine performance, multiple bug fixes and stability improvements.

2 hours ago
Security

CVE-2024-XXXX Vulnerability Fix

We have fixed a potential security vulnerability. All users are advised to update to the latest version.

1 day ago
Tutorial

Clash Configuration: Getting Started

Learn about Clash config file structure, how to write rules, and set up routing strategies.

3 days ago
Release

Clash Verge v2.0: New Interface

Rebuilt with Tauri, 60% faster startup, subscription management and rule editor included.

5 days ago
Community

ACL4SSR Ruleset Major Update

New domestic app routing rules added, ad blocking list optimized. Thanks to community contributors.

1 week ago
Tutorial

Using Clash as System Proxy on Linux

Detailed guide for configuring Clash as a global proxy on Ubuntu/Debian systems.

2 weeks ago
View More

Download Clash Client

Choose your platform and get the latest stable version

Clash Verge

v2.0.1 2026-06-20 12.4 MB

Cross-platform GUI client based on Tauri. Supports Windows / macOS / Linux.

Checksum Info
SHA256: a1b2c3d4e5f6... (example)

Install Guide | Changelog

Clash for Windows

v0.20.39 2026-05-15 38.2 MB

Classic Windows client with comprehensive features and wide community usage.

Checksum Info
SHA256: f6e5d4c3b2a1... (example)

Install Guide | Changelog

ClashX Pro

v1.120.1 2026-06-10 18.7 MB

Recommended macOS client with enhanced mode and system proxy toggle.

Checksum Info
SHA256: 1a2b3c4d5e6f... (example)

Install Guide | Changelog

Clash Meta for Android

v1.18.0 2026-06-18 8.6 MB

Android client. Requires allowing installation from unknown sources.

Checksum Info
SHA256: 9f8e7d6c5b4a... (example)

Install Guide | Changelog

All clients are open-source software. Please download from official channels to avoid security risks.

Why Choose Clash

Powerful, flexible, community-driven

Rule-based Routing

Flexible traffic splitting with domain, IP, GeoIP matching support.

Multi-protocol Support

Compatible with SS, SSR, VMess, Trojan, Vless and other mainstream protocols.

Strong Community

Rich config templates, rule sets, and a continuously evolving ecosystem.

Community & Resources

Friend links, not officially maintained

Frequently Asked Questions

Common questions about Clash answered

1. What is Clash? How does it differ from other proxy tools?

  1. Clash is a rule-based multi-protocol proxy tool core supporting SS, VMess, Trojan and other mainstream protocols.
  2. It defines routing rules through config files, intelligently routing traffic based on domain, IP and other conditions.
  3. Unlike single-protocol tools, Clash supports mixed multi-protocol usage with greater flexibility.
  4. Clash has an active community ecosystem providing rich config templates and rule set resources.
  5. It is open-source software with transparent code, security reviewed by the community.
  6. Clash supports cross-platform usage on Windows, macOS, Linux, Android and other systems.

2. How to choose the right Clash client for me?

  1. First confirm your operating system: Windows, macOS, Linux, Android or iOS.
  2. Windows users are recommended Clash Verge or Clash for Windows, with friendly UI and comprehensive features.
  3. macOS users are recommended ClashX Pro, supporting enhanced mode and seamless system proxy switching.
  4. Android users can choose Clash Meta for Android, supporting subscription import and rule editing.
  5. iOS users can get compatible clients through TestFlight or App Store.
  6. Download from official GitHub or mirrors provided on this page to avoid security risks from third-party modified versions.

3. What is the basic structure of a Clash config file?

  1. Clash config files are typically in YAML format, containing three core sections: proxies, proxy-groups, and rules.
  2. The proxies section defines your proxy node information, including server address, port, protocol and password.
  3. The proxy-groups section groups multiple nodes, supporting strategies like load balancing and auto-select.
  4. The rules section defines traffic routing rules, matching in order to determine whether traffic goes through proxy or direct.
  5. You can also configure DNS settings and general options (mixed-port, allow-lan, etc.) to customize behavior.
  6. Beginners are advised to refer to community-provided template configs and modify them to suit their needs.

4. How to import subscription links and update configs?

  1. Open your Clash client and find the "Config" or "Profiles" management interface.
  2. Click "New" or "Add", select "URL" type, and paste your subscription link.
  3. Name the config (optional), then click "Download" or "Import" to fetch the remote config file.
  4. After successful import, select the config to activate it, and Clash will run with this configuration.
  5. For subsequent updates, click the "Update" button to re-fetch the latest subscription content.
  6. Some clients support auto-update interval settings, configurable to refresh every few hours automatically.

5. What proxy protocols does Clash support? What are their features?

  1. Shadowsocks (SS): Lightweight encrypted proxy protocol, simple deployment, suitable for basic usage scenarios.
  2. ShadowsocksR (SSR): Enhanced version of SS, adding obfuscation and protocol parameters for better anti-detection.
  3. VMess: V2Ray original protocol, supporting TLS and WebSocket transport with good concealment.
  4. Trojan: Simulates normal HTTPS traffic, difficult to identify by deep packet inspection, high security.
  5. Vless: Lightweight evolution of VMess, removing encryption layer and relying on TLS for security.
  6. Clash Meta core has good support for all above protocols and continues to follow new protocol features.

6. How to troubleshoot connection failures when using Clash?

  1. First check if the network connection is normal, confirming the device can access the internet (direct connection).
  2. Check Clash log output to locate specific error messages (such as connection timeout, authentication failure, etc.).
  3. Confirm whether the proxy node is available, try switching to other nodes to test if it recovers.
  4. Check if node information in the config file is correct, including address, port, password and protocol parameters.
  5. Confirm system proxy settings are correct; some clients require manually enabling the "System Proxy" option.
  6. If the problem persists, try updating the Clash core version or re-importing the subscription config.