Clash usually refers to a rule-based proxy core or tools in its ecosystem. A client provides the GUI, subscription management, system proxy controls, and log viewing. Distinguish the core, client, and YAML configuration to find the right downloads and troubleshooting material. For everyday desktop use, start with a GUI client; manage the core directly only for servers, routers, or automated deployments.
First determine whether you are dealing with a core, client, or configuration
Check whether you downloaded a standalone core, a GUI client, or a YAML configuration. Their names are similar, but they serve different purposes.
Confirm whether you downloaded a core or GUI client
Confirm the core used by the client, such as Clash, Mihomo, or Clash Meta
Confirm that the configuration contains proxies, proxy-groups, and rules(See Configuration file structure)
How regular users should choose
- For typical desktop use, choose a GUI client first(See Complete list of Clash clients)
- Use the core directly when you need command-line or service deployment
- When a configuration error occurs, record both the client version and core version
- Review the documented configuration structure and confirm that the YAML fields are supported by the current core
This site does not provide proxy nodes, subscription services, or account services
Protocol and field support differs across cores
When client names are similar, rely on the project repository and release-page documentation