Setup Guide · About 10 Minutes
Clash Setup Guide: From Subscription Import to Connection Verification
The whole setup boils down to four steps: import your subscription → choose a proxy mode → connect to a node → verify it's working. Windows, macOS, Linux, Android, and iOS all follow this same path — any interface differences are called out along the way.
Before You Start
One client, one subscription link — get both ready before you begin
First, grab a client. If you haven't installed one yet, head to the client downloads page and pick the version for your system: Clash Plus is the top pick for Windows and macOS, with Clash Verge Rev as a solid alternative; Clash Meta for Android is recommended on Android; on iOS, install Clash Plus from the App Store. Installation is the usual next-next-finish process — once it's done, open the app and leave it on the main screen.
Next, get your subscription link. It's a URL starting with http, provided by your node/proxy service in their dashboard — usually under a menu labeled "Subscription," "One-Click Subscribe," or "Copy Subscription URL." This single link bundles the node list, proxy groups, and routing rules — once your client has it, you're set with a full configuration, no manual server details required.
Interface Differences Between Clients
Button placement varies slightly between clients, but the page layout is largely consistent: the page for managing subscriptions is called "Profiles" or "Subscription"; the page for managing nodes is called "Proxies"; the master toggle is usually labeled "System Proxy" or shown as a big button on the home screen. This guide uses Clash Verge Rev (desktop), Clash Meta for Android (Android), and Clash Plus (iOS) as references — if you're using a different client, just look for the equivalent section by name; the steps are the same.
Import Your Subscription
Turn one URL into a full list of nodes inside your client
Open your client and find the profile management page. In Clash Verge Rev, click "Profiles" in the left sidebar; in Clash Meta for Android, tap the second tab at the bottom, "Profile"; in Clash Plus, go to the "Profile" tab and tap the plus icon in the top-right corner. This page has one job: telling the client where to get its configuration.
Paste the full subscription link into the address field — don't miss a single character from start to end, and don't leave any spaces before or after (a long-press to select all is the safest way to copy it). Give it a name you'll recognize at a glance, such as your provider's name, then confirm. The client will immediately fetch from that URL and pull in the nodes, proxy groups, and rules in one go, saving them as a profile card.
Success looks like this: a new profile card appears in the list, showing the node count and last update time. Next, set it as the active profile — in Verge, click the card to highlight it; on Android, tap the profile name directly; in Clash Plus, it's enabled automatically once added. Switch to the "Proxies" tab and you should see a row of node names — that means the import is complete.
Import failures usually come down to three causes: extra spaces or a truncated link from copying; an expired subscription, which means going back to your provider's dashboard to copy a fresh link; or a network that can't reach the subscription URL, in which case try a different network. For a more detailed breakdown, see the subscription section of the Troubleshooting page.
Your Subscription Link Is Your Access Key
Whoever has this URL can use your traffic. Never paste it into group chats, forums, or public screenshots. If you suspect it's been leaked, reset the subscription link in your provider's dashboard and update the URL in your client.
Choose a Proxy Mode
Rule, Global, Direct — understand the three modes before you switch
The mode determines which traffic goes through the proxy — there are three options. Rule mode routes traffic based on the rule set bundled with your profile: traffic that should go through the proxy does, and everything else connects directly. This is the default for everyday use. Global mode forces all traffic through the proxy unconditionally — turn this on temporarily only for troubleshooting or when a specific service needs to be proxied at all times. Direct mode sends everything through your regular connection, effectively pausing the proxy — mainly useful for comparison testing.
The toggle is easy to find. In Verge, it's at the top of the "Proxies" page or in Settings; in Clash Meta for Android, it's in the dropdown on the home screen; in Clash Plus, tap the mode selector on the home screen. Switching takes effect immediately — no restart needed, and you can switch back anytime.
Where do the rules come from? Your subscription already includes a ready-to-use rule set covering common services, so there's nothing to fill in manually as a beginner. If you want to understand rule syntax, GEOIP, MATCH, and similar terms, check the "Rules & Routing" section of the glossary for a full breakdown. For more advanced setups like TUN mode, which takes over all system traffic, there's a dedicated guide on the blog. Finish these four steps first — those topics can wait.
Connect to a Node
Pick a node, flip a switch — that's all it takes to get running
Open the "Proxies" page and start by identifying the proxy group — common names include PROXY, Node Select, and Auto Select. A proxy group is a slot holding several nodes; the client decides which one to use based on the group's strategy. As a beginner, you only need to touch the manual-select type group like "Node Select" — leave everything else at its default. For exact definitions of terms like proxy group, node, and latency, check the glossary anytime you're unsure.
Tap the latency test button — usually shown as a lightning bolt icon — and wait a few seconds. A latency number in milliseconds will appear next to each node; lower means faster response. Nodes showing a timeout are temporarily unavailable — just skip them. Pick a node with low latency, or simply switch the proxy group to "Auto Select" and let the client choose based on latency automatically. Test results only reflect the current moment, so re-testing every few days gives a more accurate picture.
Now flip the master switch. Desktop: in Verge, turn on "System Proxy" on the home screen — the toggle lights up once active. Android: go back to the home screen and tap the big start button; the first time, you'll get a VPN connection prompt — tap "OK" to grant permission. iOS: in Clash Plus, turn on the main toggle, which also triggers a one-time system VPN authorization prompt. This authorization is a system-level action asked only once per client — it won't interrupt you again on future launches.
Signs of a successful connection: the toggle lights up, a VPN key icon appears in the status bar on mobile, and the traffic stats on the client's home screen start ticking up. At this point, traffic that should go through the proxy already is.
Verify It's Working
Check your outbound IP once, compare it a second time, and confirm the traffic route
The most direct way to verify: open any IP lookup site in your browser and check the outbound IP and location shown. If it matches the node's region, the proxy is working; if it still shows your local ISP's address, traffic isn't going through the proxy — go back to step three and check the toggle.
If you're not sure, use the comparison method. Turn off the system proxy toggle and refresh the lookup page — the IP should revert to your local address. Turn the toggle back on and refresh again — it should switch back to the node's region. Getting different results each time confirms the proxy is actually doing something, rather than the lookup page just showing a cached result.
If you're comfortable with the command line, you can verify it there too. Send a request to an IP lookup API to check the outbound address; to explicitly route through the proxy, add the -x flag with your local proxy port — Clash-based clients default to a mixed port of 7890:
curl ipinfo.io
curl -x http://127.0.0.1:7890 ipinfo.ioIf both commands return the same result, the system proxy and the manually specified route are going through the same path. If it's still not working, don't rush to reinstall — the most common cause is a standalone proxy extension in your browser overriding the system proxy; another common one is that terminal tools don't read the system proxy by default and need to be pointed at it manually. For a full troubleshooting walkthrough organized by symptom, see the Troubleshooting page — it has dedicated sections for system proxy not working, node timeouts, and DNS issues, and following them should help you pinpoint the problem.
Quick Answers
Frequently Asked Questions
The four questions people get stuck on most often during setup — a quick answer here, with links to full details where it matters.
Where do I get a subscription link?
Subscription links are provided by node/proxy services — the client itself doesn't come with any nodes built in. Once you've picked a provider, log into their dashboard, find the subscription section, copy the URL, and come back to step one on this page to import it. The client just runs whatever configuration it's given; where the nodes come from is entirely up to the subscription.
What's the difference between System Proxy and TUN mode?
System Proxy only affects apps that read the system's proxy settings — browsers and most software fall into this category, and it's enough for most beginners. TUN mode creates a virtual network adapter that intercepts all traffic, including apps that ignore the system proxy setting. If you need that, see the guide to enabling TUN mode.
What's a normal latency for a node?
Somewhere from a few dozen to over a hundred milliseconds is normal for a node in the same region, and 200–300ms is common for cross-continent connections. Latency isn't the only thing that matters — stability counts just as much: a node with high packet loss is still frustrating to use even with low latency. If tests time out or the connection keeps dropping, try a different node first, then check the node timeout section of the Troubleshooting page.
Will my setup carry over to a new device?
Your configuration lives on the local client, not tied to any account. When you switch to a new device, just import the same subscription link again, and your nodes and rules will be right back — each device works independently of the others.
What's Next
Where to Go After Setup
Once you've finished all four steps, everyday use should be smooth sailing. Here's what else is on hand if you need it.