Open-source core · Configuration guides updated regularly

Clash Downloads & Setup Guides

Choose a compatible client for your platform, then use YAML examples to understand mihomo ports, DNS, and traffic routing.

Open-source code English documentation

01 Downloads

Download a Clash client for your platform

Check your operating system first, then choose the right package architecture. On desktop, distinguish GUI clients from standalone cores. For your first setup, start with a GUI client.

Windows

Check your processor architecture in your device’s system information. Most Intel and AMD PCs use x64 packages; for ARM devices, confirm that the client offers a matching build. After installation, import your config before enabling the system proxy. If a test works but certain apps bypass the proxy, check whether they use system settings before replacing your subscription.

Go to downloads

macOS

Check About This Mac for your chip or processor, then choose the Apple Silicon or Intel package. The menu bar can show whether the client is running, but not whether it handles traffic from every app. After switching configs, check the connection log for the current request. When testing is done, make sure your system proxy settings are restored.

Go to downloads

Android

Choose a package for the app architectures supported by your device; don’t rely only on whether its processor is 64-bit. On first launch, you’ll usually need to approve a system VPN request. If the connection drops in the background, check the client’s status and system battery settings. If you also have a work profile or another VPN, confirm which app manages the active connection.

Go to downloads

iOS

Open the App Store from the download page to check compatible clients and system requirements. After importing your config, allow the VPN configuration when prompted, then return to the client and verify which config is selected. A desktop YAML file can be a starting point for migration, but local file paths, proxy mode names, and advanced fields may not carry over unchanged.

Go to downloads

Linux

For desktop Linux, choose a package format and processor architecture supported by your distribution. Check which formats your package manager uses; different formats for the same architecture are not interchangeable. Terminal commands and desktop apps may use separate proxy settings. If only terminal requests fail, check the proxy configuration that the command-line program actually reads.

Go to downloads

02 Config Reference

Clash Configuration Fields and YAML Examples

Start by distinguishing inbound traffic, outbound connections, and match conditions. Select a field to see a relevant example. These snippets explain individual parts of a config; they are not complete files with subscriptions and nodes.

Mixed proxy port

A mixed port accepts both HTTP and SOCKS connections from apps on the local device. It’s the port apps use to connect to the core—not the port used by a remote node. For local use only, you can disable LAN access and check the address and port set in each app. If the port is already in use, identify the process using it, then update both the core and app settings. If only one is changed, requests may never reach the core, so the connection log won’t show a matching rule.

DNS resolution modes

First check whether requests reach the core’s DNS module, then decide whether the resolution mode is appropriate. fake-ip can return a mapped address so the core can identify the domain during the subsequent connection; it doesn’t automatically route every system DNS query through the core. When troubleshooting, distinguish browser Secure DNS, system resolution, and core DNS. If only certain domains don’t work with mapped addresses, check filters for those domains rather than changing DNS settings across the board.

config.yaml
mixed-port: 7890
allow-lan: false
dns:
  enable: true
  enhanced-mode: fake-ip
  fake-ip-range: 198.18.0.1/16

How to read a config: Start with top-level fields such as mixed-port and mode, then check which outbounds are defined under proxies, and finally see how proxy-groups and rules reference them. Policy group names are part of those references. When renaming one, update nested group references and rule targets too; otherwise, the YAML may parse but the core can still refuse to load it.

Where changes take effect: A subscription source, local overrides, and the final config generated by a client are different layers. If an edit disappears after an update, first check which layer you changed. For persistent local changes, use an override layer supported by your client, and check whether lists are appended or replaced. Be especially careful with rules: replacing the whole section can remove existing exceptions, while appending after MATCH can leave new rules unreachable. See the full syntax in the configuration reference.

03 Quick Start

Import a Clash Config and Verify the Connection

