Choose a graphical client for your operating system. This page covers Windows, macOS, Android, iOS, and Linux, with commonly used Mihomo core packages for servers and routers listed separately below.
Each tab keeps its platform anchor in the address bar, so you can copy the current link to open the matching section directly. Cards explain differences by maintenance status, setup difficulty, and common use cases.
Windows users usually choose an x64 installer. The installed version adds Start menu and uninstall entries; FlClash also offers a ZIP package for users who prefer to manage the application directory themselves.
| Check | Recommendation |
|---|---|
| System | Windows 10 or Windows 11, 64-bit |
| Processor | x86-64 / AMD64 |
| Installation permissions | Grant permission when prompted by Windows while installing a service or enabling TUN mode |
Best for Windows users who want to quickly install the client, import a subscription, and configure the system proxy. The GUI brings configuration, proxy groups, connections, and logs together.
The interface covers subscription management, proxy-group selection, connection monitoring, and system proxy settings for desktop users familiar with Clash configuration.
The same workflow works across desktop and Android, making it suitable for users who want a consistent configuration experience on different systems.
Provides graphical configuration and proxy-management tools for Windows users comparing different desktop client workflows.
This client is no longer maintained. The archived installer is retained for migrating existing setups and handling legacy configurations. For new installations, choose a client that is still updated.
Open About This Mac or System Information first and check the chip field. Choose ARM64 for Apple M-series chips and x64 for Intel processors. On first launch, follow the prompts to configure network extension or proxy permissions.
| Device type | Package to choose |
|---|---|
| Apple M1, M2, M3, or M4 series | Apple Silicon / ARM64 |
| Mac with an Intel Core processor | Intel / x64 |
| Installer format | DMG; open it and follow the prompts to move the app to Applications |
Provides Apple Silicon and Intel installers for macOS users who need a GUI, subscription management, and common system integration.
Suitable for users who need connection logs, configuration overrides, and multiple subscriptions. Open the DMG after downloading and move the app to Applications.
Designed for users who want a consistent cross-platform workflow, with configuration, proxy groups, and connection details in one GUI.
This client is no longer maintained. The archived package is mainly for existing installations and legacy configuration migration. For new devices, choose a macOS client that is still updated.
Most recent phones use arm64-v8a. Older 32-bit devices may need armeabi-v7a, while some tablets and emulators use x86_64. If unsure, check the CPU ABI with a device information tool.
| Architecture | Common devices |
|---|---|
| arm64-v8a | Most recent Android phones and tablets |
| armeabi-v7a | Older 32-bit ARM devices |
| universal | For unknown architectures; the package is usually larger |
Designed for ARM64 phones and tablets, with a mobile GUI for importing subscriptions, switching proxy groups, and controlling connections.
A Clash Meta GUI client for Android, offering ARM64, 32-bit ARM, and universal packages so you can choose precisely for your device architecture.
Provides ARM64, 32-bit ARM, and x86_64 packages for users who want the same interface on phones, tablets, or Android emulators.
An Android rule-based proxy client for users with compatible subscriptions who want a clean mobile management interface.
On iOS, get Clash Plus through the App Store. After installation, import subscriptions, choose proxy groups, and create the network configuration as prompted by iOS.
| Check | Details |
|---|---|
| Device | iPhone or iPad |
| Get it from | App Store listing |
| First connection | Allow the network configuration when prompted by iOS |
A GUI client for iPhone and iPad, with in-app subscription configuration, proxy-group selection, connection controls, and common network settings.
Debian, Ubuntu, and derivatives usually use DEB; Fedora, RHEL, and compatible distributions usually use RPM. Check your package manager before downloading.
| Distribution type | Recommended format |
|---|---|
| Debian、Ubuntu、Linux Mint | AMD64 DEB |
| Fedora and RHEL-based distributions | x86_64 RPM |
| Other desktop distributions | Confirm package-manager compatibility first; for FlClash, also check AppImage |
Designed for Linux desktops, with configuration, proxy-group, connection, and system proxy management. Choose DEB or RPM according to your distribution's package system.
Provides AMD64 packages in DEB, RPM, and AppImage formats. DEB and RPM work well with system package managers; AppImage runs independently.
Mihomo handles configuration parsing, proxy connections, DNS, and rule-based routing. These archives and system packages are mainly for servers, software routers, container hosts, and users who manage the process themselves.
Most desktop and mobile users do not need to install the core separately; use a GUI client with the core integrated above. A standalone deployment requires your own YAML configuration, process management, log directory, and system proxy integration.
| System | Architecture and format | Compatibility | Download |
|---|---|---|---|
| Windows | AMD64 ZIP | Common 64-bit Intel / AMD Windows hosts | Download AMD64 |
| Windows | ARM64 ZIP | Windows on ARM devices | Download ARM64 |
| macOS | Intel x64 GZ | Macs with Intel processors | Download Intel |
| macOS | Apple Silicon ARM64 GZ | Macs with Apple M-series chips | Download Apple Silicon |
| Linux | AMD64 DEB | AMD64 Debian, Ubuntu, and similar systems; install through the package manager | Download DEB |
| Linux | AMD64 GZ | General-purpose x86-64 Linux hosts | Download AMD64 |
| Linux | ARM64 GZ | 64-bit ARM servers, development boards, and routers | Download ARM64 |
| Linux | ARMv7 GZ | 32-bit ARM devices compatible with ARMv7 | Download ARMv7 |
| Linux | MIPS softfloat GZ | Routers using the MIPS softfloat ABI | Download MIPS |
The core needs a valid, parseable YAML configuration to start. It typically includes listening ports, operating mode, DNS, proxy nodes, proxy groups, and rule sets. Indentation errors can prevent the core from loading the file.
On servers, use a system service manager to start, restart, and stop the process, and write logs to a location that can be rotated. Stop the old process before upgrading the binary to avoid a port conflict.
Running the core alone does not automatically route all system traffic. Configure an explicit proxy, transparent proxy, TUN interface, or routing rules for the device, and make sure the DNS path matches the rule design.
Downloading is only the first step. After installation, verify configuration loading, proxy-group selection, and system integration in order to avoid cases where the program is open but traffic is not passing through the client.
When multiple proxy clients enable the system proxy or listen on the same port, startup failures, port conflicts, or repeatedly overwritten proxy settings are common. Quit the old client before installing or migrating, then use Task Manager or Activity Monitor to confirm related processes have ended.
Open the client's configuration or subscription page, add the URL from your service provider, and refresh it. For a local YAML file, confirm that indentation, field names, and references can be parsed by the core. Proxy groups appear on the proxy page only after the configuration loads successfully.
Choose a suitable node for the main proxy group on the proxy page, then enable system proxy or TUN mode for your use case. System proxy works for apps that follow system proxy settings; to cover more traffic, review the client's TUN and permission requirements.
Visit the site you want to test while watching the client's connections or logs. Confirm that the request is identified correctly, matches the expected rule, and is sent to the right proxy group. If it fails, check DNS, connection timeouts, missing rules, and port usage in the logs instead of repeatedly reinstalling.
These answers cover client selection, processor architecture, archived software, and first-time configuration. For more complete connection and rule diagnostics, visit the FAQ page.
Most desktop and mobile users should start with a GUI client. For Windows, macOS, Android, and iOS, check Clash Plus first; on Linux, start with Clash Verge Rev. GUI clients integrate configuration management, proxy groups, logs, and system proxy controls, making setup shorter than deploying the core alone.
Choose Apple Silicon or ARM64 for Macs with M1, M2, M3, or M4 chips. Choose Intel or x64 for older Macs with Intel Core processors. Open About This Mac in System Settings and check the chip or processor field before downloading.
Most recent Android phones and tablets use arm64-v8a. armeabi-v7a targets some older 32-bit ARM devices; the universal package supports more architectures and is useful when the CPU ABI is unknown, but it is usually larger. FlClash's x86_64 package is mainly for matching devices or emulators.
Archived installers still work for existing setups and legacy configuration migration, but they receive no new features or compatibility updates. For a new installation, choose Clash Plus, Clash Verge Rev, FlClash, or Clash Nyanpasu. Record existing ports, subscriptions, and overrides before migrating, and avoid letting both clients control the system proxy.
Mihomo is the core program for configuration parsing, connections, DNS, and rule-based routing; it does not provide a complete desktop management interface. GUI clients usually integrate the core and add subscription management, proxy switching, log viewing, and system integration. Servers, software routers, and automated environments can deploy the core separately, while most users will find a GUI client more straightforward.
Install and open the client, go to its configuration or subscription page, add the URL from your service provider, and refresh it. After parsing succeeds, choose a node for the main proxy group, then enable system proxy or TUN mode. If proxy groups are still missing, check the logs for configuration parsing errors.
View the complete getting started guide and follow the steps for importing subscriptions, choosing proxy groups, connecting, and verifying the setup.