Processor architecture · SmartScreen · File verificationA curated list of Clash clients for Windows 10 and Windows 11, with maintenance status, versions, x64 or ARM64 architecture, installer sizes, and download sources, plus setup guides, configuration tutorials, and FAQs.
A maintained cross-platform desktop client built on Mihomo. It is a strong first option for a new Windows device.
Check your Windows version and processor architecture before downloading.
A classic desktop client with extensive Windows documentation and tutorials. The project is no longer maintained, so it should not be the default choice for a new device.
Back up subscriptions and profiles before migrating to a client that is still maintained.
An archived Clash Meta desktop client that retains legacy features such as rule-based routing and proxy-group management.
Clash Verge is different from Clash Verge Rev. Check its maintenance status before choosing it.
Built with Flutter for Windows, macOS, Linux, and Android, with a similar interface and setup workflow across devices.
A particularly useful option to compare if you need the same client across desktop and Android.
Includes stable and preview Mihomo cores, with rule overrides, TUN, subscription management, and WebDAV backup.
Before using it, understand the difference between subscriptions, Rule mode, and TUN.
A cross-platform Tauri client. Version v1.6.1 supports Clash Premium, Mihomo, and Clash Rust.
Compare it with Clash Verge Rev if you prefer a Material You interface.
Confirm the system architecture and download source before importing a configuration. For the first connection, test with the system proxy.
Open “Settings > System > About” and check System type. Intel and AMD computers generally use x64; choose ARM64 only for devices with an ARM processor.
Download the EXE, MSI, or 7Z file from the project release or verified backup identified on this page. If SmartScreen displays a warning, verify the publisher, filename, and SHA256 before proceeding.
Import your own Clash / Mihomo configuration, select a node, and enable the system proxy to test browser connectivity. Configure TUN as documented by the client only if you need to capture traffic from more applications.
Focus on processor architecture, installer source, system security prompts, and the client's maintenance status.