For your first setup, do three things: import and select a config, enable a traffic entry point, and verify it with a request. Get the basic flow working before changing DNS or rules.

  1. 01

    Import and enable a config

    Open the client’s config page and choose a subscription URL or local YAML file. Once the update succeeds, select that config and check that its policy groups expand on the proxy page. Seeing a filename only confirms that the entry was saved; seeing groups and their members is a stronger sign that it loaded. If import fails, check the reported line, field, or download message rather than adding the same subscription again.

    config.yaml · Import a config

  2. 02

    Choose a mode and route traffic

    If you need to route by domain or address, start in rule mode and confirm the active outbound in the policy group. On desktop, enable the system proxy as described by your client; on mobile, follow the prompt to establish a VPN connection. Don’t change the traffic entry point and policy group at the same time, or it’ll be hard to tell which change made a difference. If another proxy is already running, confirm which entry point you want to use.

    mode: rule · System proxy

  3. 03

    Check a real connection

    Reopen a page in a commonly used app, then find its domain, matched rule, and outbound in the connection log. If there’s no entry, check whether the app is using the active traffic entry point. If there is an entry but the request fails, check DNS, policy, and node status. Cached pages and existing connections can affect the result, so make a fresh request. Once a test succeeds, restore custom settings one at a time.

    Request → matched rule → actual outbound

Quick troubleshooting

Why are there nodes on the proxy page but no requests in the connection list?
Loaded nodes don’t mean traffic is routed through the client. Check the system proxy or VPN status, then make sure the app is using that entry point.
Why doesn’t a page already open change after I switch policies?
The app may reuse an existing connection. Make a new request and check the new connection instead of using an old log entry to judge whether the switch worked.
Why did changing one rule affect several sites?
A suffix match also covers subdomains, and an earlier match skips later rules. Check match scope and order in the rule syntax reference.

For more installation and connection help, see Clash FAQs.

04 Project Sources

The mihomo Open-Source Core and Config Sources

Source code, clients, and subscriptions come from different projects and services. When something goes wrong, identify which one is responsible, then check its documentation, release notes, or issue tracker.

Project history: Clash, Clash.Meta, and mihomo

Clash ecosystem configs share several concepts: defining nodes, grouping them into policies, and choosing outbounds with rules. mihomo continues the development lineage of Clash.Meta and extends that structure with additional features. Common syntax in older guides can still help you get started, but check the running core’s documentation for specific protocols, DNS fields, and rule types. The same label in two client interfaces doesn’t guarantee that both interpret a field the same way. When migrating an older file, test a minimal config first, then restore advanced options a section at a time.

Open-source ecosystem: find the right upstream project

mihomo’s source repository is public and licensed under GPL-3.0. For questions about field meanings or implementation, check the relevant code, change history, and known issues in that repository. If the problem involves a tray menu, subscription update button, or device permission, check the client project instead—the core repository usually doesn’t contain UI code. License terms and source history describe each project’s own releases and licensing; they don’t replace subscription service terms or determine the license for other clients or rule data.

Core and client: distinguish importing from processing

The client downloads and assembles the config; the core reads the final config and handles live connections. A failed subscription fetch occurs during retrieval, an unsupported field during loading, and a matched rule that can’t connect during runtime. First identify which stage failed, then check the subscription response, load error, or connection log. When sharing reproduction steps, keep the field structure and error type but replace real node addresses with documentation examples. This shows what went wrong without exposing a subscription URL that grants access.

Updates: check packages, subscriptions, and rule data separately

Updating a client can change its interface and bundled core. Refreshing a subscription usually fetches the config again; updating geo databases or rule sets is a separate process. When investigating a change, note which kind of update ran most recently and keep a working local config from before it. If the issue started after a subscription update, compare the final rule order or node fields. If geographic matches changed, check the data source, update time, and whether it loaded successfully. Change one category at a time, then retry the same destination from the same app.

05 Field Notes

Clash Tips and Guides

Browse the configuration reference by field and practical guides by task. The articles below cover syncing across devices, importing on mobile, and navigating client interfaces.

Clash Download