FAQ

The Clash core is a command-line program that handles proxy forwarding and rule matching. GUI clients like Clash Verge Rev and FlClash sit on top of the core, providing a subscription manager, node switcher, and system proxy toggle.

The core is already bundled inside every client installer, so desktop and mobile users don't need to download it separately; the standalone mihomo core archive listed on the download page is meant for servers and routers. For the full lineage and feature differences across core variants, see the protocol handbook.

There's no difference in content. This site mirrors the GitHub Releases of each client — every installer is byte-for-byte identical to its official counterpart, with no modifications and no repackaging.

The mirror exists to give users with unstable direct access to GitHub a reliable download route. Version numbers are shown on each client card on the download page.

The original Clash core stopped receiving updates in 2023. Clash Meta is a community fork built on top of it, adding support for more proxy protocols and a more complete set of rule types; mihomo is the new name for the Clash Meta project — they're the same project.

Every actively maintained client today ships with the mihomo core, and its config syntax remains backward-compatible, so original Clash configs still work as-is. See the core section of the protocol handbook for a detailed comparison of all three.

Both the client and core are open-source and completely free. A subscription is a URL provided by a proxy service that contains node info and routing rules — once imported into the client, it's ready to use.

The subscription service itself is provided and billed by a third-party provider, unrelated to the client software or this site. This site only mirrors software downloads; it doesn't provide or recommend any subscription service.

Rule mode matches traffic against the rules in your config file one by one, applying the matched action (proxy, direct, or reject) — this is the recommended mode for everyday use. Global mode routes all traffic through the currently selected node, useful for debugging rules or when you temporarily need everything proxied. Direct mode sends all traffic without going through a proxy at all.

You can switch between the three modes right from the client's main window, and changes take effect instantly with no restart needed.

SmartScreen flags open-source installers with low download counts or no commercial signing certificate, showing "Windows protected your PC." Click "More info," then "Run anyway" to continue installing.

This warning comes from Windows' download-reputation system and has nothing to do with the installer's actual content. If your browser blocks the file during download instead, choose "Keep" in your download history before running it.

Open System Settings → Privacy & Security, scroll down to find the notice about the blocked app, click "Open Anyway," and confirm with your password.

On first launch, the client will also ask for network extension and keychain access — allow both: the former lets it manage system proxy and TUN mode traffic, the latter stores local credentials. Denying either will break proxy functionality; you can re-grant them later in System Settings.

Copy the subscription URL from your provider, open the client's Subscriptions or Profiles page, choose "New → Import from URL," paste it, and confirm — the client will download the config and list the nodes automatically.

If you get a format error, double-check that the link is a Clash/mihomo-format subscription, not one meant for a different core. Once imported, pick a node on the Proxies page and turn on the system proxy toggle. For a step-by-step walkthrough with screenshots, see the setup guide.

The key one is the VPN connection request: the first time you tap Start, the system will prompt you to confirm a VPN connection — you must allow it, since Clash on Android relies on the system VpnService to intercept traffic.

It's also worth setting the client's battery policy to "Unrestricted" in system settings to prevent background kills from dropping the connection. Notification access is used to show status and traffic info in the notification bar and can be granted as needed.

Clash Plus is the top pick across the board, covering Windows, macOS, Android, and iOS (via the App Store). On desktop, Clash Verge Rev and FlClash are solid alternatives — both run on the mihomo core and are actively maintained; Android also has Clash Meta for Android.

Clash for Windows and ClashX Meta are no longer maintained and are kept on the download page only as archives — not recommended for new users. For a detailed side-by-side comparison, see the client comparison page.

TUN mode creates a virtual network adapter that intercepts all of a device's traffic at the network layer, regardless of whether an app respects the system proxy setting. Command-line tools, games, or other apps that ignore the system proxy can still be routed through the proxy with TUN mode.

Enabling it requires extra permissions: Windows usually needs the service mode installed first, and macOS requires approving a network extension. For everyday browser use, the system proxy is enough — you don't need to keep TUN on all the time.

In Rule mode, routing behavior is controlled by the rules section of your config file. Most subscriptions already include common direct/proxy rules; if you need custom behavior, add entries in the client's rules or override feature — for example, DOMAIN-SUFFIX,example.com,DIRECT sends that domain and all its subdomains directly, bypassing the proxy.

Rules are matched top to bottom and stop at the first match, so custom entries need to come before the general rules to take effect. See the glossary and protocol handbook for common rule syntax.

The client's latency test sends a single HTTP request through the node to a test URL and measures the round-trip time. The number reflects a combination of your current network, the node's load, and the test target — it's not a fixed property of the node itself.

A lower number usually means a faster response, but it doesn't mean higher bandwidth; a timeout means the node is unreachable right now. It's worth running a few tests during the time you actually plan to use it before settling on a go-to node.

Yes. Most clients let you set an update interval in the subscription's settings, automatically pulling the latest config on schedule — no need to manually track node or rule changes.

If your provider changes their subscription domain, auto-updates will start failing, and you'll need to get a new link from them and re-import it. The manual update option is usually in the subscription's right-click menu or detail page.

Desktop clients have a launch-at-startup toggle in Settings — it's worth pairing it with the silent-start option so it stays in the system tray without popping open a window.

On Windows, if you want TUN mode active right from boot, also enable service mode to skip the admin permission prompt on every startup. On Android, set the battery policy to unrestricted, so the system doesn't kill it after auto-launch.

Work through this checklist in order: first confirm the system proxy toggle is actually on, checking both the client's main window and your system network settings; run a latency test on the current node and switch nodes if it times out; check that you haven't accidentally switched to Direct mode; finally, clear your browser's DNS cache or try a different browser to rule out local cache issues.

Our technical notes have the full step-by-step checklist with details for each step.

If everything times out, it's probably not the nodes themselves. First turn off the proxy and check your raw network connection works fine; then check your system clock is accurate — some protocols are sensitive to time drift and will fail the handshake if it's off by even a few minutes; then manually update your subscription to rule out stale node data.

If it's still not working, try switching to another network, like your phone's hotspot, to check whether your current network is blocking the proxy ports. If everything still fails after ruling all this out, contact your provider to check the node status.

This usually comes down to three causes: an expired link, exceeded data quota, or an incompatible format. First open the subscription URL directly in your browser — a 404 or error page means the link has expired and you need a new one from your provider. If it downloads fine but the client fails to import it, it's likely not in Clash format — confirm your provider gave you a Clash/mihomo-specific link.

If the update succeeds but nodes disappear, this often means your plan's data quota is used up and the provider returned an empty config — log in to your provider's dashboard to check your usage.

The system proxy setting is only a suggestion — only apps that respect it (like browsers) will route through it; command-line tools and some desktop apps ignore it entirely. There are two fixes: set the http_proxy and https_proxy environment variables specifically for your terminal, or just turn on TUN mode to intercept everything at the network layer.

Also worth noting: Windows UWP Store apps block access to the local loopback address by default, so you'll need to enable loopback exemption before they can reach the local proxy port.

On Windows, first confirm service mode is installed and you've approved the UAC prompt; if you see a wintun-related error, try running as administrator again or reinstalling the client. On macOS, go to System Settings → General → Login Items & Extensions and allow the client's network extension.

Conflicts with virtual network adapters from other VPN or security software can also cause this to fail — close similar software and try again. If TUN starts successfully but you still have no internet, check whether the DNS section in your config is enabled, since TUN mode relies on the built-in DNS resolution in the config.