mihomo core
An open-source proxy client built on the mihomo core, with built-in subscription management, rule-based routing, and TUN mode, plus Chinese configuration docs and multi-platform installers.
Clash Verge is an open-source proxy client built on the mihomo core, supporting Windows, macOS, Linux, Android, and iOS. The client handles subscription management, config generation, and the UI, while the core handles traffic forwarding; the config format is compatible with the broader Clash ecosystem. The download page lists available clients, package formats, and system requirements for each platform, with installers kept in sync with official release channels. The links below jump directly to the download card for each platform.
Windows 10/11 x64 and ARM64, with installers such as Clash Verge Rev and FlClash.
Go to DownloadIntel and Apple Silicon, with Clash Plus, Clash Verge Rev, and FlClash available.
Go to DownloadAndroid 8.0 and above, with Clash Meta for Android, FlClash, and Surfboard APKs.
Go to DownloadUniversal for iPhone and iPad; install App Store clients, including Clash Plus.
Go to DownloadClash Verge is an open-source proxy client built on the mihomo core, supporting Windows, macOS, Linux, Android, and iOS. The client handles subscription management, config generation, and the UI, while the core handles traffic forwarding; the config format is compatible with the broader Clash ecosystem. The download page lists available clients, package formats, and system requirements for each platform, with installers kept in sync with official release channels. The links below jump directly to the download card for each platform, with supported OS versions, recommended clients, and installation notes clearly marked.
Windows 10/11 x64 and ARM64, with installers such as Clash Verge Rev, FlClash, and Clash Nyanpasu. First-time installs need the WebView2 runtime.
Go to DownloadIntel and Apple Silicon, with Clash Plus, Clash Verge Rev, and FlClash. On ARM chips, choose the Apple Silicon build.
Go to DownloadAndroid 8.0 and above, with Clash Meta for Android, FlClash, and Surfboard APKs, supporting V2Ray and Trojan protocols.
Go to DownloadUniversal for iPhone and iPad; install App Store clients, including Clash Plus. Config files use the same format as the desktop versions.
Go to DownloadOffers .deb and .rpm packages for x64 and ARM64, suitable for Debian/Ubuntu and Fedora-based distros, plus standalone mihomo core binaries.
Go to DownloadClash Verge turns common proxy client features into ready-to-use settings: importing a subscription generates a complete config automatically, rule-based routing matches domains and IPs to policy groups, TUN mode takes over system traffic, and the DNS section gives fine-grained control over the resolution chain. The four panels below mirror the real modules in the client's settings page, and each one has corresponding configuration docs and troubleshooting steps in the usage documentation and advanced pages.
Subscription management imports the subscription URL from your provider into the client and automatically parses it into three config sections: proxies, proxy-groups, and rules. Multiple subscriptions can coexist, and each profile has its own update interval and enabled state; updates only pull remote changes and never overwrite your local override layer. Compared with hand-editing YAML, subscription management collapses node additions/removals and policy group tweaks into a single import. When a link goes bad, the panel shows a parse error that helps you tell whether the link expired, the content format is wrong, or the network is blocked.
TUN mode uses a virtual network adapter to take over all IP traffic at the system level, without relying on apps to read proxy settings on their own. Command-line tools, games, and UDP apps are often bypassed under system proxy mode; with TUN enabled, that traffic goes through the core and is forwarded according to the rules. The settings page provides the TUN mode switch, stack type, and DNS hijacking options, and pairing it with Fake-IP reduces resolution latency. On Windows, enabling it for the first time requires installing a service and allowing it through the firewall; if that fails, check the logs page for the service installation error code.
Rule-based routing sends different domains and IPs to different policy groups. Rules are matched top-down and stop at the first hit; common patterns include DOMAIN-SUFFIX for subdomains, DOMAIN-KEYWORD for keywords, GEOIP for region-based routing, and MATCH as the fallback. The rule sets generated by subscriptions cover common streaming and ad domains, and advanced users can add custom rules in the override layer to route mainland China traffic directly, outside-China traffic through the proxy, and specific sites through dedicated nodes. Rule order changes take effect immediately without restarting the core.
The DNS section determines how domain resolution results enter the core. nameserver handles regular resolution, fallback handles a second round for sensitive domains, and fallback-filter controls which domains participate in the fallback; with DNS hijacking enabled in TUN mode, all resolution requests go through the core to avoid leaks. Fake-IP mode assigns virtual IPs to domains so rule matching completes before the connection is established, reducing first-packet latency. Misconfiguration often shows up as certain sites failing to load; check each field against the docs.
Both the Clash Verge client and its core are hosted in public repositories, with release history, issue discussions, and commit records all traceable. The information below helps you gauge the project's maintenance status and update cadence.
Clash Verge originally emerged as a replacement for Clash for Windows, solving the lack of a unified entry point for Windows and macOS users after the original client stopped being maintained. The project uses Tauri for the UI layer and delegates config generation and traffic forwarding to the core, keeping the UI decoupled from the core. As a result, core upgrades don't wait for UI rewrites, and UI updates don't affect already-generated configs.
mihomo is the actively maintained core in the Clash ecosystem. It's compatible with Clash's config file format and adds rule sets, domain sniffing, and more transport protocols. Clash Verge ships with mihomo built in, and the config.yaml generated after importing a subscription can be read directly by other Clash-family clients, so migration costs are low and configs are interchangeable with ClashX Meta and Clash for Android.
The client and core are versioned separately: UI updates focus on settings layout, subscription management, and TUN behavior, while core updates focus on protocol implementations and security fixes. The download page provides installers for each platform, and updates preserve local configs so you don't need to re-import subscriptions; the core binary is also available separately for server and router users.
The project is open source under GPL-3.0, with source code, build scripts, and release notes in public repositories. The Issues section tracks reported problems and fix progress. Community-maintained Chinese documentation covers installation, subscription import, rule writing, and troubleshooting; when you run into a problem, search existing discussions by keyword.
git clone https://github.com/clash-verge-rev/clash-verge-rev.gitThe repository contains client source code, build scripts, and release notes under GPL-3.0. After cloning, follow the build steps in the README to compile installers for your platform locally.
Hands-on notes on installation, DNS resolution, TUN mode, and subscription troubleshooting, with the three latest posts in reverse chronological order. See the technical notes page for the full list.
Walk through the full Windows setup in order: install, import subscription, enable system proxy, switch to TUN. Then break down the issues beginners hit most, one by one — missing WebView2, service installation failures, firewall blocks, and more.
Read more →Starting with enable and listen in the dns section, this post explains field by field how nameserver and fallback divide the work, how fallback-filter filters, and why DNS hijacking in TUN mode only works when paired with Fake-IP.
Read more →Compares how system proxy depends on apps reading proxy settings on their own while TUN takes over all IP traffic through a virtual adapter, explains why command-line tools, games, and UDP apps behave differently under each mode, and covers which scenarios suit each one.
Read more →These questions come from the most frequent installation and configuration inquiries. See the FAQ page for the full categorized answers.
First check whether the proxy port is already in use by another program, then verify the system proxy switch actually took effect. Some browser extensions override system proxy settings — try setting the extension to direct and keeping only the system proxy.
Check in order: whether the subscription link has expired, whether the provider returns Clash-format YAML, whether the network can reach the link directly, and whether your core version supports the new fields in the config.
Yes, but usually you don't need to. TUN already takes over all traffic, so adding system proxy just adds another forwarding layer. If you need command-line tools and UDP to go through the proxy, enable TUN only; for regular web browsing, system proxy alone uses fewer resources.
Check whether the update interval hasn't elapsed yet, whether the provider is rate-limiting the subscription link, and whether the client can't reach the subscription URL because of the proxy's own network. You can also trigger a manual update from the settings page and check the logs.