Clash Terminology Guide: Proxies, Rules, DNS, and Configuration Fields

A subscription is usually a remote configuration URL that clients use to retrieve nodes, proxy groups, rules, and DNS settings. Updating it reloads content published by the provider, so locally edited sections may be overwritten.

If a subscription link will not import, first check that the URL is complete and still valid, and that the response uses a configuration format supported by the client. A subscription is not a node; nodes are just one part of its contents.

A node is a proxy server entry available for connection, usually containing a server address, port, protocol, authentication details, and transport parameters. After a node is selected, the core establishes the connection using those settings.

A node name is only a label for identification and says nothing by itself about actual speed. Connection quality is also affected by the local network, server load, route distance, and destination website.

Latency is the time a test request takes from being sent to receiving a response, usually measured in milliseconds. A lower value means the test target responded faster at that moment, but does not guarantee higher download speeds.

Client latency tests depend on the test address, timeout, and current network conditions. Compare nodes using the same test method, then judge them by real-world access as well.

An HTTP proxy receives application requests through a local listening port, after which the client determines how to handle the connection. Browsers and many apps that follow system proxy settings can use this interface directly.

When only the system proxy is enabled, command-line tools, games, and some background services that ignore system settings may bypass the client. Set a proxy for those apps individually or use TUN mode instead.

SOCKS5 is a general-purpose proxy interface that can carry multiple types of connections and supports username-and-password authentication. Some developer tools, download clients, and command-line programs provide a separate SOCKS5 setting.

Enter the client's local listening address and SOCKS port. Whether DNS queries are also sent through the proxy depends on the application's implementation and the address format used.

Rule mode matches each connection against the rule list in order, then sends it through a proxy, directly, or rejects it according to the matched policy. It suits everyday use by giving different websites and apps different paths.

Rule order matters. A broad rule placed too early can prevent later, more specific rules from taking effect. When troubleshooting routing, check the matched rule and final policy in the logs first.

Global mode sends most connections intercepted by the client through the currently selected proxy policy. Fine-grained rules in the configuration generally do not participate in everyday routing decisions.

It is useful for briefly testing whether a node works or determining whether rules are causing a problem. For long-term use, still watch for LAN traffic, system services, and connections that should not use a proxy.

Direct mode sends intercepted connections straight to their destinations without using proxy nodes. It is often used to temporarily restore the local network path or determine whether a problem is related to the proxy route.

Switching to Direct does not necessarily stop the client: local ports, DNS, or TUN may still be running. To stop interception completely, turn off the relevant option or exit the program.

Rule Provider stores a set of rules in a separate file or remote URL, which the main configuration references by name. It shortens the main configuration and allows frequently used rule sets to be updated independently.

The rule set's behavior type must match its content format, such as domain, IP-CIDR, or classical rules. If the types do not match, the file may download successfully but still fail to match as expected.

GeoIP matches the geographic association of a destination IP in a database and is commonly used to route connections by country or region. It matches address data, not the language used by a webpage.

If the database is not updated for a long time, newly assigned or reclassified IPs may be categorized incorrectly. When geographic rules behave unexpectedly, check the database update time and download source.

GeoSite is a domain-rule database organized by purpose or affiliation. It can match groups of media, search, messaging, and common service domains. It classifies domains, unlike GeoIP, which evaluates address location.

A website may use multiple third-party domains, so one category may not cover every request. During troubleshooting, use connection logs to add more specific domain rules.

A proxy group organizes multiple nodes, direct policies, or other proxy groups for use by rules. Common behaviors include manual selection, health-check selection, failover, and load distribution.

Rules usually match a proxy group name rather than the final node name. The actual route depends on which member the group has selected at that time.

YAML is a common data format for Clash configurations and uses indentation to express field hierarchy. It is sensitive to spaces, colons, and list markers; tabs or misaligned indentation can cause parsing failures.

Keep indentation consistent at the same level when editing configuration, and avoid changing node names casually. If a name contains special characters, wrapping it in quotes is usually safer.

port sets the local listening port for the HTTP proxy. When an app enables an HTTP proxy, it typically connects to the loopback address and this port.

If another program is using the port, the core may fail to start listening. After changing it, update the system proxy and any apps configured manually.

mixed-port is a mixed listening port that accepts both HTTP and SOCKS connections. Applications can connect to the same port according to the proxy type they support.

It reduces the number of local ports, but does not change the protocol used by the remote node. If multiple listening ports are configured, make sure their values do not conflict.

proxies stores static node definitions written directly in the main configuration. Each entry typically includes a name, server address, port, protocol, and authentication parameters.

Proxy groups reference these entries by node name, so renaming one also requires updating the relevant groups. For many nodes, use a Proxy Provider to move them into a separate file.

proxy-groups defines proxy groups, including their names, behavior types, and optional members. Rules typically send traffic to a group, which then selects the final node.

Group members can be nodes, built-in policies, or another proxy group. Referenced names must match exactly; otherwise the core may report that the proxy or policy cannot be found.

rules stores routing conditions and target policies from top to bottom. Usually, specific domains and special services come first, broader category rules follow, and a final fallback rule comes last.

Once a connection matches an earlier rule, later rules are normally not evaluated. If a new rule has no effect, check whether a broader condition earlier in the list catches it first.