
ClashX
If you do not depend on an old profile or a specific tutorial, start with ClashX. It is the clearer starting point for this use case.
Clash for Windows: Widely referenced in older tutorials, but new users should check source and maintenance status carefully. ClashX: Familiar menu bar behavior for users following older ClashX tutorials.
Compare Clash for Windows and ClashX by platform support, maintenance status, subscription import, proxy modes, tutorial coverage and best-fit users before choosing.
| Item | Clash for Windows | ClashX |
|---|---|---|
| Best for | Users with specific legacy setup needs | Mac users who prefer a menu bar workflow |
| Learning curve | Medium | Low to medium |
| Supported platforms | Windows / Mac | Mac |
| Subscription import | Subscription link and profile files | Subscription link and local profiles |
| Proxy modes | System proxy, rule and global | System proxy, rule and global |
| Core / ecosystem | Clash | Clash |
| Positioning | Classic legacy desktop client | Classic macOS menu bar client |
| Repository / store status | GitHub API returned 404 | Public, not archived |
| Releases / store page | View releases | View releases |
| Links | Clash for Windows / Tutorial | ClashX / Tutorial |
| Repository | Fndroid/clash_for_windows_pkg | alvincrisuy/clashX |
| Public repository | Original repo is currently inaccessible | Yes, public GitHub repository |
| Open-source status | Public source status is currently unverified | Yes, public repo with MIT license |
| License | Currently unverified | MIT |
| Author / maintainer | Fndroid | alvincrisuy |
| 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 ClashX when it matches your platform and workflow; choose Clash for Windows 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. It is the clearer starting point for this use case.

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