Estimated time: 10 minutes

Clash Quick Start Setup

Complete the initial setup in this order: “Import subscription → Choose a proxy mode → Establish a connection → Verify the result.” Confirm each step before moving on so problems are easier to pinpoint.

Download Clash View the YAML Manual

Four-Step Guide

Start with step one. Use the guide to return to the current step; skipping configuration checks is not recommended.

CONFIGURATION

Import a Clash Subscription

After launching the client, find the page used to manage configuration files. Depending on the client, it may be called “Configuration,” “Subscription,” “Profiles,” or “Config Files.” This page typically lists local configurations, remote subscriptions, and their latest update times. An empty list on first launch is normal; use the subscription URL from your service provider to create a remote configuration.

Copy the subscription URL from your service provider’s user panel using its dedicated copy button so you do not miss parameters at the end of the address. Return to the client and click “New Subscription,” “Import from URL,” or a similar option, then paste the complete URL. Use a recognizable name such as “Daily subscription” or the service name, or keep the automatically generated name. Click “Import,” “Download,” or “Save” to confirm.

The client will request the remote configuration. Normally, a new entry appears within a few seconds with an update time, configuration name, or traffic information. Do not enable the system proxy immediately. First click the new entry and set it as the active configuration. Some clients select it automatically after import, but it is still worth checking that the selection marker is on the newly imported item.

After selecting the configuration, open the “Proxy” or “Proxies” page. If you see policy groups and several nodes, the configuration was parsed correctly. Group names come from the subscription and may include “Node Select,” “Auto Select,” “Failover,” “Global Media,” or “Final.” Exact names vary; what matters is that the page is not blank and does not show only the basic DIRECT and REJECT actions.

If no nodes appear after import, return to the configuration page and run “Update” once. If the list is still empty, open the subscription URL directly in a browser to confirm that the current network can reach it, then check the service status and subscription expiry. If the browser shows a login page, error, or blank response, the problem is usually with the subscription source rather than the client button. Avoid creating multiple copies of the same configuration, or you may select the wrong one later.

Completion Criteria

A new subscription appears in the configuration list, it is set as the active configuration, and the proxy page shows policy groups and nodes. Once all three conditions are met, continue to proxy mode selection. If the client reports a YAML syntax error or incompatible fields, see the YAML Manual for configuration structure, field hierarchy, and rule syntax; complex configuration edits are outside the scope of this page.

Ready: Configuration loaded Next: Choose a proxy mode →

ROUTING MODE

Choose a Proxy Mode and Node

After loading the subscription, decide how traffic should be handled. Open the client’s “Mode,” “Routing Mode,” or similar setting. You will usually find Rule, Global, and Direct modes. For initial setup, choose “Rule.” This mode reads the rules in the configuration and decides whether to use a proxy node, connect directly, or reject a request based on the domain, IP, process, or other conditions.

Rule mode works well for everyday use because local services, sites that should connect directly, and destinations requiring a proxy can use different paths. Global mode sends most connections through one proxy policy and is useful for temporarily checking whether a problem is caused by rule matching, but it should not be left enabled long-term without understanding the configuration. Direct mode bypasses proxy nodes and is useful for pausing proxying or running comparison tests.

Mode Traffic Handling Best For
Rule Choose proxy, direct, or reject separately according to the configuration rules Everyday browsing, split tunneling, and regular use
Global Send most traffic through the selected proxy policy Temporarily testing node connectivity or ruling out a policy problem
Direct Connect without using a proxy node Pausing the proxy or comparing results with and without proxying

Once the mode is set, open the proxy policy page. Find the main policy group that provides the default route, then expand the node list. Do not judge speed from the node name alone; names usually indicate only a region or route label, not actual quality on your network. If the client has a latency test, run URL Test once. The result can rule out clearly unreachable nodes, but lower latency does not necessarily mean faster downloads.

After selecting an available node, check whether the policy group’s current value updates accordingly. Some subscriptions offer an “Auto Select” group that switches nodes based on a configured test URL and interval; others require manual node selection. For the first test, choose one clearly named node to reduce interference from automatic changes. Once the connection works, try auto selection, failover, or load-balancing policies.

If every node times out, do not change the port, DNS, or rule file immediately. Return to the subscription page, update the configuration once, then test another node. Universal failure may be caused by network restrictions, service maintenance, or an incorrect device clock. First determine whether all nodes are affected before moving to deeper network troubleshooting.

Completion Criteria

The mode shows “Rule,” the main policy group has an available node selected, and no persistent configuration errors appear. Routing selection is complete, but applications on the system may not yet be sending traffic through Clash. The next step is to enable the appropriate traffic interception switch.

← Back: Import subscription Next: Enable connection →

CONNECTION

Enable the System Proxy and Connect

After configuring the client and selecting a node, return to the home or settings page and find “System Proxy,” “Set as system proxy,” or a similar switch. Enabling it writes the proxy address to the operating system’s network settings, allowing browsers and desktop apps that follow the system proxy to send requests to Clash’s local listening port.

Windows clients usually provide a direct system proxy switch, and the local address can then be seen in the system proxy settings. macOS may ask for permission to modify network configuration; when a confirmation dialog appears, verify that the request comes from the client you are using. Android commonly intercepts traffic through a local VPN interface and shows a system-level authorization dialog on the first connection. iOS clients likewise request permission to add a VPN configuration; after confirmation, the status bar or Control Center shows the connection status.

