This page lists Clash GUI clients for Windows, macOS, Android, iOS, and Linux. Confirm your operating system first, then choose a package matching your processor architecture. For servers, software routers, and command-line environments, see the Mihomo core section.
The platform tag is synced to the address bar, so you can share the current URL for that platform. Client cards are ordered by recommendation; the primary button offers the most common architecture, while other architectures appear in the same card’s secondary options.
Most Windows 10 and Windows 11 devices use the x64 package. After installation, import your subscription and enable the system proxy or TUN mode as needed. When migrating from an older client, export your configuration first and note the local port.
Windows GUI client for first-time installation
Includes subscription import, rule mode, system proxy controls, and common connection settings. The installer creates standard application shortcuts, making it suitable for users who prefer configuring everything through the interface.
Desktop configuration and rule management client
The interface covers subscriptions, proxy groups, rules, connection history, and system proxy settings. It suits users who need to inspect rule matches, switch proxy groups, or fine-tune Mihomo settings.
Cross-platform GUI client with a consistent interface
Windows, macOS, Linux, and Android share a similar interface structure, making it easier to keep the same workflow across devices. The installer is convenient for daily use, while ZIP is useful for manually managing the program folder.
Clash client for desktop environments
Provides subscription management, proxy group selection, connection monitoring, and configuration editing. It suits desktop users who understand rule modes and proxy groups and want to manage configurations in one place.
Retained for legacy configuration migration and compatibility
This client is no longer actively maintained. The installer remains available so users with legacy configuration folders can complete migration. For new installations, choose one of the maintained GUI clients above.
Check your Mac’s chip type before downloading. M1, M2, M3, M4, and later M-series chips use Apple Silicon; Macs showing an Intel processor need the Intel build. The first launch may ask you to approve network extension or proxy permissions.
macOS GUI client for everyday use
Provides Apple Silicon and Intel packages. After importing a subscription, select a rule mode and enable the system proxy in the client. A practical choice for getting started with basic configuration.
Mihomo configuration and proxy group management client
A good fit for macOS users who manage multiple subscriptions, review connection history, edit configuration overrides, or use TUN mode. After installation, follow macOS prompts to move the app and approve permissions.
Consistent cross-platform workflow
Suitable for users who switch between Mac, Windows, and Android. Subscriptions, proxy groups, and settings are organized similarly across systems, making features easier to find when changing devices.
Retained for existing macOS configurations
This client is no longer actively maintained and is intended for restoring legacy configurations or completing migration. For new installations, choose a maintained client with a clear core management interface.
Recent Android phones and tablets usually use ARM64. Older 32-bit devices can use ARM; choose Universal if you cannot identify the architecture. After installation, import a subscription, allow the client to create a VPN connection, and select a rule mode.
GUI client for recent Android devices
The primary download is an ARM64 package covering most current Android phones and tablets. On the first connection, approve Android’s VPN permission request, then switch proxy modes in the client as needed.
Android client based on the Meta feature set
Provides ARM64, ARM, and Universal packages for users who need compatibility across Android architectures. Choose Universal when the processor is unknown; it is typically larger than a single-architecture package.
Android client with a consistent cross-platform interface
A good choice for users who also run FlClash on desktop. ARM64 covers most newer devices, ARM suits some older devices, and x86_64 is mainly for matching emulators or a small number of devices.
Android rule-based proxy client
Designed for Android users familiar with configuration files and rule-based routing. Import a working configuration after installation and choose proxy groups based on its contents. If rules do not apply, check connection logs and DNS settings first.
On iOS, install Clash Plus from its App Store page. After installation, import a subscription; iOS will request permission to add a VPN configuration when the first connection is established. Once approved, switch between rule, global, and direct modes in the client.
iOS client available on the App Store
For iPhone and iPad, with subscription import, proxy modes, and a system VPN connection entry point. Follow the guide to add a subscription link, then approve system permissions on the first connection.
Debian, Ubuntu, and derivatives usually use DEB; Fedora, RHEL, Rocky Linux, and other RPM-based distributions use RPM. GUI clients suit desktop environments, while servers and routers should use the Mihomo core below.
Mihomo GUI client for Linux desktops
Suitable for AMD64 Linux desktops with a graphical environment. Use DEB on Debian and Ubuntu, and RPM on Fedora and RHEL-based distributions. Manage subscriptions, rules, and the system proxy from the interface after installation.
Cross-platform Linux GUI client
Provides three desktop packages: DEB, RPM, and AppImage. Prefer the native package for your distribution so it can launch from the system application menu; AppImage suits AMD64 desktops that need a standalone single-file app.
The Mihomo core is intended for servers, routers, containers, bypass gateways, and users who manage configuration files themselves. It does not include a full desktop GUI; prepare config.yaml, startup arguments, and a service management method. Desktop and mobile users should prefer the GUI clients above and usually do not need to install the core separately.
| System | Architecture and format | Use case | Download |
|---|---|---|---|
| Windows | AMD64 ZIP | 64-bit x86 Windows command-line environment | Download AMD64 |
| Windows | ARM64 ZIP | Windows on ARM device | Download ARM64 |
| macOS | Intel AMD64 GZ | Intel Mac command-line environment | Download Intel |
| macOS | Apple Silicon ARM64 GZ | M-series Mac command-line environment | Download Apple Silicon |
| Linux | AMD64 DEB | Debian and Ubuntu servers | Download DEB |
| Linux | AMD64 GZ | General x86_64 Linux environment | Download AMD64 |
| Linux | ARM64 GZ | 64-bit ARM servers, routers, and single-board computers | Download ARM64 |
| Linux | ARMv7 GZ | 32-bit ARMv7 routers and embedded devices | Download ARMv7 |
| Linux | MIPS softfloat GZ | MIPS soft-float router environment | Download MIPS |
At minimum, prepare a configuration file recognized by the current Mihomo version and confirm the proxy port, controller listen address, DNS, rule-set paths, and data directory. Server deployments commonly use systemd, container orchestration, or router service scripts to manage startup and restarts.
GUI clients handle subscription updates, core startup, configuration directories, system proxy settings, and log display, making connection issues easier to troubleshoot. Running the core directly requires manually maintaining configuration paths and startup arguments and is better suited to users familiar with Clash configuration structure.
The same operating system name does not guarantee the same processor architecture. Spend a minute checking the OS version, CPU architecture, and package format before downloading to reduce installation failures, startup errors, and unsupported-format messages.
Open “Settings → System → About” and check “System type.” If it shows an x64-based processor, choose an x64 or AMD64 package. The Windows GUI clients listed here primarily target common x64 desktop devices.
Open “About This Mac” from the Apple menu. If you see an Apple M-series chip, choose Apple Silicon or ARM64; if you see an Intel processor, choose Intel or x64. Do not identify the chip solely from the macOS version.
Most Android phones and tablets released in recent years use ARM64. Older devices may still use 32-bit ARM. Universal packages include files for more architectures, offering broader compatibility but usually taking up more space.
Ubuntu, Debian, Linux Mint, and similar distributions usually use DEB; Fedora, RHEL, Rocky Linux, and similar systems usually use RPM. AppImage runs directly, but its desktop integration and permission handling differ from native packages.
These questions cover client selection, processor architecture, package formats, and migration from legacy clients. For usage topics such as subscription updates, port settings, and TUN configuration, see the tutorials and user guide.
Most users should choose the top pick or recommended GUI client for their platform. GUIs include configuration import, proxy modes, system proxy controls, and logs, so Mihomo does not need to be downloaded separately. Windows, macOS, and Android users can start with Clash Plus; Linux desktop users can choose Clash Verge Rev.
The EXE installer suits most Windows users and creates the program folder and launch entry. ZIP is for users who manage the program folder manually; shortcuts, update folders, and configuration migration must be handled yourself. Choose EXE for a first installation.
Choose Apple Silicon for Macs with M1, M2, M3, M4, or later M-series chips; choose Intel for older Intel Macs. Check the chip or processor under “About This Mac” in the Apple menu. Choosing the wrong architecture may prevent the app from launching or require an extra compatibility layer.
Recent Android phones and tablets usually use ARM64. Older 32-bit devices use ARM. If you cannot identify the architecture, choose Universal, though it is typically larger. x86_64 is mainly for matching emulators or a small number of devices, not the usual choice for phones.
The Mihomo core is mainly for servers, routers, containers, and environments managed from the command line. GUI clients are more convenient for desktop and mobile users and usually include a compatible core while handling subscription updates, process startup, system proxy settings, and log display.
Clash for Windows is no longer actively maintained. The archived installer remains available for migrating old configurations and specific compatibility cases. For new installations, consider maintained clients such as Clash Plus, Clash Verge Rev, FlClash, or another current option. Before migrating, record your subscription URL, proxy port, and custom rules.