Open the slot for your operating system, verify the processor architecture, then choose a GUI client or standalone core. Version details come from the download manifest; if no version is returned, the page keeps only valid download links.
Windows and Linux mainly distinguish x64 and ARM64; Android mainly distinguishes arm64-v8a and armeabi-v7a.
EXE, DMG, APK, DEB, and RPM target different systems; archives usually require manual extraction and setup.
For new installations, prefer a maintained client. Archived clients are intended for legacy compatibility and configuration migration.
Platform labels sync with the URL anchor. Copy the current link to open the download list for the corresponding operating system.
Choose an x64 package for most Intel or AMD PCs. After installation, import your configuration in the client, then enable the system proxy or configure TUN mode if needed.
A GUI client for the Windows desktop. It suits first-time setup, subscription management, rule-mode switching, and standard system-proxy routing. Run the installer after downloading, then import your subscription URL.
A desktop GUI client with configuration switching, rule viewing, system-proxy controls, and TUN-related settings. The current listing provides a Windows x64 installer and does not list a native Windows ARM64 package separately.
A GUI client for desktop and Android. On Windows, choose an installer or ZIP archive: the installer suits standard desktop use, while the ZIP is better for manually managed directories.
A Windows desktop client for configuration-file management, policy selection, and proxy-status controls. It suits users familiar with subscriptions, rule modes, and policy groups who want to compare different desktop interfaces.
An archived desktop client for opening existing configurations, reproducing legacy environments, or completing a migration. For new installations, prefer a maintained Windows client and verify the configuration directory, ports, and DNS settings during migration.
| Check | Recommendation | Before installation |
|---|---|---|
| Processor architecture | x64 / AMD64 | Most Intel and AMD desktops and laptops use x64 |
| File format | Prefer EXE; deploy ZIP manually | Enterprise devices may require administrator approval to install or take over network traffic |
| Proxy routing | Test the system proxy first, then evaluate TUN | TUN requires extra permissions; check DNS and firewall status after enabling it |
Check the chip type in About This Mac. Choose ARM64 for Apple M-series processors and x64 for Intel processors; open the downloaded DMG and move the app to Applications.
A macOS GUI client with separate Apple Silicon and Intel packages. On first launch, follow the system prompts for network permissions, then import your configuration and check the connection status in the menu bar.
Provides desktop configuration management, proxy switching, and TUN controls. The current listing keeps separate Apple Silicon and Intel download keys; choose the button matching your Mac's chip.
A cross-platform GUI client. Its macOS downloads are mapped separately by chip type and suit users who want a similar workflow on desktop and Android. Check system-proxy permissions after importing the configuration.
An archived macOS menu-bar client. The download link is still resolved through the version manifest, making it suitable for legacy configuration migration and existing-environment recovery. For new deployments, choose a maintained macOS client.
| Device information | Architecture to choose | Installation instructions |
|---|---|---|
| Apple M1, M2, M3, and M4 series | Apple Silicon / ARM64 | Download the matching DMG and move the app to Applications |
| Intel Core Mac | Intel / x64 | Choose the x64 package; do not infer the architecture from the macOS version name |
| First launch | Follow the system prompts to grant permission | Enable the system proxy or TUN only after network permissions are granted |
Recent phones and tablets typically use arm64-v8a. Choose armeabi-v7a for older 32-bit devices; when uncertain, prefer the universal package offered by the client.
An Android GUI client whose current download targets ARM64 devices. After installation, import a subscription or local configuration, allow the system to create a VPN connection on first connect, then check policy groups and connection status.
An Android client built around Meta-series core capabilities, offering ARM64, 32-bit ARM, and universal packages. ARM64 suits most devices; choose universal when the architecture is unclear.
A cross-platform GUI client with arm64-v8a, armeabi-v7a, and x86_64 Android builds. Phones usually use ARM64; emulators and certain tablets may use x86_64.
An Android rule-based proxy client using a universal package. It suits users with a compatible configuration who understand rules, policy groups, and remote configuration management. Import a valid configuration manually after installation.
| Package identifier | Compatible devices | How to choose |
|---|---|---|
| arm64-v8a | Most recent Android phones and tablets | Prefer this when the system uses 64-bit ARM |
| armeabi-v7a | Older 32-bit ARM devices | Use only when the device does not support ARM64 |
| universal | Unknown architecture or broad compatibility needed | The file is usually larger, but avoids architecture detection |
| x86_64 | Some emulators and specific devices | Do not choose this package for standard ARM phones |
Open the Clash Plus app page in the App Store. After installation, import your configuration and follow the system prompts to allow a VPN connection.
A GUI client for iPhone and iPad. Import subscriptions or configuration files in the app and route traffic through iOS VPN permissions. On first enablement, confirm system authorization, then check the active policy and rule mode.
| Stage | Action | Expected result |
|---|---|---|
| Install | Open the Clash Plus page from the App Store | The app appears on the Home Screen or in the App Library |
| Configure | Import a valid subscription or configuration file | Policy groups and proxy nodes appear in the client |
| Connect | Follow the system prompt to allow the VPN configuration | The system status bar and client show the connection status |
Choose DEB for Debian, Ubuntu, and derivatives; choose RPM for Fedora, RHEL, and compatible distributions. These desktop packages target AMD64.
A Linux desktop GUI client with AMD64 DEB and RPM packages. Choose the format matching your distribution, then check the desktop session, system proxy, and network permissions after installation.
A Linux AMD64 GUI client. The primary entry in the fixed order is DEB, with RPM and AppImage also available for compatible desktop environments. Grant execute permission before launching AppImage.
| Package format | Common distributions | Deployment note |
|---|---|---|
| DEB | Debian、Ubuntu、Linux Mint | Install through the system package manager to handle desktop dependencies more easily |
| RPM | Fedora, RHEL, and compatible distributions | Install with the package-management command for your distribution |
| AppImage | Various desktop distributions | Grant execute permission before launching; the configuration directory still requires separate management |
| Standalone core | Servers, routers, and command-line environments | Go to the Mihomo section below and choose a file by architecture |
For server, router, container, and command-line deployments. Regular desktop and mobile users should prefer the GUI clients above.
| System | Processor architecture | Format | Use case | Download |
|---|---|---|---|---|
| Windows | AMD64 | .zip | Windows x64 command-line and service deployment | Download AMD64 |
| Windows | ARM64 | .zip | Windows on ARM devices | Download ARM64 |
| macOS | Intel AMD64 | .gz | Intel Mac command-line environment | Download Intel |
| macOS | Apple Silicon ARM64 | .gz | Apple M-series chip | Download Apple Silicon |
| Linux | AMD64 | .deb | Debian and Ubuntu servers | Download DEB |
| Linux | AMD64 | .gz | Generic x64 Linux environment | Download AMD64 |
| Linux | ARM64 | .gz | 64-bit ARM servers and routers | Download ARM64 |
| Linux | ARMv7 | .gz | 32-bit ARMv7 router devices | Download ARMv7 |
| Linux | MIPS softfloat | .gz | MIPS router devices using the soft-float ABI | Download MIPS softfloat |
Prepare the main configuration file before startup, and confirm the paths required for rule sets, GeoIP, databases, and external control interfaces. The service account must be able to read the configuration directory and write runtime logs.
On Linux servers, use systemd to manage startup, restarts, and boot-time execution. After each configuration change, run a foreground test to verify syntax and ports before handing control to the service manager.
Do not choose a file based only on the router brand. Confirm the CPU instruction set, bitness, operating system, and floating-point ABI; an architecture mismatch makes the core impossible to execute.
Before downloading, confirm the device, maintenance status, and traffic-routing scope. Choosing the right client helps avoid startup failures, insufficient permissions, and architecture mismatches.
Windows, macOS, Android, and iOS users usually start with a GUI client. The interface centralizes configuration import, policy-group switching, system-proxy controls, and log viewing, making each step easier to verify.
Clash Plus is the top pick on Windows, macOS, Android, and iOS. On the Linux desktop, start with Clash Verge Rev, then choose DEB or RPM according to your distribution.
The same operating system can run on different processors. macOS supports both Intel and Apple Silicon; Android includes ARM64, 32-bit ARM, and x86_64; Linux servers and routers have even wider architectural differences.
A successful package download does not prove that the architecture is correct. If startup shows a format error, execution failure, or installer refusal, recheck the CPU architecture instead of repeatedly changing proxy settings.
After the first launch, import a valid subscription or local configuration. A successful import usually shows policy groups, nodes, and rules; if the content is empty, check the update log and configuration parsing errors.
Choose a policy before connecting, then enable the system proxy. Evaluate TUN mode and administrator permissions only when you need to route traffic from apps, games, or command-line tools that do not follow the system proxy.
Clash for Windows and ClashX Meta are no longer maintained. Their archived entries are kept for legacy recovery, configuration export, and migration troubleshooting, not as the default choice for new devices.
Do not change every network setting at once during migration. Keep the original configuration, then verify the subscription, ports, rule mode, DNS, and system proxy in sequence; confirm each result through logs or an access test.
These questions cover architecture selection, first connection, standalone cores, and archived clients. See the Quick Start page for the complete configuration-import workflow.
For typical desktop use, start with Clash Plus. To compare interfaces, configuration workflows, or TUN controls, review Clash Verge Rev, FlClash, and Clash Nyanpasu.
Clash for Windows is no longer maintained and is mainly for legacy configuration compatibility, existing-environment recovery, and migration. For new installations, choose a maintained client rather than treating legacy behavior as the current configuration standard.
Open About This Mac from the system menu and check the chip or processor field. If it shows an Apple M1, M2, M3, or M4 model, choose Apple Silicon or ARM64; if it shows an Intel processor, choose x64 or Intel.
Do not identify the architecture solely by the macOS version. The same macOS version can run on either processor family; choose the package based on the chip.
arm64-v8a targets 64-bit ARM devices and is the common choice for most recent phones and tablets. armeabi-v7a targets older 32-bit ARM devices. A universal package includes support for more architectures and is useful when the processor type cannot be confirmed.
x86_64 is common on emulators and a small number of specific devices. Standard ARM phones usually cannot install or run an x86_64 package, so check the device system information first.
The package only provides the client or core. After first launch, import a valid subscription or local configuration, wait for parsing to finish, choose an available policy, and enable the system proxy or another routing method.
If no policies or nodes appear after import, check the subscription update log, network response, and configuration syntax first. If nodes are available but websites do not load, check the active policy, system proxy, DNS, and firewall status.
Usually not. Most GUI clients include or manage the core required at runtime. Standalone Mihomo files are mainly for servers, routers, containers, command-line services, and environments where you arrange the working directory yourself.
A standalone deployment also requires handling configuration files, service accounts, logs, ports, autostart, and permissions. If you only need to import a subscription and switch policies on a personal computer, a GUI client offers a more direct workflow.
A discontinued client may still run on some existing systems, but it will not receive new features or compatibility fixes. Keep it mainly to read existing configurations, complete a migration, or troubleshoot a legacy environment.
Copy configuration files and subscription details before migrating. After launching the new client, restore the basic configuration first, then verify rules, DNS, mixed ports, the system proxy, and TUN settings one by one instead of overwriting all network parameters at once.