Choose your operating system first, then verify the CPU architecture and maintenance status. Most users should start with a graphical client; servers, routers, and command-line environments can continue to the Mihomo core section.
Your selected tab is preserved in the page URL, so you can copy the current link to open the corresponding platform directly. Cards are ordered by recommendation; the primary button covers common devices, while other architectures appear as secondary links on the same card.
Most Windows PCs with Intel or AMD processors use an x64 package. First-time users can start with Clash Plus; if you want more core and interface options, compare Clash Verge Rev, FlClash, and Clash Nyanpasu.
A good fit for Windows users who want to import subscriptions, switch rule modes, and configure the system proxy quickly. Its clear installer and focused common settings make it easier to follow tutorials on a new device.
Offers comprehensive interfaces for proxy groups, connections, rules, and TUN settings. It suits desktop users who understand subscriptions, node selection, and proxy modes and want more control over their configuration.
Its layout is consistent across desktop and mobile platforms, making it a good fit for users who work across multiple systems and want a familiar workflow. On Windows, choose either the installer or a ZIP archive for manual extraction.
Provides desktop configuration management, proxy-group switching, and connection monitoring for Windows users who prefer its interface. If another client is already installed, export or preserve the existing configuration before migrating.
The archive link is mainly for restoring older devices, migrating legacy configurations, and maintaining existing setups. For a new installation, compare the maintained clients above for a core and feature set better suited to current systems.
| Check | Recommendation | Before installation |
|---|---|---|
| Windows version | Use a supported 64-bit version of Windows | Older systems may lack the runtime environment or WebView components required by the client. |
| CPU architecture | Choose x64 for most Intel and AMD PCs | Check the system type under “Settings → System → About.” |
| Installation permissions | Use an account authorized to install desktop applications | TUN services or system-level network components may require administrator approval. |
| Configuration migration | Keep your subscription URLs and custom rules | Before switching clients, record the current proxy mode, port, and override settings. |
Check the chip type under “About This Mac.” Apple M-series Macs use ARM64, while Intel Macs use x64. After downloading and installing, follow the client’s prompts to authorize network extensions, background items, or helper services.
Designed for macOS users who need graphical subscription management, rule modes, and a system-proxy switch. Separate Apple Silicon and Intel packages are available; choose the one matching your chip.
A fit for macOS desktop users who need connection details, override editing, core options, and TUN mode. After the first launch, import a configuration and verify the system proxy status.
Suitable for users who work across macOS, Android, and other desktop systems and want a consistent workflow. After installation, import a subscription from the configuration page and choose a policy group on the proxy page.
For users who still rely on older configurations and want to restore the original menu-bar workflow. As an archived client, it is better suited to migration and temporary recovery; for long-term use, compare the maintained clients above.
| Check | Apple Silicon | Intel Mac |
|---|---|---|
| Package architecture | ARM64 | x64 |
| Where to check the chip | Open “About This Mac” from the Apple menu to view the chip or processor name. | |
| First launch | Follow the system prompts to allow the app to run and approve network extensions, helper services, or background items. | |
| Proxy activation | Import and select a configuration, then enable the system proxy. Configure TUN only when more applications need to be intercepted. | |
Most recent Android phones use ARM64. Older 32-bit devices may require an ARMv7 package; when the architecture is unclear, the universal package for Clash Meta for Android is a convenient compatibility starting point.
Designed for ARM64 Android phones and tablets, with common controls for subscription import, proxy-group selection, rule mode, and connection toggling. For an initial setup, start with Rule mode and adjust it for individual apps as needed.
Provides ARM64, ARMv7, and universal packages for users who need to match an older device precisely. If you are unsure of the processor type, start with the universal package and switch to a dedicated architecture build after confirming compatibility.
A good fit for users who want a similar interface on Android and desktop. It offers ARM64, ARMv7, and x86_64 builds; most phones use ARM64, while emulators and specialized devices may require x86_64.
An Android rule-based proxy client for users with compatible configurations who are familiar with importing them. Before importing, confirm that the subscription format is supported so format issues are not mistaken for network problems.
| Package | Common devices | Selection guidance |
|---|---|---|
| ARM64-v8a | Recent mainstream phones and tablets | Most users should choose this architecture first. |
| ARMv7 | Some older 32-bit Android devices | Use only after confirming that the device is 32-bit ARM. |
| x86_64 | Some emulators and development devices | Usually not needed for standard physical phones. |
| Universal package | Devices with an unconfirmed architecture | The file is usually larger but supports a wider range of processors. |
iPhone and iPad users can open the Clash Plus page in the App Store. After installation, import a subscription, choose Rule mode, and follow the system prompts to allow a VPN configuration.
For iPhone and iPad, common actions include adding a subscription, choosing a proxy group, switching rule modes, and starting a connection. On the first connection, iOS displays a VPN configuration authorization prompt; approve it to let the client create the network tunnel.
| Step | Action | Completion check |
|---|---|---|
| Install the app | Open the Clash Plus listing in the App Store and complete the installation. | The client icon appears on the Home Screen. |
| Import a configuration | Add a valid subscription URL or import a compatible configuration in the app. | A selectable configuration appears in the configuration list. |
| Allow the connection | Start the connection and approve the VPN configuration authorization shown by iOS. | A VPN connection status appears in the system status area. |
| Choose a policy | Open the proxy-group selector and choose a policy; for everyday use, start with Rule mode. | Connections matching the rules are routed according to the configuration. |
Desktop users can choose between Clash Verge Rev and FlClash. Debian, Ubuntu, and derivatives typically use deb; Fedora, RHEL, and related distributions typically use rpm. Confirm that the system is amd64 before downloading.
For Linux desktop users who need graphical subscription management, system proxy controls, rule inspection, and TUN settings. Choose deb or rpm for your distribution, then handle desktop integration and system-service permissions after installation.
Suitable for users who want a similar workflow across Linux, Windows, macOS, and Android. Linux offers deb, rpm, and AppImage packages; standard Debian-based desktops can start with deb.
| Package format | Common distributions | Usage |
|---|---|---|
| deb | Debian, Ubuntu, Linux Mint, and similar distributions | Install with the system software installer or the distribution’s package manager. |
| rpm | Fedora, RHEL, and related derivatives | Install with the rpm package-management tool for your distribution. |
| AppImage | Various desktop distributions | Grant execute permission and run it; suitable when you do not want to install a system package. |
| Network permissions | All distributions | TUN, transparent proxying, and system-service operations may require elevated privileges. |
The clients serve broadly similar purposes; the main differences are their interfaces, platform coverage, core management, and system integration. First-time users do not need to install several clients. Start with the Featured or Recommended option for your platform, complete subscription import, Rule mode, and system-proxy setup, then compare alternatives if needed.
Running multiple proxy clients on one device can cause repeated system-proxy changes, port conflicts, or TUN-service collisions. Before switching, exit the old client and disable its system proxy and TUN mode; restart the device if necessary before launching the new client.
The Mihomo core is intended for servers, software routers, containers, automation scripts, and users comfortable with configuration files. It does not provide the same graphical management interface as desktop clients, so you must prepare configuration files, startup arguments, service management, and update procedures yourself. Most computer and phone users should choose a GUI client above.
| System | CPU architecture | Format | Use case | Download |
|---|---|---|---|---|
| Windows | AMD64 | ZIP | Common 64-bit Intel or AMD computers and Windows servers. | Download |
| Windows | ARM64 | ZIP | Windows on ARM devices; confirm the system architecture before downloading. | Download |
| macOS | Intel AMD64 | GZ | Macs with Intel processors. | Download |
| macOS | Apple Silicon ARM64 | GZ | Macs with Apple M-series chips. | Download |
| Linux | AMD64 | DEB | amd64 servers or desktops running Debian or Ubuntu. | Download |
| Linux | AMD64 | GZ | A generic amd64 binary for custom service configurations. | Download |
| Linux | ARM64 | GZ | 64-bit ARM servers, development boards, and some software routers. | Download |
| Linux | ARMv7 | GZ | Some 32-bit ARMv7 routers and development boards. | Download |
| Linux | MIPS softfloat | GZ | MIPS router environments using software floating point. | Download |
Confirm that the package matches the operating system and chip architecture, then install it through the system workflow. On desktop systems, read and approve prompts for network extensions, background services, or administrator permissions as needed. Do not run another proxy client at the same time after launch.
Copy a valid subscription URL and import it from the client’s Configuration, Subscription, or Profiles page. Importing does not enable it automatically: select the newly added item in the configuration list and wait for proxy groups and rules to finish loading.
For everyday use, start with Rule mode so each connection follows the configured routing rules for proxying or direct access. Then enable the system proxy and test the browser connection; install the service and enable TUN only when you need to intercept apps that ignore system-proxy settings.
This section covers client selection, CPU architectures, first connections, and archived versions. For a specific error, note the system version, client name, and steps that triggered it, then troubleshoot by symptom on the troubleshooting page.
Most desktop and mobile users can start with the graphical client marked Featured or Recommended for their platform. Clash Plus is a good first choice on Windows, macOS, Android, and iOS; Linux desktop users can start with Clash Verge Rev. Learning one client’s configuration workflow makes troubleshooting easier than installing several at once.
Most Intel and AMD Windows PCs use x64; Apple Silicon Macs use ARM64, while Intel Macs use x64. On Android, check the device processor details first. If unsure, use the client’s universal package. Routers and development boards also require distinguishing ARMv7, ARM64, and MIPS; the operating-system name alone is not enough.
After installation, import a valid subscription or configuration file, choose an available policy on the proxy page, and enable the system proxy or TUN mode as needed. The installer does not include subscription settings. If the configuration is already imported, confirm that it is selected and check the rule mode and system-proxy switch.
Both clients retain archive links for migrating existing configurations and older devices. For a new installation, choose a maintained client with a newer core for better compatibility and feature support on current systems. Before migrating, record the subscription URL, proxy port, custom rules, and override settings.
The Mihomo core is mainly intended for servers, routers, containers, and users comfortable with command-line configuration. Most computer and phone users will find a graphical client easier for importing subscriptions, switching modes, and handling updates. Direct core deployment also requires managing configuration paths, startup arguments, and system services yourself.
Confirm that the file matches your operating system and CPU architecture, then follow the system’s installation steps. After the first launch, import your subscription, select it in the configuration list, choose Rule mode, and enable the system proxy. If another proxy client is installed, exit it completely first to avoid port and system-proxy conflicts.