
ClashX Meta
If you do not depend on an old profile or a specific tutorial, start with ClashX Meta. It is the clearer starting point for this use case.
Clash Verge: Good for users who already have a Clash Verge workflow and want a lower-friction continuation. ClashX Meta: A better fit when your provider or profile expects Clash Meta / Mihomo behavior.
Compare Clash Verge and ClashX Meta by platform support, maintenance status, subscription import, proxy modes, tutorial coverage and best-fit users before choosing.
| Item | Clash Verge | ClashX Meta |
|---|---|---|
| Best for | Desktop users following older Verge tutorials | Mac users needing Mihomo behavior |
| Learning curve | Medium | Medium |
| Supported platforms | Windows / Mac | Mac |
| Subscription import | Subscription import | Common subscription imports |
| Proxy modes | System proxy, rule and global | Rules, proxy groups and Meta-related capabilities |
| Core / ecosystem | Clash Meta / Mihomo ecosystem | Clash Meta / Mihomo |
| Positioning | Earlier cross-platform desktop client | Mac client aligned with Meta / Mihomo |
| Repository / store status | Archived | Active, not archived |
| Releases / store page | View releases | View releases |
| Links | Clash Verge / Tutorial | ClashX Meta / Tutorial |
| Repository | zzzgydi/clash-verge | MetaCubeX/ClashX.Meta |
| Public repository | Yes, public GitHub repository | Yes, public GitHub repository |
| Open-source status | Public source, but GitHub API did not detect a license | Yes, public repo with AGPL-3.0 license |
| License | Not identified by GitHub API | AGPL-3.0 |
| Author / maintainer | zzzgydi | MetaCubeX |
| Official source type | GitHub repository | GitHub repository |
| Verification source | GitHub API, 2026-05-18 | GitHub API, 2026-05-18 |
For a new setup, start with ClashX Meta when it matches your platform and workflow; choose Clash Verge 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 ClashX Meta. It is the clearer starting point for this use case.

Choose Clash Verge 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 Verge still makes sense.