Download plate · 01
Choose a client by operating system, CPU architecture, and maintenance status. Graphical clients suit desktops and mobile devices; the Mihomo core is intended for servers, routers, and command-line environments.
Platform specimens · 02
The interface entry points may differ between clients, but the core processing path usually includes loading the configuration, matching rules, selecting proxy groups, resolving DNS, and taking over network traffic.
Windows plate
For everyday desktop proxying, subscription management, and proxy-group switching. New users should start with an EXE package that includes a setup wizard; choose a client with a ZIP package only when you need a portable deployment.
The Windows graphical clients in this section are primarily x64 builds. On Windows on ARM, first confirm compatibility with x64 desktop applications.
For Windows users who want to manage subscriptions, proxy groups, and the system proxy through a graphical interface. The setup wizard suits standard desktop environments; after the first launch, you can import a subscription URL or local configuration file.
A desktop client with Mihomo compatibility, offering configuration management, proxy-group switching, system proxy controls, and TUN-related options. Suitable for users who need to inspect connections, rules, and logs.
Offers a cross-platform interface and common configuration management features. Windows users can choose between an installer and a ZIP archive: the installer suits a fixed setup, while the ZIP is intended for portable folders or controlled deployments.
For users who prefer desktop configuration management and switching between multiple configurations. Before installation, close any other client currently controlling the system proxy to prevent competing changes.
An archived download remains available for migrating existing configurations or handling compatibility issues in legacy environments. For new installations, prefer a maintained client that supports current Mihomo configuration capabilities.
| Check | Recommendation | Why it matters |
|---|---|---|
| CPU architecture | x64 | The graphical client installers in this section are mainly intended for 64-bit Windows desktop environments. |
| Installation permissions | Allow the installer to write to the application directory | Restricted permissions can cause installation, updates, or service-component registration to fail. |
| System proxy | Close other proxy clients before enabling it | Multiple programs changing the system proxy at once can cause port conflicts or repeated state changes. |
| TUN mode | Install the required components as prompted by the client | TUN takes control of system networking and typically requires elevated permissions and the appropriate driver support. |
macOS plate
Before downloading, check the chip type in About This Mac. Choose Apple Silicon or ARM64 for Apple M-series chips; choose Intel or x64 for Intel processors.
After opening the DMG, move the app to the Applications folder and follow macOS security prompts to complete the first launch. Authorization may be required when enabling the system proxy or TUN.
Provides Apple Silicon and Intel installers for managing subscriptions, proxy groups, and the system proxy through a graphical interface. Select the DMG that matches your chip before downloading.
For macOS users who need to inspect proxy groups, rules, connections, and runtime logs. Select the package matching the Mac’s chip type.
Maintains a broadly consistent configuration workflow across platforms, making it suitable for users managing both desktop and mobile devices. You must still import a configuration and select a proxy group after installation.
An archived download is retained for reinstalling existing ClashX Meta setups, migrating configurations, and investigating compatibility issues. For new deployments, choose a maintained macOS client.
| Mac information | Download selection | Installation notes |
|---|---|---|
| Apple M-series chip | Apple Silicon / ARM64 | Prefer the native ARM64 build to avoid extra dependencies from a compatibility layer. |
| Intel processor | Intel / x64 | Choose the x64 DMG and move the app to the Applications folder. |
| System proxy authorization | Follow the system prompt | macOS displays an authorization prompt when the client needs to modify network proxy settings. |
| Network extension | Enable only when the selected mode requires it | Traffic interception methods such as TUN may require additional system network-extension permissions. |
Android plate
Most current devices use arm64-v8a. Older 32-bit ARM devices can use armeabi-v7a; when the architecture is unknown, use a client that offers a universal package.
If a device already has an app with the same name but a different signing source, Android may block the upgrade. Back up the in-app configuration before handling the existing installation.
For mainstream 64-bit Android devices, with a graphical interface for importing configurations, choosing proxies, and authorizing VPN interception. Confirm the system VPN request on the first connection.
An Android Mihomo-compatible client offering ARM64, 32-bit ARM, and universal packages. When the device architecture is known, choose the matching package; otherwise use universal.
Offers ARM64, 32-bit ARM, and x86_64 builds for users who want a consistent cross-platform workflow. Use the x86_64 package with emulators or the few x86 Android environments that support it.
Provides a universal Android package for users who prefer a simple configuration entry point. Before importing, confirm that the subscription or configuration format is supported by the client.
| Architecture | Typical devices | Selection guidance |
|---|---|---|
| arm64-v8a | Recent mainstream Android phones and tablets | The preferred choice for most newer devices. |
| armeabi-v7a | Older 32-bit ARM devices | Use only when both the device OS and processor are 32-bit. |
| x86_64 | Some emulators or specialized devices | Do not choose this build for ordinary ARM phones. |
| universal | Devices with an unknown architecture | Broader compatibility, but the package is usually larger. |
iOS plate
On iOS, install Clash Plus from its App Store page. After installation, import a configuration through the in-app entry point and confirm system VPN permission on the first connection.
The App Store page and official website are listed together so you can verify the app name, usage information, and follow-up documentation.
For iPhone and iPad. Install it from the App Store, then import a Clash configuration, select a proxy group, and establish a system VPN connection. The official website is clashplus.io.
| Stage | Action | Expected result |
|---|---|---|
| Install | Open the Clash Plus page in the App Store | Confirm the app name, then install it through the store’s normal process. |
| Configure | Import a subscription URL or supported configuration file | The configuration list should show selectable proxy groups. |
| Authorize | Confirm the VPN configuration request on the first connection | Test the network after the VPN status appears in the system status bar. |
| Verify | Check proxy groups, rule mode, and connection logs | Confirm that requests match the expected rules and policies. |
Linux plate
For graphical Linux desktops, choose Clash Verge Rev or FlClash. For servers, software routers, and command-line-only environments, see the Mihomo core section below.
Debian, Ubuntu, and derivatives typically use DEB; Fedora and RHEL-based distributions typically use RPM. Confirm the distribution’s package-management system before installing.
For configuration management, proxy-group switching, and system proxy control on Linux desktops. Provides AMD64 DEB and RPM packages; do not use these desktop packages on ARM routers.
Provides AMD64 DEB, RPM, and AppImage builds. DEB and RPM suit systems managed by package managers; AppImage suits desktop environments that should not write to the system package database.
| Package format | Common distributions | Before installation |
|---|---|---|
| DEB | Debian、Ubuntu、Linux Mint | Confirm the system is AMD64 and prepare to use dpkg or apt for package management. |
| RPM | Fedora and RHEL-based distributions | Confirm the system is x86_64 and use the package-management tool for the distribution. |
| AppImage | Multiple desktop distributions | Add execute permission after downloading, then launch it from the desktop session. |
| Desktop environment | GNOME, KDE, and others | System proxy integration varies by desktop environment and distribution. |
Kernel archive · 03
The Mihomo core is intended for servers, routers, containers, and command-line deployments. Ordinary desktop and mobile users should prefer the graphical clients above, which provide configuration directories, system proxy controls, logs, and update entry points.
| System | CPU architecture | File format | Typical use | Download |
|---|---|---|---|---|
| Windows | AMD64 | ZIP | Windows Server, command-line testing, and service wrapping | Download AMD64 |
| Windows | ARM64 | ZIP | Windows on ARM command-line environments | Download ARM64 |
| macOS | Intel AMD64 | GZ | Terminal use and service scripts on Intel Macs | Download Intel |
| macOS | Apple Silicon ARM64 | GZ | Terminal deployment on Apple M-series Macs | Download ARM64 |
| Linux | AMD64 | DEB | Package deployment on Debian and Ubuntu servers | Download DEB |
| Linux | AMD64 | GZ | x86_64 servers, containers, and custom service directories | Download GZ |
| Linux | ARM64 | GZ | 64-bit ARM servers and newer software routers | Download ARM64 |
| Linux | ARMv7 | GZ | 32-bit ARMv7 routers and embedded devices | Download ARMv7 |
| Linux | MIPS softfloat | GZ | MIPS routers using a soft-float ABI | Download MIPS |
Config path
On the first run, load the configuration in the foreground and watch port listeners, subscription rule sets, DNS, and proxy nodes. Once the basic configuration works, hand it over to systemd, a scheduled task, or another service manager for long-term operation. Registering a background service immediately can hide early errors and make path, permission, and configuration-syntax issues harder to locate.
Architecture
AMD64, ARM64, ARMv7, and MIPS are not interchangeable. On Linux, use uname -m to check the architecture, but router firmware may also involve ABI and floating-point differences. If the program reports a format error immediately after launch, recheck the architecture first instead of changing the configuration.
Installation notes · 04
Finishing the download does not mean the network is already under proxy control. Verify the configuration in a fixed order to separate subscription, policy, DNS, and system-proxy issues.
When migrating from an old client, first export or copy the current configuration files, local override rules, scripts, and subscription URLs. Do not delete the old directory before confirming that the new client works. Some clients use different configuration directories or override formats, so compare each item during migration instead of overwriting the entire application data directory.
The subscription URL must return a configuration structure readable by Clash or Mihomo. Run one manual update after importing and check the update log for parsing errors. If the configuration list exists but contains no proxy nodes, inspect the subscription response, configuration format, and client compatibility range.
For everyday use, start with rule mode so requests match the rules in the configuration file in order. Then open the main proxy group and select an available node or an automatic policy. Global mode sends more requests through one policy, while direct mode bypasses the proxy; during troubleshooting, identify the active mode clearly.
Browsers and software that follow the system proxy can start with the system proxy. For broader application coverage, UDP requests, or apps that ignore system proxy settings, evaluate TUN next. Change one interception option at a time and record the before-and-after results; avoid stacking the system proxy, TUN, and in-app proxy simultaneously.
Open the target website or app, then review the connection log for the resolved domain, rule type, target proxy group, and final node. If the request does not appear, the issue may be in the system proxy or TUN layer. If it appears but the policy is unexpected, check rule order, rule-set updates, and proxy-group references.
Download FAQ · 05
These answers cover client selection, package formats, CPU architectures, archived clients, and connection checks after installation.
If you want a graphical interface for importing subscriptions, switching proxy groups, and managing the system proxy, start with Clash Plus listed first for each platform. Windows, macOS, and Linux users can also choose Clash Verge Rev or FlClash based on interface preferences. Servers and routers typically run the Mihomo command-line core.
When choosing a client, consider the operating system, CPU architecture, TUN requirements, configuration-format compatibility, and project maintenance status together. Do not choose solely by appearance, and do not enable traffic interception in multiple clients on the same system.
For a standard desktop installation, use the EXE installer; it writes the application to the expected directory and creates the usual launch entry. For portable folders, temporary testing, or controlled deployments, choose FlClash when a ZIP package is available.
After extracting a ZIP package, preserve its internal directory structure. Do not copy only the main executable, or required resources, dynamic libraries, or configuration directories may be missing. Back up the configuration and exit the running process before upgrading a portable version.
Open About This Mac in System Settings. If the chip is an Apple M-series model, choose Apple Silicon or ARM64; if the processor is Intel, choose Intel or x64. You can also run uname -m in Terminal: arm64 indicates Apple Silicon, while x86_64 indicates an Intel environment.
A mismatched architecture may prevent the app from opening directly or require a system compatibility layer. Prefer a native build matching the Mac’s chip to reduce extra dependencies and simplify troubleshooting.
Most recent Android phones use arm64-v8a. Older 32-bit devices can use armeabi-v7a. If you cannot identify the architecture, use the universal package for Clash Meta for Android, though it is usually larger.
x86_64 is mainly intended for some emulators and specialized devices, not most ARM phones. If installation reports that the package is incompatible, recheck the architecture and Android version instead of repeatedly changing the subscription configuration.
Both clients retain archived download links for migrating existing configurations, reinstalling legacy environments, and reproducing compatibility issues. Discontinued status means new system changes, core capabilities, and configuration-format updates may no longer be adapted, so new installations should prefer maintained clients.
Before migrating, back up configuration files, subscription URLs, and local override rules. After migration, verify basic proxy connectivity first, then restore DNS, TUN, scripts, and complex rules gradually to avoid bringing incompatible legacy settings into the new environment all at once.
The installer contains only the client itself. You must also import a readable Clash or Mihomo configuration, select a valid proxy group, and enable the system proxy or TUN as needed. If the client shows nodes but cannot connect, first check the node connection error and system time.
If node tests succeed but the browser cannot access websites, check whether the system proxy is enabled, whether the browser uses separate proxy settings, and whether the request appears in the connection log. For DNS failures, check DNS settings, the Fake-IP range, rule-set downloads, and local network restrictions. For complete procedures, continue with the usage documentation and advanced troubleshooting guide.