Clash Plus
Ideal for users who want to quickly import subscriptions, switch rule modes, and control the system proxy through a centralized GUI.
- Install type: x64 installer
- Best for: Everyday desktop use
Confirm your operating system and CPU architecture first, then choose the matching installer. For everyday use, choose a client with a graphical interface; servers, routers, and automated environments can use the Mihomo core directly.
Windows clients
For Windows 11 and supported Windows 10 devices, use the 64-bit installer. After installation, import a subscription and enable the system proxy or TUN mode as needed.
Ideal for users who want to quickly import subscriptions, switch rule modes, and control the system proxy through a centralized GUI.
A full desktop interface for subscriptions, proxy groups, rules, logs, and system proxy settings—well suited to users who need detailed runtime information.
A cross-platform GUI client with a consistent interface and workflow across operating systems, suitable for users managing both computers and mobile devices.
Provides a desktop GUI and common proxy controls as another Windows client option.
A classic desktop client with an archived installer for older configurations or migrating an existing setup. For new installations, choose a client that is still being updated.
| Item | Recommendation | Details |
|---|---|---|
| Operating system | Windows 10 / 11 64-bit | Keep system patches and the WebView runtime components available and up to date. |
| Processor | x86-64 | The primary Windows GUI installers on this page target 64-bit Intel and AMD processors. |
| Permissions | Installs with standard permissions; some modes require elevation | Windows may request administrator approval when enabling TUN or service mode, or changing certain network settings. |
macOS clients
Check the chip type in About This Mac before downloading. Choose Apple Silicon for M1, M2, M3, and M4 models; choose Intel for older Intel Macs.
Provides subscription import, policy switching, and system proxy controls, with separate installers for Apple Silicon and Intel Macs.
Suitable for desktop users who need to inspect rules, proxy groups, and runtime logs. Both architecture downloads in this list are maintained through the same download service.
A cross-platform client for users who want a similar workflow across macOS, Windows, and Android.
A menu bar macOS client with an archived download for migrating older setups. For new configurations, use a GUI client that is still maintained.
| Item | How to choose | Details |
|---|---|---|
| Chip | Apple Silicon or Intel | Check the chip or processor name in About This Mac from the Apple menu. |
| Installation | Open the DMG and move the app to Applications | The first launch may show prompts for network extensions, VPN configuration, or system proxy permissions. |
| Background operation | Allow required login items and network permissions | If you need the app to launch at login or keep the proxy active reliably, review the related permissions in System Settings. |
Android clients
Recent phones and tablets typically use ARM64. After installation, Android requests VPN permission on the first connection; background reliability also depends on the device’s battery optimization settings.
Designed for mainstream 64-bit Android devices, with subscription management, policy selection, and system VPN interception controls.
A commonly used Android client with ARM64, ARM, and universal installers for precise architecture matching.
A cross-platform GUI client for users who want a similar configuration workflow on computers and Android devices.
An Android rule-based proxy client that imports compatible configurations and routes traffic through the system VPN interface as an alternative option.
| Item | Recommendation | Details |
|---|---|---|
| Architecture | ARM64 preferred | Most recent devices use ARM64; older 32-bit devices can try ARM, while universal is the fallback when the architecture is unknown. |
| Connection permissions | Allow VPN connection requests | Android displays a system authorization dialog the first time a proxy is started. |
| Background operation | Exclude from battery optimization | If the connection drops after the screen locks, allow the client to run in the background under Battery settings. |
iPhone and iPad
Clash Plus is available through the App Store. After installation, import a subscription and follow the system prompts to add a VPN configuration, then choose rule modes and proxy groups in the client.
A GUI client for iPhone and iPad with subscription import, proxy group switching, rule modes, and connection controls. App details and support are available at clashplus.io.
| Item | Requirement | Details |
|---|---|---|
| Device | iPhone or iPad | Open the app listing in the App Store on your device and install it. |
| Network permissions | Allow VPN configuration | This system prompt is used to establish a local proxy connection. |
| Configuration source | Subscription URL or compatible configuration file | After installing the client, you still need to import a valid configuration of your own. |
Linux desktop
Desktop environments can use DEB, RPM, or AppImage. Servers and routers typically do not need a GUI client; see the Mihomo core section below.
Suitable for common Linux desktop distributions, with Debian-based and RPM-based packages plus subscription, rule, and log interfaces.
A cross-platform desktop client offering DEB, RPM, and AppImage packages for AMD64 Linux desktop environments that need flexible installation options.
| Distribution | Package format | Installation notes |
|---|---|---|
| Debian / Ubuntu and derivatives | DEB | Use the system software installer or install the local file with a package-management command. |
| Fedora / RHEL family distributions | RPM | Install through the system software center or an RPM package-management tool. |
| Other desktop distributions | AppImage | Grant the file execute permission, run it, and configure the system proxy according to your desktop environment. |
Command-line and service environments
The Mihomo core is intended for servers, software routers, containers, and environments with an existing management panel. It does not provide a complete desktop GUI, so prepare a configuration file and start it through the command line, systemd, or a device management panel. Everyday computer and phone users should choose a GUI client above.
| Operating system | Architecture | Format | Use case | Download |
|---|---|---|---|---|
| Windows | AMD64 | ZIP | Common 64-bit Intel or AMD computers and servers | Download AMD64 |
| Windows | ARM64 | ZIP | Windows on ARM devices | Download ARM64 |
| macOS | Intel | GZ | Intel-based Macs | Download Intel |
| macOS | Apple Silicon | GZ | Apple Silicon Macs, including M1, M2, M3, and M4 | Download ARM64 |
| Linux | AMD64 | DEB | Debian, Ubuntu servers or desktop systems | Download DEB |
| Linux | AMD64 | GZ | General 64-bit server deployments | Download AMD64 |
| Linux | ARM64 | GZ | 64-bit ARM servers, development boards, or routers | Download ARM64 |
| Linux | ARMv7 | GZ | Some 32-bit ARM development boards and embedded devices | Download ARMv7 |
| Linux | MIPS softfloat | GZ | Specific routers using soft-float MIPS architecture | Download MIPS |
After extracting it, start the core from the command line with a configuration directory or file. For long-running deployments, Linux commonly uses systemd to manage the process, with configuration, logs, and executables stored in stable paths. Router environments are usually handled by the device management panel or startup scripts.
The core requires parseable YAML, typically containing ports, mode, DNS, proxy nodes, proxy groups, and rules. Keep a known-good configuration before updating; after changes, review startup logs before routing system traffic through it.
Choosing an installer
A single client may offer several files with the same general features. The main differences are the operating system, CPU architecture, and installation method. Choosing incorrectly may cause the system to reject the installation or fail to launch.
Download questions
These questions focus on client selection, CPU architecture, core usage, and first-time connections. For fuller configuration and troubleshooting, continue to the tutorials and troubleshooting guides on this site.
Choose the GUI client marked as a top pick or recommendation in the section for your operating system. GUI clients include subscription import, system proxy, proxy groups, and logs, making them better suited to everyday desktop and mobile use. Download the Mihomo core directly only when running on a server, router, or existing management panel.
For Macs with M1, M2, M3, or M4 chips, choose Apple Silicon or ARM64; for older Intel Macs, choose Intel or x64. Open About This Mac from the Apple menu to check the chip or processor name. If the app installs but will not launch, verify the selected architecture again.
Most recent Android phones use ARM64, usually shown as arm64-v8a in filenames. Older 32-bit devices can use ARM or armeabi-v7a; when the architecture is unknown, choose the universal installer. x86-64 is mainly for a small number of specific devices or emulated environments.
GUI clients combine the core, subscription management, policy selection, system proxy controls, and log viewing in one interface. The Mihomo core mainly runs through configuration files, the command line, or a service manager, making it suitable for servers, routers, and automated environments. Most computer and phone users do not need to manage core files separately.
Client installers do not include a working subscription. After installation, import the subscription URL provided by your service provider or a local configuration file, wait for it to parse successfully, then choose a proxy group and enable the system proxy, VPN connection, or appropriate interception mode. If loading fails, check the specific message in the client logs first.