Clash Meta HubClash Meta HubMihomo client hub
Choose language

Config explained

How a Mihomo config file is structured

What base settings, proxies, proxy-groups, and rules each cover in the YAML profile, before you edit one.

Content reviewed · Nov 3, 2026

Who it is for

People who want to read a YAML profile, or need to compare settings while troubleshooting.

Before you read

  • A text editor to open files
  • A sample profile from an official source

Structure overview

  1. 1

    The top level has four common parts: the proxies list, proxy-groups, rules, and base settings such as dns and mixed-port.

  2. 2

    proxies define nodes: each entry lists the protocol type, server address, port, and credentials. Subscriptions generate this section automatically, so you rarely hand-write it.

  3. 3

    proxy-groups define groups: select for manual choice, url-test for lowest latency, fallback for failover. Groups bundle nodes into entry points that rules reference.

  4. 4

    rules decide where traffic goes: matched top to bottom, first hit wins. A common layout allows LAN and direct domains first, splits by GEOIP, and ends with MATCH pointing at a group.

  5. 5

    Back up before editing: indentation is the classic YAML trap. After editing, use the client’s profile validation or start with a minimal profile to verify.

Common issues

YAML parse error

Almost always tabs used for indentation or misaligned nesting. YAML only accepts spaces; realign the lines and retry.

Rule edits do not take effect

Confirm you edited the profile that is actually selected. Subscription updates overwrite manual edits with the provider’s version, so check how your subscription refreshes.

Next step

For the protocol names used in rules, read the protocols guide.

Read next:What is Clash Meta?

This site is an independent Clash Meta / Mihomo ecosystem hub and is not affiliated with the related open-source projects.

Download links point to official GitHub Releases or official websites whenever available.