Clash Glossary

Clash CoreClash core

A network-processing program that listens on local ports, matches routing rules, and forwards connections—not the desktop window itself. The client interface passes settings to the core. Which fields and protocols are supported depends on the core and its version. A toggle in the interface does not mean an older core can perform the corresponding operation.

mihomoFormerly Clash.Meta

A proxy core that continues the Clash configuration ecosystem. The project was previously known as Clash.Meta and is commonly found in actively maintained GUI clients. It shares some configuration conventions with earlier Clash cores, but the two do not support exactly the same features. Before using an online example intended for mihomo, check your core version; do not copy it straight into an older CFW setup.

Proxy NodeProxy node

A set of parameters required for a connection to a remote proxy, usually including the server address, port, protocol, and authentication details. The node name is just a label for identification; a region in the name does not prove the actual exit location. After importing, confirm that the service is available, the parameters match, and the right member is selected in a proxy group.

Proxy ProtocolProxy protocol

The conventions a client follows to exchange data with a remote proxy, such as Shadowsocks, VMess, or Trojan. The protocol, authentication method, transport layer, and TLS settings must match the server. A configuration file being readable only means it passed some format checks; it does not prove that the current core supports the protocol or that a connection will succeed.

Latency TestLatency test / url-test

A test in which the client requests a test URL through a specified proxy and records the response time. A proxy group's url-test can use these results to select a member automatically. The test URL, timeout, and connection reuse can all affect the result, so the number is not a measure of line bandwidth. When choosing a proxy, also check how real websites load, sustained download speeds, and connection stability.

YAMLYAML configuration

A common text format for Clash configuration, YAML uses indentation to show field hierarchy and hyphens to mark list items. Indent with spaces, not tabs, and don't place nodes, proxy groups, and rules at the same level indiscriminately. Valid syntax is only the first step: also check field names, value types, and whether the core supports them.

mixed-portMixed proxy port

A configuration field that lets HTTP and SOCKS proxies share one listening port, for example mixed-port: 7890. The proxy address and port in the app must match the actual listening endpoint; don't enter a number just because it appears in a guide. LAN access also depends on the listening address, Allow LAN, and firewall settings.

modeRule / Global / Direct

Controls how the core chooses an outbound route after a connection enters it. Common values are rule, global, and direct. Rule mode evaluates rules in order, global mode uses the global policy, and direct mode uses the direct policy. “Global” describes the proxy decision; it does not mean traffic from every app is automatically sent to the core.

proxy-providersProxy providers

Defines proxy providers that load a set of nodes from a remote URL or local file and update them according to the configuration. It is not a complete Clash configuration: proxy groups usually need to reference the nodes, and rules then select the groups. Treating a full configuration subscription as a proxy provider may fail because the content has a different structure.

Overrides and MergingOverride / Merge

A way to add to or modify local settings on top of a subscription's original content, often to retain personal port, DNS, or rule settings. The processing order varies between clients; lists may be replaced entirely or rebuilt by a script. After saving, check the final active configuration rather than assuming a setting took effect because it remains in the editor.

System ProxySystem Proxy

A set of proxy settings provided by the operating system for apps to read. In CFW's General page, the System Proxy toggle changes these settings; apps that follow them send requests to the specified listening port. Games, command-line tools, and apps with their own networking stack may ignore these settings. In that case, check the app's own configuration instead of repeatedly switching proxies.

TUN ModeVirtual network interface

Uses a virtual network interface and routing configuration to send eligible traffic into the core, including traffic from some apps that ignore the system proxy. Enabling it typically involves permissions, a service, routing, and DNS; the exact setup varies by client. TUN is not the same as global proxy mode: captured connections can still go direct under the rules or bypass the core due to excluded routes.

DNSDomain Name System

A system that translates domain names into records such as IP addresses. Seeing a website address in the browser does not mean Clash resolved it. System caches, encrypted DNS in the browser, and app-specific resolvers can all affect the path. When troubleshooting, distinguish a DNS resolution failure from a proxy connection failure. Before changing resolvers, make sure the network path to the chosen resolver works.

Fake-IPSynthetic IP mapping

