Guides / First-Time Setup

Import a Clash Subscription URL and Connect for the First Time

Start with a subscription URL you already have and complete setup in four steps. Use connection records to verify the result—“import successful” or “connected” alone is not enough.

Step 1: Import a Subscription

Copy a URL for your current client from your subscription provider’s account page. If the provider offers Clash, universal subscription, and individual-node options, choose the one labeled Clash or a format compatible with your client’s core. The account page URL in your browser is not the subscription URL, and copying node names alone won’t give you a configuration. Keep all query parameters when copying the URL; don’t edit or remove them. Subscription URLs may contain account credentials, so don’t post them in public comments, shared screenshots, or unfamiliar conversion tools.

Open the client’s “Profiles” or “Subscriptions” page and choose “New,” “Add,” or “Import from URL.” Some clients put the import button beside the URL field. Paste the full address into the URL field and give it a recognizable name, such as one based on its source or purpose. Save or import, then wait for the download and parsing to finish before leaving the page. When the new entry appears, check its name and update time. If an error is still displayed, resolve it before continuing—an entry in the list doesn’t mean the import succeeded.

Select the entry you just imported. In some clients, clicking it activates the profile; others require you to click “Use” or “Enable.” Make sure the selection indicator is on the new entry. Then open the Proxies page and check that nodes and proxy groups are visible. If the device already has an older subscription, verify the active profile name carefully: an old profile can show nodes too, so a populated node list doesn’t prove the new subscription is enabled. For your first setup, avoid editing YAML or adding multiple subscriptions at once. That makes it easier to match the rules and groups you see in the next step to their source.

If the import fails, read the error before deciding what to retry. For an invalid URL, copy it again from the provider’s page. For an authentication error, check that the subscription is still active and the URL hasn’t been reset. For a format or parsing error, check whether you used a universal subscription or account page by mistake, or whether the client core supports the returned fields. If the request times out, first confirm the device can reach other sites on the current network. If the error persists, use Troubleshooting to investigate the subscription error. Once the profile is confirmed as loaded, choose a mode.

Step 2: Choose a Proxy Mode

Go to the home, status, or Proxies page and find the mode menu with options such as Rule, Global, and Direct. For your first connection, choose Rule, sometimes shown as Rule. Rule mode evaluates requests in the order defined by the configuration; the first matching rule determines the outbound route. It doesn’t send every site through a proxy—traffic marked for direct access should remain direct. After switching modes, check the status bar to confirm Rule is still selected, then choose a proxy group. Otherwise, requests may use a different mode even if you selected a node.

The mode determines how requests are routed; the node selected in a proxy group determines where proxied traffic exits. Open the Proxies page and find the proxy group you want to use. Group names are set by the subscription provider. A group might be called “Node Selection” or have a name based on its purpose or region, so don’t identify it by its position in the list. If there are multiple groups, check the subscription instructions. If the client has a Rules page, you can also see which group a rule sends traffic to. Requests without a specific match may fall through to MATCH. So don’t just check that a node is selected in a group—make sure the request is routed to that group.

If the group allows manual selection, choose a node with an available test result and confirm the selection indicator moves to it. If you selected another proxy group, expand it to check the final selection. Choosing DIRECT sends traffic directly. If the client offers latency tests, test two or three candidate nodes. The result measures response time to the test target; it doesn’t indicate sustained download speed or guarantee access to a particular site. If the client automatically tests and selects nodes, leave that setting as is and verify the actual node in the connection records.

Global mode generally sends traffic handled by the client through the global policy, which can be useful for temporary comparisons while troubleshooting. Direct mode sends handled traffic straight out. Neither mode turns the system proxy or VPN on or off. For this setup, keep Rule selected, note the group name and current selection, then send test app traffic through the client.

Step 3: Start the Connection

Desktop: Enable the System Proxy

Find “System Proxy” on the client’s home or settings page and turn it on. If the client asks you to start its core first, wait until the status shows it’s running, then enable the switch. For an initial test, use a browser that follows the system proxy settings. Don’t enable TUN at the same time, change system DNS, or enter a local port manually. Start with just one traffic-routing method. If no test request appears, you can first check whether the app is ignoring the system proxy instead of troubleshooting several changes at once.

If another proxy app is running, quit it or turn off its system proxy so the current client can handle traffic on its own. Test with a browser that normally follows system proxy settings. If the browser has its own proxy settings or proxy extension, check that it isn’t forcing a direct connection or using another proxy. A tray icon or enabled switch only shows that the client tried to set the proxy; it doesn’t prove the app’s requests reached the client. Check the Connections page in the next step.

Mobile: Connect and Approve the System VPN Prompt

First, confirm the active subscription and selected node in the client. Then tap “Connect,” “Start,” or the power icon on the home screen. The first time the system asks to add a VPN configuration, check that the prompt is for the client you just opened, then approve it as instructed. Wait for the client to show connected, then check the VPN status in the system. Depending on the OS version, it may appear in notifications, Control Center, or system settings. If the client immediately returns to a disconnected state, check its error message instead of repeatedly approving the prompt.

If another app is using the VPN, disconnect it before starting the client. During testing, stay on the same network rather than switching between Wi-Fi and mobile data. Once connected, leave the client running and switch to your browser to make a new request. If the device has per-app routing, make sure the browser is included; otherwise, its activity may not appear in the connection records even when the VPN is active.

Step 4: Verify the Connection

Open the client’s Connections or Logs page, then return to your browser and visit a site you expect to access through a proxy. Make a new request rather than relying on a page that was already open: an existing connection, cached content, or a request the browser sent in advance can make a page look normal without generating a matching record. Note the hostname in the address bar and the time of the request, then check the client right away. If the page redirects to another domain or loads resources from several domains, find the specific request you want to verify rather than using an unrelated background connection.

When you find the record, check the destination domain, matched rule, proxy group, and final outbound route in that order. A request expected to use a proxy should go to the relevant proxy group and through one of its nodes. A request expected to connect directly should show DIRECT. Some clients show the full route only in “Connection Details”; ended connections may appear only in the logs. If the request did go through a proxy but the page won’t load, traffic has reached the client. Check the selected node or whether the site is reachable through it before reimporting the subscription.

Now test a destination that the current configuration should route directly. If the proxied and direct requests follow their expected routes and both pages load, your first connection is verified. A public IP lookup site can provide an additional check, but first confirm the lookup request itself goes through a proxy. If the rules send it direct, seeing your local IP is expected. Conversely, seeing a proxy IP on one lookup page only confirms that particular request used a proxy; it doesn’t mean every app on the device follows the same route.

If you can’t find the request, return to Start the Connection, check the traffic-routing method, and try again in the same app. If the request appears but takes the wrong route, return to Proxy Mode and Proxy Groups and check the mode and matching rule. If the route is correct but keeps timing out, change just one node in the same group and retry the same destination. Change one thing at a time to pinpoint whether the issue is traffic capture, routing, or the node. For further help with DNS, TUN, or mobile VPN disconnects in the background, see Troubleshooting.

Download the Latest Clash