clash-download/Clash: a navigation index for Clash and Mihomo clients

What this repository is, and what it is not

The description says it collects the official GitHub repositories and configuration tutorials for Clash core clients across platforms: Clash Verge Rev, Clash for Windows, Clash for Android, FlClash and others. The table itself is the product. Each row names a client, shows a version badge and an update-date badge, marks which of Windows, macOS, Android/HarmonyOS and Linux it supports, and links to the upstream repository and, for some rows, to a tutorial page on clash.download.

The repository has exactly one top-level entry: README.md. There is no source tree, no build file, no release asset and no licence file. Anyone arriving expecting to run something should understand that the deliverable is a maintained list, and the value of that list is that it separates clients that still ship from clients that do not. Clash for Windows is pinned at v0.20.39 with the badge 已停更, stopped updating; Clash for Android at v2.5.12, ClashX at v1.118.0, ClashX Pro at v1.118.1 and the old Clash Verge at v1.3.8 carry the same marker.

That distinction is the whole reason a page like this exists. A search for a Clash client returns a mix of live projects and abandoned ones, and the abandoned ones still have working download links. A table that labels them is more useful than a list that does not.

How the version tracking actually works

The live rows do not store version numbers as text. Each cell points at an image endpoint on a Cloudflare Workers host, githubdate.bcdyf49t45.workers.dev, and passes the upstream owner and repository as a path, for example clash-verge-rev/clash-verge-rev or chen08209/FlClash. The endpoint returns a shields.io-style badge, and the README uses two variants: one with type=version for the version column and one without for the update date.

This is a pull-at-render design. Nothing in the repository is refreshed on a schedule by a workflow you can inspect; the badges resolve when the page is viewed. The consequence is that the table is only as accurate as the worker behind it, and the worker is a third-party service with no documented fallback in the README. If that host goes down, every live row shows a broken image while the static rows (the stopped clients, which use hardcoded badges) keep rendering. The README does not document what happens in that case, and does not list a mirror endpoint.

The README also carries a warning about its own persistence: it states that the project may disappear at any time and suggests forking the repository to keep it and starring it to follow updates. Treat the fork suggestion as the real backup plan, because a fork preserves the table but not the badge worker.

Installing a Clash client: what the index tells you to do

There is nothing to install from this repository. The README states that fast download addresses and detailed illustrated tutorials are available on the official site, clash.download, and several rows link to a per-client page there, such as clash.download/clash-verge and clash.download/flclash. The installation path is therefore: pick a row, open the upstream releases link, and download the asset for your platform.

The README recommends forking the repository to preserve it. In the GitHub web interface that means using the Fork button on the repository page; the README gives no command-line steps for this, so there is no shell command to copy here. Once you have your fork, the README.md file is the artifact you keep, and it contains the client table with platform marks.

From there, the upstream release page is the install source. For the Windows, macOS and Linux desktop clients the README links to GitHub releases, for example https://github.com/clash-verge-rev/clash-verge-rev/releases. What you should see on that page is the upstream project's own release list, with assets per platform. The index does not host those binaries and does not verify them. For Android, the README points at https://github.com/MetaCubeX/ClashMetaForAndroid/releases; for macOS-only users it points at https://github.com/MetaCubeX/ClashX.Meta/releases. FlClash is the only client in the table marked as covering Windows, macOS, Android/HarmonyOS and Linux in one row.

Note the two rows that are not Clash clients at all: v2rayN and v2rayNG appear in the same table with their own upstream links. If you are looking strictly for a Mihomo-based client, skip those two rows.

Where the index stops being useful

The README documents no configuration format, no proxy group syntax, no rule syntax and no subscription handling. If you need to know how a Clash config file is structured, this repository will not tell you; it defers to the tutorial pages on clash.download, which are outside the repository and therefore outside anything a fork preserves. That is the sharpest limitation: the durable artifact is a table of links, and the explanation lives on a site the README itself says may vanish.

Second, the platform matrix is coarse. A checkmark for Linux does not tell you whether an AppImage, a deb or a tarball is published, and a cross for Android on Clash Verge Rev does not tell you whether a community build exists. You have to open the upstream release page to learn any of that.

Third, the index carries commercial content. One line offers a free trial of a paid node service with a pricing figure per gigabyte and a registration link carrying a referral code. That is not a defect in the table, but it does mean the page is not a neutral directory, and a reader evaluating clients should weigh the client rows on their upstream repositories rather than on the surrounding copy.

How it differs from just following one client upstream

The obvious alternative is to watch a single client repository directly, for example subscribing to releases of Clash Verge Rev or of FlClash. That gives you release notes, asset lists and issue history for one project, and it is strictly more information than a badge. What it does not give you is the cross-client view: which clients exist, which platforms each covers, and which have stopped shipping.

The second alternative is a package manager or an app store. FlClash and Clash Verge Rev publish desktop builds, and a Linux user could take a client from a distribution repository or a flatpak remote instead of a GitHub release. The trade-off is version lag and packaging differences, but the update mechanism is handled for you, which the index does not do at all.

The third alternative is a general proxy-client comparison site. Those usually cover more protocols and more clients, including non-Clash ones, and often include setup walkthroughs. This repository is narrower: it stays inside the Clash and Mihomo core ecosystem, and its distinguishing feature is the stopped-updating column, which comparison sites tend to omit because they keep listing legacy clients as options.

Maintenance, licence and what a fork preserves

The last push to this repository was on 2026-09-21, two days before the date used for this review, so the index is being touched. That says nothing about the upstream clients it tracks; each of those has its own release cadence, and the badge endpoint is what reflects it.

The repository has no licence file among its top-level entries, so there is no licence text to read here. The clients it links to carry their own licences in their own repositories, and those are what govern the binaries you download. Nothing in this repository grants rights over the upstream software, and nothing here should be read as a distribution of it.

Upgrade cost is close to zero in the software sense, because there is no software. The cost is editorial: the table needs new rows when clients appear and needs rows moved to the stopped column when projects end, and the badge endpoint needs to stay reachable. A fork preserves the README as of the fork date and nothing else, so a fork made today will keep showing the clients that existed today, with badges that may or may not still resolve.

Which client row to pick for your platform

If you are on Windows, macOS or Linux and want one graphical client, Clash Verge Rev is the first live row in the table and is marked for all three desktop platforms, with the upstream at clash-verge-rev/clash-verge-rev. If you want a single client that also covers Android or HarmonyOS, FlClash is the only row marked across Windows, macOS, Android/HarmonyOS and Linux.

If you are Android-only, Clash Meta for Android is the live row, and the table marks it for Android only. macOS-only users have ClashX.Meta as a live option; the older ClashX and ClashX Pro rows are marked stopped at v1.118.0 and v1.118.1.

The table also lists Clash Mi, GUI.for.Clash, Clash Party and Pandora-Box as live desktop options, each with its own upstream repository, and none of them has a tutorial link in the table. For any of those, the upstream releases page is the only documented path, and the README gives no further guidance.

Editorial conclusion

Adopt this repository as a pointer, not as a dependency. It suits someone who wants one page listing which Clash clients exist, which platforms each covers, and which upstream repository to visit for releases, and it is useful precisely because the table also marks Clash for Windows, Clash for Android, ClashX and the old Clash Verge as stopped. Do not use it as an install source: the README sends you to clash.download for downloads and tutorials, and the only file in the repository is README.md, so there is no code to build, no release to pin and no licence text to read. Before relying on it, open the upstream repository linked in the row you care about and confirm the version badge there matches what you intend to install.

Frequently asked questions

Official sources

1. clash-download/Clash on GitHub
2. Issues
3. Project website
4. README