Frequently Asked Questions

Clash Verge is a graphical client, running on the mihomo core (formerly Clash Meta). The interface handles subscription management, node switching, and the system proxy toggle, while the actual traffic forwarding, rule matching, and DNS handling are done by the core. Updating the client and updating the core are two different things; most clients bundle a matching core version with each release.

A subscription is an HTTP(S) link that returns a configuration file containing nodes and rules when accessed. The link is provided by a proxy service provider through the user's account panel; you copy it and paste it into the client's subscription import field. This site does not provide any subscription service — only client downloads and configuration guidance.

Rule mode matches traffic against the rules in the configuration file one by one, routing each match to its designated policy — this is the recommended default. Global mode routes all traffic through a single proxy outlet, useful for quickly testing a node. Direct mode sends all traffic out without any proxy. All three can be switched from the client's main screen and take effect instantly.

Not exactly. Clash refers to the original open-source core, which is no longer updated. Clash Meta was a community fork that continued development and was later renamed mihomo, adding support for more protocols and rule types. Mainstream clients today (Clash Verge Rev, Clash Plus, FlClash, etc.) all run on the mihomo core, which is generally compatible with older Clash configuration files.

The clients listed on this site are all open-source or free software — downloading and using them costs nothing. What you pay for is the proxy service itself: subscriptions are sold by service providers and have nothing to do with the client software. If you encounter a channel charging for the installer itself, go back to the official release page or this site's download page instead.

This is Windows' default warning for installers that haven't yet built up signing reputation. Click "More info", then "Run anyway" to continue. This is safe as long as the installer came from the official release page or this site's download page — don't bypass this warning for installers from unknown sources.

Go to System Settings → Privacy & Security, find the blocked app further down the page, and click "Open Anyway". If it says the app is damaged, that's usually caused by the quarantine attribute on the downloaded file — run xattr -cr followed by the app path in Terminal to clear the quarantine flag, then reopen it. Make sure you download the correct installer for Intel or Apple Silicon.

The general approach: copy the subscription link, open the client's subscription/profile page, choose "Import from URL" and paste it in. After confirming, the client downloads the configuration and lists the nodes. Some clients support one-tap detection from the clipboard or QR code import. Success is confirmed when the node list appears and latency tests can run.

TUN mode needs to create a virtual network adapter. On Windows, the system service must be installed with administrator rights (most clients have an "Install Service Mode" button in settings); macOS and Linux require authorizing a system extension or running the core with elevated privileges. Restart the client after installing the service, then enable TUN. Once TUN is on, you don't need the system proxy toggle as well — don't enable both at once.

Turn on "Launch at Startup" in the client settings so it starts with the system; pair it with "Auto-start proxy" or the option to remember the last system proxy/TUN state, and the connection restores automatically after a reboot. On Windows, if service mode is enabled, TUN can also come up right after autostart. On Android, you'll also need to allow background running in system settings so it doesn't get killed by battery optimization.

UWP apps are blocked by the system from accessing the local loopback address by default, so they can't reach local ports even with the system proxy enabled. There are two fixes: use the "UWP loopback exemption" tool available in supported clients to lift the restriction for the target app, or switch to TUN mode, which takes over all traffic at the network layer and bypasses the loopback restriction entirely.

Fake-IP returns a reserved-range virtual address for every domain, which the core maps back to the real domain during forwarding — fast resolution and accurate rule matching, and it's the current default recommendation. Redir-Host returns the actual resolved result, which is compatible with a handful of programs that rely on real IPs, but it's no longer mainstream. If you run into issues with LAN services or online gaming, add a fake-ip-filter exception for the relevant domains.

In the client's Rules or Override feature, append an entry using Clash rule syntax — for example, DOMAIN-SUFFIX,example.com,DIRECT sends that domain and its subdomains through a direct connection; replace DIRECT with a policy group name to route it through a proxy instead. Rules are matched top to bottom, so custom entries need to sit above any wildcard rules to actually take effect.

Most clients let you set the subscription auto-update interval in hours. Setting it to 12–24 hours is fine for daily use; shorter intervals don't add much benefit and may trigger rate limits from the provider. If nodes act up, manually refresh the subscription once first and see if that resolves it.

select is a manual-choice group where you pick the node yourself; url-test periodically tests latency across the group's nodes and automatically picks the fastest one; fallback checks availability in list order and automatically switches to the next entry when the current one fails. A common setup is to use url-test for automatic selection, wrapped inside a select group for occasional manual override.

First paste the subscription link into a browser — if it returns content, the link is valid; if it returns an error, go back to the provider's panel to re-copy or reset the link. If the link works but the client fails to fetch it, that's usually a network path issue during the update — try updating while the proxy is on, or switch the User-Agent used for subscription requests in settings.

Check these in order: whether the system proxy toggle is actually on and whether the port matches the client's listening port; whether the browser has a separate proxy-controlling extension overriding the setting; and whether you're currently in Direct mode. Command-line programs don't read the system proxy — set environment variables separately or switch to TUN mode to take over.

First refresh the subscription to rule out stale node data; then switch the test URL or try a different node group to rule out a single blocked test address. If everything is still timing out, it's usually an expired subscription, exhausted data quota, or local network interference with the relevant protocol — check the first two in the provider's panel, and for the third, try switching node ports or protocol types.

Four common causes: a syntax error in the configuration file, a port already in use by another program, a leftover core process from a previous exit, or missing system runtime libraries. First end any leftover core process in Task Manager and try launching again; if it still fails, check the error in the client's log directory and fix the configuration or change the listening port as indicated; on Windows, install the required WebView2 or VC runtime if that's missing.

Disconnects usually happen because the system's power-saving policy killed the process — add the client to the battery optimization whitelist and allow background running and autostart; the exact menu names vary by manufacturer but are usually found in battery or app management settings. High battery drain is related to TUN staying active and the size of the rule set — trim down the subscription rules, extend the update interval, and switch to per-app proxy mode instead of full takeover when you don't need it.