CLASH / CLIENT PACKAGES
Choose an operating system, then check the processor architecture. Use a graphical client for everyday configuration or the Mihomo core for standalone deployments.
DESKTOP / WINDOWS
Most desktop downloads are currently x64. Check your system type under “Settings → System → About,” then choose the matching installer.
A good choice for a first install or everyday subscription use. After installation, import your configuration and make sure a proxy is selected in a proxy group before enabling the system proxy. When switching clients, turn off the old client’s system proxy and launch-at-startup options first to prevent both apps from changing proxy settings.
clashplus.io
For desktop users who want configuration management, rule inspection and TUN settings. The system proxy and TUN mode cover different traffic. Verify a basic connection first, then install or enable service mode as prompted by the client. If you change a port, check proxy settings in your browser and other apps too.
For users who want a similar workflow across desktop and mobile. Subscriptions can be reused, but window preferences, configuration overrides and permissions may need to be adjusted separately. This is the Windows AMD64 installer; quit any running instance of a similar client before installing.
For users who prefer a graphical desktop app and manage multiple configurations. When migrating, check configuration files, the selected core and proxy ports separately; don’t overwrite the entire application data directory. If the old configuration contains scripts or client-specific fields, load it in the new environment and review the parsing logs first.
The archived download is for reproducing legacy environments and migrating existing configurations. “Windows” in the client name does not mean its core is still updated. Check support for newer protocols, rule fields and current Windows versions separately. For a new installation, choose a maintained client and save a copy of your original configuration before migrating.
| Check | What to look for |
|---|---|
| Operating system | Use a version of Windows 10 or 11 that still receives security updates. Check the installer for its specific minimum version; an archived package does not guarantee compatibility with newer systems. |
| Processor | This section mainly offers x64 / AMD64 packages. On Windows on ARM, check x64 app compatibility. Driver and TUN service support cannot be confirmed just because the app launches. |
| Permissions | The basic interface and configuration import usually don’t require ongoing administrator access. Grant permission when prompted to install a service or virtual network adapter, or change routes. |
DESKTOP / MACOS
Check your chip type in About This Mac. Apple Silicon and Intel use different native installers, so compare the download label with the architecture of the actual file.
Both ARM64 and x64 disk images are available. Choose Apple Silicon for an M-series chip and Intel x64 for an Intel processor. Open the DMG and follow the installer to copy the app. Approve any required permissions on first launch, then import your configuration and check the system proxy.
clashplus.io
For macOS users who want to manage subscriptions, rules and service mode. Both current download options are x64 disk images; Apple Silicon users should check Rosetta requirements. Installing a service or enabling TUN may require system authorization. Afterward, check routing and DNS behavior.
Manage proxy configurations and routing choices on macOS. The current download points to an AMD64 disk image; Apple Silicon users should check compatibility requirements. When importing a configuration from another client, check listening ports, DNS settings and local file paths.
An archived client for restoring legacy menu bar workflows and migrating configurations. The current listing provides an x86_64 image, and both architecture options point to the same file. Background permissions and helper services may behave differently on newer systems; choose a maintained client for a device you plan to use long term.
| Check | What to look for |
|---|---|
| macOS version | Use a macOS version that still receives updates. Minimum requirements depend on the client build. Check the system compatibility prompt before installing; don’t assume another client has the same requirements. |
| Chip type | If About This Mac lists an Apple M-series chip, choose ARM64. If it lists an Intel processor, choose x64. For compatibility builds, also check Rosetta and background service support. |
| System authorization | If you see a security prompt, check the app’s source and the reason for the warning, then approve it in System Settings if appropriate. Disabling macOS security protections entirely should not be a routine installation step. |
MOBILE / ANDROID
Most modern phones use ARM64. Check for an ARM build if you have an older device. If you’re unsure which architecture it uses, Clash Meta for Android offers a universal build.
For ARM64 Android devices. Install the APK, import a subscription and approve the system VPN request the first time you connect. Background operation also depends on your device’s battery settings. Allow background activity if needed, while keeping essential system security restrictions in place.
clashplus.ioAndroid installers are available for multiple architectures. ARM64 suits most modern phones; ARM is for devices still running a 32-bit environment; and the universal build is for when you’re unsure of the architecture. After importing a subscription, check that the intended configuration is enabled, then grant VPN access.
For users already running FlClash on desktop who want a similar configuration workflow on their phone. VPN routing on mobile is not the same as the desktop system proxy. Even with the same subscription, check app routing, DNS and background settings again.
Surfboard uses its own configuration syntax and supported protocols, so don’t assume it can read every Clash YAML configuration. If you already have a Clash subscription, ask the provider whether a Surfboard-compatible format is available. Simply changing the file extension is not enough to make it importable.
| Check | What to look for |
|---|---|
| Android version and architecture | Check your device’s Android version and CPU ABI. The APK installer will indicate the specific minimum Android version. A 64-bit processor does not necessarily mean the operating system supports every 64-bit app. |
| Installation permissions | Android may ask you to temporarily allow app installs from the browser or file manager you’re using. After installation, adjust this permission to suit your device management preferences. |
| VPN and background operation | Multiple VPN-based apps generally can’t run at the same time in the same user environment. If another app takes over the connection, check which VPN is active before reviewing background restrictions. |
MOBILE / IOS
Check Clash Plus in the App Store for compatible devices, system requirements and updates, then install the app and import your configuration.
Install from the App Store, import a configuration you’re authorized to use, and approve the system VPN configuration the first time you connect. Check the App Store listing for updates and device compatibility. Before using the app, review your proxy groups and rule mode—installation alone doesn’t mean it’s configured.
clashplus.io| Check | What to look for |
|---|---|
| Device compatibility | Check the App Store compatibility section for minimum iOS versions and supported devices. Before installing, make sure you have enough storage and keep a recoverable copy of your configuration. |
| Connection authorization | The first connection requires approval to add a VPN configuration. If your device is managed by an organization, follow its device management policies and network use requirements. |
| Prepare a configuration | Get a subscription or configuration file supported by the client. Subscriptions, proxy services and client installation are separate things; you’ll still need to import and test your configuration after installing the app. |
DESKTOP / LINUX
Graphical clients are for desktop sessions. Choose DEB for Debian- and Ubuntu-based distributions, RPM for RPM-based distributions, or switch to the core section for server deployments.
Desktop installers are available as AMD64 DEB and x86_64 RPM packages. Use your distribution’s software installer or package manager to handle dependencies; package format is not the same as CPU architecture. Before enabling TUN, check service permissions, virtual network adapter support and existing system routes.
This section provides a Linux AMD64 DEB package for desktop environments that support its package format and dependencies. After installation, launch it in a graphical session and check that the tray icon and window appear correctly. If the app runs but other programs aren’t using the proxy, check your desktop environment’s system proxy settings.
| Check | What to look for |
|---|---|
| CPU architecture | Run uname -m to check the architecture. x86_64 matches the AMD64 packages in this section; aarch64 devices can’t use these desktop packages. |
| Distribution and dependencies | DEB and RPM packages are for their respective package management systems. Runtime library requirements depend on the client build. If dependencies are missing, use your distribution’s package manager to install them. |
| Desktop and network permissions | A graphical client requires an active desktop session. The system proxy may not cover every command-line program; TUN requires additional network permissions and appropriate routing configuration. |
ENGINE / MIHOMO
For servers, routers and command-line users. Desktop and mobile users should choose a graphical client above to avoid managing permissions, startup and configuration themselves.
| Platform | Architecture | File format | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download core |
| Windows | ARM64 | ZIP | Download core |
| macOS | Intel AMD64 | GZ | Download core |
| macOS | Apple Silicon ARM64 | GZ | Download core |
| Linux | AMD64 | DEB | Download core |
| Linux | AMD64 | GZ | Download core |
| Linux | ARM64 | GZ | Download core |
| Linux | ARMv7 | GZ | Download core |
| Linux | MIPS softfloat | GZ | Download core |
When choosing a core, check the operating system, CPU instruction set and device environment. AMD64 and ARM64 are not interchangeable, nor are ARMv7 and ARM64. For MIPS routers, also confirm endianness, floating-point ABI and firmware integration. Don’t choose a file based only on the product name.
GZ files are usually compressed executables; extract them and set execute permissions as required by your system. Extract ZIP files before use, and install DEB files with a compatible package manager. Don’t try to run a compressed file directly. Before replacing an existing service, back up its configuration and confirm the new core can read it before switching processes.
Standalone operation requires writable configuration and data directories. DNS, listening ports and TUN may also require additional permissions; grant only what the required features need. For protocol support and configuration fields, see the protocol and core reference. For the basics, see the Clash configuration guide.
AFTER INSTALLATION
The installer deploys the app; your subscription and rules determine how connections work. Follow these checks to help pinpoint configuration and permission issues.
01 / CONFIGURATION
Prepare a subscription URL or local YAML file you’re authorized to use, then import it from the client’s configuration page. Downloading the client does not provide a proxy service. After importing, check for parsing errors and make sure the imported configuration—not a blank example or older config—is enabled.
Subscription updates may overwrite configuration changes. To keep custom rules, use the client’s supported override or merge features rather than editing a file that the next update will replace.
02 / NETWORK MODE
In rule mode, outbound connections are selected according to the matching order in your configuration. The system proxy mainly affects apps that follow system proxy settings. TUN may capture more connections and also involves a virtual network adapter, DNS and routing. Test with the simpler system proxy first, then decide whether to enable TUN.
Don’t run multiple clients that modify the system proxy at the same time. If a port is already in use, quit the old process and check listening ports instead of reinstalling repeatedly.
03 / MIGRATION
Before updating, back up your subscription source, custom rules and key settings. Client and core versions are separate; an update doesn’t necessarily mean every protocol behaves the same way. When switching clients, check that the target core supports your protocols, rule sets and DNS fields.
When troubleshooting, note the operating system version, package architecture and log errors. Hide subscription URLs, credentials and personal network details before sharing screenshots. For help choosing a client, see the client comparison.
DOWNLOAD / QUESTIONS
Start with Clash Plus on Windows, macOS, Android or iOS, and Clash Verge Rev on Linux. Check your operating system and CPU architecture before choosing a package. For a comparison of interfaces, configuration management and operating modes, see the client comparison.
Choose based on your device’s processor, not just its operating system. x64 and AMD64 generally refer to the same architecture; ARM64 and AArch64 generally do too. If you’re unsure which architecture your Android device uses, choose the universal build of Clash Meta for Android. Some macOS download options currently point to the same x64 file; Apple Silicon users should check Rosetta compatibility.
The client installer does not include a proxy service. You’ll need a subscription URL or configuration file you’re authorized to use. Import it, then check your proxy groups, rules and DNS settings. Test the system proxy first; consider TUN mode only if your apps require it.
Usually not. Before updating, export your configuration and note your subscription source and custom rules. Quit the running client before installing the update. When moving to a different client, check interface preferences, scripts and configuration overrides separately, as they may not be compatible.
Both clients are discontinued. Their archived downloads are provided for reproducing legacy environments and migrating existing configurations. Older cores may not support newer protocols or configuration fields, so these clients are not recommended for new devices. Keep a copy of your original configuration and verify it in a maintained client before migrating.
Mihomo is a proxy core, not a complete desktop app with a graphical interface. Running it on its own requires you to prepare a configuration, set up how it starts and manage permissions. It’s suited to servers, routers and command-line environments. Desktop and mobile users should generally choose a graphical client.