Open-source project
Z-Siqi/Clash-for-Windows_Chinese avatar
Z-Siqi/Clash-for-Windows_Chinese

Clash for Windows Chinese: an unofficial modified build with a switchable Mihomo core

Chinese localization of Clash for Windows - provides the localized version, language patches and installer.

28,659 stars3,191 forksJavaScriptLicense varies

At a glance

What is it?
Z-Siqi/Clash-for-Windows_Chinese is a community maintained, modified and localized copy of Clash for Windows that can run either the 2023 Clash core or the Mihomo core. It is explicitly unofficial, minimally maintained, and ships with conditions you must accept before downloading.
Who is it for?
Use this build if you already depend on the Clash for Windows interface and want Mihomo features such as AnyTLS in it. Avoid it if you need a vendor backed or audited release, a stated license, or any support from the maintainer when you are in mainland China; read the terms in the README before you download.
Can I use it commercially?
Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
Is it still maintained?
Yes. The repository last received commits 18 days ago.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • Z-Siqi/Clash-for-Windows_Chinese28,659 ★ · +87
Star history
Repository2026-09-282026-11-15
Z-Siqi/Clash-for-Windows_Chinese28.6k28.7k

87 Stars in the last 48 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

It is a modified fork of a deleted original, so bugs have nowhere upstream to go

The first thing the project says about itself is that it is unofficial. The Clash for Windows distributed here has been modified, and the original project's repository has been deleted. The README once told users to switch back to the original build before reporting bugs, and that sentence is now struck through for exactly that reason. In its place, you can file an issue in this repository, but the maintainer states there is no guarantee of a fix.

The consequence is that this repository is both the downstream localization and the only place where problems get looked at. The README says the code base of the current Optimize version has changed a great deal and points readers to the commit history for a record of how it was modified, rather than offering a change list. If you want to know what differs from the version you used before, the history is the document. The repository also carries an older note that it was archived on November 3, 2023. That note is crossed out, and the repository is not archived today.

Mihomo is the default core, and the old Clash core is one setting away

The main reason this build exists is the core switch. By default it runs the Mihomo core. If you want the previous behaviour, go to Settings, then General, then Proxy Core, and choose the 2023 Clash core. After the switch the application restarts the proxy core automatically, so that older configurations and habits keep working.

The README describes the two options in terms of age and protocol coverage: the old 2023 Clash core on one side, and on the other the Mihomo core, which supports newer protocols such as AnyTLS. If your subscription or profile uses a protocol the old core does not understand, the answer is to stay on Mihomo. If your configuration was written against the 2023 core and breaks under Mihomo, the way back is that single setting. The announced compatibility range runs from version 0.15.3 up to the latest release, so very old configuration setups are within the stated range but are not described in detail.

AnyTLS is editable in the built-in config editor, with advanced fields preserved

In Mihomo mode the app supports AnyTLS, and the built-in configuration editor can edit the common AnyTLS fields. When you edit the same profile again, the editor keeps the advanced fields it does not expose directly: ShadowTLS, ResTLS and JLS. That matters for anyone who hand edits profiles, because a visual editor that rewrites a file can silently drop settings it does not understand.

The limit to keep in mind is that only the common AnyTLS fields are editable through the interface. If you rely on the advanced fields, you set them in the file itself and trust the editor to leave them alone. The README states the preservation behaviour but gives no list of every field the editor exposes, so open a copy of your profile after the first edit and compare. The statement also covers only Mihomo mode, so do not expect these protocol fields to work if you switch back to the 2023 Clash core.

Cores are bundled for seven platform builds, and the download is a 7z archive

The current build resources include Mihomo cores for Windows x64, Windows x86, Windows ARM64, Linux x64, Linux ARM64, macOS Intel and macOS Apple Silicon. Despite the name, then, this is not only a Windows tool. The package.json of the maintenance repository defines packaging scripts for win-x64, win-arm64, linux-x64, linux-arm64, mac-x64 and mac-arm64, plus DMG packaging for both Mac architectures. A script named mihomo:prepare fetches the cores, and mihomo:update refreshes them.

