Clash Beginner FAQ: Core, Subscriptions, Nodes & Modes Explained

Almost everyone new to the Clash ecosystem gets stuck on the same batch of questions: whether these similarly named pieces of software are actually the same thing, where to find a subscription link, which client to pick out of so many options, and what really separates Rule mode from Global mode. This article groups the ten most frequent questions by topic and gives a concise answer to each, so you can go straight into configuring things afterward instead of piecing together information from a dozen different sources.

Three Basic Concept Questions

1. Are Clash and mihomo the same piece of software?

Not exactly. Clash started out as an open-source proxy core project. After the original repository stopped receiving updates, the community forked it into an enhanced version, and that fork was later renamed mihomo (it was also known as Clash Meta for a while). Today, the vast majority of actively maintained clients run on the mihomo core underneath, just with different front-end interfaces. "Clash" now mostly refers to the whole protocol and ecosystem rather than one specific executable.

2. Where do I get a subscription link?

Subscription links are generated by proxy service providers and take the form of a URL containing your account information. Paste it into the client's subscription field and every node under that account is imported at once. The client itself doesn't provide or sell nodes — it only handles parsing the subscription, routing traffic according to rules, and displaying latency, purely technical functions. When choosing a provider, prioritize one that supports the standard Clash/mihomo format, so you don't end up with an incompatible proprietary format that fails to import.

3. There are so many Clash clients — which one should a beginner pick?

If you just want something stable and consistent across platforms, Clash Verge Rev is currently one of the more actively maintained graphical clients, supporting Rule/Global/TUN mode switching with a configuration interface that's more intuitive than earlier clients. macOS users might also consider ClashX Meta; on Android, FlClash and Clash for Android are both common choices. You can check specific versions and download links by platform on the download page.

Four Usage and Configuration Questions

4. What's the difference between Rule mode and Global mode?

In Rule mode, the client matches domains or IPs against the rules listed in the config file one by one, and whichever rule matches decides whether that traffic goes direct or through a specific proxy node — sites in mainland China can stay on a direct connection while only the traffic that needs it goes abroad. Global mode ignores the rules entirely and routes all traffic through whichever node is currently selected. It's useful for temporarily checking whether the rules are actually taking effect, or confirming whether a given node works at all, but it's not recommended for everyday use, since accessing local sites also gets routed through the proxy, which hurts both speed and experience.

5. What do the colors of the client icon and status dot mean?

The exact styling varies a bit by client, but the general logic is consistent: a highlighted icon or a green status dot means the proxy is currently connected and active; gray or an "off" state means the proxy is disabled and traffic is going through the device's original network; if the status dot turns yellow or red, it usually signals a node connection failure, an expired subscription, or a rule-matching problem — open the log panel to see the exact error.

6. What is TUN mode, and should I turn it on?

TUN mode (sometimes labeled virtual adapter mode in a client) creates a virtual network adapter at the system level and takes over almost all outbound traffic on the device, which covers far more ground than the default system proxy mode — especially useful for apps or games that ignore system proxy settings. The tradeoff is that it needs higher system privileges (usually admin rights on Windows, and a network extension or authorization on macOS/Linux), and the setup is slightly more involved. Beginners should get everything working with the default system proxy mode first, then try enabling TUN once they've confirmed the proxy itself works.

7. How should I read the latency number next to each node, and which node should I choose?

The latency number is the round-trip time the client measures when it pings a node, in milliseconds — a smaller number generally means a faster connection and a smoother experience. But low latency doesn't guarantee fast actual downloads; a node's real-world performance also depends on bandwidth, concurrent load, and the location of the destination server. For everyday use, favor nodes with latency reliably under two or three hundred milliseconds, and if a specific site feels sluggish, manually switch to another node in the same group and compare.

Two Troubleshooting Questions

8. The subscription update fails when I click it — what now?

First check whether the subscription link itself is still valid; your provider's dashboard usually shows the expiration date and remaining data, and either running out will cause the update to fail. Next, check whether your local network can reach the subscription link's domain directly — if that domain itself is blocked, the client naturally can't fetch the latest content without a proxy already running, in which case turning on the "update subscription via proxy" option in the client works around the restriction. Finally, keep in mind that a small number of providers occasionally change their subscription format, which older client versions may fail to parse; updating to the latest client version usually fixes this.

9. The proxy is on but I still can't reach certain sites, or the rules don't seem to be taking effect?

First confirm the client's status indicator actually shows "Connected" rather than idle, then check whether you're currently in Global mode — under Global mode every site goes through the same node, so if that node itself is down, nothing will load. In Rule mode, if a site that should go through the proxy is going direct instead, it's most likely because the rule order or matching conditions aren't precise enough; open the log panel to see exactly which rule that request actually matched, then adjust the DOMAIN-SUFFIX or GEOIP entries accordingly.

One Advanced Follow-Up Question

10. Is it worth learning to write config files by hand?

If you're only using a subscription from a provider, most of the routing rules and policy groups have already been written for you, so day-to-day use doesn't require touching the config file at all. But if you want finer-grained customization — grouping streaming services separately, blocking specific ad domains, or understanding the matching order and priority of rules — it's worth spending some time learning the core fields like proxy-groups, rules, and rule-providers. That way, whenever a subscription's rules don't quite fit your needs, you can adjust them yourself instead of relying entirely on the provider.

Suggested Order for Getting Started

If this is your first time in the Clash ecosystem, following this order will save you a lot of back-and-forth:

1. Download and install a mainstream client first — don't worry about which one has the most features, getting it running is what matters.
2. Once you have a subscription link, test it in Rule mode first, confirming that local sites connect directly and target sites route through the proxy correctly.
3. Check whether the latency numbers actually match how fast pages load, and pick one or two stable nodes to use regularly.
4. Only try enabling TUN mode once you need to cover more app traffic, and grant permissions as the client prompts you.
5. Set the subscription update interval to something reasonable (once a day, for example) so stale node info doesn't cause connection failures.

Once you've worked through this flow, most beginner-level confusion tends to resolve itself, and you can just look up the relevant section above whenever a specific error comes up later.