Client Downloads / Platforms and Architectures
Choose your operating system, then confirm your processor architecture. Use a graphical client for everyday use; see the Mihomo core section for servers and routers.
Already have a configuration file? Import the YAML after installation, then check your proxy groups and listening ports. Setting things up for the first time? Start by importing a subscription—there's no need to change core settings first.
See the post-install setup steps →The recommended client appears first for each platform. Alternatives follow in a fixed order, with archived software clearly marked.
This section offers x64 graphical clients. Check your system type under Settings → System → About before choosing a client.
Manage configurations, switch proxies, and check connections in a graphical interface. After installation, import and enable a subscription before turning on the system proxy. Use TUN only if you need to handle apps that don't follow the system proxy.
Start in rule mode and test the websites you use most. Confirm that both local apps and your browser work as expected. See clashplus.io for product details.
A desktop option for managing subscriptions, configuration overrides, and mihomo settings. Follow the prompts to grant permissions during installation. After launch, check which configuration is active—not just whether the subscription appears in the list.
TUN and the system proxy route traffic in different ways. Before enabling TUN, check service mode and permissions. If connections fail, review the logs and troubleshoot one item at a time rather than changing DNS, ports, and routes all at once.
A good fit if you want a similar workflow across desktop and mobile. Use the installer for a standard setup. For the ZIP, extract all files to a permanent folder before running the app; don't launch it from the archive preview.
Before migrating an existing setup, keep the original YAML and local rules. The client may save UI settings and configuration overrides differently, so recheck proxy group selection and startup behavior after importing.
An alternative for desktop configuration management, useful for comparing subscription workflows and configuration layouts. Quit any other running proxy clients before installation to avoid port conflicts.
If your existing configuration relies on specific core fields, confirm they're supported by the selected core before enabling the subscription. A successful import doesn't mean every setting is active; check the runtime logs.
This archived download is for reproducing older setups, migrating configurations, and compatibility checks. The client is discontinued. For new installations, choose a maintained client above; compatibility with historical configurations does not guarantee support for future protocols.
Before migrating, back up subscription URLs, rule overrides, and port settings. Launch the old and new clients separately, then verify proxy groups, DNS, and TUN one by one before removing the old setup. See the archived client comparison.
| Check | Before you install |
|---|---|
| Processor architecture | This section provides x64 / AMD64 packages. Windows on ARM users should first confirm that their system supports x64 apps. |
| Windows version | Use a supported version of Windows 10 or 11 where possible. Check each client's release notes for its minimum system requirements. |
| Permissions and ports | Installing services or enabling TUN may require administrator permissions. Before launch, make sure another client isn't using the mixed port. |
Check your chip type in About This Mac. Choose the Apple Silicon or Intel option as appropriate; some alternative downloads currently provide x64 packages, so check each card's notes before installing.
Downloads are available for Apple Silicon and Intel. Open the DMG, move the app to Applications, and launch it from there for easier permission management and updates.
After importing a subscription, check the active configuration and proxy mode. If macOS asks you to authorize the system proxy or network extension, approve it if needed. Product details: clashplus.io.
For desktop subscription management and mihomo configuration. Both the Apple Silicon and Intel fallback links currently serve an x64 DMG. Apple Silicon users may need Rosetta to run it; this is not a native ARM build.
On first launch, import your configuration before setting the system proxy. If the old client left proxy settings behind, restore your system network settings before testing the new client to avoid mistaking a leftover proxy for a subscription issue.
For users who want a consistent setup across desktop and mobile. Both links currently serve an AMD64 DMG. Apple Silicon users should check Rosetta compatibility before installing.
You can import the same subscription on multiple devices, but configure the system proxy, TUN permissions, and local ports on each device separately. Don't substitute an app state folder copied from another operating system for a proper import.
Discontinued; retained for legacy setups and configuration migration. Both links currently serve an x86_64 DMG. Apple Silicon users should check compatibility before running it.
When migrating from an older setup, don't copy proxy nodes alone. Note your DNS mode, local overrides, rule order, and system proxy ports, then restore and verify each setting in the new client.
| Check | Before you install |
|---|---|
| Chip type | If Chip shows an Apple M-series processor, choose a native ARM64 build. If Processor shows Intel, choose an x64 build. |
| Compatibility | Apple Silicon may need Rosetta to run x64 packages. Check the release notes for the minimum macOS version. |
| Installation location | Move the app to Applications before launching it. Grant permissions for the system proxy, helper service, and TUN separately as prompted by the client. |
Most recent phones use arm64-v8a. For older devices, check whether armeabi-v7a is supported. If you're unsure of the ABI, check the device specifications or choose a universal package if available.
For Android devices that support arm64-v8a. After downloading the APK, allow your browser or file manager to install apps when prompted. Import your subscription after installation.
When you connect for the first time, Android will ask you to authorize the VPN connection. After approving, check the rules and proxy selection. If the connection stops in the background, review the device's battery and background activity restrictions. Official site: clashplus.io.
Includes architecture-specific APKs and a universal package. Choose the matching build when you know your device's architecture. A universal package avoids the guesswork, but compatibility still depends on your Android version and device.
After importing a subscription, select the configuration and start the connection. If the file imports but won't start, check the configuration error, YAML syntax, protocol fields, and whether the subscription URL returned a webpage instead of a configuration.
An alternative mobile client with ARM64 and ARMv7 downloads. Check your device's architecture before installing; desktop AMD64 builds aren't interchangeable with mobile ARM64 builds.
On phones, connections usually use Android's VPN interface rather than the system proxy controls used on computers. If another VPN is already connected, check whether your device allows simultaneous VPN connections before starting the client.
A universal Android package is available. Surfboard uses a configuration format different from Clash YAML. Before choosing it, check that your subscription provider supports a compatible format; changing the file extension alone won't make it importable.
If you already have a Clash subscription, check which subscription formats the provider offers. When converting a configuration, verify that protocols, policy groups, and rules are preserved. After importing, test the actual routing behavior.
| Check | Before you install |
|---|---|
| Device ABI | ARM64 corresponds to arm64-v8a, and ARMv7 to armeabi-v7a. Check which ABIs your device actually supports. |
| Android version | Minimum Android versions vary by client. If the installer reports that the app is incompatible, check your Android version and processor architecture first. |
| Connection permissions | Authorize the VPN connection on first use. Background operation may be affected by your device's battery management settings. |
Check the Clash Plus App Store listing for app details, device compatibility, and the latest release information.
Check device and system compatibility on the App Store listing before installing. On first launch, import a supported subscription or configuration, check your proxy groups, choose a proxy, and allow the VPN configuration when prompted.
You can import the same configuration source on a phone and tablet, but check your subscription provider's device and connection limits. Find product features and usage information at clashplus.io.
| Check | Before you install |
|---|---|
| Device and system | Check the App Store listing for iPhone and iPad compatibility and the minimum iOS version. |
| Install source | Open the App Store link in this section to install and receive future updates. |
| First connection | After importing a valid configuration, authorize the VPN connection and check the selected proxy and current network status. |
This section offers AMD64 graphical clients. Choose DEB or RPM to match your distribution. For servers, ARM devices, and routers, see the core downloads below.
For Linux users with a graphical desktop. Debian- and Ubuntu-based distributions usually use DEB; distributions with RPM package management use RPM. Check that your distribution has the required runtime dependencies.
After installation, launch the app from a terminal or application menu and confirm the interface and core work. Whether desktop apps follow the system proxy depends on each app. TUN requires separate permission and routing checks.
An AMD64 DEB graphical package for users of DEB-based package management who prefer a cross-platform workflow. This is not a universal binary for every Linux distribution.
If dependency resolution fails, use your system package manager to identify missing dependencies instead of repeatedly reinstalling. For background services, containers, or transparent proxy setups, the standalone Mihomo core is often easier to maintain.
| Check | Before you install |
|---|---|
| Architecture and package format | Use uname -m to check the architecture; x86_64 corresponds to AMD64. Choose DEB or RPM based on your distribution's package management system. |
| Desktop dependencies | Graphical clients require a desktop session and runtime dependencies. See the release notes for specific dependencies and minimum system requirements. |
| Network permissions | TUN requires appropriate system permissions. Command-line tools may also need proxy environment variables configured separately. |
Mihomo / Standalone
For servers, routers, and command-line setups. Most users should choose a graphical client above; the core itself has no subscription management window or system proxy controls.
Prepare your own YAML configuration, working directory, and startup method for the core. Extract ZIP archives fully. On Unix-like systems, make the executable file executable after extracting a GZ archive. Install DEB packages with your distribution's package manager; don't try to run the archive directly.
For routers, don't choose a file based only on the CPU brand. Check the instruction set, bitness, floating-point ABI, and firmware environment. MIPS softfloat is only suitable for devices with a matching soft-float environment. Transparent proxying involves the gateway, DNS, and firewall; test in a staging environment first to avoid disrupting your main network.
| Operating system | Processor / 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 |
Downloading installs the program, but a working connection also depends on your subscription, proxy selection, and how your system routes network traffic.
Create a configuration from a valid subscription URL or local YAML file. Wait for the client to parse it, then set it as the active configuration. Reinstalling won't fix an import problem if the URL returns a login page, error page, or unsupported format.
Test common apps in rule mode first, then check that the system proxy points to the port the client is actually listening on. mixed-port is often set to 7890, but use the value in your active configuration; don't overwrite existing settings blindly.
The system proxy mainly affects apps that follow system settings. TUN routes connections through a virtual network interface and requires additional permissions and routing configuration. If something goes wrong, check the logs and change one setting at a time. See the proxy mode guide for details.
First identify whether the issue is with installation, configuration, or connectivity, then follow the relevant troubleshooting steps.
If you're new to Clash, start with a graphical client. It provides subscription import, proxy selection, system proxy controls, and logs. The Mihomo core is mainly for server and router users who manage YAML files, startup commands, and service configuration themselves.
On Windows, check System type in Settings > System > About. On macOS, check the chip or processor in About This Mac. On Android, check the device's ABI in its specifications. x64 and AMD64 usually refer to the same architecture; ARM64 corresponds to arm64-v8a, and ARMv7 to armeabi-v7a. Don't choose a download based on the operating system name alone.
The installer doesn't include a proxy service. After installation, import a valid subscription or local configuration, enable it, and select a proxy. Turn on the system proxy or TUN if needed. Then check the logs for rule matches and proxy results. If import fails, verify the subscription format and URL.
Both clients are discontinued. Their archived downloads are intended for migrating older setups, comparing configurations, and compatibility testing. For a new installation, choose a maintained client. Before migrating, back up your subscription source, local rules, and overrides, then verify DNS, proxy groups, and TUN behavior.
Back up your subscription source, local YAML files, override scripts, custom rules, and listening ports. Quit the old client before installing the update, and don't let two clients control the system proxy at the same time. After upgrading, check the active configuration, proxy group selection, DNS, and TUN permissions.
Open the Clash Plus App Store listing from the iOS panel and install it if your device and system meet the store's compatibility requirements. After installation, import a supported subscription or configuration and allow the VPN configuration when prompted. Product details are available at clashplus.io.