A DNS method that returns a virtual IP for a domain, then uses a mapping to recover the original domain after the connection enters the core. This helps the core retain domain information, but the virtual IP is not the website's real server address. Some apps rely on real-address behavior and may need targeted filter adjustments. A result that looks unusual does not, by itself, mean the network is malfunctioning.

DNS LeakDNS leak

A DNS leak occurs when DNS requests stray from the expected resolution path and reach an unintended resolver. The resolver's reported location on a test page may not match the connection's exit location, and one location label alone does not prove a leak. Check browser DNS settings, the system's resolution path, core logs, and actual routing. Enabling TUN or switching to encrypted DNS is not, by itself, enough to rule out a leak.

Rule RoutingRule-based routing

A way to choose direct, proxy, or reject handling for each connection based on conditions such as domain, destination IP, or process. Rules are usually checked from top to bottom, and the first match takes effect, so specific exceptions should come before broad rules. If a website takes the wrong route, check the matched rule and policy name in the logs first, then determine whether the issue is rule order or proxy group selection.

DOMAIN-SUFFIXDomain suffix rule

A rule type that matches a specified domain and its subdomains. For example, DOMAIN-SUFFIX,example.com,DIRECT matches that domain and its subdomains. It does not match webpage paths, titles, or arbitrary keywords in the address bar. The core must have domain information to apply the rule; if an app provides only an IP, a domain rule may never match.

GEOIPIP geolocation rule

Matches based on geographic regions in an IP geolocation database, for example GEOIP,CN,DIRECT. Database records are not real-time location data; changes in address allocation or differences between databases can affect results. With no-resolve, the rule will not actively resolve a domain that has not yet been resolved, but it can still check the destination IP if the connection already provides one.

Proxy GroupProxy group

A configuration unit that organizes nodes, other proxy groups, or built-in policies for rules to reference. select lets you choose manually, url-test selects based on test results, and fallback checks members in order until it finds one that works. The group name does not determine its behavior. To see whether it switches automatically, check the group type and settings, not just whether its name contains “auto.”

MATCHFinal catch-all rule

Catches connections not matched by any earlier rule and is usually the last entry in the rules list, for example MATCH,DIRECT. The policy that follows it must be a valid policy name or built-in policy, not a group that does not exist. Putting MATCH near the top catches connections early and prevents subsequent rules from matching.

Clash for WindowsCFW

A desktop GUI client commonly abbreviated as CFW, with options for importing configurations, choosing policies, viewing logs, and setting the system proxy. The original project is discontinued, and archived installers and existing guides do not mean compatibility fixes are still being released. For a new installation, compare Clash Plus, Clash Verge Rev, and FlClash. If keeping an older setup, check that its configuration matches the original core's capabilities.

SubscriptionSubscription URL

A remote URL for periodically fetching a configuration or a set of proxy nodes. The term “proxy subscription” often refers to a link provided by a proxy service. It may return a full YAML configuration or another node format, so check client compatibility before importing it. Links often contain access credentials; hide the full URL when sharing screenshots or logs. If an update fails, check the network and response content before repeatedly deleting the configuration.

GUI ClientGraphical User Interface

An app that gives a core a visual interface, letting users manage configurations through menus, buttons, and lists. Even two clients using the same core may differ in subscription updates, configuration merging, system permissions, and where settings appear. When migrating, compatible configurations may be reusable, but don't assume that toggle states, installed services, or local overrides will transfer with them.

Service ModeService Mode

A mechanism that uses a background system service to perform operations requiring elevated permissions, often to help run the core or configure networking. CFW's Service Mode is not the same as its TUN toggle; installing the service does not mean a virtual network interface is capturing traffic. Troubleshoot each separately: check that the service is running, the correct core is loaded, and the relevant routes and DNS settings are active.

System Architecturex64 / ARM64 / x86

The instruction set used by the processor and operating system. Common installer labels include x64, ARM64, and x86; AMD64 generally refers to x64 as well. In Windows, check Settings → System → About for your system type; wording may vary slightly between versions. Choose an installer based on the architecture, not just the file extension: executables do not necessarily run natively on every architecture.