Windows
Windows 10 64-bit and above
The go-to desktop platform for work and gaming; Clash Verge Rev ships a GUI with one-click TUN.
DownloadOPEN SOURCE · Clients for Five Platforms, Continuously Updated
Clash Client Downloads and Setup Guide for All Platforms
Download links for Windows, macOS, Android, iOS, and Linux, paired with subscription import steps, TUN mode setup, and rule-based routing explanations — download and configuration in one place. This site provides no proxy nodes of its own; it only distributes clients and maintains the documentation, and every installer can be verified against the checksums on the upstream release pages. Connect the world, instantly.
- Free to Get
- Open Source Code
- English Documentation
01
Core Features
SECTION / FEATURESRule-Based Routing
Rules match by domain, IP range, and geographic location, sorting traffic before it reaches an exit — proxy, direct connection, and blocking each follow their own path. The core problem it solves is deciding which traffic goes through the proxy and which connects directly: local sites stay on the direct route, cross-border services use the matching exit, and ad or tracker domains can simply be rejected. For everyday use the rule sets bundled with your subscription are enough; advanced users can prepend custom entries at the top of the config, relying on first-match-wins ordering to override defaults. Compared with toggling a global proxy by hand, rule-based routing is configured once and works continuously, giving you both speed and accuracy.
- Match Criteria
- DOMAIN-SUFFIX / DOMAIN-KEYWORD / IP-CIDR / GEOIP
- Execution Order
- Rules are checked top to bottom; matching stops evaluation and later rules are skipped
- Fallback Policy
- A trailing MATCH rule sends unmatched traffic to a single default exit
- How Changes Apply
- Reload the config after editing — no client restart required
Multi-Protocol Support
The core has multiple proxy protocols built in, so a single config can mix nodes of different protocols without installing separate software for each. What it removes is the maintenance burden of running several tools side by side: Shadowsocks, VMess, and Trojan used to demand a client each, while now one core handles them all — whatever protocols your subscription mixes in just work. There is nothing extra to set up; after importing a subscription the core resolves protocol differences automatically, and switching nodes never requires thinking about the underlying implementation. Compared with single-protocol clients, the key difference is that changing providers or protocols never means changing software: the config stays one YAML file, and the learning cost is paid only once.
- Supported Protocols
- Shadowsocks / VMess / VLESS / Trojan / Hysteria2 / TUIC
- Transport Layer
- TCP / WebSocket / gRPC / QUIC
- Config Format
- Standard YAML, compatible with common subscription output formats
- Node Count
- No built-in cap; actual limits depend on device memory
TUN Mode
A virtual network adapter takes over all outbound traffic on the system, covering programs that ignore system proxy settings, such as command-line tools and game processes. It targets the built-in blind spot of the system proxy: many programs never read the proxy settings at all, so in normal mode their traffic bypasses the proxy entirely. To enable it, flip the TUN switch in the client settings and grant system permission — run as administrator on Windows, or install and approve the system extension on macOS. Compared with a plain system proxy, TUN works at the network layer, is fully transparent to applications, and captures UDP traffic and DNS queries as well, making it the standard approach for game acceleration and full-system takeover scenarios.
- Coverage
- All TCP / UDP traffic, without relying on an app's own proxy support
- Permission Requirements
- Administrator rights on Windows; system authorization on macOS and Linux
- Stack Implementation
- Choose from system / gvisor / mixed implementations
- DNS Handling
- Built-in fake-ip and redir-host resolution modes
Subscription Management
Once a subscription link is imported, it updates automatically at a set interval, refreshing the node list and rule set together, with usage data read on each update. It solves the chore of manual syncing: when your provider adds or removes nodes or adjusts rules, the client picks up the latest config on its next scheduled update, without pasting the link again. Just set an update interval after importing — 12 or 24 hours is typical — and the subscription panel will clearly show when traffic is running out or the plan is near expiry. Compared with maintaining a local config by hand, subscription management leaves node operations entirely to the provider while your local overrides stay untouched; moving to a new device only takes pasting the link once to restore everything.
- Import Methods
- URL import / clipboard read / local file
- Update Interval
- Customizable; a common setting is every 12–24 hours
- Usage Data
- Data used and expiration date parsed from the subscription response headers
- Multiple Subscriptions
- Multiple subscriptions can coexist and be enabled or disabled individually
Latency Testing
Test requests are sent to nodes in bulk and sorted by latency; proxy groups can auto-select an exit based on the results. It answers the ever-recurring question of which node is fastest right now: instead of trying nodes one by one, a single test run shows millisecond values and timeout status for the whole list. In daily use, just hit the test button on the proxies page; set a group's type to url-test and the client will retest on a fixed interval and switch to the lowest-latency node automatically, while a fallback group fails over to backups when the preferred node breaks. Compared with switching nodes by feel, data-driven selection is more stable, timed-out nodes are clearly flagged, and diagnosing line problems gains a direct reference.
- Test Method
- Timed HTTP requests sent to a specified URL
- Proxy Groups
- url-test auto-selection / fallback failover
- Trigger Timing
- Run manually, or automatically at a set interval
- Result Display
- Millisecond values color-coded by tier, with timed-out nodes flagged separately
02
Quick Start
SECTION / QUICKSTART
S-01
Get a Subscription
Copy the subscription link from your provider's account center, or prepare a local YAML config file. Copy the link once — future updates are handled automatically by the client. Treat the subscription link as an account credential: never paste it in public, and reset it in the account center immediately if it leaks.
S-02
Import into Client
Open the client's subscription or config page, paste the link, and confirm the import. Once the client pulls nodes and rules, the configuration takes effect immediately. If the import fails, first check that the link is complete and the subscription server is reachable, then consult the tutorial for format issues.
S-03
Verify Connection
Enable the system proxy or TUN mode, pick a node with normal latency, and visit a target site to confirm the routing result matches the rule's expectations. It also helps to open the connections panel and watch the live log to confirm each domain hits the expected rule and exit.
03
Client Downloads
SECTION / DOWNLOADmacOS
macOS 11 and above
Available for both Intel and Apple Silicon — pick the installer that matches your chip.
DownloadAndroid
Android 8.0 and above
A universal APK for phones and tablets, built on VpnService — no root required.
DownloadiOS
iOS 15 and above
Compatible apps come from a non-CN App Store region; see the download page for account and purchase notes.
Access MethodsLinux
Mainstream x86_64 / arm64 distributions
Desktop distros can use the GUI client; servers and soft routers should run the mihomo core directly.
Download
04
Maintained by an Open Source Community
SECTION / OPEN SOURCE
R-01
Publicly Auditable Code
The core and mainstream clients are released under open source licenses. Protocol implementations, rule-matching logic, and network behavior are all present in the source code — anyone can read, build, and review it, with no closed black box. The original Clash project went open source on GitHub in 2018; after the original repository stopped maintenance, the community carried the core forward as mihomo (formerly Clash Meta), adding newer protocols such as VLESS and Hysteria2. Clash Verge Rev, FlClash, and ClashMetaForAndroid all wrap a GUI around this same core — clients follow core releases, and swapping in a newer core brings the latest features.
- LicenseGPL-3.0 / MIT (varies by project)
- Maintenance ModelCommunity submissions merged after public review
- Release CadenceVersion history is traceable on the repository's release page
- Core LineageGUI clients share the mihomo core, so configs are interchangeable
- Update MechanismChecksums on release pages; in-app update checks available
GET SOURCE / Get Kernel Source
git clone https://github.com/MetaCubeX/mihomo.gitAfter cloning, follow the documentation in the repository to build it yourself. Everyday use doesn't require building from source — just download the matching client above. To verify an installer's origin, compare the files distributed here against the checksums of the same version on the release page.
05
FAQ Picks
SECTION / FAQ PICKS
Q-01
No internet after installing?
First confirm the system proxy is on and node latency tests don't time out, then work through the troubleshooting checklist for port conflicts and DNS settings.
Q-02
Where does the subscription link come from?
Subscriptions come from your node provider — this site sells none; import steps are in the user guide and the setup Q&A.
Q-03
Which client should I pick?
Clash Verge Rev is the desktop default, while Android users can choose ClashMetaForAndroid or FlClash — see the client usage Q&A for a comparison.
Q-04
How do Fake-IP and TUN relate?
Fake-IP is a DNS resolution strategy used in TUN mode that cuts resolution wait time; the concept is explained in the glossary.
06
Latest Articles
SECTION / BLOGClash Subscription Link Import Guide: Three Methods and Common Format Notes
Starting from getting a subscription link, this article compares URL import, clipboard import, and local file import step by step, and explains where to find the update interval and usage data.
Read More →Clash Connection Failed Checklist: From Port Conflicts to System Proxy Settings
A checklist covering local port usage, system proxy toggles, node availability, DNS resolution, and firewall blocking, in order, with verification commands for each step.
Read More →How TUN Mode Works and How to Enable It: The Right Way to Capture Global Traffic
Explains the difference between the TUN virtual adapter and a system proxy, which programs need TUN mode to route through the proxy at all, and the permission and DNS considerations when enabling TUN on each platform.
Read More →