● Config IndexCLASH / YAML

Clash Client Downloads and Configuration Guide

Find an installer for your system, start by importing a subscription, then check routing rules and YAML fields one by one.

Open-source core ecosystemYAML field reference
Install optionsOS / ARCH

Choose a Clash installer for your system

Choose your operating system first, then confirm your processor architecture and package format. The download page lists clients and system requirements by platform. Apps with the same name may use different cores or support different override methods on different systems.

Browse all clients →

Projects and sourcesCORE / GUI

The Clash ecosystem: open source and project ownership

When apps have similar names, check their project history, core source, and maintenance status before deciding whether to migrate your config.

Mihomo source repository ↗

git clone https://github.com/MetaCubeX/mihomo.git

Project history: identify which projects older docs refer to

Clash originally referred to a proxy core configured with rules, and the name also became shorthand for a range of desktop and mobile tools. Mihomo continues the development line of Clash Meta, so older tutorials that mention Meta may refer to the Mihomo project today. When reading older material, check whether it covers the original core, a later fork, or a specific client UI. A change in button labels or screenshots does not necessarily mean the YAML syntax changed too. Conversely, a similar-looking interface does not guarantee that older config extensions still work.

Community resources: what to look for in repositories and client docs

Mihomo source code is released under GPL-3.0. Its repository is a place to review code, issue discussions, and release notes. Desktop and mobile clients are maintained by their respective projects; using the same core does not mean they share a license or distribution method. When looking up community reports, compare the operating system, connection method, and exact error first—matching symptoms alone does not guarantee the same fix will apply. The clone command above fetches the core source for reading or development. It does not install a GUI client or import a subscription.

How the layers work: the UI builds the config, the core handles network traffic

GUI clients typically handle subscription downloads, config switching, system proxy controls, and log display. The core parses the active configuration and runs listeners, DNS, rule matching, and outbound routing. Whether a setting takes effect depends on whether the client writes it to the final file, whether the core recognizes the field, and whether the operating system allows the network operation. When migrating, import the original config into the new client and verify that it connects before restoring local overrides one at a time. See the Client Comparison to compare clients; appearance alone need not decide your choice.

Updates: manage the app, core, and subscription separately

An app update may change where configs are stored or where settings appear. A core update may change supported fields and network behavior. A subscription refresh may replace the provider's proxies, groups, or rules. Handle these changes separately. Before updating, save a config you can re-import and any local overrides, and note the current connection method. Afterward, confirm the active config, check whether the local port is listening, and see which rule matches a frequently used site. If something changes, roll back only the layer you just updated so the rest of your troubleshooting config remains intact.

Common installation and configuration questions

If port 7890 is listening, does that mean the system is using the proxy?

Not necessarily. mixed-port only specifies where the core accepts proxy requests; the system or app still needs to point to the actual listening address and port. Some apps have their own network settings and may use those even when the system proxy is enabled. Start with the port field guide, then check whether the client's connection view shows the request you just made.

Why did my selected outbound disappear after refreshing the subscription?

A subscription refresh may change group names, entry names, or member order. If the saved selection points to a removed member, the client may switch to an available option in the current group. First confirm which config is active, then compare the proxy groups and override references before and after the refresh. If you encounter unfamiliar terms such as group types, see the glossary.

Can I move the same config to another device unchanged?

Basic fields are usually easier to migrate, but virtual network adapters, interface names, local file paths, and client override scripts often depend on the device. First confirm that the target client supports the config's import format, then move device-independent rules and policies. Once those work, set up the system proxy and connection permissions on the new device. Avoid carrying over paths from the old device as-is.

Clash Technical Notes

Find guidance on client selection, connection issues, and importing a config on mobile for the first time.

Browse all articles →