
Clash Verge Rev
If you do not depend on an old profile or a specific tutorial, start with Clash Verge Rev. It is the clearer starting point for this use case.
Clash Verge Rev: Clear interface, broad tutorial coverage and straightforward profile and proxy group handling. ClashX: Familiar menu bar behavior for users following older ClashX tutorials.
Compare Clash Verge Rev and ClashX by platform support, maintenance status, subscription import, proxy modes, tutorial coverage and best-fit users before choosing.
| Item | Clash Verge Rev | ClashX |
|---|---|---|
| Best for | Most Windows / Mac desktop users | Mac users who prefer a menu bar workflow |
| Learning curve | Low to medium | Low to medium |
| Supported platforms | Windows / Mac | Mac |
| Subscription import | Subscription link and local profiles | Subscription link and local profiles |
| Proxy modes | System proxy, rule, global and TUN depending on version and permissions | System proxy, rule and global |
| Core / ecosystem | Mihomo | Clash |
| Positioning | Modern mainstream desktop client | Classic macOS menu bar client |
| Repository / store status | Active, not archived | Public, not archived |
| Releases / store page | View releases | View releases |
| Links | Clash Verge Rev / Tutorial | ClashX / Tutorial |
| Repository | clash-verge-rev/clash-verge-rev | alvincrisuy/clashX |
| Public repository | Yes, public GitHub repository | Yes, public GitHub repository |
| Open-source status | Yes, public repo with GPL-3.0 license | Yes, public repo with MIT license |
| License | GPL-3.0 | MIT |
| Author / maintainer | clash-verge-rev | alvincrisuy |
| 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 Clash Verge Rev when it matches your platform and workflow; choose ClashX 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 Verge Rev. It is the clearer starting point for this use case.

Choose ClashX 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, ClashX still makes sense.