Clash for Android Client Download and Android Setup Guide

Uses the system's VpnService to create a virtual network adapter that intercepts all app traffic at the network layer, so there's no need to configure a proxy address per app. This also works for games, command-line tools, and background services that ignore system proxy settings. The core offers both system and gVisor stack implementations, selectable based on device performance and compatibility; IPv6 support and DNS hijacking can each be toggled independently in settings, letting you fine-tune the scope and stability of the takeover as needed.

Matches traffic by domain, IP range, process name, and GeoSite category, so local sites can go direct, target sites route through the proxy, and ad domains get blocked — all within a single configuration. Rule sets support remote subscriptions and local overrides, so updating rules doesn't require touching the main config file. Compared to simple clients with only global and direct modes, a rule engine lets one configuration handle most access scenarios long-term, with almost no need to manually switch modes during everyday use.

Save multiple profiles and switch between them with one tap — different subscription providers, self-hosted node configs, and test setups stay fully isolated from each other. Each profile independently tracks its subscription URL, last update time, and auto-update interval, and switching profiles doesn't require restarting the app; proxy group node selections are preserved after switching. For anyone managing multiple subscription sources, or regularly moving between home and office networks, this is the key feature that cuts down on repetitive setup work.

Subscriptions can be set to auto-update in the background on an hourly or daily interval, so node changes and subscription URL updates don't need manual intervention. If an update fails, the previous working configuration is preserved, so a single network hiccup won't wipe out the node list. Notification-bar status alerts make each update's result clear at a glance; you can also trigger an update manually from the profile details screen and view the returned error, making it easy to pinpoint expired links or malformed responses right away.

The access control list lets you exclude specific apps from the proxy, or restrict proxying to only apps on an allowlist. When a banking app needs a direct connection, or a LAN tool shouldn't route through the virtual adapter, there's no need to stop the whole client — just toggle the relevant package in the app list. Control operates at the package level and stacks with domain-based rules, letting you manage traffic by both "which app" and "which destination" simultaneously without conflict.

The client ships with the Meta (mihomo) core, which supports more modern proxy protocols and outbound types beyond the original protocol set, while keeping rule syntax backward-compatible with original-format config files. The core tracks upstream updates continuously alongside client releases, so improvements to protocol handshakes, latency testing, and load-balancing strategies don't have to wait for a major client version. For users whose subscription provider has already moved to newer protocols, switching to a Meta-core client is typically the lowest-cost upgrade path, since existing configs mostly carry over as-is.