Clash Meta for Android · Open-source mihomo core

Clash for AndroidAndroid client downloads and setup

Choose a client for your device, then set up subscription import, VPN access, and rule-based routing.

  • YAML rule examples
  • Chinese configuration docs
Read the configuration docs

Download a Clash client for your platform

Choose your platform first, then check the processor architecture and package format. Before switching clients, save your subscription URL or config file so you can import it again.

Choosing an installer

A 64-bit phone processor doesn't mean the system can install every 64-bit app. If the download page offers packages for different architectures, choose one supported by your system. If you're unsure, look for a universal package; don't rely on numbers in your phone's model name. If the system reports a conflict with an app of the same name, back up your config first, then check whether both apps came from the same release channel.

Migrating from an older client

When moving from the discontinued Clash for Windows, note which config is active and which proxy groups you've selected manually. Then import the original subscription or local file into the new client. Don't copy the entire app data directory. The old client may have left system proxy settings pointing to its port. Before switching, stop the old client from handling traffic, then make a new request in the same browser and confirm it appears in the new client's connection log.

Client routing and configuration features

Separate system-level traffic capture, rule matching, and outbound selection. A working step doesn't guarantee the next one is working too.

First, confirm traffic reaches the client

When connecting for the first time, approve the VPN request in the Android system prompt. Once authorized, traffic from apps covered by the client's capture settings can enter the client without setting a proxy address in each app. Android may already have assigned the VPN to another app, and work profiles may have separate restrictions. If some apps aren't being routed, check which apps the client is set to capture, then review the connection log. System-wide capture describes how traffic enters the client; it doesn't mean you have to use global proxy mode. In rule mode, traffic can still go direct according to your rules.

See the first-time VPN authorization steps →
When routing isn't working, check traffic capture, rules, then outbound selection
What you seeWhat to check firstHow to test again
Request missing from the connection logCheck whether the system has granted access and whether the app is covered by traffic capture. On desktop, also check whether the app uses the system proxy.Close the page that's making the request, then open it again. Compare the logs before and after to see whether the destination appears.
Request appears, but the rule is wrongCheck whether the client is in rule mode. See if a broader rule comes before and overrides the specific rule, and confirm the config has been reloaded.Use the same app to access the same destination. Keep the network and proxy group unchanged, then check the rule name in the new connection log.
Rule matches, but the connection failsDetermine whether the issue is DNS resolution, an outbound connection failure, or an app timeout. A rule match means an outbound was selected, not that the data reached its destination.Keep the traffic capture method and rules unchanged. Change only the outbound for that proxy group and see whether the error changes.

Open-source projects and configuration resources

Check upstream source code, release notes, and client docs to verify features. Download links, core support, and subscription services are separate things.

Original Clash, Clash.Meta, and mihomo

Early Clash established many configuration conventions still in use today: define nodes in one place, organize outbounds with proxy groups, and reference them in ordered rules. Clash.Meta extended this system and was later maintained under the name mihomo. Older guides may still use the first two names. When you see the same config key, an older guide can help explain its basic purpose, but don't assume the default value, support, or behavior is identical. When troubleshooting, first identify which core your client uses, then consult the relevant project's docs.

What the client and core each do

Clash Meta for Android manages configs and provides Android VPN access; mihomo parses the config, matches rules, and establishes outbound connections. Saving a config only confirms that the file reached the client. Whether it loads and matches rules depends on the core's runtime logs. Conversely, if the system hasn't granted VPN access or a battery-saving policy has stopped the background service, changing YAML outbounds usually won't help. Before reporting an issue, identify which layer is involved: installation, system prompts, and interface issues belong with the client project; fields, rules, and connection parsing should be checked against the core docs.

How to verify community resources

Upstream repositories provide source code and commit history, and issue trackers can help you find similar errors. Search using the exact field name and error type, and check which platform and setup the discussion refers to. For example, a working system proxy on desktop doesn't prove that Android VPN capture is configured correctly. To reproduce an issue, keep the config minimal and include the steps and a redacted error excerpt. Before posting publicly, remove subscription URLs, proxy credentials, and private domains. Connection logs may also expose the destinations you visit.

Keep a working config before updating

Client packages, core changes, and subscription content all have their own update schedules. A client update may change the core, while a subscription refresh may alter node names, proxy groups, or rule order. If routing changes after an update, back up the current file and keep the last working copy. Compare release notes and config differences, and avoid reinstalling the client, refreshing the subscription, and changing DNS all at once. Change one thing at a time, then retest on the same network, app, and destination to narrow down the cause.

Installation and configuration FAQ

Why is the proxy group list still empty after installation?
The installer provides the client; proxy groups come from the config currently in use. Confirm that your subscription imported successfully and is enabled. Importing a file into the list doesn't automatically switch the active config.
Why are some requests going direct even though the VPN icon is visible?
The VPN icon means Android has established a VPN connection. Requests that enter the client can still go direct if they match DIRECT. First check whether the request appears in the connection log, then verify which rule it matched.
What should I check if the problem only occurs after switching Wi-Fi networks?
Check whether the new network requires sign-in and can resolve domains, then see whether the client re-established its connection. Retest without changing the rules to distinguish a network issue from a config change.
Why is my terminal still using the old address after I changed the port?
An open terminal may still have the old proxy environment variables. Check the current terminal session and any proxy settings used by the command itself; the new system proxy port may not be applied there automatically.

Technical notes

Find guidance by symptom: connections dropping in the background, desktop apps bypassing the proxy, or DNS resolution taking an unexpected path.

Keep Clash Meta for Android running in the background: VpnService access and battery optimization settings

Learn what the VpnService authorization prompt means, why some manufacturers' battery policies stop background connections, and how to configure battery optimization exemptions and auto-start permissions.

Read the background operation guide →

System proxy is enabled but not working: troubleshoot browsers and terminals separately

Browser extensions taking over, terminals ignoring the system proxy, and mismatched ports are three common causes. Follow separate checks for browsers and terminals, including how to set environment variables.

Read the system proxy troubleshooting guide →

How to test for Clash DNS leaks and configure fake-ip and nameserver-policy

Use a DNS test page to see where requests are going, then adjust enhanced-mode, fallback, and nameserver-policy settings. Includes YAML snippets you can use as a reference.

Read the DNS configuration troubleshooting guide →