CLIENT PACKAGE RACK
Confirm your operating system and CPU architecture first, then open the matching platform section. Desktop and mobile users should choose a GUI client; servers, routers, and command-line environments should use the Mihomo core.
PLATFORM SELECTOR
Platform tabs are reflected in the address bar. Copy a link with its platform anchor and reopening the page will return to the same category.
WINDOWS OUTPUT
Designed for common Windows 10 and Windows 11 desktops. The current download options focus on x64 installers. Close other proxy clients before installation to prevent an old process from occupying the system proxy port.
A good choice for first-time installation and everyday subscription management. After installation, paste the subscription URL into the configuration section, update the configuration, and choose a proxy group. To route traffic from apps that ignore the system proxy, enable TUN mode when required.
Offers configuration management, proxy group selection, and system proxy controls. It suits users familiar with subscription updates and routing modes. Before importing an old configuration, check its override scripts, port fields, and TUN settings against the current system.
Suitable for users who want a similar workflow across desktop operating systems. The installer writes to the standard application directory; the archive is useful for temporary testing, but you must manage its configuration directory and startup behavior yourself.
Provides desktop configuration management and proxy switching. When migrating an existing subscription, importing only the subscription URL usually makes troubleshooting easier. Copying the entire configuration directory also requires checking the core path, overrides, and local ports.
The archived installer is retained mainly for restoring older devices, migrating configurations, and checking historical setup details. Do not build new workflows around this client. Before migrating, record the subscription URL, mixed port, system proxy status, and overrides.
| Check | Recommendation | Why it matters |
|---|---|---|
| System version | Windows 10 or Windows 11 | Newer system components and network interfaces work better with current clients. |
| CPU architecture | x64 | The desktop installers in this section primarily target 64-bit systems. |
| Installation permissions | Approve prompts from the system | TUN drivers, service installation, and firewall rules may require administrator privileges. |
| Port conflicts | Close older proxy clients | Multiple clients listening on the same port can prevent startup or traffic takeover. |
MACOS OUTPUT
Open About This Mac from the Apple menu and check the chip type. Apple M-series hardware uses the ARM64 or Apple Silicon option; Intel processors use the x64 or Intel option. Choosing the wrong architecture may prevent the app from opening or require an extra compatibility layer.
Provides Apple Silicon and Intel installers. On first launch, follow macOS prompts to authorize the app. After importing a subscription, update the configuration first and check the system proxy; configure TUN permissions only if you need broader traffic coverage.
Suitable for desktop setups that need configuration overrides, proxy group management, and TUN controls. After installation, move the app to the Applications folder and follow the security prompts on first launch. Disable the old client before migrating its configuration.
The workflow is similar to versions on other platforms, making it suitable for users managing several devices. After installing the DMG, verify that the subscription updates successfully before enabling the system proxy. Follow macOS System Settings when permission prompts appear.
Retained for migrating older configurations and checking historical menu bar workflows. Before switching, disable the system proxy and fully quit the old process, then import the subscription again. Do not let two clients modify the same system proxy settings at once.
| Check | How to choose | Next steps |
|---|---|---|
| Chip type | Check Apple or Intel in About This Mac | Choose ARM64 for Apple M-series hardware and x64 for Intel. |
| Application directory | Drag the app into Applications | Launching from a standard directory keeps permissions and updates consistent. |
| Network permissions | Follow the System Settings prompts | System proxy and TUN routing use different permission scopes. |
| Old client | Disable the proxy and quit completely | Prevents a menu bar process from continuing to overwrite proxy settings. |
ANDROID OUTPUT
Most Android phones released in recent years use arm64-v8a. Older 32-bit devices may require armeabi-v7a. If you cannot identify the architecture, check a device information tool or choose a universal installer when available.
For common 64-bit Android phones and tablets. After installation, import the subscription, allow the system to create a VPN connection, and choose the required proxy from the proxy group. Battery-saving settings may stop background connections, so adjust them for your device.
Provides ARM64, 32-bit ARM, and universal installers. If you know the device ABI, choose the matching architecture; otherwise use universal. After importing the subscription, confirm that the configuration loaded successfully before granting Android VPN access.
Provides ARM64, 32-bit ARM, and x86_64 packages. Phones and tablets usually use ARM64; older devices use ARM; Android emulators and some x86 devices use x86_64. After installation, approve the VPN connection request.
For users who need an Android GUI and rule configuration controls. After installation, import a supported configuration format, verify proxy and DNS settings, and allow the system to establish a VPN connection. Configuration fields depend on the client’s actual support.
| Check | Common choice | Details |
|---|---|---|
| Device ABI | arm64-v8a | Most recent phones and tablets use 64-bit ARM. |
| Older devices | armeabi-v7a | Choose this only when the device uses a 32-bit ARM environment. |
| Architecture unknown | Universal | The file is usually larger but supports a wider range of device architectures. |
| Background operation | Check battery-saving and background restrictions | When the system limits background activity, the proxy connection may be terminated. |
IOS OUTPUT
Install Clash Plus on iPhone and iPad through the App Store. Open the client after installation, add the configuration using the method provided by your subscription service, and allow the VPN configuration when prompted. Choose proxy groups and update subscriptions inside the client.
For subscription management, proxy group selection, and VPN routing on iPhone and iPad. After installation, add the subscription URL and update it, confirm the configuration is working, then choose a proxy group. iOS will request authorization the first time it creates a VPN configuration.
Official site: clashplus.io
| Step | Action | Expected result |
|---|---|---|
| Install the app | Open the App Store listing | Complete the standard store installation process. |
| Add a configuration | Import the subscription URL | The subscription appears in the configuration list and can be updated. |
| Establish a connection | Allow VPN configuration | The system status area shows the VPN connection status. |
| Background stability | Check the system network status | Switch between Wi-Fi and cellular data and confirm the connection recovers. |
LINUX OUTPUT
This section targets common x86_64 desktop distributions. Debian, Ubuntu, and derivatives typically use DEB; Fedora, RHEL, and compatible distributions typically use RPM. For servers and routers, see the Mihomo core section.
Suitable for common Linux desktop environments. Choose DEB or RPM according to your distribution’s package management system. After installation, confirm the desktop session, system proxy interface, and required permissions before importing a subscription. TUN mode also requires checking kernel modules and routing.
Provides DEB, RPM, and AppImage options. Prefer the format that matches your distribution’s package manager. AppImage suits desktops that should not modify the system package database, but you must manage execution permissions, file location, and the launch entry yourself.
| Check | Choose | Details |
|---|---|---|
| Distribution package format | DEB or RPM | Using the native package manager makes removal and dependency handling easier. |
| CPU architecture | AMD64 / x86_64 | The GUI client options here target common 64-bit desktop processors. |
| Desktop session | Confirm tray and system proxy support | Tray behavior and proxy interfaces vary between desktop environments. |
| TUN permissions | Check service permissions and routing | Starting the interface alone cannot resolve kernel module or routing conflicts. |
MIHOMO CORE BAY
For servers, routers, containers, and command-line environments. The core does not provide a complete desktop interface; you must prepare YAML configuration, startup arguments, service management, and log-checking procedures yourself. Typical desktop and mobile users should use the GUI clients above.
| System | CPU architecture | Format | Best for | Download |
|---|---|---|---|---|
| Windows | AMD64 | ZIP | 64-bit Windows command-line and service environments | Download AMD64 |
| Windows | ARM64 | ZIP | Windows on ARM devices | Download ARM64 |
| macOS | Intel x64 | GZ | Command-line environments on Intel processors | Download Intel |
| macOS | Apple Silicon | GZ | Apple M-series processors | Download ARM64 |
| Linux | AMD64 | DEB | Debian, Ubuntu, and compatible systems | Download DEB |
| Linux | AMD64 | GZ | Servers, containers, and manual service deployments | Download AMD64 |
| Linux | ARM64 | GZ | 64-bit ARM servers and routers | Download ARM64 |
| Linux | ARMv7 | GZ | 32-bit ARMv7 routers and embedded devices | Download ARMv7 |
| Linux | MIPS softfloat | GZ | MIPS routers using the soft-float ABI | Download MIPS |
CONFIG
Mihomo requires a readable YAML configuration before startup. At minimum, check ports, mode, DNS, proxy nodes, proxy groups, and rules. Indentation errors, misspelled fields, or references to missing proxy groups will prevent loading.
SERVICE
Use system services or container orchestration to manage startup, stopping, and restarts on servers. Run a syntax check before reloading after configuration changes. Record log paths and the runtime user’s permissions during deployment.
ROUTING
TUN, transparent proxying, and DNS hijacking involve system routes, firewalls, and permissions. Confirm the traffic entry point first, configure DNS next, and then check rule matches. Do not enable overlapping routing methods at the same time.
INSTALL SEQUENCE
A completed client installation only means the program can start. You still need to configure the subscription URL, proxy groups, traffic mode, and system permissions one by one.
On desktop systems, first confirm that the app launches normally; on mobile systems, allow VPN configuration when prompted. TUN mode also requires driver, service, or network extension permissions. Do not run multiple proxy clients at this stage.
Paste the subscription URL into the Configuration, Subscription, or Profiles section. These URLs often contain long paths and parameters, so copy them in full. Run one manual update after importing and confirm there is no format or network error.
Open the proxy groups and confirm that all groups referenced by the rules were created. Rule mode is generally best for everyday use; Global mode sends all traffic through the selected proxy; Direct mode is mainly useful for checking whether client routing affects the local network.
Use the system proxy first for browsers and desktop apps that respect system proxy settings. Consider TUN for games, command-line tools, or apps that ignore the system proxy. The two methods differ in permissions, DNS paths, and traffic coverage.
After confirming that the current configuration loads normally, set the subscription auto-update interval. Automatic updates only fetch the configuration again; they do not replace proxy selection or permission checks. Review the proxy groups after configuration changes to ensure they were not reset.
DOWNLOAD FAQ
These questions cover architecture choices, configuration imports, legacy client migration, and core usage. If the client starts but cannot connect, troubleshoot subscription updates, proxy groups, and traffic routing in that order.
Open the Help CenterFor a typical Windows 10 or Windows 11 desktop, start with Clash Plus. If you need a different interface or configuration workflow, compare Clash Verge Rev, FlClash, and Clash Nyanpasu. Clash for Windows is no longer maintained; its archived installer is mainly for restoring legacy environments and migrating configurations.
Before switching clients, disable the old client’s system proxy and fully quit its process. Record the existing subscription URL, local ports, overrides, and TUN status, then restore them one by one in the new client. Copying the entire configuration directory may also carry over obsolete paths and core settings.
Open the Apple menu, select About This Mac, and check the chip or processor field. If it shows Apple M1, M2, M3, or another Apple M-series chip, choose the ARM64 or Apple Silicon installer; for Intel, choose the x64 or Intel installer.
Move the app to the Applications folder after installation and follow the system prompts for first-launch permissions. If the architecture does not match the device, the app may fail to run or require a compatibility layer, so confirming the chip type before downloading is safer.
Most recent Android phones use arm64-v8a, so ARM64 is usually the right choice. Older 32-bit devices use armeabi-v7a. x86_64 is mainly for some emulators and a small number of specialized devices. If the ABI is unknown and a universal package is available, use universal.
After installation, allow the system to create a VPN connection. If the connection frequently stops after the screen locks, check battery-saving policies, background activity limits, and network switching settings. The names of these controls vary by device manufacturer.
The installer contains only the program, not your personal subscription configuration. After installation, import a valid subscription URL in the configuration section, update it, confirm that the proxy groups were created, and then choose the system proxy or TUN mode to route traffic.
If the subscription update fails, check that the URL is complete, the device time is correct, and the current network can reach the subscription URL. If the configuration updates but the app has no traffic, check the proxy group, system proxy status, TUN permissions, and DNS settings.
Existing installations can still be used for short-term compatibility checks and configuration migration, but both projects are no longer maintained. On new devices, prefer a client that is still updated. Keeping legacy clients long term increases the risk of compatibility issues after system updates.
Do not enable the system proxy in both the old and new clients during migration. Export or record the subscription URL and overrides, close the old client, then install the new client and import them again. Delete the old configuration directory only after the connection works normally.
The Mihomo core is better suited to servers, routers, containers, and command-line environments. It requires you to manage YAML configuration, startup arguments, service permissions, logs, and updates yourself. The core file alone does not provide a complete desktop subscription management interface.
Typical Windows, macOS, Android, and iOS users should choose the GUI clients above. For deployment on a software router or server, select the matching core file based on the operating system, CPU architecture, and package format.