Clash Configuration Notes

Clash DownloadsSubscription Setup

Choose a client for your operating system, start by importing a subscription, then use routing rules and connection logs to see where traffic goes.

  • Chinese-language docs
  • YAML examples

CONFIG WORKBENCH

Clash Configuration: Fields and Actions

First identify what you need to change: the configuration source, where traffic goes, or how often remote resources refresh. Each has its own settings. The snippets on the right need to be merged into an existing configuration; they are not complete, ready-to-connect subscriptions.

Configuration Sources and Proxy Groups

Tell Full Configurations Apart from Proxy Providers

Start with the name of the option provided by your service. A full Clash subscription is usually imported from the client’s configuration page and may define proxies, proxy groups, and rules. A proxy provider supplies proxies only; the main configuration references it under proxy-providers. If you use a full configuration as a provider, the URL may still load, but the proxy groups might not get any proxies. To confirm the format before importing, check your provider’s documentation. Avoid pasting URLs with access credentials into online detection tools.

View the Tutorial
Reference Providers from Proxy Groups

Enter the provider name in the proxy group’s use list; don’t add it as a single proxy under proxies. In this example, “Manual” offers DIRECT, the latency test group, and a remote provider as options. “Auto Test” selects proxies from that same provider. After importing, check that the expected options appear in each group, then test the connection. You can rename groups, but update every reference too; names, spaces, and capitalization must match their definitions.

Check Which Configuration Is Active

Seeing a subscription name in the list only means the client created a configuration entry; it doesn’t necessarily mean the core is using it. Switch to the new entry and check whether the proxy group names change. If the switch fails, check the logs for syntax errors or unsupported fields. There’s no need to reinstall the client first: keep the old configuration available for comparison. When sharing screenshots, hide URL query parameters, account details, and any unnecessary connection information.

config.yaml · Proxy Groups
proxy-groups:
  - name: Manual
    type: select
    proxies: [DIRECT, Auto Test]
    use: [remote]
  - name: Auto Test
    type: url-test
    use: [remote]
    url: https://example.com/
    interval: 300

Choose a Clash Client for Your Operating System

Check your operating system and processor architecture first, then compare configuration overrides, connection logs, and system integration. The download page lists clients by platform. If you switch to another frontend, keep your subscription source, but don’t assume local settings will carry over from the old client.

Windows

Check your system type in the About settings. If you’re new to Clash, test the system proxy first before enabling TUN. If you still use the discontinued Clash for Windows, keep your current configuration and compare it with actively maintained alternatives before switching.

Go to Downloads

Android

Choose a package for your device’s architecture, and look for the system VPN permission prompt when you first connect. If the connection drops only when the screen locks, check background activity and battery settings first. If only one app bypasses the proxy, check its per-app settings.

Go to Downloads

iOS

Open the store from the download page and first check that your device meets its listed system requirements. After importing, confirm that the client has selected the configuration and that the system allows a VPN connection. Once both are in place, test the traffic route with a known destination.

Go to Downloads

macOS

Check About This Mac to see whether your Mac has Apple silicon or an Intel processor, then choose the matching installer. The system proxy may change with the active network service. After switching to Wi-Fi or a dock’s Ethernet port, check again that the client is handling traffic.

Go to Downloads

Linux

Desktop users should choose a graphical client based on their Linux distribution and package format. Server users can find standalone cores on the download page. Desktop proxy settings may differ from the environment used by command-line programs, so test with the application you actually plan to use.

Go to Downloads

Browse all clients → · Compare client features

Three Steps to Your First Clash Connection

Get one configuration working with one app first, then add features like startup launch, automatic testing, or TUN one at a time. If something breaks, you can return to the last known-good setup.

  1. 01

    Import a Subscription

    Add a remote entry on the configuration page, paste the Clash subscription URL from your provider, and save. You still need to enable the entry after it downloads. Continue once the proxy page shows the groups and proxy options defined by the configuration. If your provider gave you a local file, use the file import option instead.

  2. 02

    Choose a Mode and Proxy

    Select rule mode, then manually choose a proxy in the group you want to test so automatic switching won’t affect the result. On desktop, start by enabling the system proxy. On mobile, follow the client’s prompts to establish a VPN connection. If another proxy or VPN is already active on your device, check which app is handling traffic.

  3. 03

    Check the Connection Logs

    Open a destination that should use the proxy, then visit one that should connect directly. For each, check the matched rule and actual outbound proxy in the logs. If there’s no log entry at all, check how the system is routing traffic before blaming proxy latency.

Read the full tutorial → · Troubleshoot by symptom

The Clash Open-Source Ecosystem and mihomo Core

Project History: Shared Configuration Format, Different Maintenance

Early versions of Clash used YAML to define proxies, proxy groups, and rules in a single configuration, keeping proxy management separate from traffic routing. Since then, different graphical frontends and forked cores have emerged, carrying on this structure but varying in maintenance status and field support. Clash for Windows is no longer maintained, so don’t assume that menu locations or installation advice in older documentation applies to current clients. When migrating, start with a minimal configuration to test core functionality, then restore your custom settings once the connection works.

Community Support: Check the Project That Owns the Problem

Source code, release notes, and issue discussions in open-source repositories can help verify specific behavior. If a window won’t open, the tray stops responding, or startup fails, check the graphical frontend you’re using first. If the same minimal configuration produces the same rule error in different frontends, check the core they share. When reviewing community reports, compare the platform, system environment, and reproduction steps. The same issue title doesn’t guarantee the same cause; “can’t connect” can involve system integration, DNS, or the proxy connection itself.

How the Core Fits In: The Client Manages, the Core Runs

mihomo is derived from Clash Meta and is licensed under GPL-3.0. Graphical clients mainly handle configuration, status displays, and system integration. The core handles protocol connections, rule matching, and some DNS behavior. Two clients using the same core may still behave differently because of their defaults, system proxy settings, or override methods. Likewise, a client recognizing a configuration entry doesn’t mean the core supports every field it references. If you encounter a compatibility issue, first determine whether the client failed to import the configuration or the core failed to load it.

Update Types: Manage the App, Core, and Configuration Separately

An app update may change the interface or system permissions; a core update may change supported fields or runtime behavior; a subscription refresh mainly changes remote configuration content. Test each type separately: note the active policies and necessary overrides before making a change, then compare the logs using the same test destinations afterward. If you change both the client and subscription at once, it’s hard to tell which caused a problem. Keep a rollback copy of your local configuration, and store any copy containing access credentials in a private location.

Clash Configuration and Troubleshooting Notes

Browse by what you need: check traffic routing for your first connection, look up configuration fields when making changes, and compare possible causes layer by layer if your connection works but speeds are unstable.

Browse all articles →

Download the Latest Clash Version