
Clash Meta for Android
If you do not depend on an old profile or a specific tutorial, start with Clash Meta for Android. It is the clearer starting point for this use case.
Clash for Android: Useful when you are following older Android Clash tutorials or keeping older profiles. Clash Meta for Android: A better fit when you need Clash Meta / Mihomo related behavior on Android.
Compare Clash for Android and Clash Meta for Android by platform support, maintenance status, subscription import, proxy modes, tutorial coverage and best-fit users before choosing.
| Item | Clash for Android | Clash Meta for Android |
|---|---|---|
| Best for | Android users with older Clash guides | Android users needing stronger protocol or rule support |
| Learning curve | Medium | Medium |
| Supported platforms | Android | Android |
| Subscription import | Subscription link and profile import | Common subscription imports |
| Proxy modes | Android VPN mode, rule and global | Android VPN mode, rules and Meta capabilities depending on version |
| Core / ecosystem | Clash | Clash Meta / Mihomo |
| Positioning | Classic Android Clash client | Android client aligned with Meta / Mihomo |
| Repository / store status | GitHub API returned 404 | Active, not archived |
| Releases / store page | View releases | View releases |
| Links | Clash for Android / Tutorial | Clash Meta for Android / Tutorial |
| Repository | Kr328/ClashForAndroid | MetaCubeX/ClashMetaForAndroid |
| Public repository | Original repo is currently inaccessible | Yes, public GitHub repository |
| Open-source status | Public source status is currently unverified | Yes, public repo with GPL-3.0 license |
| License | Currently unverified | GPL-3.0 |
| Author / maintainer | Kr328 | MetaCubeX |
| Official source type | Historical GitHub repository | GitHub repository |
| Verification source | GitHub API, 2026-05-18 | GitHub API, 2026-05-18 |
For a new setup, start with Clash Meta for Android when it matches your platform and workflow; choose Clash for Android when you rely on existing profiles, older tutorials or a specific feature.

If you do not depend on an old profile or a specific tutorial, start with Clash Meta for Android. It is the clearer starting point for this use case.

Choose Clash for Android when you already use it, or when a tutorial, profile or required feature clearly depends on it.
New users should follow the default pick; existing users should check migration fit first. If you already have a related setup or a tutorial requires it, Clash for Android still makes sense.