Midnight Proxy Toolkit

Clash Client Downloads for Every Platform
Subscription Setup & Usage Guide

Download links for Windows / macOS / Android / iOS / Linux clients, plus a subscription import guide, a handbook and a troubleshooting index — everything from install and subscription import to verifying your first connection, all in one place so newcomers can simply follow along.

  • Free Forever
  • Open-Source Core
Features

Core Capabilities at a Glance

The core handles protocols and routing; the client handles subscriptions and toggles — that two-layer split is the key to understanding Clash. Below are the most-used capabilities in two groups, "Core & Rules" and "Connection & Experience", each noting the real problem it solves; see the tutorial, handbook and blog pages for implementation details.

Rules Engine01

Rule-Based Routing Engine

The pain of a traditional global proxy is that everything goes through the tunnel — local sites get slower for no reason. Clash's rules engine matches every connection against domain names, IP ranges and GEOIP databases, then routes it by proxy-groups into direct, proxied or blocked traffic: local sites connect directly, overseas services go through the proxy, and ad or tracker domains are simply rejected. Rule sets support remote subscriptions and scheduled updates, so there's nothing to maintain by hand; browsers, terminals and background processes each follow their own path without interfering with one another, and no per-app configuration is required. This rule-driven automatic routing is exactly what sets Clash apart from ordinary proxy tools — see the handbook and the config-file deep dive for rule syntax.

DNS02

Fake-IP & DNS Takeover

DNS tampering resolves domains to wrong addresses, creating "node works but pages won't load" phantom failures. The built-in DNS server offers two modes: Fake-IP returns a reserved-range virtual address first and only resolves when the connection is made, all but eliminating resolution wait; Redir-Host keeps the real IP so IP-range rules can match. Switch modes and set upstreams in the config's dns section — start here whenever resolution misbehaves.

Protocols03

Multi-Protocol Core

Switching protocols used to mean switching clients. The mihomo core supports Shadowsocks, VMess, VLESS, Trojan, Hysteria2 and other mainstream proxy protocols in a single config — nodes of different protocols can live in one group and be swapped freely with zero extra steps. Imported subscriptions have their protocol fields recognized automatically; for hand-added nodes, just follow each protocol's field names in the proxies section without worrying about internals.

Platforms

Get the Client for Your Platform

Each of the five platforms maintains its own client release lineup and system requirements: Clash Verge Rev and ClashX Meta lead on desktop, while mobile splits into direct APK installs and store distribution — click through to the download page's matching section to pick a version.

Windows

Windows 10 and later, x64 / ARM64. Clash Verge Rev is the go-to pick, with a full GUI and TUN toggle — ideal for daily desktop and laptop use.

Go to Download

macOS

Both Intel and Apple Silicon. ClashX Meta lives in the menu bar and starts at login — lightweight and unobtrusive for long-running background use.

Go to Download

Android

Direct-install ARM64 / ARMv7 APK, no store account needed. Runs as a VPN service to capture all traffic, covering both new and older devices.

Go to Download

iOS

Distributed through the App Store; requires an overseas-region account. Stash and similar clients accept Clash configs, on both iPhone and iPad.

Go to Download

Linux

deb packages and core binaries. Desktop distros can run the GUI client; servers and soft routers run the mihomo core directly under systemd.

Go to Download
Quick Start

Get Connected in Three Steps

The full tutorial covers every action with screenshots plus common error fixes; here's just the core sequence — follow it in order to get up and running, and jump to the matching tutorial chapter if any step blocks you.

Step01

Import Your Subscription

Paste the subscription link from your provider into the client's config page to pull in every node and routing rule; once imported, that config is automatically set as active, and an auto-update interval saves you future maintenance.

Step02

Pick a Mode and Node

Stay on Rule mode day-to-day so local and overseas traffic split automatically, switching to Global only when needed; on the Proxies page, select a node group, test latency in bulk and pick a low, stable node — or let a url-test group choose for you.

Step03

Connect and Verify

Turn on the system proxy toggle, load an overseas webpage to confirm connectivity, and watch the connections panel to see traffic hitting the expected rules; terminal users should also set environment variables and check requests really pass through the local listening port.

Open Source

Open-Source Ecosystem & Verifiable Sources

The Clash ecosystem is maintained long-term by the community: the original Clash project grew in the open from 2018, and after the original repository was archived the community carried the torch — mihomo (formerly Clash Meta) extended the core and is now the de facto primary engine. The core, rule sets and every platform client have publicly available source code and commit history, with a transparent release cadence.

Source07

On-Site Core Source Mirror

The current primary core, mihomo, is released under an open-source license — anyone can review the code, track changes and build it themselves. The core ships on a steady stable-release cadence, and every change to protocol support or rule formats comes with public commits and release notes; this site's download page updates its installers in step with core releases. We also host a synced mirror of the core source — copy the command below to clone and check it:

git clone --depth 1 https://clashxxx.com/git/mihomo.git
Ecosystem08
  • Core source is public, builds are reproducible, and releases can be verified against source
  • Rule sets and the GEOIP database are community-built, updated as the network landscape shifts
  • Clash Verge Rev, ClashX Meta and the other five-platform clients ship in sync with core releases
  • Config files are plain-text YAML — routing behavior is auditable line by line, no hidden logic
  • Founded in 2018, carried on by the community after the original repo was archived — the ecosystem never stopped
FAQ

Frequently Asked Questions

The four questions newcomers ask most, each answered in one line with a link to the relevant page — see the tutorial and handbook for anything deeper.

Q1

Clash for Windows is discontinued — what now?

Switch to the community-maintained Clash Verge Rev; configs and subscriptions are fully compatible, available in the Windows section of the download page. Go to downloads

Q2

Proxy is on but pages won't load?

Batch-test latency and switch to a working node first, then check the system proxy port and browser-extension conflicts following the checklist article. See the checklist

Q3

Rule mode or Global mode?

Keep Rule mode for automatic routing day-to-day; switch to Global only when all traffic must go through the proxy temporarily. About modes

Q4

Where does the subscription link come from?

From your provider — copy it into the client's config page to import; the full import and update flow is covered in the tutorial. Import guide

Download Clash Client