PACKAGES / PLATFORM / ARCHITECTURE
Windows, macOS, Android, iOS, and Linux. Choose your operating system first, then check your CPU architecture. Use a GUI client on desktops and phones, or the Mihomo core on servers and routers.
01 / CLIENT PACKAGES
Installers contain the client app only; they do not include a proxy service. If you already have a subscription, import it after installation. New users can start with the getting started guide. The formats and architectures listed below apply to the packages on this page and do not guarantee compatibility with every legacy system.
These GUI installers are x64. Check your system type under Settings → System → About, then download the matching client. Do not treat an x64 installer as a native ARM app on ARM devices; compatibility depends on your system and the client.
The recommended starting point for a first installation. After setup, import a subscription, select a configuration and node, then enable the system proxy. If you need to route apps that ignore the system proxy, check service permissions and configure TUN afterward. Avoid enabling multiple connection methods at once.
For desktop users who want a GUI to manage configurations, proxy groups, and connection details. When moving an existing setup, check subscription content and client overrides separately; rules, ports, and DNS options saved in the UI may not be included in the subscription file.
Use a similar workflow across desktop and mobile devices. The installer is best for typical desktop use. Extract the ZIP archive fully before running it; do not launch the app from within an archive utility. Quit background processes before updating, and keep your existing configuration and subscription details.
For users who want to adjust proxy settings in a desktop dashboard. Start with the defaults, import a subscription, and test the connection before adding custom settings. If prompted for permissions, check whether the action involves installing a service or virtual network adapter.
This archived download is provided for compatibility with existing setups and configuration migration. The older core may not recognize newer protocols, rule fields, or subscription formats. For new installations, see the maintained clients above. During migration, keep the original YAML file instead of relying only on settings saved in the old client.
| Check | Requirements and steps |
|---|---|
| Processor | These installers are x64 / AMD64; check the architecture in System Information. |
| System compatibility | Use a version of Windows that is still supported by Microsoft. Check the installer for the client's specific minimum version. |
| Permissions | Installing a service or enabling TUN may require administrator approval. Importing a subscription does not install a service. |
| Connection checks | Turn off the old client's system proxy before switching, and check for conflicts on local listening ports. |
Open About This Mac from the Apple menu. If the chip is an Apple M-series processor, choose Apple Silicon; if it says Intel, choose Intel. Some downloads currently offer an x64 compatibility build, clearly labeled on the button. It may require Rosetta on Apple silicon; verify compatibility by running the app.
Choose the native package for your chip. Open the disk image and move the app to Applications before launching it. Grant any permissions requested on first launch. After importing a subscription, test the system proxy before enabling more extensive traffic routing.
Both links currently point to the same x64 file; neither is a native build for a different architecture. Apple silicon users should account for compatibility requirements. After installation, check your subscription and service mode. Turn off the old app's system proxy before switching clients.
A good fit if you want a similar setup across desktop and mobile devices. The listed package is AMD64 (x64), so treat it as a compatibility build on Apple silicon. When moving a subscription, recheck your proxy group selections; permissions and network settings do not automatically carry over between devices.
Kept for users who need to reproduce a legacy setup. This is an x86_64 package and may require Rosetta on Apple silicon. The discontinued GUI and core have compatibility limitations. If a new configuration fails to import, consider migrating instead of repeatedly reinstalling.
| Check | Requirements and steps |
|---|---|
| Chip | Check whether your Mac has Apple silicon or Intel. Running an x64 package on Apple silicon may require Rosetta. |
| System compatibility | Minimum macOS version depends on the selected client; requirements vary. |
| Install location | Copy the app from the DMG to Applications. Do not run it from the mounted disk image long-term. |
| Security and permissions | If macOS blocks the app, check its source and compatibility first. Disabling system security protections globally is not recommended. |
Most newer Android phones use ARM64, but a 64-bit-capable processor does not guarantee that the system runs 64-bit apps. Check your device's system information first. If you can't confirm the architecture, choose the universal package for Clash Meta for Android. Approve the system VPN prompt on first launch.
The recommended option for ARM64 phones. Grant app-install permission only to the browser or file manager you're using. After importing a subscription and starting the client, check for the system VPN indicator. If the connection drops in the background, review battery optimization and background activity restrictions.
Choose a package for your device architecture, or use the universal build to skip the guesswork. After importing Clash YAML, set it as the active configuration in the configuration list. Downloading a subscription file without activating its configuration will not switch the running service to that subscription.
Available for ARM64 and 32-bit ARM devices. Android's VPN service can only be used by one app at a time. Before testing, quit any other app managing your network so a permission conflict isn't mistaken for a node issue.
Before using it, confirm that your provider offers a configuration format compatible with Surfboard. Clash YAML and Surfboard configurations cannot be converted by simply changing the file extension; protocols, rule syntax, and proxy group support may differ. If you already have a Clash subscription, request the appropriate format before importing it.
| Check | Requirements and steps |
|---|---|
| Architecture | ARM64 uses arm64-v8a; 32-bit ARM uses armeabi-v7a. |
| Install permissions | Allow apps to be installed from the source you're using. You can revoke this permission afterward if needed. |
| Network access | Approve the system VPN prompt when starting the service, and check whether another VPN app is running. |
| Background activity | If the connection drops when the screen locks, check battery saver, background activity, and the manufacturer's auto-start settings. |
Check the App Store listing for device compatibility, then install the app. Import a subscription after installation and approve the prompt to add a VPN configuration on first connection. Installing the app and getting a node subscription are separate steps.
iOS client download. Check the App Store listing for compatibility, features, and current availability. Before first use, prepare a working subscription. After importing it, select a proxy group and node, then connect as prompted by iOS. Once a webpage loads, check any other apps you want to route.
Official site: clashplus.io. Subscription URLs often grant access to your account. Store them securely after importing, and hide the full URL in screenshots you share.
| Check | Requirements and steps |
|---|---|
| OS version | Check the App Store listing for compatible devices and operating systems. |
| Installation | Install Clash Plus using the App Store link above. |
| VPN configuration | Approve the system prompt on first connection. Check whether another VPN configuration is already routing traffic. |
| Subscription | Prepare a subscription or configuration supported by the client, and check that your service is active and has data available. |
These GUI clients are AMD64. Choose DEB for Debian, Ubuntu, and compatible distributions; choose RPM for distributions that use RPM package management. For headless servers, ARM devices, or routers, use the Mihomo core below instead of a desktop package.
The recommended starting point for Linux desktop users. Use your distribution's package manager to handle dependencies, then check tray and desktop integration on first launch. If the app won't start, inspect dependency errors in a terminal instead of treating an installation issue as a subscription connection problem.
For desktop environments using DEB packages. Confirm the app opens correctly before importing a subscription and testing the proxy. TUN requires different permissions from a regular desktop launch. If you need the client to run in the background, plan separately for its service and desktop session.
| Check | Requirements and steps |
|---|---|
| CPU architecture | Run uname -m to check; these desktop packages support x86_64 / AMD64. |
| Package manager | Choose DEB or RPM for your distribution. Renaming a file extension does not convert a package. |
| Runtime environment | Requires a working graphical desktop and its runtime dependencies. For headless systems, use the command-line core. |
| TUN permissions | Install a service or grant capabilities as documented by the client. Avoid running the entire desktop app with elevated privileges long-term. |
02 / CORE BINARIES
This section provides the core binary, not a GUI for managing subscriptions. Most users should choose a GUI client above. Before deployment, prepare a YAML configuration, confirm your operating system and CPU architecture, and manage processes, permissions, and logs yourself.
| System | Architecture | Format and use | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP / 64-bit x86 systems | Download ZIP |
| Windows | ARM64 | ZIP / Windows ARM devices | Download ZIP |
| macOS | Intel / AMD64 | GZ / Intel Mac command line | Download GZ |
| macOS | Apple Silicon / ARM64 | GZ / Apple M-series command line | Download GZ |
| Linux | AMD64 | DEB / Debian-based package management | Download DEB |
| Linux | AMD64 | GZ / Manual deployment | Download GZ |
| Linux | ARM64 | GZ / 64-bit ARM systems | Download GZ |
| Linux | ARMv7 | GZ / Compatible 32-bit ARM systems | Download GZ |
| Linux | MIPS softfloat | GZ / Check endianness and floating-point ABI | Download GZ |
03 / AFTER INSTALLATION
01 / IMPORT
Get a configuration compatible with your client from your service provider. Paste the link on the subscription or configuration screen, update it, then set it as active. If the link won't load, check the URL and service status first. Never submit an authorized subscription URL to an untrusted conversion service.
02 / ROUTE
Start in rule mode and choose an available node in a proxy group. On desktop, begin by enabling the system proxy; on Android and iOS, establish a VPN connection as prompted. TUN is a traffic routing method, not a substitute for a subscription.
03 / VERIFY
Test a direct destination and a proxied destination separately, then check the connection log to confirm which rules matched. A successful latency test only means that test address is reachable; it does not guarantee access to every service. If something fails, check the configuration, node, DNS, and permissions one at a time.
View the full getting started guide →View setup guides for all platforms →
04 / DOWNLOAD QUESTIONS
For Windows, macOS, Android, and iOS, start with the first-listed Clash Plus option for your platform. For Linux, start with Clash Verge Rev. Check your operating system and CPU architecture before choosing a package. For background services, servers, or routers, use the Mihomo core.
AMD64 and x64 both refer to the common 64-bit x86 architecture; ARM64 is for ARM processors. If you can't confirm your Android device's architecture, choose the universal package for Clash Meta for Android. On macOS, check your chip in About This Mac. An x64 compatibility package may require Rosetta on Apple silicon; it is not a native ARM build.
The client and proxy service are separate. After installation, import a valid subscription or local YAML configuration, select that configuration and a node in its proxy group, then enable the system proxy or configure TUN if needed. Subscription validity, node availability, and service permissions can all affect connectivity.
Export your local configuration and custom rules first. Note your subscription URL, proxy group selections, listening ports, and TUN settings, then quit the old client before installing the update. Moving between clients does not copy every UI setting, so recheck your subscription, DNS, system proxy, and service permissions.
Both clients are discontinued. Their download links remain available for compatibility with existing setups and migration. Older clients may not support newer protocols or configuration fields, so new installations should favor a maintained client for the same platform. Back up your configuration before migrating, then retest your rules and connection.
No. Start by testing your browser with the system proxy. Enable TUN as documented only if an app ignores the system proxy or you need to route more traffic. TUN usually requires additional permissions. When testing, avoid having multiple proxy clients manage routes at the same time.