Clash Plus
A GUI client for everyday desktop use, with convenient access to configuration imports, rule modes, the system proxy, and TUN. A good fit for Windows users who want one interface for installation and basic setup.
Choose a client by operating system, processor architecture, and installation method. Desktop users can choose Clash Plus, Clash Verge Rev, or FlClash; Android offers native clients and multi-architecture packages; servers and routers can use the Mihomo core directly.
Confirm the operating system first, then check the processor architecture and installer format. Platform labels support direct links, so copying the current URL preserves the selected platform.
For x64 desktop systems running Windows 10 or Windows 11. Close any older version before installation, and follow the system prompts for network and firewall permissions on first launch.
| Recommended system | Windows 10 / 11 |
|---|---|
| Processor | x64 |
| Common format | EXE installer |
A GUI client for everyday desktop use, with convenient access to configuration imports, rule modes, the system proxy, and TUN. A good fit for Windows users who want one interface for installation and basic setup.
A desktop client built around the Mihomo ecosystem, with comprehensive configuration editing, proxy group switching, rule inspection, and service-mode controls. Suitable for users who want finer control over TUN, DNS, and rule behavior.
Available for Windows, macOS, Linux, and Android, with a broadly consistent interface and workflow across platforms. Windows users can choose an installer or keep the archive for manual directory management.
A desktop Mihomo client with configuration management, proxy group selection, connection history, and rule inspection. Suited to users familiar with Clash configuration structure who want a different desktop workflow.
A classic Windows client provided as an archived release. Useful for opening legacy configurations or preserving an existing workflow; for new installations, prefer Clash Plus, Clash Verge Rev, or FlClash, which are still maintained.
Choose ARM64 for Apple Silicon Macs and x64 for Intel Macs. After downloading the DMG, move the app to Applications and follow system prompts to grant network extension or proxy permissions.
| Recommended system | Recently maintained macOS versions |
|---|---|
| Processor | Apple Silicon / Intel |
| Common format | DMG disk image |
Provides Apple Silicon and Intel installers for managing subscriptions, configuration files, proxy modes, and the system proxy through a GUI. Confirm your Mac's chip type before downloading.
For macOS users who need to inspect rules, edit configurations, and adjust Mihomo options. The two architecture entries are resolved from the release list, so confirm your Mac's chip type before installation.
Keeps a similar interface across platforms, making it suitable for users who work across Mac, Windows, and Android devices. The architecture buttons currently map to download files through the release list.
An archived macOS menu bar client retained for legacy configurations and established workflows. For new installations, prefer a maintained client for broader system compatibility.
Recent phones and tablets generally use ARM64. Older 32-bit devices use ARM; if the processor architecture is unknown, choose the universal Clash Meta for Android package.
| Recommended system | Android 8 or later |
|---|---|
| Common architectures | ARM64 |
| Package format | APK |
For mainstream 64-bit Android devices, with subscription import, configuration switching, proxy group selection, and connection controls. Most phones released in recent years can use the ARM64 version.
An Android Mihomo-based client offering ARM64, 32-bit ARM, and universal packages. Use the matching build when the device architecture is known; otherwise choose the universal version.
Uses an interface structure similar to the desktop versions, making it suitable for managing Clash configurations across multiple systems. Offers ARM64, 32-bit ARM, and x86_64 packages.
An Android rule-based proxy client suited to compatible configurations and mobile proxy group management. The universal package provided here covers common Android device architectures.
iPhone and iPad users can get Clash Plus from the App Store. After installation, allow the system prompt to create a VPN configuration, then import a valid subscription or configuration file.
| Supported devices | iPhone / iPad |
|---|---|
| How to get it | App Store |
| Configuration source | Subscription URL or configuration file |
A proxy configuration client for iPhone and iPad, supporting configuration imports, proxy group switching, and connection management. Install it from the App Store; product details and usage guidance are also available on the official website.
Desktop environments can use DEB, RPM, or AppImage. Debian, Ubuntu, and derivatives generally use DEB; Fedora, RHEL, and related distributions generally use RPM.
| Common architectures | AMD64 / x86_64 |
|---|---|
| Package | DEB / RPM / AppImage |
| Environment | Linux desktop |
A Mihomo GUI client for Linux desktop users. Provides AMD64 DEB and RPM packages; after installation, launch it from the desktop menu to manage configurations, rules, and proxy groups.
Provides three AMD64 desktop formats: DEB, RPM, and AppImage. Choose DEB or RPM for package-manager maintenance, or AppImage for standalone execution.
The standalone Mihomo core is intended for servers, routers, gateway devices, containers, and command-line environments. Most desktop and mobile users should choose a GUI client above, which already includes configuration management, proxy group switching, and system integration.
| System | Architecture | Format | Use case | Download |
|---|---|---|---|---|
| Windows | amd64 |
ZIP | Common Windows servers and x64 devices | Download |
| Windows | arm64 |
ZIP | Windows on ARM devices | Download |
| macOS | amd64 |
GZ | Intel-based Macs | Download |
| macOS | arm64 |
GZ | Apple Silicon Mac | Download |
| Linux | amd64 |
DEB | Debian, Ubuntu, and related distributions | Download |
| Linux | amd64 |
GZ | Generic Linux x64 binary | Download |
| Linux | arm64 |
GZ | 64-bit ARM servers and development boards | Download |
| Linux | armv7 |
GZ | 32-bit ARMv7 devices | Download |
| Linux | mips-softfloat |
GZ | MIPS softfloat embedded devices | Download |
Archives usually contain a single core executable. After extracting it, prepare a configuration file, set the executable permission, and specify the configuration directory through terminal arguments. For long-running services, use systemd, container orchestration, or the device's service manager.
Mihomo supports Clash-style YAML configuration and extends it with rule sets, DNS, TUN, and additional protocol capabilities. When migrating an older configuration, check field compatibility first, then use startup logs to locate unrecognized options.
Downloading is only the first step. Choose the correct architecture, complete system authorization, and import a valid configuration before the client can be used.
Windows desktops generally use x64; Macs require a choice between Apple Silicon and Intel; recent Android devices are mostly ARM64. A mismatch commonly causes installation failure, an app that will not open, or an incompatible-package warning.
For a first installation, choose a GUI client that is still maintained. The interface centralizes subscription imports, proxy groups, rule modes, the system proxy, and the TUN switch, reducing manual startup-argument and background-process management.
Windows may show firewall and service permission prompts; macOS may ask you to approve a network extension; Android and iOS request permission to establish a VPN connection. These permissions route system traffic through the client and should match your intended proxy method.
The installer does not include a ready-to-use proxy configuration. After launch, import a valid subscription or YAML file, update it, choose a proxy group, and confirm whether the current mode is rule-based, global, or direct. Configure TUN according to the guide when more app traffic needs to be handled.
These questions cover platform selection, processor architecture, configuration imports, and standalone core usage. Expand an item to view the recommended steps.
Most Windows users can start with Clash Plus. Choose Clash Verge Rev for desktop rule management and Mihomo features, or FlClash for a consistent interface across platforms. Clash for Windows is no longer maintained and is intended only for legacy configurations and archival use.
Macs with Apple chips such as M1, M2, M3, or M4 should use the Apple Silicon or ARM64 installer; older Intel Macs should use the x64 or Intel installer. Open About This Mac to check chip or processor information. If both entries map to the same file, follow the release notes and verify that it runs on your Mac.
Recent Android phones and tablets usually use ARM64. Older 32-bit devices can use ARM; choose the universal build if the architecture is unknown. Universal builds cover more processors and are usually larger. Emulators or some x86 devices can use an explicitly provided x86_64 version.
The client does not include a ready-to-use proxy configuration. After installation, import a valid Clash configuration file or subscription URL, then choose a proxy mode and proxy group. If the browser connects but other apps do not, check the system proxy, TUN mode, app-specific proxy settings, and rule matching.
Usually not. Desktop and mobile GUI clients already include the core and management interface they need. The standalone Mihomo core is mainly for servers, routers, gateway devices, containers, and users who manage configuration directories, startup arguments, and service processes themselves.
First confirm that the operating system version, processor architecture, and installer format match. On Windows, check old client processes, system permissions, and firewall prompts; on macOS, check the chip type and security alerts; on Linux, confirm the package system, executable permissions, and desktop dependencies. If an upgrade fails, fully exit the old version before running the installer again.
Continue with the complete workflow for importing subscriptions, choosing a proxy mode, enabling the system proxy, and checking the connection.