Choose a GUI client for your device. This page covers Windows, macOS, Android, iOS, and Linux, with separate Mihomo core files for servers and routers.
On desktop platforms, choose a package based on the processor architecture and file format. On mobile platforms, download and install directly on the device.
For standard desktop systems, choose the x64 installer. After installation, import a configuration, select a proxy group on the Proxy page, and enable the system proxy or TUN mode as needed.
For Windows users who want straightforward configuration import, proxy-group switching, and system proxy controls. The setup wizard creates standard application shortcuts.
A desktop interface built around the mihomo core, with configuration management, proxy-group controls, connection details, logs, and a system proxy switch.
Provides both an installer and a ZIP archive. Choose the installer for normal use; download and extract the archive when you need to manage the application directory yourself.
For Windows users who need a graphical configuration manager, proxy-group selection, and log viewer. The download is an x64 installer.
Kept for users who need the legacy interface or want to migrate historical configurations. For new installations, choose a GUI client that is still maintained.
| Check | Recommendation | Details |
|---|---|---|
| Windows version | 64-bit Windows 10 or later | Newer desktop clients are generally built around current system components. |
| Processor architecture | x64 | All Windows GUI installers listed here are x64 files. |
| Network access | Allow the client to access the network | If Windows displays a prompt on first launch, grant network access according to your intended use. |
| TUN mode | Install the service when prompted by the client | Enable it only when you need to cover applications that do not read the system proxy. |
Check the chip type in About This Mac first. Choose Apple Silicon or ARM64 for M-series Macs, and Intel or x64 for Intel processors.
Provides DMG installers for Apple Silicon and Intel. Open the disk image after downloading, then move the app to the Applications directory.
Provides subscription configuration, proxy groups, system proxy controls, TUN mode, and a log viewer. The two architecture links in this list are matched by the download resolver.
For users who prefer a consistent cross-platform interface. Both processor entries are maintained in the release list; confirm your Mac’s chip type before installing.
Kept for users who need the legacy menu-bar workflow or want to migrate historical configurations. For new devices, choose a client that is still maintained.
| Check | How to choose | Details |
|---|---|---|
| Chip type | System Settings or About This Mac | Choose ARM64 when Apple M series is shown, or x64 when Intel is shown. |
| Installation location | Applications directory | After opening the DMG, drag the client to the Applications directory. |
| Network extension | Follow the system prompt | When enabling enhanced traffic interception, macOS may ask you to approve a network extension or enter your device password. |
| Background operation | Keep the menu-bar process running | Closing the main window may not stop the proxy. Check the running status from the client menu. |
Most recent Android phones use ARM64. If you cannot confirm the architecture, start with a client offering a universal package and follow the system prompts to install it.
A GUI client for common 64-bit Android phones and tablets. Import configurations, choose proxy groups, and establish a system VPN connection after installation.
Provides ARM64, ARM, and universal packages. Prefer ARM64 on recent 64-bit devices; choose the universal version when the architecture is unknown.
Provides ARM64 and 32-bit ARM packages. Its interface closely resembles the desktop version, making workflows consistent across devices.
An Android proxy configuration client for users who need rule and proxy-group management. This page provides a universal APK package.
| Check | Recommendation | Details |
|---|---|---|
| Processor architecture | ARM64 preferred | Most recent Android phones and tablets use arm64-v8a. |
| Installation permission | Authorize the current browser when prompted | Android generally grants installation permission only to the source used for the current file. |
| VPN permission | Confirm on the first connection | The client uses Android’s VPN interface to handle the selected traffic. |
| Background restrictions | Adjust battery settings as needed | If the system terminates the background process too early, the proxy connection will also be interrupted. |
Clash Plus can be installed through the App Store. Open the store page to check device compatibility, then import your own configuration after installation.
A GUI client for iPhone and iPad. Manage configurations, proxy groups, and connection status, then establish a proxy connection through the system network interface.
| Check | Action | Details |
|---|---|---|
| Device compatibility | View store details | The App Store displays compatibility for the current device. |
| Network access | Confirm on the first connection | Before establishing a connection, iOS will ask to add a network configuration. |
| Configuration import | Use a subscription URL or supported configuration file | After importing, check the proxy groups before enabling the connection. |
| Connection status | Check both the client and the system status bar | If the connection drops after switching networks, return to the client and reconnect. |
Debian, Ubuntu, and derivatives generally use DEB; Fedora and RHEL-based distributions generally use RPM. All GUI clients here are AMD64 desktop packages.
Provides DEB and RPM desktop packages. After installation, manage configurations, proxy groups, the system proxy, and connection logs from the GUI.
For Debian, Ubuntu, and derivative desktop distributions. Launch it from the application menu after installation, then import a subscription or local configuration.
| Check | Recommendation | Details |
|---|---|---|
| Processor architecture | AMD64 / x86_64 | The GUI clients in this section are 64-bit desktop packages in the current list. |
| Package format | Choose DEB or RPM based on the distribution | Do not rely only on the filename; use the package management system of the current distribution. |
| Desktop environment | An available graphical session | Headless servers and routers are better suited to the Mihomo core below. |
| System proxy | Check the desktop environment’s proxy settings | Desktop environments may handle reading and writing system proxy settings differently. |
The Mihomo core is suited to servers, routers, containers, transparent gateways, and environments where you manage the process yourself. Most desktop and mobile users should use a GUI client above.
| System | Architecture | Format | Environment | Download |
|---|---|---|---|---|
| Windows | amd64 |
ZIP | 64-bit Windows server or command-line environment | Download |
| Windows | arm64 |
ZIP | Windows on ARM device | Download |
| macOS | amd64 |
GZ | Intel-based Mac | Download |
| macOS | arm64 |
GZ | Apple Silicon Mac | Download |
| Linux | amd64 |
DEB | Debian, Ubuntu, and derivatives | Download |
| Linux | amd64 |
GZ | Generic 64-bit Linux environment | Download |
| Linux | arm64 |
GZ | 64-bit ARM servers and routers | Download |
| Linux | armv7 |
GZ | 32-bit ARMv7 devices | Download |
| Linux | mips-softfloat |
GZ | MIPS router devices using soft-float | Download |
On Linux, run uname -m to check the architecture. The common result x86_64 corresponds to amd64, while aarch64 corresponds to arm64. For routers, also verify the firmware ABI and floating-point type.
Place the executable, configuration files, and geographic data in a directory with clearly defined permissions. When running as a system service, set the working directory and configuration path explicitly in the service definition.
YAML is indentation-sensitive. If startup fails, read standard output or the service log first, paying particular attention to proxy-group references, occupied ports, DNS fields, and rule order.
Installing the client is only the first step. Traffic will follow the intended proxy rules only after you import a configuration, choose a policy, and verify the connection.
Windows desktop devices generally use x64 installers; macOS requires choosing between Apple Silicon and Intel; Android should use ARM64 when available; Linux requires DEB or RPM based on the distribution. A mismatched architecture may prevent the installer from launching or cause the system to reject it.
Desktop systems may ask you to approve network access, background services, or network extensions. Android and iOS request a system VPN configuration when a connection is established for the first time. Permissions determine whether the client can handle traffic; they do not replace the configuration file.
Paste a working subscription URL on the configuration page, or import a supported YAML file. After importing, update or reload it, then confirm that it appears in the list. If parsing fails, first check YAML indentation and field names.
Open the Proxy page to review proxy groups. Manual selection usually requires an explicit outbound choice; automatic selection, failover, and load-balancing groups follow the tests and switching rules in the configuration. Then choose Rule, Global, or Direct mode as needed.
Browsers and most desktop applications read system proxy settings, while terminals and some independent network stacks may ignore them. Use TUN mode when broader application coverage is needed, but first check for conflicts among the local network, DNS, and other networking software.
After connecting, do not rely only on the toggle state. Open the Connections page to confirm that requests are actually appearing, then inspect rule matches, DNS resolution, and outbound policies in the logs. When troubleshooting, recording the first error is usually more effective than repeatedly switching nodes.
For the complete workflow, continue with the Clash user guide. See protocol reference for protocol types and core differences.
These questions cover client selection, processor architecture, installation formats, and first-time configuration. More complete troubleshooting is available on the FAQ page.
Most desktop and mobile users should choose the GUI for their platform. Clash Plus supports several common platforms; on Windows, macOS, and Linux, you can choose Clash Verge Rev or FlClash based on the package format. Consider the Mihomo core for servers, routers, and command-line environments.
The installer uses a setup wizard to place the app in its application directory and usually creates a Start menu shortcut, making it suitable for everyday use. A ZIP archive must be extracted and managed manually; exit the program before moving it to avoid breaking its working path or shortcuts.
Choose Apple Silicon or ARM64 for Macs with an M-series chip, and Intel or x64 for older Intel-based Macs. Open General > About in System Settings and check the chip or processor entry.
A GUI client provides interfaces for importing configurations, choosing proxy groups, managing the system proxy, using TUN mode, viewing connections, and reading logs. The Mihomo core is intended mainly for servers, routers, containers, and command-line environments, where you manage configuration files, startup arguments, process supervision, and updates yourself.
First confirm that the subscription URL is reachable and check that the client has network access. When importing a local YAML file, verify indentation, proxy-group references, rule fields, and DNS settings. Reload the configuration after making changes, then check the first parsing error in the logs.