Windows · macOS · Android · iOS · Linux
Choose a client by operating system, CPU architecture, and usage scenario. Desktop and mobile users should generally choose a graphical client; servers, routers, and automated environments can select the Mihomo core below.
Platform Installers
The platform tab is preserved in the page URL, so you can copy the current link and return directly to the relevant download section. Version details appear only when the manifest returns valid data.
WINDOWS / DESKTOP
Windows 10 and Windows 11 users can choose from Clash Plus, Clash Verge Rev, FlClash, and Clash Nyanpasu. For a first installation, the installer is recommended because it creates shortcuts and simplifies future upgrades. On managed devices where drivers or administrator access are restricted, test the basic connection with the system proxy first before enabling TUN.
| Check | Recommendation |
|---|---|
| System | 64-bit Windows 10 or Windows 11 |
| Processor | x64; this page does not provide a separate Verge ARM64 build |
| Permissions | Administrator access is required to install services or enable TUN |
A graphical client for everyday desktop use, with convenient access to subscription imports, policy selection, the system proxy, rule modes, and connection logs. Ideal for users who want a clear path from installation to a working connection.
Suited to desktop users who need to inspect rules, policy groups, overrides, and runtime logs. System proxy and TUN can be controlled separately after installation; avoid enabling multiple traffic-capture methods before verifying the configuration.
A consistent cross-platform interface for users who work across Windows, macOS, Linux, or Android. The installer suits standard desktops, while the archive is better for users who understand portable directories and configuration locations.
Provides a graphical desktop interface and configuration management for subscription updates, proxy-mode switching, and connection-log review. When moving from another client, re-import the subscription instead of overwriting the other client’s entire data directory.
This client is no longer maintained. The download remains available mainly for compatibility with and migration from older configurations. For new installations, choose a maintained client; during migration, record the subscription URL, proxy mode, custom rules, and port settings.
MACOS / DESKTOP
Before downloading, check the chip type in About This Mac. Models with M1, M2, M3, M4, and other M-series chips should use Apple Silicon or ARM64; Macs showing an Intel processor should use x64. The first launch of an app downloaded from the internet may require confirmation. Enabling a proxy extension or network service may also require system approval.
| Check | Recommendation |
|---|---|
| Chip | Apple Silicon: ARM64; Intel: x64 |
| Installation | Open the DMG and move the app to Applications |
| Permissions | Follow the system prompts to approve the network extension or proxy service |
A macOS interface for managing subscriptions, policies, the system proxy, and connection status. Choose the installer that matches your Mac’s chip; after installation, import the configuration before allowing the client to change system proxy settings.
For macOS users who need to manage rules, overrides, DNS, and TUN. The two architecture links in this list are maintained by the version service; after downloading, confirm compatibility between the package and your Mac’s actual chip.
A cross-platform client for users who want a similar workflow across operating systems. After installing the DMG, launch the app from Applications and recheck the configuration location and system proxy status inside the client.
This client is no longer maintained. The download is retained for existing-user migration and older configuration compatibility. For a new macOS proxy setup, choose a maintained client and migrate subscriptions, custom rules, and DNS settings individually.
ANDROID / MOBILE
Most recent Android phones use ARM64. Older 32-bit devices can use ARM; if the architecture is unknown, use the universal package for Clash Meta for Android. On the first connection, Android asks to create a VPN connection, a required system permission for routing app traffic.
| Check | Recommendation |
|---|---|
| Common devices | Prefer ARM64-v8a |
| Older devices | Choose ARMv7 after confirming the device is 32-bit |
| Background operation | Allow the client to run continuously and disable aggressive battery-saving restrictions |
For mainstream ARM64 Android phones and tablets, with subscription imports, policy-group selection, connection controls, and logs. After installation, allow the VPN connection and adjust battery optimization to prevent the system from terminating background connections.
A commonly used Clash Meta graphical client for Android, offering ARM64, ARM, and universal packages. Choose the matching file when the device architecture is known to reduce download size; choose the universal build for easier installation when it is unclear.
For users who run FlClash on both desktop and Android and want a similar interface and configuration workflow. ARM64 and ARM builds are available; choose according to the device’s CPU ABI, with ARM64 preferred for most newer devices.
An Android graphical client for importing compatible configurations and creating a system VPN connection. The universal package suits devices with varied Android CPU architectures; before importing, confirm that the configuration format and rule fields are supported by the client.
IOS / IPADOS
iOS and iPadOS users can get Clash Plus from the App Store. After installation, import a subscription or configuration, choose a policy, and allow the system to add a VPN configuration. Once connected, look for the VPN indicator in the system status area, then use a browser test page to confirm the traffic path.
| Check | Recommendation |
|---|---|
| Device | iPhone or iPad |
| How to get it | Install from the App Store |
| First connection | Follow the system prompt to allow a VPN configuration |
A proxy tool for iPhone and iPad with subscription imports, policy switching, and system VPN connectivity. After installation, add a subscription, wait for the configuration to finish parsing, select a policy group, and start the connection. Official information is available at clashplus.io.
LINUX / DESKTOP
Desktop Linux users can choose Clash Verge Rev or FlClash. Debian, Ubuntu, and derivatives generally use DEB packages; Fedora, RHEL, Rocky Linux, and other RPM-based distributions use RPM packages. If you need to route all traffic after installation, also check desktop proxy settings, service permissions, and firewall rules.
| Distribution | Package format |
|---|---|
| Debian / Ubuntu | AMD64 DEB |
| Fedora / RHEL family | x86_64 RPM |
| Other desktop distributions | Use AppImage when compatible |
For AMD64 Linux desktops, with DEB and RPM packages. Use the package for your distribution for standard installation and application-menu integration. If the system proxy does not activate automatically, check the HTTP, HTTPS, and SOCKS proxy fields in the desktop network settings.
Provides DEB, RPM, and AppImage builds for Linux AMD64. For standard installations, use the package matching your distribution for easier menu management; AppImage is better suited to desktops that should not write to the system package database.
Mihomo Core
The core is intended for servers, routers, containers, and command-line environments. You must provide the configuration file, service startup method, log directory, and permission rules. Most desktop and mobile users should choose a graphical client above.
| System | CPU architecture | File 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 soft-float | GZ | Download MIPS |
Server environments typically specify the configuration directory through command-line arguments and use systemd or another process manager to keep the service running. Check the listening address before deployment so the control interface is not exposed to an untrusted network. After changing rules or DNS, review the startup log to confirm that the configuration parses correctly.
Routers require a binary that matches the CPU architecture and firmware runtime. ARM64, ARMv7, and MIPS soft-float builds are not interchangeable. The core handles proxy processing only; transparent forwarding, DNS hijacking, policy routing, and startup services must be configured by the router system or management plugin.
Installation and Migration
Installing the client is only the first step. Follow the order “back up, install, import, verify, then route traffic” to reduce conflicts between old settings, the system proxy, and the TUN driver.
Before upgrading or switching clients, save the subscription URL, custom rules, overrides, DNS settings, and frequently used policy-group selections. Client data directories differ, so copying an entire directory can carry old caches, databases, or incompatible fields into the new client. A safer approach is to re-import the subscription and restore only the custom content you actually need.
Windows and common Linux desktops mainly use x64 or AMD64; Apple Silicon Macs use ARM64; Intel Macs use x64. Android devices are mostly ARM64, while older devices may still use ARMv7. Choosing the wrong architecture commonly causes the installer to fail, an incompatibility warning, or a command-line file-format error.
After installation, open the client and paste the address supplied by your service provider into the subscription or configuration page. Wait for parsing to finish. If no policy groups or nodes appear, check that the subscription URL is complete and reachable, then review network requests and parsing details in the log. Do not repeatedly switch the system proxy and TUN before the configuration has loaded successfully.
Choose an available policy, start with rule mode, and enable the system proxy. Use a browser to test basic web access and direct-connection sites. Rule mode determines traffic routing according to the configuration’s matching order, making it a useful starting point for the first connection. If every request fails, check the client log before changing multiple DNS or routing parameters.
Some games, command-line programs, and apps that ignore system proxy settings require TUN. Before enabling it, confirm that the client has administrator access and close other VPNs, virtual adapters, or similar proxy programs. If the network goes down, disable TUN first, restore the system proxy and DNS settings, and isolate the conflict one variable at a time.
For complete Windows, macOS, Android, iOS, and Linux installation workflows, see the full-platform documentation. If you only need to import a subscription and connect quickly, open the quick-start guide.
Download Issues
These questions cover client selection, CPU architecture, configuration imports, and core usage. For connection problems, start by checking whether the configuration loaded successfully, whether the system proxy is enabled, and whether the log reports errors.
For everyday desktop use, start with Clash Plus, which covers subscription imports, policy switching, the system proxy, and log review. Choose Clash Verge Rev for more detailed management of rules, overrides, DNS, and TUN. FlClash suits users who want a similar interface across multiple systems, while Clash Nyanpasu is useful for managing multiple configurations. Clash for Windows is no longer maintained and is retained mainly for migration from older environments, so it is not recommended for new deployments.
Open the Apple menu in the upper-left corner and select About This Mac. If the chip shows an Apple M-series processor, choose Apple Silicon or ARM64. If it shows an Intel processor, choose Intel or x64. A mismatched architecture may prevent the app from opening or cause it to rely on system translation. Confirm the chip type before downloading to avoid installation and upgrade problems.
Most recent Android phones use ARM64-v8a, so ARM64 is the preferred choice. Older 32-bit devices use armeabi-v7a, also labeled ARM. If you cannot confirm the architecture, choose the universal package for Clash Meta for Android. After installation, the first connection requests system VPN permission. If the connection drops after running in the background, check battery optimization, background activity, and the manufacturer’s power-saving restrictions.
The client itself does not include a ready-to-use proxy configuration. After installation, import a valid subscription or local configuration, wait for policy groups and rules to finish parsing, choose an available policy, and enable the system proxy. Mobile platforms also require permission to create a system VPN connection. If no policies appear after import, check that the subscription URL is complete. If policies exist but websites do not load, review connection errors, DNS errors, and rule-matching results in the log.
The Mihomo core reads configurations, matches rules, handles DNS, and forwards connections, usually through the command line, a system service, or router management tools. It does not provide a full desktop interface and does not manage services, transparent forwarding, or startup behavior for the system. Most Windows, macOS, Android, iOS, and Linux desktop users should choose a graphical client; server and router administrators can select a core binary based on the architecture.
At minimum, record the subscription URL, custom rules, overrides, DNS parameters, policy-group selections, and local-network access settings. If TUN is enabled, also note the virtual adapter and service installation status. When migrating to a new client, import the subscription and test rule mode first. Restore custom rules, DNS, and TUN only after basic access works, so subscription issues, system-permission problems, and conflicts from old settings can be distinguished.