Clash Subscription Import & Connection Guide

Step 1

Import the subscription and complete the first update

After opening the Clash client, go to the subscription or configuration management page. On desktop clients, the entry is usually in the left navigation; on Android, it is often near the current configuration name on the home screen. Look for “Add Subscription,” “New Configuration,” “Import from URL,” or a plus button to open the add screen. If both “Local File” and “Remote Link” are available, choose the remote link so the subscription can be updated directly from the provider later.

Enter an easy-to-recognize name, such as “Daily Subscription” or the provider name, in the name field, then paste the complete subscription link into the URL field. Check that no spaces were added at either end, especially when copying from a chat app, and make sure periods, parentheses, and explanatory text were not included. Click “Save,” “Import,” or “Add” when everything looks correct. Some clients download the configuration immediately; others create the subscription entry first and require one more click on the update button.

Keep the client in the foreground during the update and wait for the status to change from “Updating” to a success state. Normally, the subscription entry will show the configuration name and most recent update time, while the proxy page will display policy groups. Group names are determined by the provider and may refer to node selection, automatic selection, failover, or a specific purpose. There is no need to edit them individually; confirming that the page is no longer blank means the client has parsed the configuration.

After the subscription downloads successfully, select it as the current configuration. Some clients activate the latest imported configuration automatically, while others keep the previous one active. If this step is skipped, the proxy groups shown later may still come from the old subscription. Check the current configuration name, update time, or proxy group names to confirm the switch.

Set a suitable automatic update interval

After importing the subscription, find the automatic update option in the entry settings. Daily use does not require frequent refreshes, so choose an hourly interval offered by the client. Updating at startup can work well when switching devices often or when subscription content changes frequently. If the subscription service is occasionally unreachable, a failed startup update does not immediately invalidate the existing configuration; clients usually retain the last successfully downloaded content.

At this point, the client should show the current configuration and at least one selectable proxy strategy. Do not enable every network option yet. First choose a proxy mode so the client knows which requests should go through the proxy.

Step 3

Enable the system proxy and establish the connection

Return to the client home screen or settings page and enable “System Proxy,” “System Proxy,” or a similar toggle. This directs applications that support system proxy settings to Clash’s local listening port. Most desktop browsers read the system proxy, so use it for the first verification instead of enabling TUN immediately.

Watch the client status after enabling it. Normally, the core shows that it is running, the system proxy remains enabled, and the log does not repeatedly report a port conflict or permission error. If the toggle turns off immediately, fully quit other proxy programs and restart the client. When another process occupies the port, Clash cannot listen properly; a selected subscription and strategy will not create a usable connection on their own.

Android and iOS clients usually capture traffic through the system VPN interface. On first launch, the system displays a connection permission prompt; after approval, a VPN indicator appears in the status bar. This permission only allows the client to create a local network tunnel. Actual traffic routing is still determined by the current Clash configuration and proxy mode. If permission is denied, the client may retain its configuration, but requests from other applications will not enter the proxy path.

When to Enable TUN Mode

If the browser works normally but a desktop application, game launcher, or command-line program consistently bypasses the proxy, consider enabling TUN. The first time TUN is enabled on a desktop system, the client may request administrator access, install a service, or create a virtual network adapter. Follow the client’s prompts, wait for the interface to come up, and reopen the application you want to test.

Do not change TUN, DNS, ports, and rules simultaneously before completing basic verification. Changing several options at once makes the source of a failure difficult to identify. If enabling TUN disconnects the entire device, turn TUN off first and confirm that the system proxy path still works, then check permissions, DNS interception, and routing settings. For a fuller explanation of TUN behavior and DNS configuration, see the TUN section of the user manual.

Once the connection toggle remains stable, keep the client running and move to the final step. Do not rely only on an “Connected” label, which usually means merely that the local core has started. A working setup also requires confirming that browser requests enter the client, match the expected rules, and receive a normal response.