The README also lists software that can unpack 7z files: NanaZip, which is marked as compatible with Windows 11, 7-Zip and WinRAR. That tells you the release assets arrive as 7z archives, so a machine without an extractor cannot open them. The README points to the releases page for the download and to a wiki that holds an online copy of the Clash for Windows documentation. Because the original download page is gone, that wiki copy is the practical manual for the interface.

The obfuscated original was reverse engineered so that the code can be audited

One of the three headline claims is that the obfuscated code of the original version was fully reverse engineered, in order to allow auditing, contribution and extension. For a proxy client that handles your traffic, that is the most relevant promise, because readable source is the precondition for anyone checking what the application does.

Contribution is organised around a few documents and one command. Before developing, contributors are told to read AGENTS.md and the docs folder, and the unified test entry is npm test, which runs on Windows, Linux and macOS. The package scripts show that installing dependencies also builds the Monaco editor and the renderer, and the test run repeats those two builds first. There is a build:release script and a release:check script that verifies release synchronisation. Pull requests are the route to becoming a co maintainer, and a label on the issue tracker marks the issues where help is wanted. Reading the source does not replace an audit, and the README does not say that anyone has completed one.

You must accept the terms, and mainland China gets no support

Downloading counts as agreement with a short list of conditions, and the README says you must agree. The project provides no help or support for mainland China. Everything from the sponsor is unrelated to the repository. The repository takes no responsibility for what users do with it. All of its content exists only on GitHub.

Two more details affect real use. The sponsor section is an advertisement for a paid proxy provider, and the README separates it from the project, so treat it as a banner and nothing more. And the license is not identified in the repository information, so there is no stated license to rely on if you plan to redistribute or build commercial work on the modified code. The maintainer's own words on the subject are brief: the modifications are described only through the commit history. If you need clear redistribution terms, ask in the discussions or the issue tracker before you ship it inside something else.

Maintenance runs at the minimum usable level, with releases in bursts

The README is candid about pace: updates follow the lowest usable level of maintenance, offered irregularly and within what the maintainer is able to do. The release history matches that description. Release 0.20.39.5, titled Clash for Windows Opt-5, appeared on 2026-10-25. Release 0.20.39.4, the Opt-4 optimized build, appeared on 2026-09-26. Before it came CFW-OPT-3_BETA-1, a beta that tested replacing the core with Mihomo, on 2026-09-22. The last push to the main branch was on 2026-10-28.

So the project is clearly being worked on, but in bursts rather than on a fixed schedule, and one person decides what gets fixed. For a daily driver that sits between you and the network, that means you should expect to wait for fixes, and keep the previous release archive until a new one has proven itself. The README invites readers to start discussions on the Discussions page and to help with open issues carrying the Need Help label.

Editorial conclusion

Use this build if you already depend on the Clash for Windows interface and want Mihomo features such as AnyTLS in it. Avoid it if you need a vendor backed or audited release, a stated license, or any support from the maintainer when you are in mainland China; read the terms in the README before you download.

Frequently asked questions

Is Clash for Windows Chinese the official Clash for Windows?

No. The README labels it unofficial and modified, and says the original Clash for Windows repository has been deleted. Problems can be raised as issues in this repository without a guarantee of a fix.

Which core does Clash for Windows Chinese use by default?

It uses the Mihomo core by default. You can switch to the 2023 Clash core in Settings, General, Proxy Core, and the app restarts the proxy core automatically after the switch.

Which platforms does Clash for Windows Chinese cover?

The build resources bundle Mihomo cores for Windows x64, x86 and ARM64, Linux x64 and ARM64, and macOS Intel and Apple Silicon. Downloads come from the releases page as 7z archives.

Official sources

  1. Issues
  2. README
  3. Releases
  4. Z-Siqi/Clash-for-Windows_Chinese on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/z-siqi-clash-for-windows-chinese.svg)](https://hysenlabs.com/projects/z-siqi-clash-for-windows-chinese)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/z-siqi-clash-for-windows-chinese.svg)](https://hysenlabs.com/projects/z-siqi-clash-for-windows-chinese)

Was this useful?