Clash for Windows: status and what to use instead
The once-dominant Clash desktop client is no longer developed. Here is what happened, whether it is still safe to use, and how to move to Clash Verge without losing anything.
Development has ended
In November 2023 the Clash for Windows developer deleted the repository and stopped all work. The final release is 0.20.39 — there will be no further features and, more importantly, no security patches.
What Clash for Windows was
Clash for Windows (CFW) was an Electron-based GUI for the Clash core and, between 2018 and 2023, effectively the default choice on Windows: solid subscription handling, a capable rule editor and TAP/TUN support.
Since development ended, every "new CFW build" circulating online is a third-party repack of unknown origin. There is no way to verify what was added, so we advise against installing CFW on any new machine.
Clash Verge vs. CFW
| Clash Verge (Rev) | Clash for Windows | |
|---|---|---|
| Maintenance | Actively developed, monthly releases | Discontinued since November 2023 |
| Core | Mihomo (Clash Meta): VLESS, Hysteria2, TUIC | Legacy Clash core, no new protocols |
| Stack | Tauri + Rust, lightweight installer | Electron, heavyweight installer |
| Memory | Typically 150–300 MB | Typically 400 MB and up |
| TUN mode | Built-in service mode, one switch | Manual TAP driver or service setup |
| Security | Open source, official releases continue | No patches; third-party repacks are risky |
Why migrating is worth it
A proxy client handles literally all of your traffic. Running one that no longer receives security fixes is a poor long-term bet — and providers keep adopting protocols like VLESS and Hysteria2 that the old core simply cannot speak.
The switch itself is cheap: Clash Verge consumes the same standard Clash subscriptions. Re-import your subscription URLs, mirror your old settings, and you are done in about ten minutes.
Need a historical CFW build anyway?
If you have a genuine compatibility reason, only use the Internet Archive snapshot of the original repository's releases and verify file hashes yourself. Treat any site claiming to ship "updated" CFW builds with suspicion.