There Are Really Only Three Steps

A lot of people assume Clash setup is complicated the first time around, but the core process really is just three steps: download and install the client, import a subscription link, and enable the system proxy. Everything else — rule matching, node latency testing — is handled automatically by the client; you don't need to write any config files by hand. Let's walk through it in order.

Before you start, confirm two things — it'll save you a lot of wasted effort. First, make sure you actually have a valid subscription link. This is usually provided by your proxy service after you purchase or sign up, and it takes the form of a URL starting with http or https; if all you have is a pile of scattered node details with no subscription link, your provider is using a different distribution method, and you'll need to contact them to find out how to get one. Second, confirm your device's OS version meets the client's minimum requirement — an OS that's too old may not be able to install the latest client version, in which case the download page usually offers an older release compatible with legacy systems.

Step 1: Download the Client for Your Platform

Clash covers five platforms — Windows, macOS, Android, iOS, and Linux — so which version you install depends on the device you're using. Head to the download page and pick your system; it lists the matching installer and system requirements.

Step 2: Get Your Subscription Link and Import It

A subscription link is a URL your proxy service gives you. Open the client's "Config / Profiles" page, paste the link in, and click download — the node list and routing rules will import automatically, with no need to manually edit any files.

If what you have isn't a link but a config.yaml file instead, choosing "Import from file" on the same page works just as well — the only difference is it won't auto-update.

If you want to dig deeper into details like auto-updates and managing multiple subscriptions, check out the subscription import section of the full setup guide.

Step 3: Enable the System Proxy

Once your subscription is imported, the client defaults to "Rule mode" — mainland China sites connect direct, everything else routes through the proxy, and ad domains get blocked, all decided automatically. You just need to flip on the system proxy toggle. Its location varies by platform (right-click the tray icon on Windows, or check the menu bar icon on macOS) — see how to enable it on each platform for details.

Once it's on, open any webpage in your browser to test it — if it loads normally, your setup is working.

The Three Most Common Beginner Errors

1. Shows 0 Nodes After Importing the Subscription

The most common cause is accidentally copying leading/trailing spaces or a line break along with the link — re-copying and pasting it usually fixes this. Another possibility is that the subscription URL itself requires network access that your current connection can't reach — in that case, use your phone's mobile data hotspot for the first import, and after that you'll be able to update normally through your own proxy.

2. Proxy Is On, But the Page Still Shows My Local IP

First check that the connection status in the bottom-left of the client says "Connected" rather than "Not connected." If the status looks fine but your IP hasn't changed, check whether your browser has an extension that overrides system proxy settings (for example, some extensions with a built-in VPN feature of their own) — temporarily disable it and test again.

3. An App I Installed Isn't Going Through the Proxy at All

The system proxy only affects apps that respect system proxy settings — some command-line tools and game clients don't read that setting at all. In that case, you'll need to enable "TUN mode," which lets the client take over all traffic directly at the network layer. This is a slightly more advanced feature — see the explanation of TUN mode in the glossary and the corresponding steps on the setup guide for how to turn it on.

Two Quick Things to Do Right After Setup

Once your connection test passes, spend two minutes on these two things to save yourself a lot of repeated troubleshooting later. First, set the client to launch at startup — most clients have a toggle for this in settings, and once it's on it'll connect automatically every time you boot up, no manual clicking required. Second, check whether the subscription's auto-update interval makes sense — it's usually set to once a day by default, and if your provider's nodes change frequently, you can shorten that interval to make sure you're always working with the latest node list.

Final Thoughts

Getting it installed and connected is just the first step — where Clash really shines is in custom rules and node management down the line. If everything works after these three steps, congratulations, you've already finished 90% of the setup; if you get stuck along the way, this site's FAQ page and full setup guide cover more detailed troubleshooting. Once you're comfortable with the basics, take a look at how routing rules actually work — that's where you'll find Clash's real power is just getting started.