FAQ

In common parlance, "Clash" often refers to an ecosystem of clients **compatible with Clash configuration formats and rule concepts**. Specific software is usually **independently developed open-source GUI**, with cores like Mihomo (Clash Meta). Our download page lists mainstream maintained packages; names and versions are based on respective release notes.

Prioritize recommended items on the Download Page: **Windows / macOS** users typically use Clash Verge Rev, **Android** users use FlClash. **iOS** is available via App Store only (mostly paid), requiring a non-mainland Apple ID. Ensure the architecture (x64, ARM64, etc.) matches your device.

Menu names vary; typically look for "Configuration / Subscription / Profiles" to add a new subscription URL, save, and then **Update / Pull**. If it fails: first check if the link is complete or requires a specific User-Agent; then try switching networks or changing nodes as suggested in client logs. If still failing, verify subscription status with **your configuration source provider**. This site does not provide subscriptions.

**Rule**: Determines whether each connection uses proxy or direct based on configuration rules; suitable for most scenarios. **Direct**: Bypasses the proxy node. **Global**: Typically routes all traffic through a selected proxy exit regardless of rules (behavior varies by client and config). **System Proxy**: Directs apps that respect system settings to use the client's local proxy port.

For more detailed explanations and diagrams, see Tutorial · Modes & Advanced.

TUN incorporates more application traffic into the client's scheduling through a virtual network card, suitable for programs that do not follow system proxy settings or scenarios requiring global monitoring of listening ports. It is not mandatory for everyone: most users should first stabilize their experience with System Proxy + Rules. Before enabling, please read your client's documentation regarding TUN, as it may require additional permissions or drivers. See Tutorial · TUN for details.

A common reason is that split-tunneling rules or DNS are misleading local traffic to the proxy, or the DNS resolution path has become longer. Check if the "Local Domain Direct" rules in your configuration are effective and avoid keeping Global mode on for long periods. Refer to Tutorial · Slow Local Access.

First, check in the client if settings like DNS, fake-ip, or redir-host are correctly understood according to your configuration; reload the configuration and test again. Different clients handle DNS very differently; it's recommended to follow the official documentation for your specific version. For an overview, see Tutorial · DNS.

Due to platform policy restrictions, such applications are mostly provided in non-mainland App Stores as paid apps. This site does not provide IPA files or instructions for signed installations. Preparation steps for a US Apple ID can be found in Download Page · iOS.

Capabilities like virtual network cards and route-level management often require elevated permissions. Please authorize only in a trusted environment after carefully reading the client's prompts; if you only need proxies for browser-like apps, prioritize a non-TUN solution.

Suggested order: Check client logs and error codes → Confirm subscription is updated and clock is accurate → Try switching nodes and proxy modes → Finally, consider DNS/TUN/Firewall blocking. See Tutorial · Troubleshooting for detailed steps and cases.

Legacy versions may still work, but they no longer receive security or feature updates. It is recommended to migrate to a maintained client (e.g., Verge Rev) and re-verify your download source. The "Archived" section on our download page contains descriptions and access points for legacy versions.