Installer selection / architecture check / configuration import
Choose an entry by operating system, then verify the processor architecture. For everyday use, start with a graphical client; for servers, routers, and self-hosted environments, see the Mihomo kernel section.
Graphical clients
Buttons identify the package format and architecture. Mobile VPN authorization, desktop system proxies, and TUN permissions are handled separately; do not let multiple clients take over the network at once.
Open “System → About” in Windows Settings and confirm the system type. The client installers in this section are x64; an ARM device cannot be judged compatible from the Windows edition name alone.
Start here for a first installation. After installing, import an existing configuration, then choose a policy and proxy-takeover method. Avoid enabling every network option before a valid configuration has loaded.
For desktop users who want to manage configurations, policy groups, and local overrides through a graphical interface. When searching for Clash Verge downloads, distinguish the project name carefully; menus in older guides may not match the current Rev interface.
A practical client option for use across devices. Permissions and network-takeover methods still differ by system; after importing the same configuration, verify DNS, rules, and policy groups individually.
For desktop users who want to compare configuration-management workflows. When switching clients, disable the old instance's system proxy and background service first to avoid a port conflict that could be mistaken for a damaged subscription or node.
Kept for reproducing legacy environments and reference during configuration migration, not recommended for new installations. The older kernel has limited support for newer protocols and fields; importing YAML does not prove that every rule is active.
| Check | Requirement or limitation | Recommended action |
|---|---|---|
| Processor | This section primarily provides x64 installers | In System Information, confirm “x64-based processor”; check compatibility separately for ARM devices. |
| System and dependencies | Minimum system versions vary by project | Keep Windows updated; follow the installer prompt when a dependency is missing instead of repeatedly downloading the same file. |
| Proxy permissions | System proxy and TUN are separate switches | Use the minimum permissions needed to connect; enable service installation and virtual-network-adapter access only when required. |
Check the chip in “About This Mac”: Apple M-series machines use Apple Silicon, while Intel models should use x64. After installation, move the app to Applications, then launch it and import your configuration.
Choose the installer that matches your chip. On first launch, import the configuration and choose a policy before enabling the system proxy; if the app requests additional network permissions, confirm the scope against the takeover method you actually use.
For desktop setups that use subscription configurations and retain local overrides. Record the configuration merge method before updating, then check the final configuration afterward rather than relying only on source files in an editor.
Consider this option when you want a similar configuration-management workflow across devices. A phone's VPN authorization does not transfer to Mac; first launch still requires separate proxy setup, configuration selection, and browser-connection testing.
This archived option is for reviewing and migrating legacy configurations. A name containing Meta does not mean the kernel will keep up with new fields; recheck compatibility after upgrading the system or changing subscription formats.
| Check | Requirement or limitation | Recommended action |
|---|---|---|
| Chip | Choose separately between Apple Silicon and Intel | Check the chip in “About This Mac” rather than guessing from the model name or purchase year. |
| System version | Follow the installer and app release requirements | If the app will not open, record the system prompt first; architecture and minimum system version are separate requirements. |
| Network takeover | Proxy settings may be managed by a client helper service | Exit the old app before migrating and confirm that the system proxy no longer points to a discontinued local port. |
Confirm the ABI supported by your system before choosing an APK. Most newer phones use ARM64, but a 64-bit processor does not necessarily mean the system provides a 64-bit app environment.
For Android environments supporting arm64-v8a. Grant installation permission only to the browser or file manager actually being used; when starting a connection, approve the VPN request according to the system prompt.
For Android users who need to import Clash Meta-compatible configurations. Architecture-specific packages avoid unnecessary components; if the ABI is unknown, consider the universal package, but it does not lower the minimum system requirement.
Supports configuration import and policy selection on phones. Check app selection, background persistence, and system VPN status separately; a VPN icon only shows that takeover was established, not that the remote proxy is reachable.
Listed as an alternative Android configuration solution. Surfboard uses a configuration syntax different from Clash YAML; confirm that the subscription service provides compatible output before installing, and do not copy Clash policy-group fields directly.
| Check | Requirement or limitation | Recommended action |
|---|---|---|
| ABI | ARM64, 32-bit ARM, or universal package | Check the device specifications or system ABI information; do not choose a package solely from processor marketing specifications. |
| Installation authorization | Allow apps to be installed from the current source | Grant permission only to the installation source used this time, and record the system's reason if installation fails. |
| VPN and background operation | Normally, only one VPN service should take over a given user environment | Stop other VPNs first; for long-running connections, check battery optimization and background restrictions. |
Check device compatibility, app details, and update information in the App Store before installing Clash Plus. Network takeover uses system authorization; importing a configuration and authorizing the connection are separate steps.
After installation, prepare a trusted configuration in a compatible format and import it through the app's configuration or subscription entry. Read the system VPN prompt on first connection; after approving it, choose a policy and verify with actual access rather than watching the toggle alone.
| Check | Requirement or limitation | Recommended action |
|---|---|---|
| Device compatibility | Follow the device and system requirements listed on the store page | Check compatibility notes before installing; do not apply support information from other platforms to iOS. |
| VPN authorization | The system confirms the first takeover request | Confirm that the request comes from the installed client; if there is a conflict, stop other VPN connections first. |
| Configuration and verification | A valid configuration and reachable proxy service are required | Load the subscription first, then test the target app; retest separately after switching between Wi-Fi and cellular networks. |
Confirm the distribution's package system and CPU architecture first. This section provides AMD64 / x86_64 desktop packages; on headless servers, go directly to the Mihomo kernel.
Debian- and Ubuntu-based distributions generally use DEB; distributions built around RPM packages use RPM, then continue checking dependencies. A correct package format does not guarantee that every distribution release meets the runtime requirements.
For desktop environments using the DEB package system. After installation, verify the graphical interface, configuration loading, and proxy takeover separately; terminal programs may not use the desktop system proxy and must be configured individually.
| Check | Requirement or limitation | Recommended action |
|---|---|---|
| Architecture | Desktop packages are AMD64 / x86_64 | Use uname -m to check the architecture; do not install the x86 package from this section on an ARM device. |
| Package system | DEB and RPM cannot be swapped by changing only the file extension | Choose the format supported by the distribution, then let the package manager check dependencies. |
| Graphical session | GUI clients require a compatible desktop runtime | Use kernel deployment on headless servers; TUN also requires separate device and network permissions. |
Command line and service deployment
For servers, routers, and users who manage configuration files themselves. Everyday desktop and mobile users should choose a GUI client above; the kernel file does not automatically provide a subscription-management interface.
| System | Processor architecture | Package format | Download |
|---|---|---|---|
| Windows | AMD64 / x64 | ZIP | Download Windows AMD64 |
| Windows | ARM64 | ZIP | Download Windows ARM64 |
| macOS | Intel / AMD64 | GZ | Download macOS Intel |
| macOS | Apple Silicon / ARM64 | GZ | Download macOS Apple Silicon |
| Linux | AMD64 | DEB | Download Linux AMD64 DEB |
| Linux | AMD64 | GZ | Download Linux AMD64 GZ |
| Linux | ARM64 | GZ | Download Linux ARM64 |
| Linux | ARMv7 | GZ | Download Linux ARMv7 |
| Linux | MIPS softfloat | GZ | Download Linux MIPS softfloat |
Keep a recoverable network setup first, and store configuration and logs in a separate directory. Limit listening addresses and management interfaces to the smallest necessary scope; never expose a debug interface directly to the public internet. Grant only the permissions needed for TUN or route changes, and do not use administrator privileges as a substitute for checking architecture and dependencies.
Check configuration parsing and startup errors in the foreground first, then arrange a background service and startup on boot. Successful startup only confirms the basic prerequisites; also verify rule matches, DNS resolution, and real requests. See configuration validation and troubleshooting for field details, and do not load client-only override scripts directly into the kernel.
From installer to usable configuration
Finishing a download does not mean the connection is ready. Build the smallest verifiable workflow first, then add complex rules, DNS overrides, or full network takeover.
A subscription URL, complete YAML, node list, and single-node share link are different inputs. Check the import types supported by the client, then confirm that the configuration is selected as active rather than merely listed.
A download page requiring login may not be a subscription URL. If it returns a webpage instead of configuration content, check the subscription source and format again. Never submit links containing access credentials to unknown conversion sites.
Rule mode selects handling targets according to the ruleset, while policy groups determine the final proxy or direct-connection path. Changing modes cannot repair a failed node or replace system-proxy or VPN takeover.
For first-time use, keep the rules supplied by the subscription and adjust only the necessary policy-group selections. If you add local overrides, check that the merged configuration still references existing policy groups and node names.
Confirm that the local network works without a proxy first, then enable the selected takeover method and test the target app. A working browser does not mean every app uses the proxy; command-line tools, games, and independent DNS settings require separate checks.
If something goes wrong, stop takeover and restore the original network state before checking whether the log shows a configuration parse error, DNS issue, or connection timeout. When sharing errors, redact subscription URLs, credentials, and private domain names.
A concise guide to installers, system compatibility, and update migration. For deeper field behavior, see the configuration reference.
For everyday desktop and mobile use, start with a client that includes a graphical interface. If your platform has a matching installer, consider Clash Plus first; on Linux, start with Clash Verge Rev. The Mihomo kernel is mainly for users who manage configuration, services, and routing themselves, and downloading it does not include a complete graphical management interface.
Check your processor architecture in system information first. x64, x86_64, and AMD64 generally refer to the same 64-bit x86 architecture; ARM64 and arm64-v8a refer to 64-bit ARM; armeabi-v7a is for compatible 32-bit ARM environments. Universal packages include multiple architectures, so they are usually larger and still subject to minimum system-version requirements.
In the current download list, both Mac architecture links for Clash Verge Rev, FlClash, and ClashX Meta point to their respective x64 files. The page preserves and clearly labels this original mapping. Apple Silicon users should not treat these links as native ARM packages; confirm Rosetta compatibility or choose a client with an explicitly labeled ARM64 installer.
An installer is not the same as a usable proxy configuration. Import a trusted, compatible subscription or local YAML, choose an available policy, and enable the system proxy or approve VPN access according to your platform. Confirm that the local network works first, then check configuration loading, DNS, and proxy takeover; an open interface alone does not prove a successful connection.
Save the original configuration, local overrides, subscription source, and any essential client settings first. Keep backups in a trusted local location. Disable proxy takeover in the old client before updating to prevent two instances from competing for a port. After updating, recheck the active configuration, policy-group selection, and permission status; never publicly share subscription URLs or credentials found in logs.
Compatibility should not be assumed. Clash for Windows and ClashX Meta are retained here as archived options, but older kernels may not recognize newer protocols, DNS options, or rule fields. For a new installation, choose a client suited to your current system; when reproducing an old environment, back it up first and test behavior with an isolated configuration.