CLIENT PACKAGES / CLIENT DOWNLOADS
Check your operating system first, then your processor architecture. Choose a GUI client for desktop or mobile; use the Mihomo kernel on servers and routers if needed.
Clients are listed in a consistent order for each platform. Start with the recommended option, then choose based on what you’re used to. Downloading the app doesn’t complete setup—you’ll still need to configure your subscription and connection.
Most downloads here are x64 builds. Check your system type under Settings → System → About. Windows on ARM users should also verify app emulation and virtual network adapter driver compatibility. A successful x64 installation does not guarantee that TUN will work.
A good starting point for a first installation. Download the x64 installer, then import your subscription on the configuration page and check your proxy group and rule mode. The system proxy and TUN are separate connection methods. Start by getting one working to make troubleshooting easier.
Official site: clashplus.io · Setup guide
A good fit for managing configurations, proxy groups and connections through a desktop interface. Before installing, quit other clients that manage the system proxy to prevent them from overwriting the same settings. To use TUN, install or enable the service as prompted and approve any firewall access.
Consider FlClash if you want a similar workflow across desktop and mobile. This download is the Windows installer. When migrating, import your subscription again instead of copying another client’s entire data directory. Review custom rules and overrides individually.
Another GUI client for desktop. If you’re used to its workflow, you can keep using your existing configuration, but back up subscription records and local changes before updating. An imported configuration may include fields that the bundled kernel does not support.
Archived download for reference and migration from existing setups. The old client and its kernel may not recognize newer protocols or configuration fields. For new installations, choose another client above. Keep a copy of your original configuration, verify it in the new app, and only then remove the old setup.
| Check | Before installing |
|---|---|
| System | Use a supported version of Windows 10 or 11. Check the selected client’s release notes for its minimum requirements. |
| Processor | These builds are primarily for x64. ARM devices also need compatible emulation and driver support. |
| Permissions | Standard proxy use and TUN require different permissions. Follow the prompts for service installation, virtual adapters and firewall access. |
| First launch | Import and enable a configuration. Check that the mixed port isn’t in use by another app, then enable the system proxy. |
Open About This Mac from the Apple menu to check whether your Mac has Apple Silicon or an Intel processor. The listings are grouped by architecture, but check the actual download and app architecture before installing. Some links may return the same Intel build; check Rosetta compatibility before use.
Choose a DMG for your chip, open it and move the app to Applications. Follow system prompts to grant network permissions on first launch, then import your subscription. If you need TUN, grant its permissions separately; the system proxy and virtual network adapter are different settings.
Official site: clashplus.io
Manage subscriptions and proxy groups from your desktop. Quit the old app before copying the new one into Applications. If the app can’t change the system proxy, check system permissions and service status. Both listed downloads currently fall back to x64 filenames; Apple Silicon users should verify the actual package architecture first.
A good fit if you want a similar workflow across devices. Import subscriptions separately on each device; ports, network adapters and permissions must also be configured on each one. Both macOS listings currently point to an amd64 file, so Apple Silicon users should not assume they’re getting a native ARM app.
Kept as an archive for migrating older setups and comparing configurations. Check compatibility before using it with newer systems or subscription formats. Both listings currently return an x86_64 build, not separate native builds. For a new installation, compare the clients above.
| Check | Before installing |
|---|---|
| macOS version | Check your macOS version in About This Mac. Refer to the selected app’s release notes for minimum requirements. |
| Chip and architecture | Apple Silicon uses ARM64; Intel uses x64 / AMD64. Check Rosetta support before running an Intel app on Apple Silicon. |
| Installation | Move the app to Applications before opening it; don’t run it long-term from a temporary disk image. |
| Network permissions | Grant permissions for the system proxy, services and TUN as needed. If you see a security alert, first check the app’s source and the details of the system prompt. |
For most recent phones, start by checking whether the ARM64 build is right for your device. Older devices, TV boxes and emulators may use a different architecture. If Android reports that a package is incompatible, check the device ABI instead of repeatedly trying modified builds from unknown sources. The first connection also requires system VPN permission.
ARM64 APK. After downloading, allow your browser or file manager to install this app. You can revoke that source’s install permission afterward. Import and enable a subscription, then approve the system VPN request on first connection and check that apps can access the network as expected.
Official site: clashplus.io
Choose an ARM64, ARM or universal build based on your device’s architecture. A universal build can help if you’re unsure, but it still has to meet the Android version and app requirements. After importing a configuration, make sure it’s selected. Check that per-app settings match the traffic you want to proxy.
ARM64 and ARM builds available. If the system’s battery management interrupts background connections, check battery optimization and background activity permissions—but don’t grant everything at once. First confirm the app works in the foreground, then troubleshoot keeping it connected while the screen is locked.
Local universal APK download. Its configuration format is not interchangeable with Clash YAML, so don’t expect an arbitrary Clash subscription to work if imported as-is. Choose this option only if you already have a compatible configuration, and check support for its protocols and rule fields before converting.
| Check | Before installing |
|---|---|
| Android version and ABI | Check the Android version required by the client. ARM64-v8a and armeabi-v7a indicate different supported architectures. |
| Install source | Grant install permission only to the browser or file manager you’re using, and revoke it afterward if you wish. |
| VPN permission | On first connection, approve the system VpnService prompt. Another VPN app may already be using the connection slot. |
| Background activity | Check battery optimization, auto-start and background restrictions only if connections drop when the screen is locked. Settings vary by device maker. |
Check the App Store listing for Clash Plus availability, system compatibility and release notes. After installing, import a valid subscription you’re authorized to use. Approve the system VPN configuration when you connect for the first time.
Install from the App Store on iPhone or iPad. Check device compatibility on the app listing, then download and import your subscription. Make sure the configuration is enabled, choose a proxy group, and allow the VPN configuration when prompted. If the subscription format is rejected, check the provider’s supported import format instead of repeatedly reinstalling the app.
Official site: clashplus.io
| Check | Before installing |
|---|---|
| System compatibility | Check the App Store listing for the minimum iOS / iPadOS version and supported devices. |
| Download | Use the App Store link above to check the app name, description and release notes. |
| Configuration | Prepare a valid subscription you’re authorized to use. Installing the app and obtaining a subscription are separate steps. |
| Connection permission | Allow the VPN configuration when prompted on first connection. Check which VPN is active when switching between VPN apps. |
Check your distribution’s package manager first, then your processor architecture. GUI packages here target AMD64 / x86_64 desktops. For headless servers and devices with other architectures, see the Mihomo kernel downloads below.
For Debian- and Ubuntu-based systems, start with DEB; choose RPM for distributions that use RPM packages. Check system dependencies and desktop requirements before installing. Whether desktop apps follow the system proxy depends on the app and session settings—a single toggle won’t cover every process.
AMD64 DEB package for desktop users on compatible distributions. Launch the app after installation, import your configuration and test the connection. To use TUN, prepare the required permissions and network setup as described in the client documentation. Don’t run your entire desktop session as an administrator to work around permission prompts.
| Check | Before installing |
|---|---|
| Architecture | Run uname -m to check your architecture. These packages are for x86_64 / AMD64 and can’t be installed directly on ARM desktops. |
| Package format | Choose DEB or RPM based on your distribution’s package manager, not its desktop appearance or how similar its name is to another distribution. |
| Runtime dependencies | A working graphical session and the client’s required libraries are needed. Check release notes for the minimum supported distribution version. |
| Network permissions | TUN requires a virtual device, routing and permissions. Keep a way to roll back changes before working remotely, so you don’t lose your management connection. |
ARCHITECTURE / CHOOSING A BUILD
Common 64-bit Intel and AMD desktop processors can use x64 / AMD64 builds; ARM64 uses a different instruction set. File extensions indicate packaging or compression, not CPU architecture: DMG and APK files can contain apps built for entirely different processors.
Before downloading, check the operating system, architecture and package format. If a listing and filename don’t match, trust the actual package details and system requirements. Don’t rename files to work around incompatibility, and don’t upload a GUI installer to a router as a kernel.
Compare clients and find the right one →CORE PACKAGES / STANDALONE KERNEL
For users managing servers, routers or their own processes. The kernel reads configuration and handles network traffic; it does not include a desktop settings window. Most users should choose a GUI client above to manage configuration, services and permissions.
| System | Architecture and format | Notes | Download |
|---|---|---|---|
| Windows | AMD64 · ZIP | Common x64 desktops and servers | Download AMD64 ZIP |
| Windows | ARM64 · ZIP | ARM64 Windows environments | Download ARM64 ZIP |
| macOS | Intel AMD64 · GZ | Intel-based Mac | Download Intel GZ |
| macOS | Apple Silicon ARM64 · GZ | Apple Silicon Mac | Download Apple Silicon GZ |
| Linux | AMD64 · DEB | Debian-based package manager for the matching architecture | Download AMD64 DEB |
| Linux | AMD64 · GZ | x86_64 hosts running a manually managed process | Download AMD64 GZ |
| Linux | ARM64 · GZ | 64-bit ARM devices | Download ARM64 GZ |
| Linux | ARMv7 · GZ | 32-bit devices compatible with ARMv7 | Download ARMv7 GZ |
| Linux | MIPS softfloat · GZ | Must match byte order and soft-float ABI | Download MIPS softfloat GZ |
Whether a YAML configuration works depends on the fields and protocols supported by the kernel; similar interface names don’t guarantee identical behavior. GUI clients may also add configuration merging, overrides or service management. Before replacing a bundled kernel manually, check that the client supports it.
When configuring listening addresses, ports and control interfaces, limit access to what you actually need. Allowing LAN connections doesn’t restrict access to your own devices. Never expose subscription credentials or a control interface directly to the public internet. See the full documentation for installation and setup.
If you can’t connect, first determine whether the issue is with app installation, configuration import or network routing. Follow these steps in order instead of repeatedly trying different installers.
Import a subscription or local YAML file, then check the download and parsing status. Once it appears in the configuration list, make sure it’s enabled. If you only have a Base64 node string or a list of URIs, check whether the client can import that format directly before treating it as an installation problem.
For an initial test, try the system proxy and check whether your apps follow it. Configure TUN if you need to route more traffic. Quit other clients and VPN apps before retrying to avoid conflicts with ports, routes or DNS settings. Change one thing, then test it.
Back up your current configuration, overrides and custom rules before updating, then quit the app and background services. When switching clients, recheck configuration paths, proxy group selection, listening ports and DNS behavior. Remove the old app and data only after confirming the new setup works.
Choosing an installer, checking architecture and preparing to update. See the full documentation for platform-specific steps.
For Windows, macOS, Android and iOS, start with Clash Plus for your platform. Linux users can start with Clash Verge Rev. If you want to keep your existing interface or configuration workflow, compare clients such as FlClash. Clients do not include a ready-to-use subscription; you’ll need to import a valid configuration after installation.
ARM64 and x64 target different processor instruction sets; universal builds typically support multiple architectures. Check your system type in Windows, and your chip in About This Mac. On Android, choose a build that matches your device’s supported ABI. A filename containing x64 or amd64 does not mean the download is an ARM-native build. Before running an Intel build on Apple Silicon, check Rosetta compatibility.
The installer provides the client app; a subscription or YAML configuration provides proxy servers, proxy groups and routing rules. After installation, import a subscription you’re authorized to use in the configuration screen. Confirm it downloaded successfully and is enabled, then choose a rule mode and connection method. Don’t share subscription links that contain credentials.
For the same client, follow its update instructions. Back up your configuration, subscription records and custom rules before updating, then quit the app and any background services. When switching clients, don’t assume they share settings directories: import your configuration again and check ports, DNS and TUN permissions. If an in-place update fails, handle the old version according to the client’s documentation.
These clients remain available as archived downloads to help existing users identify their setup and migrate. Older interfaces and kernels may not support newer configuration fields, protocols or system changes. For a new installation, choose another client. Keep a backup of your original configuration during migration, and don’t overwrite your only working setup.
First, confirm that your subscription is imported and enabled. Then check your proxy group selection and the logs for errors. The system proxy only affects apps that follow that setting; TUN requires a virtual network adapter and system authorization. Change one setting at a time while troubleshooting. If regular internet access is still affected after quitting the client, check for leftover system proxy settings and see the platform setup section in the full documentation.