Clash Guide CLASH GUIDE · PRESS START
The path is mapped out: pick a platform, install the client, import a subscription, and switch on the proxy — four steps to go. Installers cover five major platforms, clients are open source, and tutorials plus troubleshooting are fully in English.
Scroll down to move through: core mechanics → five-platform download links → open-source background and kernel history → quick FAQ → latest guide articles. Each section stands on its own — no fixed order required.
▶Core Mechanics Guide
STAGE 02 / index.htmlPick a mechanic from the menu on the left; the panel on the right explains the problem it solves, where to configure it, and what to expect. Every mechanic works in any client listed on this site.
Rule Routing
Rule routing solves one problem: sending different sites through different exits. After loading a config, the kernel matches domains and IPs against the rules section top to bottom, applying the matching policy — common sites go direct, target sites go through the proxy, ad domains get blocked outright, with no overlap.
To see it in action, open the Connections tab in the client — every connection is tagged with the rule it matched. Unlike manually flipping a proxy switch, rule routing is configured once and keeps working, which is the core difference between Clash-based clients and traditional single-proxy tools.
TUN Mode
TUN mode solves one problem: catching apps that ignore the system proxy. Some games, CLI tools, and background services send traffic directly, bypassing system proxy settings — regular proxy mode can't reach them. With TUN enabled, the client creates a virtual network adapter; all traffic passes through it first and is then routed by the rules, giving process-level coverage.
The toggle lives in the client's Settings page under "TUN Mode." On Windows, the first activation asks for administrator rights; on macOS, you'll need to approve a system extension — just confirm the prompt. The system proxy is enough for everyday browsing; turn on TUN only when an app refuses to use it.
Rule · Global · Direct
Three outbound modes, matching the three paths on the hero sign. Rule mode matches traffic against the config's routing rules one by one and is the default day-to-day choice; global mode ignores every rule and routes all traffic through the currently selected node, useful for testing whether a specific site is reachable at all; direct mode sends all traffic without a proxy — the equivalent of pausing the client without quitting it.
All three modes can be switched with one click on the client's main screen, taking effect instantly with no restart needed. Suggested troubleshooting order: switch to global first to confirm the node works, then return to rule mode to check the rule syntax.
Subscriptions & Config Management
A subscription is essentially a config.yaml hosted remotely. Paste the subscription link into the client's config page, and it downloads and parses the node list, proxy groups, and rules; you can then set an auto-update interval so server-side changes sync down periodically.
The same client can store multiple configs and switch between them without overwriting anything. If you already have a local YAML file, you can import it directly. For what each field means, the blog has a field-by-field breakdown worth reading before you start editing.
Latency Testing & Auto-Select
Latency testing helps you quickly rule out unusable nodes in the list. Clicking test triggers an HTTP probe to each node and shows the round-trip time in milliseconds. Note: this number reflects response speed, not bandwidth, and doesn't guarantee long-term stability — weigh it against real-world experience when picking a node.
Proxy groups can be set to auto-select, automatically switching to the fastest node based on test results; paired with the Connections and Logs tabs, you can watch each connection's route and matched rule in real time — very handy for troubleshooting.
▶Choose Your Platform
STAGE 03 / download.htmlInstallers and recommended clients for all five platforms live on the download page — clicking any platform jumps straight to its section. The first card for every platform is Clash Plus, the top pick across the board; when in doubt, go with it.
Windows 10/11, 64-bit. Clash Plus is the top pick, with Clash Verge Rev and FlClash as alternatives — just click through the install wizard.
Go to DownloadInstallers come in Intel and Apple Silicon builds — check your chip before downloading, since the wrong architecture won't launch.
Go to DownloadInstall the APK directly; most devices should use the arm64 build. The first launch triggers a VPN connection request — just allow it.
Go to DownloadClash Plus is available on the App Store — install it directly there, and updates arrive automatically through the store.
Go to DownloadBoth a deb package and the raw kernel binary are available — desktop users should pick Verge Rev, while server setups can run mihomo directly.
Go to Download▶Open-Source Timeline
STAGE 04 / open-sourceEvery client and kernel listed here comes from a public repository with a traceable release history. Four sections cover where the project began, how the kernel evolved, what the client ecosystem looks like, and how versions on this site stay in sync.
Project Origins
Clash began as an open-source proxy kernel written in Go, establishing its place among similar tools through rule-based routing. After the original kernel repository stopped receiving updates, the community continued development on top of it, forming today's active fork ecosystem. Every download and tutorial on this site follows that continued open-source lineage.
Kernel Lineage
The de facto standard kernel today is mihomo, renamed from the Clash.Meta project. It stays compatible with the original config syntax while adding more proxy protocols and full TUN support. Nearly every mainstream client on the download page runs this kernel under the hood. A dedicated blog post compares feature differences across all three kernel generations.
Client Ecosystem
Around the kernel, the community maintains several graphical clients: Clash Verge Rev, FlClash, and Clash Nyanpasu each target different platforms and preferences, while Clash Plus covers both desktop and mobile and is listed on the App Store. Every client's code is publicly available, and release cadence follows each repository's own schedule.
Update Mechanism
Version numbers on the download page are read live from a version manifest on page load, staying in sync with upstream releases so you never have to check manually for outdated builds. Clients that are no longer maintained are clearly marked as archived to prevent installing an old version; for a deeper look at protocol and kernel differences, see the protocol breakdown page.
▶Quick FAQ
STAGE 05 / help.htmlOne-line answers to four common questions — full troubleshooting steps live in the Help Center.
▶Latest Guide Updates
STAGE 06 / blogThe three latest posts cover troubleshooting, advanced setups, and client comparisons — worth a read before you touch your config.