Default pickPreferred
Clash Verge
If you do not depend on an old profile or a specific tutorial, start with Clash Verge. It is the clearer starting point for this use case.
Clash for Windows vs Clash Verge
Clash for Windows: Widely referenced in older tutorials, but new users should check source and maintenance status carefully. Clash Verge: Good for users who already have a Clash Verge workflow and want a lower-friction continuation.
Clash for Windows vs Clash Verge: Key Differences
Compare Clash for Windows and Clash Verge by platform support, maintenance status, subscription import, proxy modes, tutorial coverage and best-fit users before choosing.
| Item |  Clash for Windows | Clash Verge |
|---|---|---|
| Best for | Users with specific legacy setup needs | Desktop users following older Verge tutorials |
| Learning curve | Medium | Medium |
| Supported platforms | Windows / Mac | Windows / Mac |
| Subscription import | Subscription link and profile files | Subscription import |
| Proxy modes | System proxy, rule and global | System proxy, rule and global |
| Core / ecosystem | Clash | Clash Meta / Mihomo ecosystem |
| Positioning | Classic legacy desktop client | Earlier cross-platform desktop client |
| Repository / store status | GitHub API returned 404 | Archived |
| Releases / store page | View releases | View releases |
| Links | Clash for Windows / Tutorial | Clash Verge / Tutorial |
| Repository | Fndroid/clash_for_windows_pkg | zzzgydi/clash-verge |
| Public repository | Original repo is currently inaccessible | Yes, public GitHub repository |
| Open-source status | Public source status is currently unverified | Public source, but GitHub API did not detect a license |
| License | Currently unverified | Not identified by GitHub API |
| Author / maintainer | Fndroid | zzzgydi |
| Official source type | Historical GitHub repository | GitHub repository |
| Verification source | GitHub API, 2026-05-18 | GitHub API, 2026-05-18 |
How to Choose Between Clash for Windows and Clash Verge
For a new setup, start with Clash Verge when it matches your platform and workflow; choose Clash for Windows when you rely on existing profiles, older tutorials or a specific feature.
When to choose the otherSpecific needs
Clash for Windows
Choose Clash for Windows when you already use it, or when a tutorial, profile or required feature clearly depends on it.
How to decide
New users need a starting point; existing users need migration fit
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.