First-Time Setup / Steps

Clash Setup Guide

Once you have a client and a compatible subscription URL or YAML file, follow these four steps in order. For your first test, use one app and one connection. After confirming the request uses the expected exit, adjust other settings as needed.

01 / Profile Setup

Import and Activate a Clash Subscription

Open the client and go to the Configuration or Subscriptions page. If you have a subscription URL, click New, Add, or the plus button, choose Import from URL or Remote Profile, paste the full URL, then click Save or Download. Wait until the profile name and update status appear before continuing. An account page URL or a link to a single shared node is not the same as a full subscription URL. If the provider offers multiple formats, choose one labeled Clash or compatible with your client's core. Don't truncate parameters after the question mark when copying the URL, and never share it in public screenshots or logs.

To import a local file, choose Import from File on the same page and select the actual .yaml or .yml file. On mobile, save it to your device's file manager first, then select it from the client. A file-imported profile is usually a separate copy; replacing the original file later won't update the copy in the client. Subscriptions can be refreshed, but check whether the latest update succeeded. Either method is fine—you don't need to import the same content both ways during initial setup.

After the import, check which profile card has the selected indicator. If the new profile isn't active yet, click its card or open the menu and choose Use or Set as Current. If there's an Apply button, click that too. Then open the Proxies page and make sure the proxy groups have loaded. Return to the profile page and confirm the newly imported profile is active. Some clients keep using the previous profile on startup, so seeing a new entry in the list doesn't mean the core has switched. If your existing profile works, keep it for now so you can switch back if needed.

If the import fails, first check whether the error is about downloading or parsing. A request timeout means no response arrived in time; check your network and make sure the URL is complete, then try updating again. A parse error means the response wasn't accepted as a valid profile. You may have received a login page or error page, or the client may not recognize some fields. Get a compatible file from the provider rather than deleting lines at random. If the error names a specific field, see the configuration field reference. Once the profile applies and the proxy groups open, move on to choosing a mode.

02 / Traffic Routing

Choose a Proxy Mode and Proxy Group Exit

On the Proxies page or home screen, find Mode and choose Rule (rule) for your first test. After switching, confirm that Rule mode is still selected. This setting determines how requests that reach the core are routed; it does not enable the system proxy. In Rule mode, requests are checked against the profile's rules in order. The first matching rule determines what happens next: direct connection, rejection, or routing through a proxy group. On the Rules page, pick a domain that's easy to test again and note the matching rule and its exit. Don't guess based on the site's region; the active profile and connection logs show what actually happens.

If the target is routed to a proxy group, find the matching group on the Proxies page. A select group is manual: open it and choose an available node, checking which item has the selected indicator. Some groups contain other groups rather than nodes. If so, follow the selection through until it ends at a proxy node or DIRECT. The core selects members of url-test and fallback groups according to their own testing or failover behavior; you don't need to change them manually for a first connection. Latency shown in the client reflects the probe conditions and doesn't replace checking an actual request later. For group types, see the glossary or proxy group fields.

The other two modes are useful for comparison. Global mode (global) doesn't route traffic by the usual rules, so check which proxy group is selected globally; if it's DIRECT, requests still connect directly. Direct mode (direct) sends requests that reach the core without using a proxy node, but it doesn't turn off the system proxy or bypass the client. If a target uses the wrong exit in Rule mode, briefly compare it in Global mode with a clearly selected node, then switch back to Rule mode. Keep the existing rules during initial setup; there's no need to edit the YAML just to test.

03 / System Integration

Enable the System Proxy or VPN

On desktop, return to the home screen and check whether the core is running. If there's a separate start button, click Start and wait for the status to stabilize, then enable System Proxy. If the client has no such toggle—as with some Linux clients that only provide a local listener—open your desktop environment's network proxy settings and enter the proxy type, address, and port shown in the client. Don't assume a commonly used port from a guide is the one configured on your system. If your browser has its own proxy settings, make sure it uses the system settings. A regular browser is enough for the first test; there's no need to enable TUN at the same time. Some apps ignore the system proxy, and existing connections may not switch immediately, so restart the test app if needed.

On mobile, return to the client's home screen and tap Connect or turn on the connection toggle. The first time, the system will usually ask to create a VPN configuration or allow the connection. Make sure the prompt comes from the client you just used, then approve it. Return to the home screen and confirm the status stays at Connected. You can also check the active app in your system's VPN settings. If the toggle quickly switches off, check whether you dismissed the permission prompt, another VPN is already using the connection, or the profile failed to start. Fix the issue before trying again; repeatedly tapping Connect won't resolve it.

If web pages stop loading as soon as you enable the system proxy on desktop, turn it off to restore your previous network settings, then check the client's startup logs. If the local port is already in use, see whether another client is listening on the same port. A browser connection will also fail if the system proxy points to a different port than the one the client is actually listening on. Fix any core startup or address mismatch before enabling the proxy again. Once the toggle stays on and an app can send new requests, check the Connections page. A normal status only means the proxy is enabled; it doesn't prove the target is using a proxy node.

04 / Verify Results

Check Rules and Traffic Routing in Connection Logs

Open the client's Connections page, then visit the target you noted in step two. Try to send a new request: close the existing tab and open the site in a new window. If you still see cached content, reload and check the request time. If the client supports filtering, search by the target domain. A page may also request images, scripts, and other domains, so start with the entry for the main page. Some clients show only active connections, and short requests may disappear quickly; watch the log as you refresh or use the client's connection log if available. Don't use an old entry to judge whether your latest change worked.

Once you find the matching entry, check Rule or Match first, then Proxy Chain or Exit. If the test target should use a proxy, confirm that the rule points to the expected group and that the chain ends at a proxy node, not DIRECT. If the rule calls for a direct connection, seeing DIRECT is expected and doesn't mean the proxy is broken. For comparison, test a site that's expected to connect directly and is normally accessible. If you use a public IP lookup service, first confirm that the lookup request itself matched the expected rule. Its result shows the exit for that request only, not for other sites or every app.

If there's no matching entry, first check whether the request reached the client. On desktop, verify the system proxy and the browser's own proxy settings. On mobile, check that the active VPN belongs to this client and that per-app settings aren't excluding the test app. If an entry exists but matched a different rule, check the mode, active profile, and rule order; see rule syntax and matching order if needed. If the rule and exit are correct but the request times out, try another available node in the same manual group without changing the test target. Change one thing at a time to tell whether the issue is with system integration, rules, or the exit.

Initial setup is complete when the test request succeeds and the log shows the expected rule and exit. Note the profile name, selected mode, and manual group choice so you can repeat the same test after updating the subscription. If you're only trying the client temporarily, restore any system proxy settings you changed on desktop before closing it. On mobile, tap Disconnect in the client and confirm the system VPN is no longer active. For DNS or listener port issues, see DNS fields and mixed proxy port; these don't need to be part of your initial connection setup.