After enabling the switch, wait for the client status to change from “Stopped” or “Disconnected” to “Running,” “Connected,” or a similar state. Keep the client running in the background and do not terminate its process immediately. On desktop systems, closing the window may leave the client in the system tray or menu bar; choosing “Quit” from that menu may stop the system proxy, depending on the client settings.

Use the system proxy for basic scenarios first. TUN mode uses a virtual network interface to intercept more programs that do not read system proxy settings, and it also involves administrator permissions, routing tables, and DNS handling. It can help with game launchers, command-line tools, or broader traffic coverage, but it is not required for a first connection. Confirm that the system proxy works before deciding whether TUN is needed, so subscription, node, and network issues do not get mixed together.

If the system proxy switch turns off immediately, check that the client has sufficient permissions, that its port is not already in use, and that another proxy tool is not running. Multiple system proxy managers can repeatedly overwrite the operating system’s proxy address. During troubleshooting, quit other proxy clients, restart the current client, and enable the system proxy again.

If the switch stays on but no websites open, turn off the system proxy first and confirm that ordinary network access returns. Then restart the client, choose another node, and test again. Do not repeatedly edit rules while the underlying network is already offline. Basic connectivity, the configuration, the proxy node, and the system proxy are four consecutive links; check them in order to keep the failure scope from expanding.

Completion Criteria

The client is running, the system proxy or mobile VPN interception is enabled, and the current node remains selected. Establishing a connection only confirms that the traffic entry point is ready; use the target page and the client’s connection log to confirm that requests actually follow the expected policy.

← Back: Choose a proxy mode Next: Verify that it works →

VERIFICATION

Verify That the Clash Proxy Works

Open a new browser window and visit a site that previously required a proxy. Do not rely only on the client’s connection button, because an enabled button does not prove that the target request was forwarded successfully. A fully loaded page is the first signal; the matching domain in the client connection list is the second; a connection entry showing the matched rule and policy group is the third.

Switch back to the client and open “Connections,” “Logs,” or a similar page. Refresh the webpage you just visited and look for a new domain entry. Records typically show the target host, connection type, upload and download traffic, matched rule, and policy used. If the target domain went through the selected policy group and node, the system proxy, rule matching, and node forwarding are working together.

Next, visit a commonly used local site and check the connection log again. In Rule mode, it may show DIRECT, meaning the request connected directly according to the configuration. This does not mean the proxy failed; it is the expected result of split-routing rules. To assess Rule mode, do not expect every request to use a proxy node. Check whether different destinations enter the policies defined by the configuration.

You can also compare Direct and Rule modes. Keep Rule mode enabled, visit the target site, and record the result. Then temporarily switch to Direct mode and reload the page. If Rule mode works but Direct mode fails, the proxy path is probably active. Switch back to Rule mode when finished so later applications do not bypass the proxy.

If the page will not open but the connection list shows the request, traffic has reached the client and the problem is more likely related to the node, remote connection, DNS, or rule action. If the connection list shows no new entry at all, first check whether the system proxy is enabled, whether the browser uses its own proxy settings, and whether the target application follows the system proxy. This distinction is more effective than repeatedly changing nodes.

After verification, you do not need to remain on the log page. Keep the current configuration, Rule mode, and an available node for everyday use. When the subscription service updates its nodes, run an update on the configuration page. If node performance changes, select another node in the policy group. Investigate TUN mode and more complete DNS settings only when an application does not read the system proxy.

Setup Complete
  • Subscription configuration imported and set as active
  • Proxy mode set to Rule
  • An available node is selected in the main policy group
  • System proxy enabled and connection records detected
  • The target webpage opens as expected
← Back: Enable connection Continue: Basic troubleshooting →
ERROR CHECK / CHECK IN ORDER

Basic Troubleshooting for Connection Failures

Do not change multiple options at once. Check one link at a time, then move to the next after it works.

What if subscription import fails or an update times out?

First confirm in a browser that the subscription URL is currently reachable, then check that the URL is complete and the account is active. Close other proxy programs and try once more. If the server returns an error page, fix the subscription source first rather than creating duplicate configurations to bypass the error.

What if the import succeeds but no nodes appear on the proxy page?

Confirm that the newly imported configuration is active, then run one update. If the client reports an invalid configuration format, the subscription may be incompatible with the current core. Try a compatible client, or use the YAML Manual to inspect top-level fields, policy-group references, and rule structure.

What if the system proxy is enabled but the browser still cannot connect?

Check whether the connection list contains the browser request. If it does, try another node and inspect the matched rule. If it does not, check browser proxy extensions, the system proxy address, and the client’s running status. Then disable the system proxy to confirm basic network access and re-enable it for comparison.

What if the browser works but other applications cannot connect?

The application may not read the system proxy or may use its own network stack. First check whether it provides proxy settings of its own. If broader traffic interception is necessary, review the permission, DNS, and routing requirements of TUN mode. Technical notes and the YAML Manual cover the differences between system proxy and TUN.

Next Task

Need a Client for Another Platform

Open the download center, choose a client for Windows, macOS, Android, iOS, or Linux, and verify the system architecture.

Go to the Download Center

Need to Edit the YAML Configuration

Review ports, DNS, proxy nodes, policy groups, rule syntax, and override or merge methods without mixing complex configuration into the quick-start flow.

Open the YAML Manual