Choose a client by operating system, processor architecture, and maintenance status. Graphical clients are best for everyday desktops and mobile devices; use standalone Mihomo for servers, routers, and automation.
Platform tabs remain in the page URL, so you can copy the current link and open the relevant download section directly. Package names on client cards are updated from a remote manifest; if the manifest is unavailable, buttons retain complete fallback paths that are currently available.
For everyday desktop proxying, rule-based routing, and subscription management. The order below balances ease of use, maintenance status, and configuration compatibility; legacy projects remain available for migrating existing setups.
Windows Graphical Client
Designed for everyday desktop use, with configuration imports, proxy group switching, system proxy controls, and connection management for users who want fewer manual setup steps.
mihomo Desktop Client
Built around mihomo configuration and desktop controls, for advanced users who need to inspect proxy groups, rule matches, proxy modes, and kernel settings.
Cross-Platform Graphical Client
Windows, macOS, Linux, and Android share a similar interface and workflow, making it easier to keep configuration habits consistent across devices.
Desktop Configuration Manager
Provides desktop controls for configurations, proxy groups, and rules, offering another mihomo graphical client option alongside Clash Verge Rev.
Archived Desktop Client
Retained for migrating existing configurations, restoring older devices, and comparing interface workflows. For new deployments, choose a maintained client with current mihomo configuration support.
| Check | Recommendation | Details |
|---|---|---|
| System architecture | x64 | The desktop installers on this page target common 64-bit Windows devices. |
| Installation format | EXE | Best for standard installations; FlClash also provides a ZIP archive for managing a standalone directory. |
| Permissions | Grant access by feature | Enabling the system proxy, service mode, or TUN may prompt Windows for administrator permission. |
| Migrating from an older client | Export your configuration first | Before switching clients, record the subscription URL, proxy group choices, and custom rules to avoid rebuilding them. |
Before downloading, check the chip type in About This Mac or System Information. Choose Apple Silicon or ARM64 for M-series devices, and x64 for Intel Macs.
macOS Graphical Client
Provides a macOS graphical interface for importing subscriptions, choosing proxy groups, and controlling the system proxy. Download the DMG that matches your Mac chip.
mihomo Desktop Client
For users who need direct control over mihomo configurations, proxy groups, and proxy modes. Separate chip-specific entries are maintained through the download manifest.
Cross-Platform Graphical Client
A good fit for users working across desktop and mobile devices, with a broadly consistent workflow between platforms. You still need to import a valid configuration and choose a proxy group after installation.
Archived Menu Bar Client
For restoring older ClashX Meta setups and migrating configurations. For long-term use, consider a maintained macOS graphical client.
| Device information | Choose | Installation notes |
|---|---|---|
| Apple M-series | Apple Silicon / ARM64 | For Macs with M1, M2, M3, M4, or later chips using the same architecture. |
| Intel processor | Intel / x64 | For devices whose Processor field in System Information shows Intel. |
| DMG installation | Move to Applications | Open the disk image, follow the prompts to place the app in Applications, then launch it from there. |
| System network permissions | Confirm when prompted | The system proxy, network extensions, or background services may require permission in System Settings. |
Most recent phones and tablets use ARM64. Choose ARM only when the device is confirmed to be 32-bit; if the architecture is unclear, use a client that offers a universal build.
Android Graphical Client
For importing configurations, choosing proxy groups, and managing connections on Android phones and tablets. The current entry provides a common ARM64 package.
mihomo Android Client
For Android users who need mihomo rule and protocol compatibility. ARM64, 32-bit ARM, and universal packages are available for different device architectures.
Cross-Platform Android Client
For users already using FlClash on desktop who want a similar workflow on mobile. Choose ARM64 or ARM according to the device architecture.
Android Proxy Client
Provides Android configuration and rule management for users with a compatible setup. Before importing, confirm that the subscription format and rule syntax match the client.
| Package label | Supported devices | Selection advice |
|---|---|---|
| arm64-v8a | Recent 64-bit phones and tablets | The first choice for most devices, usually offering better compatibility and performance. |
| armeabi-v7a | Older 32-bit ARM devices | Use only when the device is confirmed to use a 32-bit architecture. |
| universal | Devices with an unknown architecture | Supports a wider range of architectures, but the installer is usually larger than a single-architecture package. |
| Background operation | For continuous connections | Adjust battery optimization and background limits in system settings to prevent the client from being terminated repeatedly. |
On iOS, install Clash Plus through the App Store. After installation, import a compatible configuration in the app, choose a proxy group, and add the network configuration when prompted.
iPhone and iPad Graphical Client
For configuration imports, proxy policies, and connection management on iOS and iPadOS. Check the App Store listing for current app details and device compatibility.
Official site: clashplus.io
| Step | Action | Details |
|---|---|---|
| Install the app | Open the App Store listing | Review the system compatibility requirements on your iPhone or iPad, then complete the installation. |
| Import a configuration | Use a subscription URL or configuration file | Confirm that the source and format are compatible, then import it in the client. |
| Choose a proxy policy | Check the proxy group | Choose a node or automatic proxy group based on your network needs; do not rely solely on the default selection. |
| Establish a connection | Confirm system requests | When enabling the client for the first time, follow the system prompts to authorize the network configuration. |
For graphical Linux desktops, choose Clash Verge Rev or FlClash. Debian, Ubuntu, and derivatives typically use DEB; Fedora and RHEL-based distributions typically use RPM.
Linux mihomo Graphical Client
For common x86_64 Linux desktop environments, with graphical controls for subscriptions, proxy groups, rule modes, and kernel settings. Choose the format that matches your distribution's package system.
Linux Cross-Platform Client
Offers a workflow similar to other platforms, for users who want consistent habits across Linux desktops, phones, Windows, or macOS.
| Environment | Installation format | Details |
|---|---|---|
| Debian / Ubuntu-based | DEB | Use the system software installer or install through the package management command provided by the distribution. |
| Fedora / RHEL-based | RPM | Clash Verge Rev provides an RPM package for compatible package management systems. |
| Desktop environment | Graphical session | Graphical clients require an available desktop, tray, or window environment; a headless server is usually better served by the standalone kernel. |
| System proxy | Configure it through the desktop environment | Proxy controls vary by distribution and desktop environment. After enabling them, check environment variables and application behavior. |
Standalone Mihomo is intended for servers, routers, containers, and users who manage processes, configuration directories, and startup parameters themselves. Most desktop and mobile users should choose a graphical client above, since it integrates configuration imports, proxy switching, and system proxy controls.
| System | Architecture and format | Download |
|---|---|---|
| Windows | AMD64 · ZIP | Download AMD64 |
| Windows | ARM64 · ZIP | Download ARM64 |
| macOS | Intel AMD64 · GZ | Download Intel |
| macOS | Apple Silicon ARM64 · GZ | Download Apple Silicon |
| Linux | AMD64 · DEB | Download DEB |
| Linux | AMD64 · GZ | Download AMD64 |
| Linux | ARM64 · GZ | Download ARM64 |
| Linux | ARMv7 · GZ | Download ARMv7 |
| Linux | MIPS softfloat · GZ | Download MIPS |
AMD64 is common on x86_64 computers and servers; ARM64 is common on newer single-board computers, some routers, cloud hosts, and Apple Silicon. ARMv7 and MIPS are more common on older or specialized embedded devices.
Keep the executable, configuration files, and runtime data in directories with clearly defined permissions. When running as a system service, also confirm that the service account can read the configuration and write required data.
When migrating an old Clash configuration, carefully review proxy protocol fields, rule-set references, DNS settings, TUN parameters, and proxy group types. A configuration loading successfully does not mean every connection path will behave as expected.
Client names may look similar, but their platforms, architectures, kernels, and maintenance status can differ. Complete these checks before downloading to reduce the risk of failed launches, unreadable configurations, or inactive system proxy settings.
If your main needs are importing subscriptions, switching proxy groups, enabling the system proxy, and reviewing connection logs, graphical clients provide the most complete workflow. On Windows, macOS, Android, and iOS, compare the first option for each platform; on Linux desktops, choose between Clash Verge Rev and FlClash.
The same client may offer x64, ARM64, 32-bit ARM, or universal packages. Windows and common Linux computers are often x64, M-series Macs use Apple Silicon, and Android devices require an architecture check. A package can have the right format but the wrong architecture, preventing installation or launch.
The archived Clash for Windows and ClashX Meta entries can help restore existing setups, read old configurations, or complete migrations. For a new environment, focus on current maintenance status, mihomo configuration compatibility, and the target system's permission requirements.
After the client starts, import a valid configuration, check proxy nodes and groups, then choose rule, global, or direct mode. After enabling the system proxy or TUN, separately test browsers, system apps, and command-line programs to verify that they use the expected path.
These questions cover client selection, processor architecture, archived projects, and first-time configuration. For a complete connection walkthrough, continue to the quick-start guide.
For subscription imports, rule switching, and system proxy setup, start with Clash Plus. For more centralized management of mihomo configurations, rules, and proxy groups, compare Clash Verge Rev and FlClash. If you have an existing Clash for Windows setup, record its configuration before migrating to a maintained client.
Open About This Mac or System Information and check the Chip or Processor field. Choose Apple Silicon or ARM64 for an Apple M-series chip, and x64 when it shows Intel. Do not rely only on the device's appearance or purchase year, since similar models can use different processors.
arm64-v8a targets most recent 64-bit Android devices, armeabi-v7a targets older 32-bit ARM devices, and universal covers more architectures. Choose a single-architecture package when you know the device architecture; if not, choose universal when the client provides it.
These entries are mainly for migrating old configurations, restoring existing devices, and comparing interface workflows. Discontinued status means future system changes, protocol capabilities, and configuration formats are no longer actively supported, so they are not suitable as the long-term default for a new setup. Before migrating, organize your subscription URL, custom rules, proxy group choices, and system proxy settings.
Usually not. Graphical clients already provide kernel execution, configuration imports, proxy switching, and system proxy controls. Standalone Mihomo is better suited to servers, routers, containers, or scripted environments, where users manage configuration paths, startup parameters, permissions, logs, and services themselves.
After installation, prepare a compatible configuration file or subscription URL. Once imported, confirm that it loaded successfully, review the proxy groups, and choose a suitable node. Then enable the system proxy or configure TUN as needed. Finally, test your browser and common apps separately to verify routing and DNS behavior.