Choose your operating system, then pick an installer. Set up subscription import and rules after installation.
Use a GUI client on desktop or mobile. For servers, routers, and command-line environments, see the Mihomo core. Downloads are organized by platform, with discontinued clients clearly marked.
If this is your first time, start with the recommended client. Check your system architecture before installing, and back up local configuration before switching clients. When testing on the same device, let only one client manage the proxy or TUN.
The GUI clients in this section are x64 builds. Check Settings → System → About to find your system type, then choose a client. Windows on ARM devices should also be checked for x64 app compatibility; the Windows edition alone doesn’t determine whether an app will run.
A good choice for first-time users who want to import a configuration, choose proxy groups, and manage connections through a GUI. Install the app, then import an existing subscription. If it includes custom proxy groups, keep the original configuration and confirm it works before changing rules.
EXE installer · Official site: clashplus.io
Choose this client if you need to manage subscriptions, rules, and desktop proxy settings. After installation, check which configuration is active and whether the system proxy is enabled. Service mode and TUN require system permissions, so enable them one at a time after confirming a basic connection works.
EXE installer
Consider FlClash if you want a similar workflow across devices. After importing a subscription, select the configuration, then choose an outbound in the proxy groups. When migrating, check the configuration and client settings separately; system proxy and startup options usually need to be reviewed again.
EXE installer · amd64 and x64 denote the same architecture family
An alternative desktop interface for users with an existing configuration. Quit the current client before switching to avoid both apps changing system proxy settings. If a port is already in use, find the process using it instead of repeatedly reinstalling.
EXE installer
Archived download for migrating existing setups and referencing older configurations. For new installations, choose a client listed above. Older versions may not recognize newer proxy protocols or configuration fields. If parsing fails, check which features the core supports instead of deleting every flagged field.
Legacy client · Export your local configuration before migrating
| Check | What to look for |
|---|---|
| Processor | This section offers x64 GUI clients; 32-bit systems aren’t supported. |
| Windows version | Follow the installer’s requirements. Older Windows versions may need specific runtimes and a supported client version. |
| Permissions | Running the GUI and installing a service require different permissions. Follow system prompts when enabling a service or TUN. |
| After installation | Import a configuration and test rule mode first. Set up startup and background operation afterward. |
Open Apple menu → About This Mac to check whether your Mac has Apple silicon or an Intel processor. After downloading the DMG, move the client to Applications and launch it from there. Some compatibility links currently point to the same x64 file; the notes below describe the actual file architecture, not a promise of a native build.
Separate installers are available for Apple Silicon and Intel. Choose the right one for your chip, move the client to Applications, then import your configuration and check your proxy groups. Store custom rules you want to keep in a supported override location so subscription updates don’t replace them.
DMG installer · Official site: clashplus.io
A good fit if you need desktop configuration management and rule debugging. Both downloads are x64 builds; Apple Silicon users should check Rosetta and client compatibility. If macOS displays a permissions prompt on first launch, read it before granting access.
DMG installer · Check Apple Silicon compatibility first
A way to maintain a similar configuration workflow across desktop and mobile. The current macOS download is marked amd64, and the Apple Silicon link points to the same compatibility build. After installation, quit other proxy clients first to prevent conflicting system proxy settings.
DMG installer · Check your system’s compatibility prompts
Archived client for existing setups and migration of older configurations. The current file is x86_64; Apple Silicon users should check compatibility before installing. If you run into issues with a newer system or subscription, consider moving to a current client and restoring your configuration and custom rules gradually.
DMG installer · For legacy setups
| Check | What to look for |
|---|---|
| Chip | Use a native arm64 build for Apple silicon and an x64 build for Intel Macs. |
| Compatibility builds | Before running an x64 file on Apple silicon, check Rosetta and client support. |
| Windows version | Minimum requirements vary by client; follow the installer and launch prompts. |
| Permissions and location | Move the app to Applications before launching. Grant permissions for proxy helper services and network extensions as needed. |
Most recent phones use arm64, but check the ABI supported by your device. After downloading the APK, grant install permission only to the file manager or browser you’ll use. The first connection requires Android’s VPN permission; afterward, check battery optimization and whether the subscription is enabled.
An arm64 build for importing subscriptions and choosing proxy groups in a mobile interface. Enable the configuration before starting a connection. If it drops after changing networks, check Android’s VPN status and background restrictions rather than reinstalling first.
APK installer · Official site: clashplus.io
Available in arm64, 32-bit ARM, and universal builds. Choose the matching architecture if you know your device ABI; if not, consider the universal build. After installation, check that the configuration is selected and review Android’s background restrictions. If the connection drops when the screen turns off, check battery settings and connection logs.
APK installer · Choose the build for your device ABI
Available for arm64 and 32-bit ARM. A good option if you already use FlClash on another device and want a similar configuration workflow. After migrating a subscription, set up Android VPN permission and background settings again; desktop system proxy settings aren’t carried over in YAML.
APK installer
An alternative Android client. Check which configuration formats it supports before importing. Don’t assume a Clash YAML file can be used directly as a Surfboard configuration. If your configuration comes from another client, verify its format and fields first.
APK installer · Check the configuration format before importing
| Check | What to look for |
|---|---|
| Architecture | arm64-v8a is 64-bit ARM; armeabi-v7a is 32-bit ARM. |
| Windows version | Check the installer for minimum Android version and device compatibility. |
| Connection permissions | Grant VPN permission when prompted on first connection. Avoid running another VPN at the same time. |
| Background operation | Adjust battery restrictions as needed. Check when disconnections occur before changing background settings. |
Check compatibility and install through the App Store. The listing shows current system requirements, release notes, and app details. After installation, open the client, import an existing subscription, then follow the prompts to add a VPN configuration.
Install Clash Plus from the App Store. After importing a configuration for the first time, make sure a valid outbound is selected in the proxy groups before connecting. Granting system VPN permission and importing a client configuration are separate steps; completing one doesn’t finish the connection setup.
If you already have a configuration on another device, check that the current client supports its protocols and fields. Copy the full subscription URL; messaging apps may truncate its parameters. Find app details on the official site: clashplus.io.
Check the App Store listing for current compatibility and availability
| Check | What to look for |
|---|---|
| System compatibility | Check your device and OS version in the Compatibility section of the App Store listing. |
| Install source | Install from the App Store link in this section. Find app details at clashplus.io. |
| VPN configuration | Follow the system prompt to grant permission on first connection, then check VPN status in Settings. |
| Prepare your configuration | Have a subscription URL or supported configuration ready before installing. Check your proxy group selection after importing. |
Check your distribution’s package manager, then your processor architecture. The GUI installers here are amd64: choose DEB for Debian, Ubuntu, and similar systems, or RPM for distributions that use RPM packages. For headless servers, use the Mihomo core below.
DEB and RPM installers are available. Let your system package manager handle dependencies. After launching, check your desktop session, proxy settings, and service permissions. Whether an app uses the system proxy depends on the desktop environment and the app itself; the toggle alone doesn’t show how all traffic is routed.
Choose a package for your distribution
This section offers an amd64 DEB package for Debian-based distributions with a desktop environment. After installation, test configuration import and a regular proxy connection before enabling features that require extra permissions. Terminal apps may need proxy environment variables set separately and might not use desktop proxy settings.
DEB installer · Requires a compatible desktop environment
| Check | What to look for |
|---|---|
| Processor | Check with uname -m; x86_64 usually uses the amd64 package. |
| Distribution | Choose DEB or RPM to match your package manager. Follow the installer’s output for dependency requirements. |
| Runtime environment | GUI clients need a compatible desktop session. Use a core deployment in command-line-only environments. |
| Network permissions | TUN, routing changes, and service management may require administrator privileges. Configure only the features you need. |
The core handles configuration parsing and connections, but doesn’t include a full desktop interface. Most users can use a GUI client above. A manual deployment also requires a config.yaml, launch arguments, a working directory, and a service management method.
| Platform | Architecture / format | Download |
|---|---|---|
| Windows | AMD64 · ZIP | Download AMD64 ZIP |
| Windows | ARM64 · ZIP | Download ARM64 ZIP |
| macOS | Intel AMD64 · GZ | Download Intel GZ |
| macOS | Apple Silicon ARM64 · GZ | Download Apple Silicon GZ |
| Linux | AMD64 · DEB | Download AMD64 DEB |
| Linux | AMD64 · GZ | Download AMD64 GZ |
| Linux | ARM64 · GZ | Download ARM64 GZ |
| Linux | ARMv7 · GZ | Download ARMv7 GZ |
| Linux | MIPS softfloat · GZ | Download MIPS softfloat GZ |
On Linux or a router, run uname -m to identify the machine type, then check the device documentation for its ABI. For MIPS, also verify endianness and floating-point support; the MIPS softfloat build listed here won’t work on every MIPS device. Similar architectures aren’t necessarily binary-compatible. If you get an executable format error, check that you downloaded the right build first.
Extract ZIP and GZ files first; Unix-like systems may also require execute permissions. Once you have a configuration, test parsing with mihomo -t -f config.yaml. A successful test only confirms the configuration parses; you still need to check DNS, routing, and proxy group outbounds. See the YAML structure reference for field details.
Start with a minimal configuration and make sure it works before adding startup tasks, TUN, or custom rules. Change one thing at a time to help identify whether an issue comes from the app, configuration, or network.
Check the file extension after downloading. Use EXE on Windows, DMG on macOS, APK on Android, and DEB or RPM on Linux, depending on your distribution. If you downloaded a web page instead of an installer, return here and choose the right link; changing the extension won’t make it installable. If the system blocks the file or shows a compatibility warning, save the full message and check whether the issue is architecture, OS version, or permissions.
The installer only provides the app; you’ll need to supply your own subscription and proxy nodes. Open the client’s Configuration, Subscription, or Profile page and paste the full subscription URL, or import a local YAML file. Make sure the configuration is selected afterward; a successful download message doesn’t mean the new configuration is active. See how to import a Clash subscription URL. Store URLs with personal credentials somewhere secure, and redact them in screenshots or support requests.
Start with mode: rule in most cases. Open the proxy group matching proxy-groups and check that your selected node is available before enabling the system proxy or connecting on mobile. Rules are matched in order; the final MATCH determines where traffic goes if no other rule matches. If a connection works but some apps aren’t proxied, first check whether they use the system proxy. Consider TUN only after that, and don’t confuse the two traffic-routing methods.
Test connections with the apps you actually use, and check logs for domain matches and outbound policies. A latency test only reflects a specific test request; it can’t replace real-world verification. Once the basic connection works, restore custom rules, background operation, and launch at startup. When switching clients, migrate subscriptions and local overrides first rather than copying the entire data directory. Clients can handle configuration merging, caches, and permissions differently.
This section covers choosing packages and installation issues. For subscription conversion, connection problems, and rule debugging, see Troubleshooting.
For everyday desktop and mobile use, start with a GUI client. Clash Plus is a good first choice. The Mihomo core is mainly for servers, routers, and users who manage their own configuration files; it requires a separate configuration and launch method.
Check your system information to identify the processor architecture. x64 and amd64 usually refer to the same architecture; arm64 is for 64-bit ARM devices. If you’re unsure of your Android ABI, consider the universal build. Some macOS downloads currently provide x64 files; Apple Silicon users should check system compatibility and Rosetta support before installing.
The installer provides the client, not a ready-to-use proxy configuration. Import a subscription you already have or a local YAML file, enable that configuration, then check your proxy group selection and operating mode. Subscription links may contain personal access credentials, so don’t share them publicly.
First, make sure the download finished, the file extension matches your system, and the file wasn’t saved as a web page. Then check the processor architecture, available storage, and any system installation prompts. If downloading again doesn’t help, note the exact error and follow the troubleshooting guide—don’t disable system security features.
Back up your subscription URL, local YAML files, override rules, and any proxy group selections you want to keep. Data directories and override mechanisms vary between clients, so don’t replace the entire application folder. Export your configuration, quit the old client, then install and test the new one.
Both clients are discontinued. Their download links are kept for migrating existing setups and referencing older configurations. For a new installation, choose a client that supports your current system. Older versions may not support newer protocols, subscription fields, or system permissions, so their behavior doesn’t indicate whether every configuration is valid.