This page organizes Clash GUI clients for Windows, macOS, Android, iOS, and Linux, plus the Mihomo core for servers and routers. Choose your operating system first, then select a package based on processor architecture and intended use.
Labels are synced to URL anchors, so shared links open the corresponding platform directly. Version text on client cards appears only when the version list returns valid data.
Desktop users should generally choose a GUI client with an installer. After installation, import a subscription, select a proxy mode, and control the connection from the system tray.
| Item | Recommendation |
|---|---|
| System | Windows 10 or Windows 11 |
| Processor | x64 desktop processor |
| Installer format | EXE installer recommended |
Best for Windows users who want quick control over system proxy integration, subscription management, and rule switching. Its interface covers common connection tasks, making it a strong first Clash installation.
Designed for desktop users who want graphical management of configurations, proxy groups, system proxy settings, and TUN mode. A good fit for users who understand the basics of Clash and want closer visibility into rule matches and logs.
One client family covers desktop and mobile platforms, making it suitable for users who want similar workflows across devices. On Windows, choose either the installer or a ZIP package as needed.
Provides a desktop GUI and common configuration management features for users who want to compare different interface layouts. Before installing, confirm that your existing configuration files and subscription sources can be imported correctly.
A classic desktop client retained as an archived release. Existing configurations may still be reviewed or migrated, but new users should choose a maintained option such as Clash Plus, Clash Verge Rev, or FlClash.
Before downloading, open About This Mac or System Information to check whether your device uses Apple Silicon or an Intel processor. Choose based on the processor field, not just the macOS version.
| Device type | Required architecture |
|---|---|
| Apple M-series chip | ARM64 / Apple Silicon |
| Intel processor | x64 / Intel |
| Installer format | DMG disk image |
Suitable for Mac users who need subscription updates, system proxy control, and everyday policy switching. Download the DMG matching your chip, then grant the required network permissions when prompted.
Provides a full desktop interface for configuration, proxy groups, and runtime logs, making it suitable for macOS users who rely on rule mode or TUN integration. The downloads are architecture-specific, so verify your Mac's chip first.
A good choice for users working across desktop and mobile devices who want a consistent workflow. Import a subscription after installation, then switch routes from the proxy and policy group pages.
For users who need to review the legacy interface or migrate an existing configuration. For new deployments, choose a maintained client with a core and system integration suited to current macOS releases.
Android clients typically use the system VpnService to handle app traffic. After installation, allow the client to establish a VPN connection, and check battery optimization, background activity, and network behavior after the screen locks.
| Architecture | Compatible devices |
|---|---|
| ARM64 | Most recent Android phones and tablets |
| ARM | Older 32-bit ARM devices |
| Universal | Use when the architecture is unknown |
Designed for everyday proxy integration and subscription management on Android. Suitable for ARM64 phones and tablets; approve the system VPN request on first connection and allow background activity according to your device brand's settings.
An Android client built around the Clash Meta ecosystem, with configuration import, proxy group switching, runtime logs, and traffic integration. Choose the matching package when the architecture is known; use the universal build when it is not.
Suitable for users who want a similar interface on Android and desktop. ARM64, ARM, and x86_64 packages are available; check the processor architecture with a device information tool before downloading.
An Android rule-based proxy client for users who need to import compatible configurations and route traffic through the system VPN interface. The universal package supports several common Android architectures.
On iOS, use Clash Plus from the App Store for installation and updates. After installing, import a subscription, choose a policy group, and allow the VPN configuration when prompted by iOS.
| Item | Details |
|---|---|
| Devices | iPhone and iPad |
| Acquisition | App Store |
| Configuration source | Subscription URL or compatible configuration |
For proxy configuration, policy switching, and system traffic integration on iPhone and iPad. Open the app's App Store page or visit the official website for product information and usage guidance.
Linux desktop users can choose the GUI versions of Clash Verge Rev or FlClash. The current list provides AMD64 packages; for servers, routers, and other architectures, see the Mihomo core section below.
| Distribution | Recommended format |
|---|---|
| Debian / Ubuntu | AMD64 DEB |
| Fedora / RHEL family | x86_64 RPM |
| Server or router | Choose the Mihomo core by architecture |
Suitable for subscription management, rule switching, system proxy control, and log viewing on Linux desktops. Choose DEB for Debian- and Ubuntu-based systems, or RPM for distributions using RPM package management.
Provides a Linux GUI and common configuration management features for users who want a similar experience across Windows, macOS, and Android. The primary entry here is an AMD64 DEB package.
Mihomo handles rule matching, connection establishment, DNS processing, and traffic forwarding. The standalone core is intended for servers, software routers, containers, and command-line deployments; desktop and mobile users should prefer a GUI client above.
Suitable for Windows services, automation scripts, or custom control panels. Extract the ZIP archive to a fixed directory, then specify the configuration file from the command line.
Choose AMD64 for Intel Macs and ARM64 for Apple M-series Macs. After extracting the GZ file, place it in a defined working directory and grant the executable permission to run.
AMD64 is common on desktops, mini PCs, and cloud servers; ARM64 and ARMv7 are common on single-board computers and some routers. MIPS softfloat is limited to devices with the matching instruction set and floating-point ABI; the device brand alone is not enough.
| Architecture | Format | Common environments | Download |
|---|---|---|---|
| AMD64 | DEB | Debian and Ubuntu servers | Download DEB |
| AMD64 | GZ | Generic x86_64 Linux | Download GZ |
| ARM64 | GZ | 64-bit ARM servers and routers | Download GZ |
| ARMv7 | GZ | 32-bit ARMv7 devices | Download GZ |
| MIPS softfloat | GZ | Matching MIPS softfloat environments | Download GZ |
Client names may look similar, but platforms, processor architectures, and maintenance status differ. Make the checks below before downloading to reduce installation failures, startup errors, and ineffective system proxy settings.
A Windows installer cannot run on macOS, and an Android package cannot run on iPhone. Linux also requires you to distinguish between distribution package formats. If the device is for everyday browsing and app connectivity, choose a GUI client from the platform labels.
ARM64, ARMv7, AMD64, and x86_64 refer to different instruction sets or naming conventions. Newer Android devices are usually ARM64; Apple M-series Macs use ARM64; typical Intel or AMD desktop computers use x64 or AMD64.
The client runs rules and handles traffic, but the first launch still requires a subscription URL or local YAML file. After importing, update the configuration, choose a policy group and proxy mode, then check the logs to confirm that rules match as expected.
Desktop clients usually require system proxy or TUN mode. Android and iOS request permission to create a system VPN configuration. If browsers work but other apps cannot connect, check whether those apps follow the system proxy and whether TUN, DNS, and firewall settings are aligned.
Continue reading: After installation, visit Getting Started to import a subscription, choose a proxy mode, and verify the connection. For a systematic guide to rules, TUN, and routine maintenance, read the complete user manual.
These questions cover client selection, architecture checks, configuration sources, and core usage. For more on proxy modes, DNS, and connection issues, continue to the FAQ page.
Start with Clash Plus for your platform. It handles subscription import, system proxy integration, and common policy switching. For more detailed desktop rule management, compare Clash Verge Rev and FlClash. Server and router users can consider deploying the Mihomo core directly.
Most users should choose the EXE installer, which creates the application folder and shortcuts for a more direct launch workflow. ZIP is suited to users who need a portable folder and can manage application files and update locations themselves. The core purpose is the same; only installation and file management differ.
Open System Information and check the Chip or Processor field. If it shows an Apple M-series chip, choose Apple Silicon or ARM64; if it shows Intel, choose x64 or Intel. Do not guess from the Mac's purchase year, as the same product line may span different processor platforms.
Recent Android phones and tablets generally use ARM64. The ARM package targets older 32-bit devices, while the universal build offers broader compatibility when the architecture is unknown. If device information shows arm64-v8a, choose the ARM64 package.
The client reads configuration, applies routing rules, establishes connections, and handles system traffic; it does not generate subscription content automatically. After installation, import a working subscription URL or local YAML configuration. Subscription URLs, single-node links, and configuration files are different sources and cannot be used interchangeably.
Usually not. GUI clients already provide configuration management, system proxy control, policy groups, logging, and core integration. The standalone Mihomo core is mainly for servers, software routers, containers, and command-line deployments, where users manage configuration files, startup arguments, and background services themselves.