Open-source ecosystem · mihomo core · Clients updated regularly
This site lists Clash client installers and mihomo core prebuilt binaries for Windows, macOS, Android, iOS and Linux, along with complete reference docs for subscription import, rule-based routing and system proxy setup.
ROUTE OVERVIEW
This site organizes client installers and core binaries by platform, and breaks subscription import, config fields and rule syntax into dedicated reference pages. Pick an exit, then follow the signs the rest of the way.
FEATURES
Pick a topic on the left and the panel on the right expands with the full rundown. Each item links to a deeper reference page on this site — the homepage just covers what it solves and roughly how to use it.
Most mainstream Clash clients today run on mihomo (formerly Clash.Meta) as their core. Compared with the original Clash core, which is no longer updated, mihomo adds more outbound protocols and inbound methods, offers more complete rule types, and keeps up a steady release pace. In practice, choosing a client built on mihomo means new config fields get parsed correctly, and it's easier to find community answers for your specific version when something breaks. Every client listed on our download page is either built on mihomo or fully compatible with its config format.
mihomo · GPL-3.0Rule-based routing is the core mechanism of Clash configs: each request is matched top-to-bottom against the rule set by domain, IP location, process name and other conditions, and the matching rule triggers an action — direct connection, handoff to a proxy group, or a flat reject. Paired with GeoIP and GeoSite databases, a single GEOSITE rule can cover hundreds or thousands of domains without maintaining a huge manual list. For rule syntax, match order, and common pitfalls like "why isn't this rule working," check the config reference page for line-by-line YAML examples.
DOMAIN-SUFFIX · GEOSITE · RULE-SETClients support bulk node import via subscription links: paste a URL and the client fetches the remote YAML automatically, refreshing on a set schedule so node changes sync without manual effort. For advanced setups, proxy-providers fully decouples node sources from local rules, and override rules let you tweak proxy groups, DNS and rule snippets without touching the original subscription — so local customizations survive subscription updates. See the setup guide for a first-time import walkthrough, and the config reference for what each field means and how to write it.
YAML · proxy-providers · overrideSystem proxy only intercepts apps that respect proxy settings — command-line tools and some programs will bypass it. TUN mode captures all outbound traffic through a virtual network adapter, and paired with fake-ip it can also cut down DNS resolution latency. Each has its use case: system proxy is fine for everyday browsing, while TUN mode is for when you need full traffic capture. Platform-specific quirks — Windows service mode authorization, macOS system extension approval, Android's VpnService permission — are covered step by step in the platform tutorials and blog posts.
TUN · fake-ip · system-proxyAll five platforms share the same YAML config language: subscriptions, proxy groups and rules tuned on desktop can be moved straight to phone or tablet without changes. The only difference is system integration — desktop offers system proxy and service mode, Android relies on VpnService to create a virtual adapter, and iOS achieves the same result through Network Extension. This site organizes recommended clients and install notes by platform, so switching devices doesn't mean relearning your setup — just bring your existing config file along.
Windows · macOS · Android · iOS · LinuxPLATFORMS
Each platform section lists actively maintained clients and archived releases — click through to jump straight to that section on the download page.
Clash Verge Rev, FlClash and other actively maintained clients, with service mode and TUN virtual adapter support, compatible with Windows 10/11.
Go to DownloadsInstallers for both Intel and Apple Silicon, runs from the menu bar, with archived ClashX Meta releases included too.
Go to DownloadsBuilt on VpnService for a virtual network adapter, with arm64 and universal APK builds — background persistence tips are covered in our tutorials.
Go to DownloadsDistributed via the App Store, built on Network Extension for rule-based routing on par with desktop clients.
Go to Downloadsdeb installers and AppImage available, plus mihomo core prebuilt binaries ready to use on servers and routers.
Go to Downloadsmihomo core prebuilt binaries for multiple architectures (AMD64/ARM64/ARMv7/MIPS), built for server and router users.
View All Clients →OPEN SOURCE
Clash isn't a single piece of software — it's an open-source ecosystem made up of a core, a config format and multiple clients. Understanding how they fit together saves a lot of guesswork when picking a client.
The original Clash core stopped development in 2023, and early clients like Clash for Windows were discontinued soon after. The community regrouped around the mihomo core, which stayed compatible with the original config format: Clash Verge Rev, FlClash, Clash Nyanpasu, ClashX Meta and others picked up the baton, keeping config files backward-compatible so existing YAML mostly carries over as-is. When people say "using Clash" today, they're usually referring to this new generation of mihomo-based clients.
The core handles protocol implementation, rule matching and DNS resolution, while the client handles the GUI, subscription management and system integration. That's why config files are interchangeable across different clients — they're all driving the same core underneath. Choosing a client mostly comes down to platform support and UI preference, while the config capabilities are capped by the core version.
Installer links on our download page point to each project's official releases, and the listed version numbers auto-refresh from the release feed with no manual editing. Clients that are no longer maintained are clearly marked as archived, with download links kept available for anyone migrating configs off them. The core source is open for cloning and review:
git clone https://github.com/MetaCubeX/mihomo.git
BLOG
Regularly updated with installation walkthroughs and common fixes — every post is based on steps you can actually reproduce.
Explains how the Android client relies on VpnService to create a virtual network adapter, then walks through granting VPN permission, disabling battery optimization, and adding the app to manufacturer battery whitelists to fix background disconnects and vanishing notifications.
Walks through the DNS resolution flow to explain how Fake-IP mode works: why it returns fake addresses from a reserved block, how it cuts resolution latency, and why scenarios like LAN services or online gaming need a fake-ip-filter entry.
Explains the role of GeoIP/GeoSite databases in rule matching, compares three update methods — built-in client updates, manual replacement, and specifying a source in the config file — and covers the telltale signs of routing gone wrong from a stale database.