Installers / OS and architecture
Choose your operating system first, then the installer architecture. Use a graphical client on phones and desktops; for servers and routers, see the Mihomo core.
The graphical clients listed here are primarily x64 installers. Check your system type under Settings → System → About. On Windows on ARM, confirm that the app can run in a compatibility environment; an x64 installer is not a native ARM64 package.
A good place to start with a fresh install. Import your configuration, make sure the subscription loads, then choose a rule mode and outbound policy. If you already use another proxy client, disable its system proxy or virtual network adapter first to prevent multiple apps from changing your network settings.
clashplus.io
A good fit if you want to manage subscriptions, rule overrides, and operating modes on desktop. System proxy and TUN mode route traffic differently. Start by testing the system proxy, then configure TUN if your apps need it. Follow the client’s prompts when installing services or granting permissions.
A good fit if you want a similar interface on your phone and computer. Follow the installer wizard, or extract the ZIP to a writable folder before running it—don’t launch the app from the archive preview. After migrating, check permissions and where the configuration is stored.
Another option for managing desktop configurations. Override, extension script, and configuration merge workflows vary between clients. After importing a subscription, check that the expected proxy group names are active. A client opening successfully doesn’t mean your old configuration migrated completely.
For restoring older setups or checking compatibility only. This project is no longer maintained and may not support newer protocols, configuration fields, or system changes. For new devices, choose one of the maintained clients above. Before migrating an older setup, export your subscription source and local rules.
| Check | Requirements and notes |
|---|---|
| Processor | The graphical clients here are x64 / AMD64 builds. ARM devices need a compatible runtime. |
| Operating system | Use a supported Windows release. Check the selected client’s current release notes for its minimum version. |
| Permissions | Managing settings requires different permissions from installing services. TUN or service mode may require administrator approval. |
| Install location | Make sure the disk is writable and has room for updates. Extract ZIP archives fully before running them. |
Check your chip under Apple menu → About This Mac. Choose the matching architecture for Apple Silicon or Intel. Some clients currently link to the same x64 file from both download buttons; see the notes below.
Separate installers are available for each architecture. Open the DMG and follow the prompts to move the app to Applications, then launch it from there. After importing your subscription, grant network extension or connection permissions. If migrating from another client, disable its system proxy first.
clashplus.io
A good fit if you want to manage desktop rules. Both download buttons currently point to the same x64 file. Apple Silicon users need a compatible runtime such as Rosetta; this is not a native ARM64 build. After installing, check the service mode and configuration override settings.
Offers a configuration workflow similar to the mobile app, but permissions must still be set separately on each device. Both downloads are AMD64 builds, so Apple Silicon requires a compatibility environment. If you already have a local configuration, check DNS, proxy ports, and rule order after importing it.
Kept for restoring existing setups, not recommended for new installations. Both download buttons currently point to an x86_64 file. Being able to read an older configuration doesn’t guarantee support for every field in newer cores. After migrating to a maintained client, check for configuration errors and permission prompts.
| Check | Requirements and notes |
|---|---|
| Chip type | Apple Silicon uses ARM64; Intel uses x64 / AMD64. |
| Compatibility | This section labels compatibility downloads that are currently x64. On Apple Silicon, make sure Rosetta is available. |
| System version | Check the client’s release notes for its minimum macOS version before installing. Don’t assume an older system is compatible. |
| Installation and permissions | Run the app from Applications and approve network extension or connection permissions when prompted. Don’t disable system security protections without a clear reason. |
For most recent ARM phones, first check whether the ARM64 package is compatible; older 32-bit systems need ARMv7. A 64-bit-capable processor doesn’t guarantee that the system supports 64-bit apps. Check the ABI reported by your device.
A good starting point for a fresh install. After downloading, grant installation permission only to the source you’re using, then revoke it when you’re done if you prefer. Approve Android’s VPN permission when connecting for the first time. Check background settings too, so the system doesn’t interrupt the connection when the screen locks.
clashplus.ioOffers clear controls for configuration, proxy groups, and runtime settings. Choose the package that matches your architecture; if you’re unsure, consider the universal package. After importing a subscription, check for syntax errors or unsupported fields before connecting. Reinstalling repeatedly won’t fix a configuration problem.
A good fit if you want a similar workflow on your phone and desktop. Subscription updates, proxy selection, and background operation are separate settings; a successful import doesn’t mean the connection is ready. If the connection drops when the screen locks, check battery optimization and background permissions before changing the configuration’s health check interval.
For users with a compatible configuration. Surfboard uses a different configuration format from Clash YAML, so a Clash subscription won’t necessarily work. Before downloading, check whether your provider supports the required format. If not, request a compatible configuration.
| Check | Requirements and notes |
|---|---|
| App architecture | arm64-v8a is ARM64; armeabi-v7a is 32-bit ARM. |
| System version | Minimum Android versions vary by client. Check the selected package’s installation requirements and release notes. |
| Installation permission | Allow app installations only for the browser or file manager you’re using, and revoke permission afterward if you prefer. |
| Connection and background operation | Approve VPN access. Most devices allow only one app at a time to use the system VPN connection. |
Install on iPhone or iPad from the App Store. Check the store listing for current OS compatibility, app details, and availability. Review that information before installing, and have a subscription or configuration ready to import.
Import your subscription after installation. When you connect for the first time, follow iOS prompts to add a VPN configuration. Once permission is granted, return to the client to check the connection and select a proxy group. School- or company-managed devices may restrict VPN configurations through a profile; check with your administrator if needed.
clashplus.io| Check | Requirements and notes |
|---|---|
| Device and OS | Check the App Store listing for current iPhone, iPad, and OS compatibility requirements. |
| How to install | Open the Clash Plus App Store listing and follow the prompts to install or update. |
| Network permissions | Your first connection requires approval to add a system VPN configuration. Managed devices may have additional restrictions. |
| Prepare a configuration | Use a subscription you’re authorized to access and that’s in a supported format. Don’t post private subscription URLs in public comments. |
The graphical clients here are AMD64 packages. For Debian- and Ubuntu-based distributions, see DEB; for RPM-based distributions, see RPM. For headless servers, ARM routers, and other architectures, see the core packages below.
A good fit for managing subscriptions and rules on a Linux desktop. Use your distribution’s package manager to install dependencies; simply extracting the package may not set up everything the app needs. Desktop proxy settings apply only to apps that honor them; terminals and containers may need separate configuration.
A good fit for Debian-based desktops if you want a consistent workflow across devices. On first launch, check that the configuration loads and the network connection works before setting up startup behavior or TUN permissions. Wayland, X11, tray, and notification support can vary by distribution.
| Check | Requirements and notes |
|---|---|
| Processor | These packages are AMD64 / x86_64 and aren’t suitable for ARM64 desktops or ARM routers. |
| Package format | Choose DEB or RPM for your distribution. Renaming a file extension won’t convert a package. |
| Desktop dependencies | Graphical clients require a desktop environment. Check the installer prompts and release notes for specific system library requirements. |
| Network routing | TUN may require additional permissions. For server deployments, use the core and manage its configuration and process separately. |
Servers / routers / self-hosted setups
The core loads configuration and handles connections; it isn’t a complete graphical client. Most phone and desktop users should choose a client above. Choose a core package if you need to run a service, integrate with a router, or manage the control interface yourself.
Check your operating system and CPU architecture first, then choose a package format. Windows uses ZIP; macOS and most Linux builds use GZ; Linux AMD64 also has a DEB package. After extracting a GZ archive, you’ll still need to set executable permissions, configure paths, and choose how to start the program.
| OS | Architecture | Notes | Download |
|---|---|---|---|
| Windows | AMD64 | 64-bit Intel / AMD devices | Download ZIP |
| Windows | ARM64 | Native core for Windows on ARM | Download ZIP |
| macOS | Intel / AMD64 | Intel-based Mac | Download GZ |
| macOS | Apple Silicon / ARM64 | Native core for Apple Silicon | Download GZ |
| Linux | AMD64 | 64-bit systems using DEB packages | Download DEB |
| Linux | AMD64 | 64-bit Intel / AMD servers | Download GZ |
| Linux | ARM64 | 64-bit ARM servers or devices | Download GZ |
| Linux | ARMv7 | 32-bit ARMv7 devices | Download GZ |
| Linux | MIPS softfloat | Confirm endianness and firmware ABI | Download GZ |
For questions about core families, protocol support, or subscription formats, start with the protocol and core reference. To compare how graphical clients work, see the client selection guide.
Installation and migration
The installer provides the client; the subscription provides configuration data the client can load. The program alone usually can’t connect without a usable configuration. Make sure you’re authorized to use the subscription and that its format is supported. Subscription URLs may contain access credentials, so keep them private.
If importing a configuration reports missing fields or an unsupported protocol, first check its format and the core’s capabilities. Renaming the file won’t fix the problem; different configuration formats aren’t necessarily compatible.
Before updating, note your subscription source, export the configuration if possible, and save any local overrides, DNS settings, and proxy group selections. Client updates and subscription updates are separate: refreshing a subscription may regenerate remote configuration and replace edits made directly to the subscription file.
When switching clients, it’s safer to import your configuration again. Don’t copy the entire old application data directory into the new one; file layouts, cache formats, and permission records may differ.
After installation, launch the client manually and check that the configuration loads, the right proxy is selected, and connection permissions are granted. Only then enable startup or background operation on your phone, so unresolved configuration issues don’t carry over into automatic startup.
If the connection fails, identify whether the problem is with downloading, installation, configuration loading, or network routing. A specific error message is more useful than repeated reinstalls. Before asking for help publicly, redact subscription URLs and other private configuration details.
Clash download FAQ
For phones and everyday desktop use, start with a graphical client such as Clash Plus for your operating system. Mihomo core packages are intended for servers, routers, and self-managed setups; they don’t include a full subscription management interface.
Check your device information or manufacturer specifications to confirm which app architectures your system supports. ARM devices that support 64-bit apps can usually use ARM64; 32-bit ARM systems need ARMv7. If you’re unsure, try the universal package for Clash Meta for Android, provided your device meets the client’s system requirements.
A client name or download link doesn’t guarantee the binary’s architecture. Some Mac listings currently point to the same x64 installer, which requires a compatibility environment on Apple Silicon. For a native ARM64 package, see the Apple Silicon download for Clash Plus.
Get a subscription URL you’re authorized to use or a local configuration file. Import it, check the proxy groups and rule mode, then grant VPN or network extension permissions when prompted by your system. The client installer doesn’t include a subscription service. See the setup guide for instructions.
Whether data is preserved depends on the client, installation method, and version migration process. Before updating, export your configuration and note any local overrides, proxy group selections, and subscription sources. Update in place when staying with the same client; when switching clients, import your configuration again instead of copying the entire data directory.
Not recommended. Archived installers are mainly for restoring older setups or checking compatibility; they may not support newer systems, protocols, or fixes. For a new device, choose a maintained client that supports your configuration.