Clash Verge Rev · mihomo Core
Review cross-platform installers, system architectures, and configuration steps, then choose a client for your device before importing a subscription, selecting a rule mode, and enabling the system proxy.
Windows installer
Desktop clientArchitecture
Installation flow
Operations Reference
Installation, subscriptions, rules, and diagnostics are arranged in the order they are typically used. Select a topic on the left to review the relevant action and reasoning in the same workspace.
01 / PLATFORM
The most common cause of installation failure is not the configuration itself, but a mismatch between the installer and the device architecture. On standard Intel or AMD Windows PCs, choose x64; select ARM64 only for devices with ARM processors. On macOS, distinguish Intel chips from Apple Silicon, including the M-series. On Linux, verify the package format as well as the architecture: Debian and Ubuntu commonly use .deb, while other distributions may require a package-manager-specific option or an archive.
The platform links on this page route devices to the appropriate download category rather than mixing every system into one button. On the downloads page, verify the client name, file extension, and architecture label before continuing with subscriptions and the system proxy. This order separates installation-environment issues from configuration issues and avoids repeatedly editing a subscription before the client starts correctly.
02 / PROFILE
Clash Verge Rev can manage remote subscriptions and local configuration files. When importing a remote URL, first confirm that it returns configuration content the client can recognize. Then check whether a new entry appears in the configuration list and whether its update time changes. Closing the input field does not prove that the import succeeded; verify that the configuration was saved, can be set as the active profile, and loaded its proxy groups and rules.
When a subscription update fails, first distinguish among a failed network request, an empty response, and an incompatible format. Network problems usually leave connection errors in the logs; an empty response requires checking the subscription source; format issues may appear as field-parsing failures. Unlike a simplified client with only one import button, the combination of the configuration list, update time, and logs makes it easier to identify the exact stage where the failure occurred.
03 / ROUTING
Rule mode uses configured domains, IPs, processes, or rule sets to decide whether a connection should use a proxy, connect directly, or be rejected. It is generally the most maintainable choice for everyday use. Global mode sends interceptable connections to the currently selected proxy group and is useful for temporarily testing a node or investigating rule matches. Direct mode bypasses the proxy and helps determine whether an issue is related to the proxy chain. Each mode serves a different purpose, so define the test objective before switching.
Proxy groups such as select, url-test, fallback, and load-balance follow different logic. Manual selection prioritizes control, automatic testing evaluates available targets at the configured interval, failover follows candidate order, and load balancing distributes connections across multiple targets. The client provides the controls, but actual behavior still depends on the active configuration, mihomo capabilities, and rule order.
04 / DIAGNOSTICS
If the target remains unreachable after enabling the system proxy, first check that the active configuration is enabled and that the proxy group has an available selection. Then inspect the connection direction and error type in the logs. Resolution failures usually call for checking DNS settings and upstream resolvers; connection refusals may involve a busy local port, an unavailable target, or process permissions. If rules do not match as expected, verify rule order, domain type, and the current mode instead of repeatedly reinstalling the client.
Higher log levels produce more detail, but there is no need to retain extensive debugging output during normal use. A safer process is to reproduce the issue once, note when it occurred, inspect the relevant log lines, and then change one variable at a time—for example, switch configurations, disable and re-enable the system proxy, or test a direct connection. Changing one condition per test makes it possible to tell whether the cause is the subscription, rules, DNS, port, or operating-system network settings.
Downloads for Five Platforms
The homepage does not distribute installer files directly. Open the platform category first, then compare the client, processor architecture, package format, and system requirements.
For Windows 10 and Windows 11 desktop devices. Most Intel and AMD PCs use the x64 installer; ARM devices require a separate architecture check. The downloads page lists Clash Plus, Clash Verge Rev, FlClash, Clash Nyanpasu, and archived clients so you can compare maintenance status and interface preferences.
Go to downloadsBefore installing on macOS, check the chip information under “About This Mac.” Choose an ARM64 or Apple Silicon build for Apple Silicon devices, and an x64 build for older Intel Macs. The platform page also lets you compare download options for Clash Plus, Clash Verge Rev, FlClash, and ClashX Meta.
Go to downloadsAndroid devices generally use an ARM64 package first; older devices may require ARMv7 or a universal package. The downloads page lists Clash Plus, Clash Meta for Android, FlClash, and Surfboard. After installation, grant the required VPN connection permission and import a valid configuration in the client.
Go to downloadsGet Clash Plus on iPhone and iPad through the App Store. After installation, follow the system prompts to add a VPN configuration, then import a subscription and choose a policy in the app. The platform page provides the store link and clashplus.io website information for verifying the app name and usage instructions.
Go to downloadsLinux users need to verify the distribution, processor architecture, and package format together. Desktop environments can use Clash Verge Rev or FlClash; servers, routers, and command-line environments are often better suited to the mihomo core directly. Before first launch, also check the configuration directory, file permissions, and service startup method.
Go to downloadsFeatured FAQs
Clash Verge Rev is a graphical desktop client, while mihomo provides core capabilities such as configuration parsing, rule matching, DNS, and proxy connections. The interface organizes configuration imports, proxy group selection, system proxy controls, and log viewing into usable workflows, but supported protocols and configuration fields still depend on the core version and configuration content. For a systematic comparison of core families and protocol differences, read the protocol reference.
Choose x64 for Windows PCs with common Intel or AMD processors. Select ARM64 only for devices with ARM processors running Windows on ARM. Check the system type under “Settings → System → About.” If it shows an x64-based processor, do not infer the architecture from the device’s release year alone.
First confirm that the configuration entry was saved successfully and set as the active profile, then check its update time and the logs. If the response is empty, verify the subscription source; if the logs report a field-parsing failure, the issue is usually the configuration format or core compatibility. If the configuration loads but the expected proxy groups are missing, check whether the configuration actually defines proxies and proxy groups. See the installation and configuration guide for the complete workflow.
Usually not. First confirm that the active configuration is enabled, the proxy group has a selection, and the running mode matches the test objective. Then check the logs for DNS errors, connection refusals, or port issues. Temporarily switching to direct mode can help determine whether the proxy chain is responsible. Changing conditions one at a time is easier to diagnose than modifying the subscription, DNS, and port together. See the FAQ for more troubleshooting paths.
Open-Source Ecosystem and Maintenance Boundaries
Understanding how the client, core, and configuration divide responsibilities is more useful for future updates and troubleshooting than memorizing a single download button.
Clash Verge Rev continues Clash Verge’s desktop-oriented workflow, providing graphical configuration management for Windows, macOS, and Linux users. The client brings subscription lists, proxy groups, rule modes, system proxy controls, core settings, and logs into one interface. It is not a subscription service and does not replace the configuration itself; successful connections still depend on the imported configuration, target availability, the operating system’s network environment, and the core’s implementation of the relevant protocols.
mihomo is a core implementation in the Clash Meta evolution line, responsible for reading configurations, opening listening ports, handling DNS, matching rules, and executing proxy connections. The graphical client and core can be updated independently, so when new fields are unrecognized or protocol behavior changes, check the client version, core version, and configuration source together. Updating only the interface does not necessarily change core capabilities, while replacing only the core may require another compatibility review.
Public repositories can reveal code changes, release records, issue discussions, and contribution history. Regular users do not need to read the entire source code, but commit records and issues can help confirm whether a feature has been implemented, whether a system problem has been reproduced, and what maintainers recommend. For legacy clients that are no longer maintained, the downloads page clearly marks their archived status so historical projects are not confused with actively updated clients.
A client update may affect the interface, system proxy implementation, configuration directory, or how the core is invoked; a core update may change protocols, DNS, rule providers, or configuration fields. A safer update sequence is to save the currently working configuration, read the release notes, update the client, and confirm the core status. After updating, check that the configuration loads, proxy groups are complete, and the system proxy works before addressing rules for individual sites or applications.
git clone https://github.com/clash-verge-rev/clash-verge-rev.gitThe clone command is intended for developers who need to inspect the source, reproduce the build process, or contribute. For a standard installation, use the platform installer provided on the downloads page.
Latest Technical Articles
From first-use tasks to advanced configuration, these guides break down client pages, DNS fields, and system network restrictions by concrete problem.
Learn the proxy, configuration, and logs pages in the order they are used, including common controls, status information, and the areas to watch during the first connection.
Read the full article →Review the processing order, use cases, and configuration boundaries of common DNS fields to understand the relationship between resolution failures and rule matching.
Read the full article →Learn how loopback restrictions affect Store apps, how to remove them, and how to verify recovery when the system proxy works but specific apps cannot access the network.
Read the full article →