Client directory · Choose a platform
Choose your operating system, then check the processor architecture. GUI clients are for everyday configuration and connections; the standalone Mihomo core is for manual deployments.
DESKTOP / WINDOWS
The desktop installers here are primarily for x64. Check your system type under Settings → System → About. For ARM devices, don’t assume an installer is compatible just because it says Windows; check whether your system can run it.
The recommended starting point for a Windows installation. Run the installer, then import a subscription. Installing the client alone won’t create a usable configuration. The system proxy works with apps that follow Windows proxy settings; configure TUN permissions and activation as prompted by the client.
Official website: clashplus.io
A desktop GUI client based on Mihomo for managing subscriptions, routing rules, and proxy connections. A good fit if you prefer managing configurations through an interface. When switching from another client, import your configuration first, then check overrides, service mode, and system proxy settings.
A cross-platform GUI client built with Flutter and powered by Mihomo. Consider it if you want a similar experience across desktop and mobile. Even with the same subscription, configure the connection method and app permissions separately on each device.
Another desktop GUI option in the Clash ecosystem, for users who want to compare a different approach to configuration management. After installation, check which configuration and core are active. If a protocol or configuration field isn’t supported, check the core’s capabilities rather than repeatedly reinstalling the app.
Archived installer for migrating older setups and comparing configurations. The older core may not support newer protocols or configuration fields. For new installations, consider one of the clients above. Keep a backup of your original configuration during migration, and don’t let two clients control the system proxy at the same time.
| Check | What to do |
|---|---|
| Architecture | Standard installers in this section are for x64. Check the installer’s prompts for supported Windows versions. |
| Installation permissions | Installing services, virtual network adapters, and TUN features may require administrator permissions. Don’t run every routine operation with elevated privileges by default. |
| First launch | Make sure the configuration loads before enabling the system proxy. Turn off the client’s proxy handling before quitting to avoid leaving behind broken local proxy settings. |
DESKTOP / MACOS
Open About This Mac from the Apple menu to check whether your Mac uses Apple Silicon or Intel. Downloads below are listed by architecture; some entries currently point to the same x64 file, so check the downloaded file’s actual architecture.
Separate installers are listed for Apple Silicon and Intel. Open the DMG and follow the installer window’s instructions. On first launch, import your configuration and check the connection method. Before replacing an older client, turn off its system proxy and launch-at-login settings.
Official website: clashplus.io
Includes desktop configuration management and Mihomo features. Both macOS architecture links in the current listing point to an x64 DMG. Apple Silicon users should check compatibility; this is not a native ARM installer.
A good option if you want a similar interface across devices. The current macOS listing points to an AMD64 DMG, which is for Intel. Before running it on Apple Silicon, check Rosetta compatibility. A successful installation also doesn’t mean the app has all the permissions it needs to manage network traffic.
Kept for comparing and migrating older setups. Both architecture links currently point to an x86_64 file; Apple Silicon users should check compatibility. Discontinued software isn’t recommended as the default choice for a new system.
| Check | What to do |
|---|---|
| Chip | For Apple Silicon, choose a file explicitly marked ARM64. For Intel, choose x64, x86_64, or AMD64. |
| Supported macOS versions | Minimum macOS requirements depend on each client’s current build. Check the installer’s prompts; requirements for one client may not apply to another. |
| First launch permissions | If macOS displays a permission prompt, check the app’s source before proceeding and follow the system settings. Don’t disable system-wide security protections just to run a client. |
MOBILE / ANDROID
Check which app architectures your device supports before choosing an APK. ARM64 and 32-bit ARM aren’t interchangeable. The first connection usually requires approving Android’s VPN request; background behavior may also depend on battery-saving settings.
ARM64 APK available. Grant permission to install apps only to the browser or file manager you’re using, and revoke it afterward if you like. Open the client, import your subscription, confirm the configuration loads, then approve the VPN request to connect.
Official website: clashplus.io
A Clash Meta client for Android that imports compatible configurations and routes traffic through Android’s VPN interface. If you know your device’s architecture, choose the matching APK; otherwise, check the universal package. File paths, rule resources, and permissions in your configuration may need adjustments for mobile.
Android packages are available for ARM64 and 32-bit ARM. Check your device’s supported architecture first. For a persistent background connection, review this app’s battery settings in Android; you don’t need to change global battery-saving settings for every app.
An Android proxy app with its own supported configuration format. Clash YAML isn’t automatically compatible with Surfboard. Before importing, check whether your subscription provider offers a compatible format and whether the rules, policy groups, and protocols are supported.
| Check | What to do |
|---|---|
| App architecture | arm64-v8a is ARM64; armeabi-v7a is 32-bit ARM. Compatibility depends on the device’s processor and supported system ABIs. |
| Android version | The minimum Android version depends on the APK. If installation fails with a parsing error, first check your Android version, device architecture, and whether the download completed. |
| Connection permissions | Approve the system VPN request before connecting. Other VPN apps in the same user profile may conflict with the client’s connection. |
MOBILE / IOS
Check the App Store listing for installation requirements and app details. After installing, import a configuration you’re authorized to use and follow the system prompt to add a VPN configuration on first connection. Verify the configuration status and test access to confirm the connection works.
The iOS download link goes straight to the App Store. Check device compatibility, the required iOS version, and app details before installing. After importing a subscription, select the configuration you want to use. Update any desktop-only paths or rules that rely on local files so they point to resources available on your device.
Official website: clashplus.io
| Check | What to do |
|---|---|
| Device compatibility | Check the device list and minimum system requirements on the App Store page. iOS determines whether your device meets the installation requirements. |
| Network permissions | Approve the VPN configuration request when connecting for the first time. You can review added VPN configurations in Settings afterward. |
| Configuration setup | Prepare a compatible subscription or local configuration. Don’t post subscription links containing access credentials in public forums. |
DESKTOP / LINUX
AMD64 desktop packages are available below. Check your distribution’s package format and choose DEB or RPM. For servers, containers, and headless systems, consider the Mihomo core instead of installing a desktop client.
Desktop installers are available in DEB and RPM formats. Debian- and Ubuntu-based distributions generally use DEB; Fedora and some others use RPM. Your package manager handles dependencies. Launch the app from your desktop after installation and confirm the interface and configuration load before enabling proxy routing.
This section provides an AMD64 DEB desktop package. Before installing, check that your distribution version and dependencies meet the app’s requirements. TUN needs additional network permissions; importing a subscription and configuring the interface doesn’t enable virtual network routing by itself. If you have connection issues, check the client logs first.
| Check | What to do |
|---|---|
| System architecture | Check your architecture with uname -m. Packages in this section are for x86_64 / AMD64, not ARM devices. |
| Desktop and dependencies | GUI clients need a desktop environment and their required dependencies. Don’t use a DEB package as RPM, or vice versa, by simply changing the file extension. |
| Permissions and traffic routing | Whether apps use the system proxy depends on the desktop environment and the apps themselves. TUN also requires virtual network adapter, routing, and permission setup. |
ENGINE / MIHOMO
For users managing servers, routers, or processes themselves. Most users should choose one of the GUI clients above. The standalone core reads configurations and processes traffic; it has no desktop interface and doesn’t replace service management or system network configuration.
| System | Processor | File 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 ARM64 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 GZ |
Extract ZIP and GZ files before use. GZ is a single-file compression format, not a complete service installation. On Unix-like systems, check executable permissions, access to the configuration directory, and the user running the process. Install DEB packages with a package manager; check the package contents to understand how the service is set up.
Prepare a usable config.yaml. First check the configuration and startup logs in the foreground, then consider running it under a service manager. Before enabling TUN, make sure the system supports virtual network interfaces and plan your routes and DNS. Avoid changing every network setting at once over a remote connection.
| Requirement | What to check |
|---|---|
| Architecture match | Match the operating system and CPU architecture to the downloaded file. For routers, also check firmware and instruction set requirements. |
| Configuration and resources | Make sure rulesets, databases, and files referenced in the configuration are readable, and that the process has the required file permissions. |
| Network exposure | Restrict external control interfaces and proxy listener addresses to your needs. Don’t expose management interfaces directly to the public internet. |
After installation
Downloading installs the program; a working connection also requires a valid configuration, the right permissions, and traffic routing to be enabled.
After opening the client, find the configuration or subscription settings and import a subscription you’re authorized to use or a local file. Wait for it to finish parsing, check that the expected policy groups and rules appear, then set it as the active configuration. If your download succeeded but the configuration list is empty, the installation probably worked. Check whether the subscription is valid, the format is supported, and its resources are reachable.
You can have multiple clients installed on one device, but avoid enabling system proxy, VPN, or TUN in more than one at a time. Before switching clients, stop the current connection and check that the system proxy has been restored. Then start the other client. If both interfaces show as running, it can be hard to tell which one is handling traffic; port and routing conflicts can also make troubleshooting harder.
If your current client works, save local rules, overrides, and subscription details before updating or switching. Clients may handle persistent configuration differently: subscription updates can overwrite edited files, and interface overrides may not be included when exporting YAML. After migrating, check policy groups, DNS, TUN, and launch-at-login settings one by one. Don’t assume migration is complete just because the configuration has the same name.
See the subscription import and connection guide for the full process. To compare interfaces and core compatibility, read the client comparison. For issues such as no access after connecting or failed updates, troubleshoot by symptom in the Help Center.
Download FAQs
Start with Clash Plus for Windows, macOS, Android, or iOS; for Linux, consider Clash Verge Rev. Choose an installer that matches your operating system and processor, then check compatibility with the protocols and core your subscription requires. See the client comparison for interface and configuration differences.
Check your processor architecture in your system settings. x64 and AMD64 usually refer to the same 64-bit architecture; ARM64 is different. On Android, arm64-v8a corresponds to ARM64 and armeabi-v7a to 32-bit ARM. Universal packages include multiple architectures. Check the actual filename as well as the button label. Some macOS listings on this page currently link to x64 files, not native ARM installers.
The client reads configurations and manages proxies and rules; installing it does not provide a proxy service. After installation, import a subscription you’re authorized to use or a local configuration, select it, then enable the system proxy or VPN connection as instructed. Subscription links may contain credentials, so don’t share them publicly.
Save your local configuration, override rules, policy group selections, and any interface settings you want to keep. Note which subscription you use. Quit the running client before updating, then check your configuration and proxy status afterward. When switching clients, don’t overwrite the entire data directory. Import your configuration first, then review the differences item by item.
The archived Clash for Windows and ClashX Meta downloads are mainly for migrating older setups, comparing configurations, and reproducing compatibility issues. Discontinued clients may no longer receive OS compatibility updates or bug fixes. For a new installation, choose a maintained client that meets your needs.
Usually not. GUI clients generally bundle or manage the core they use, so most desktop and mobile users can follow the client’s installation process. The standalone Mihomo binary is intended for users managing servers, routers, or processes themselves; they’ll need to handle configuration, permissions, startup, and logs.