Clash Verge FAQ

Import a remote subscription or a local Clash/Mihomo configuration, activate the profile, then choose the proxy group or node defined by that profile. After the configuration loads correctly, enable system proxy for applications that honor OS proxy settings or use TUN when you need broader traffic capture. If you still need an installer, current and previous builds are listed on GitHub Releases.

Most Intel/AMD Windows PCs use x64, while Windows on ARM devices use ARM64. Apple Silicon Macs use aarch64/ARM64 and Intel Macs use x64. Linux builds are available in DEB and RPM formats for x64, ARM64 and ARMv7, so match both your distribution and CPU architecture.

Clash Verge uses Tauri, whose Windows interface depends on WebView2. If the process starts but the panel stays blank, the tray icon does nothing, or the UI closes immediately, check whether WebView2 was removed or disabled. Current Releases also provide larger builds with WebView2 included for systems that cannot install it normally.

Clash Verge is a proxy client, not a proxy-server provider. The node list, proxy groups and routing rules come from the Clash/Mihomo profile you import. If the proxy view is empty, add a remote subscription, import a local config, or load a profile that already defines the required proxies and groups.

TUN creates a virtual network interface and changes operating-system routing, so Clash Verge needs privileged service capabilities to manage it. The exact permission flow differs across Windows, macOS and Linux, but it is separate from simply opening the desktop application or using system proxy.

No. Clash Verge manages local Clash/Mihomo configuration and the proxy servers referenced by that configuration; it does not provide subscription plans, proxy nodes or network service. Those resources come from third-party providers or infrastructure you operate yourself.

Add the remote URL from the profile/subscription page or import a local configuration file. Clash Verge also supports the clash:// URL scheme for configuration import. After importing, select the active profile and then choose the proxy groups or nodes defined inside it.

Direct edits to the downloaded source profile can be replaced when the subscription refreshes. For reusable rule changes, use the profile's visual rule editor for prepend/append rules; use Extension Config for YAML overrides and Extension Script when the generated configuration needs programmatic changes.

Extension Config is YAML-based and merges or overrides fields in the generated profile. Extension Script uses JavaScript for more flexible transformations. Older Clash Verge documentation called these Merge Config and Script Config; prepend/append rule editing is now handled through the profile's visual rule editor.

Yes. Use the visual rule editor when you want to insert rules around a subscription's existing rules, or use Extension Config/Extension Script when the generated profile needs broader changes. Mihomo evaluates routing rules in order, so rule placement is just as important as rule syntax.

The project privacy policy states that configuration, credentials and logs are stored in the application's local data directory. Those files can include subscription URLs, proxy credentials and connection metadata, so back them up carefully and review them before attaching anything to a public bug report.

System proxy changes the operating-system proxy settings and only affects applications that use those settings. TUN creates a virtual network interface and can route a broader set of application traffic through Mihomo, including software that does not read the system proxy configuration.

Check the privileged service or permission state, virtual/network adapters, routing conflicts, firewalls and other networking tools. On Windows, multiple adapters can conflict with TUN routing; search GitHub Issues with your platform, version and exact error when the basic checks do not isolate it.

Rule mode lets the active Mihomo rules choose DIRECT, a proxy group or another policy for each connection. Global mode routes traffic through the global proxy policy, while Direct mode bypasses proxy routing. Switching modes temporarily can help separate a routing-rule problem from a node or connectivity problem.

Not every application reads the operating system's proxy settings. Command-line tools, games and applications with their own network stack may connect directly unless you configure an explicit proxy inside the app or use TUN to route that traffic at the network-interface layer.

Not necessarily. The latency test measures response time to the configured test URL and is useful for comparing reachability and round-trip delay. Throughput depends on many other factors, including route quality, server load, congestion and the destination you are actually using.

An abnormal shutdown can leave the operating-system proxy setting enabled even though Clash Verge is no longer running. Reopen Clash Verge and disable system proxy normally, or turn the manual proxy off in your operating system's network settings.

The current project privacy policy states that Clash Verge Rev does not collect telemetry, analytics, crash reports or usage data. Configuration, credentials and logs are stored locally, although features such as subscriptions, proxy servers, update checks, DNS, IP information and WebDAV can connect to separate third-party endpoints.

Clash Verge is the local desktop client. A subscription service provides a remote profile, and proxy nodes carry traffic when a rule selects them. Those are separate layers, so node quality, service pricing, traffic retention and provider policies are not controlled by the Clash Verge client.

The application hands traffic to the local Mihomo core through system proxy or TUN. Mihomo evaluates the active routing rules and then chooses DIRECT, REJECT or a proxy policy. Only traffic assigned to a proxy policy is forwarded through the selected proxy server; DIRECT traffic leaves through the local network normally.

In Rule mode, Mihomo evaluates the current routing rules from top to bottom. Domain rules, IP results, process rules and rule providers can send different connections to different policies. A profile update, DNS result change or rule-provider refresh can therefore change which rule matches the same destination. Version-specific implementation details can be checked in the project repository.

Local application data is normally reused across updates, but a major version can include migrations or compatibility changes. Back up the application data directory or create a WebDAV backup before a significant upgrade, and read the release notes when moving across older versions.

A Stable Release and an AutoBuild are Clash Verge application build channels: AutoBuild tracks newer development commits and may include unfinished changes. Mihomo Stable/Alpha is a separate proxy-core channel inside the client. Changing the core channel does not turn a stable Clash Verge application build into an AutoBuild.

Previous application builds and release notes remain available on the Releases page. Back up local data first, then choose the older package for the same operating system and CPU architecture; pay attention to any migration notes between the two versions.

Configure your own WebDAV server in Clash Verge, create a configuration backup, then restore that backup after a reinstall or on another desktop. The WebDAV server receives the backup file, which can contain sensitive profile information, so its credentials and privacy policy matter.

Clash Verge Rev currently targets Windows, macOS and Linux desktop systems. Android and iOS clients belong to other projects and may support a different subset of Clash/Mihomo configuration features.

Current Releases provide Windows x64 and ARM64 builds, macOS builds for Apple Silicon and Intel, and Linux DEB/RPM packages for x64, ARM64 and ARMv7. Windows 7 is no longer supported, and exact operating-system requirements can change between releases.

Clash Verge is the desktop GUI. Mihomo, formerly known as Clash.Meta, is the proxy core that handles protocols, DNS, routing rules, proxy groups and traffic forwarding. “Clash” is the broader configuration and client ecosystem name, which is why users commonly refer to Clash profiles, Clash rules and Clash-compatible configurations when working with Mihomo.

Yes. Clash Verge Rev is GPL-3.0 open source. Building it locally requires Node.js/Corepack/pnpm, Rust and the platform-specific Tauri dependencies; use the repository README and current CONTRIBUTING.md rather than relying on commands from an older release.